Cannot access 5big network 2

[pacco]

@fvdw,

did you note this previous post about a static cp command: viewtopic.php?f=26&t=2209&start=120#p18786

yes I saw that but I need to llok if that is going to work, not all binaries can be compiled static.

About the usb issue of the new standalone kernel. I recompiled the kernel but I see some issues when activating usb driver, need more time to find out what is causing this

@fvdw,

I will wait for your new kernel. Being able to connect an external usb drive is a lot easier than swapping the disk in bay 5 every time I copied some data.

Thanks!

Frank

[Mijzelf]

Does it have to be static? I guess you can simply include an OpenWRT rootfs. By dropping some unneeded stuff (luci, opkg, ...) I think it can be less then 1.5MB, compressed.

To be honest, I don't know if OpenWRT cp can handle files >2GiB, but I cannot remember I ever read complaints about it, while OpenWRT is also used on NAS boxes.

[pacco]

Work around: Download fun_plug.tgz. Tftp it to the NAS. Then

Code: Select all

mkdir /ffp
cd /ffp
tar xzf /path/to/fun_plug.tgz
rm /path/to/fun_plug.tgz

/ffp/bin/cp -r /tmp/mountpoint/shares/1 /tmp/usbdisk/

Just to let you know I followed these steps and right now I am copying share 1 (including large files up to 40GB) to the disk in bay 5. Once finished I will shut down the Lacie, take out the disk and put it in a usb<-> sata bay and hook it up to the other Lacie. After that repeat steps for the other shares.

I am confident this will work...will keep you posted!!!

Once finished I want to rebuild the old Lacie. Any good suggestions? Go back to the Lacie firmware or use the fvdw-sl firmware? How to install?

I know this is a bit premature, but THANKS to the three of you!!!!! It looks like I am able to recover all data. :punk

[Mijzelf]

Once finished I want to rebuild the old Lacie. Any good suggestions? Go back to the Lacie firmware or use the fvdw-sl firmware? How to install?

That's a matter of taste. I *think* your box will boot into Lacie firmware fine, now you removed the defective disk. And when you insert a new disk I guess it will resync.
Of course it is possible that during the resync a 2nd disk dies, or that the Lacie firmware mistakenly creates a new raidarray, deleting your data. (Which is the reason why you are now copying all data).

The fvdw-sl is fine, (install instructions), AFAIK the latest version has also raid support. (Although I would prefer 5 single volumes an a good backup protocol) And it gives you more options in case something goes wrong. Shell access.

[pacco]

Once finished I want to rebuild the old Lacie. Any good suggestions? Go back to the Lacie firmware or use the fvdw-sl firmware? How to install?

That's a matter of taste. I *think* your box will boot into Lacie firmware fine, now you removed the defective disk. And when you insert a new disk I guess it will resync.
Of course it is possible that during the resync a 2nd disk dies, or that the Lacie firmware mistakenly creates a new raidarray, deleting your data. (Which is the reason why you are now copying all data).

The fvdw-sl is fine, (install instructions), AFAIK the latest version has also raid support. (Although I would prefer 5 single volumes an a good backup protocol) And it gives you more options in case something goes wrong. Shell access.

Just to be sure...after I copied all data, should I first remove the partition from that new drive? This is the drive I am using for copying right now. Or should I just boot into the Lacie firmware with the drive inside?

[Jocko]

Hi pacco,

I think it is better to destroy the partition table on the new disk. According the Lacie manual, the firmware uses an empty disk to repair the raid but maybe it can also erase at the first step any existing partition table (I think it should do it) but there is no risk to do it before plugging the disk.

http://manuals.lacie.com/start?id=en/ma ... work2/raid

[pacco]

Hi pacco,

I think it is better to destroy the partition table on the new disk. According the Lacie manual, the firmware uses an empty disk to repair the raid but maybe it can also erase at the first step any existing partition table (I think it should do it) but there is no risk to do it before plugging the disk.

http://manuals.lacie.com/start?id=en/ma ... work2/raid

Thanks! Still copying, but when finished I will try and let you know.

[pacco]

Once finished I want to rebuild the old Lacie. Any good suggestions? Go back to the Lacie firmware or use the fvdw-sl firmware? How to install?

That's a matter of taste. I *think* your box will boot into Lacie firmware fine, now you removed the defective disk. And when you insert a new disk I guess it will resync.
Of course it is possible that during the resync a 2nd disk dies, or that the Lacie firmware mistakenly creates a new raidarray, deleting your data. (Which is the reason why you are now copying all data).

The fvdw-sl is fine, (install instructions), AFAIK the latest version has also raid support. (Although I would prefer 5 single volumes an a good backup protocol) And it gives you more options in case something goes wrong. Shell access.

Funny, copied all data to the external disk (now copying to the other NAS) and checked the old "defective" disk. Works like a charm!

Wiped its partitions and just booted the Lacie. Dashboard comes on and it says: The volume cannot be found.

So I think what caused my problems was this; the system believes sda is in slot 1, sdb in 2, sdc in 3, sde in 4 en sdd in 5. Using the standalone kernel and using udevstart corrected that problem and I was able to mount the degraded RAID. Now back in the Lacie firmware it probably expects sdd in 5 and that one is the wiped disk.

Correct me if I am wrong...and even better how to correct this (if possible).

[Jocko]

checked the old "defective" disk. Works like a charm!

how do you check that ? Do you use e2fsck ?

So I think what caused my problems was this; the system believes sda is in slot 1, sdb in 2, sdc in 3, sde in 4 en sdd in 5. Using the standalone kernel and using udevstart corrected that problem and I was able to mount the degraded RAID. Now back in the Lacie firmware it probably expects sdd in 5 and that one is the wiped disk.

You can forget udevstart if you use this kernel version (#17) instead of (#10) http://plugout.net/viewtopic.php?f=26&t=2210&start=30#p18824

So I think what caused my problems was this; the system believes sda is in slot 1, sdb in 2, sdc in 3, sde in 4 en sdd in 5. Using the standalone kernel and using udevstart corrected that problem and I was able to mount the degraded RAID. Now back in the Lacie firmware it probably expects sdd in 5 and that one is the wiped disk.

I don't think that. When you use fvdw-sl console, you works in a temporary environment and udevstart fixes only the dev issue into this environment.

Wiped its partitions and just booted the Lacie. Dashboard comes on and it says: The volume cannot be found.

I think that you should start the 5big2 without the new disk as disk replacement process is an hot-swapping. So you should get a degraded raid and when you hot plug the new disk:
- if you use the auto mode, the firmware must detect the disk as a new disk and add it in the raid to restore the raid
- if you use the manual mode you have to select it to add it in the raid

[pacco]

I think that you should start the 5big2 without the new disk as disk replacement process is an hot-swap. So you should get a degraded raid and when you hot plug the new disk:
- if you use the auto mode, the firmware must detected the disk as a new disk and add it in the raid to restore the raid
- if you use the manual mode you have to select it to add it in the raid

Tried to start it without disk 5. Same error: volume could not be found.

The only thing I can do is create a brand new array from the Lacie dashboard.

But I forgot some important files, so I am copying again to the old "defective" drive. Just partitioned and formatted it. Works ok (did a full disk check on my laptop).

Really beats me what caused it then.