All Shares Gone - Lacie 5Big Network 2

[Mijzelf]

As far as I can see there are 4 possibilities.
1) The raid array failed, and your data partition isn't mounted by the Lacie firmware.
2) Your shares are 'just there', they are only 'forgotten' by the firmware.
3) Your shares are moved to another location.
4) Your shares are deleted.

So let's first try to assemble and mount (read only) the data partition.

Code: Select all

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

mkdir /mountpoint
mount -o ro /dev/md4 /mountpoint

If that succeeds, you can search for your data in /mountpoint. One of the ways to get a listing is:

Code: Select all

find /mountpoint

or, with a filter on a specific name:

Code: Select all

find /mountpoint | grep <filter>

If mdadm fails, post the output of

Code: Select all

mdadm --examine /dev/sd[abcde]2

[fvdw]

ps mdadm is not included in the standalone kernel, you need to upload it via tftp
attached a static compiled version. Unpack the archive and put the file in the tftp directory of the fvdw-sl console
Upload it by typing in telnet client window

Code: Select all

tftp -l /sbin/mdadm -r mdadm -g pc-ip

make it executable

Code: Select all

chmod 755 /sbin/mdadm

replace pc-ip by actual ip address of the pc running the fvdw-sl console

mdadm is now available here:
http://plugout.net/viewtopic.php?f=7&t=1271&p=18801#p18801

[Patzag]

Well, thank you very much for your assistance on this.
I was WAY too chicken to dig into this without the proper schooling in Linux and general computer and RAID management.
I got some help from a recovery consultant on line and recovered all my data. It was grueling, tiresome and lengthy but it happened.

Once again thanks. If I get a chance to mess around with a unit that is not so precious to me, I'll be happy to use your tools and Explore!

Cheers,
Patrick

[abouttogocrazy]

I've got exactly the same thing happening here. Yay.

Also, due to troubleshooting one of the raid's five disks is now gone (it's raid 5) - but I'd like to think there's still hope for this, and I was just wondering whether it would be possible to drag out the 5Big Network 2 drives out and install them into a 5Big Thunderbolt chassis I happen to have?

I'm a real n00b with all Unix/Linux/whatever stuff, so I'm afraid a lot of holding hands is going to be needed. Mechanically and electronically I'm very capable, it's just that I'm a Mac user and really don't know a thing about "this stuff".

So, first: would changing the chassis make the problem a bit easier to cope with, for example with Mac's Disk Utility, or am I just making myself a clown here? Or are the different 5Big types too different, and my Network 2 disks need to be revived in the original chassis?

Second: if it doesn't help, and I need to do the stuff described up there on the Network chassis, how exactly would I be able to copy something (a whole folder) from the damaged raid to another disk? That is, if I get it done right. If.

Yep, n00b level unlimited here. :-/

[fvdw]

I think a thunderbolt has another mainboard and cpu and will probably need totally different firmware

[cwherbert]

Please help - it seems I have the same problem as mentioned. My Lacie 5big Network 2 is set up in Raid 5, all disks are clean, however my share information is all gone. I managed to get a WIN7 to download and start the FVDW-SL console. After inputting the IP of the NAS and switching the NAS off (as instructed for a standalone kernel) I get stuck ….. the laptop opens a cmd window (clunc-open -i xxx.xxx.xxx.xxx) and nothing else happens ….. :sob

PLease please please help! :please I do believe to have a solvable problem, but I am not sure I alone can fix it :oops:

Can somebody here please :please guide me through this?

Chris

[fvdw]

did you follow the instruction to load the standalone kernel ?
And do not set an ip address for nas in the console let it use the default values it comes up with

meaning switch off the 5big2 then loading and starting the standalone kernel.
After the cmd windows open and it mentions "waiting for u-boot" (did you get this window ?)
then switch on your 5big2.

Now the console should interrupt boot and load the standalone kernel, this should be visible in the command window.
If that doesn't happen it means that the nas was not detected
This could be if you use a firewall blocking netcat (nc) access to the lan, the console uses netcat to connect to the nas, it can also happen when you use a wireless connection to your lan on the pc running the console, used a wired connection.

ps also use lan1 connector

[cwherbert]

hi fvdw,

I believe the console interrupted the boot, however I then got an error from the DTelnet client - timeout..

:sob

[fvdw]

which version of the fvdw-sl console do you use ?

and did you actually see that the standalone kernel was uploaded, in the command window it should be visible and before it closes automatically it will mentions "starting kernel"

[cwherbert]

I use FVDW-SL console 5.5

No!