Stock lacie 5big network2 disk error and upgrade

[daniel304]

Apparently something was interfering on My lan i have put both on a seperate switch and it is connecting now :rock ..

[Jocko]

Ok :thumbup

So you can now post the asked outputs

[daniel304]

Hi Jocko.. Two of the disks are not responding at all they are making all the wrong noises so I am affraid they are gone...
I have now installed fvdwsl base on a new disk and going to try and add the other 4 new disks...
Thanks for all the help !!

[Quest]

If the two drives you mentioned do not work when connected to a pc, then only a professional data recovery company can help you, unless you have the files you need in a backup.
But if they should work, please check the mainboard of your LaCie5Big Network2.
I am currently dealing with a similar problem and noticed that the 2.5V 1F supercap next to the marvel controller had leaked.
This probably caused the raid5 to fail.
As all my discs were still working when connected to my pc, I was able to backup all the drives to .vhd images with winimage (free 30 day test version),
and I managed to access the xfs raid with "recovery explorer raid".

I am currently in the process of backing up all my data to a new drive.
(you basically need the free space of the drive capacity + the raid size)

however if your not willing to spend money on software, these guides that I just found would probably got me the data back as well and sureley saved me a lot of time.
I had tried to fix the virtual raid5 array with mdadm first, but did something wrong and because I didn't know there was an option to make an overlay I had to make new vhd images again.
https://raid.wiki.kernel.org/index.php/RAID_Recovery
https://raid.wiki.kernel.org/index.php/ ... tware_RAID

for the LaCie5Big N2:
I removed the defective supercap and cleaned the board and the contacts.
I also replaced all the electrolytic capacitors on the mainboard of the 5big.
(Don't try this yourself unless you have soldering equipment that works with multilayer pcb's)
As soon as my data is save, I will power up the NAS and see if I can get it working again.

[fvdw]

To my knowledge the supercap is only used for keeping hw time. Its a sort of mini battery.
However the leaking may have damaged the mainboard.
If (one of) the other capacitors on the mainboard have gone bad that may cause indeed malfunction. It is very risky to replace them as you also mentioned because of damaging the multilayer board. But nothing to loose if the mainboard was not working anymore.

Ps why wait to test? If you have a spare disk just put it in and try.

[Quest]

i agree, i think the spilled electrolyte may have caused my raid to fail.

while the mainboard was still working sort of..... i would not trust a raid that shows 2 failed drive (first drive 3, then drive 2) within a few minutes.
besides, drive 3 (at 99%) and 4 (at 76%) have unreadable sectors.

never the less, I want to try to get it back working, just out of curiosity.
maybe even with your firmware as soon as I found the first install thread :-D

I only have to backup the remaining 7TB, this should be done by the end of the day, so I don't want to rush anything with testing on the original drives. besides, after spending a ton of money on two exos X16 drives, I don't want to spend any more money on 3TB drives.

[Quest]

so, I made a backup of all my files and tried to tinker with linux.
i have not been able to reassemble my 5 virtual disk images with ubuntu (maybe due to my lack of linux skills).
i tried both, all 5 drives and 4 drives with Nr. 3 missing but always got a missung superblock error.
now it gets strange:
after putting the 5 drives back in my "recapped" and cleaned lacie-5big, the raid manager shows a degraded raid5 (1,2,4,5) and offers me to add drive 3 to replace the missing one.
it's currently synchronizing drive 3 (at 2.7%).
let's see if this runs through.

[Jocko]

Hi

i have not been able to reassemble my 5 virtual disk images with ubuntu (maybe due to my lack of linux skills).

It is not the disks you must assemble but partitions: for example all partitions 2 with a raid5

Code: Select all

mdadm --assemble /dev/md4 /dev/sd[abcde]2

[Quest]

sorry for using the wrong term :shock:

mdadm --assemble /dev/md4 /dev/sd[abcde]2

yep, tried that and also:
mdadm --assemble --force /dev/md4 /dev/sdb2 /dev/sdc2 missing /dev/sde2 /dev/sdf2
and a bunch of other stuff, but no luck.

now for the progress with the lacie.
synchronizing failed 2x between 66-100% with a failed drive 4.
i guess it failed at 76% where I got the read error on drive 4 backing up the disk images.....

.... so i started fresh with a empty raid 5 and this time synchronizing went through.
now i could start to fill up the raid again.

so the mainboard seems to be ok again,