All Shares Gone - Lacie 5Big Network 2

[Jocko]

Yes this output is ok.

you can confirm that with

Code: Select all

mdadm --detail /dev/md4

(of course after assembling it)

[cwherbert]

thanks

any known reason why mount would fail or hang … ?

[Jocko]

I am sorry cwherbert but I don't see any reason as you performed only standard mdadm commands and ran no fs commands to repair disk or fs :scratch

So it is amazing

[cwherbert]

hi jocko,

here is the output:

root@fvdw-sta-kirkwood:/ # mdadm --detail /dev/md4
/dev/md4:
Version : 1.0
Creation Time : Thu Jan 1 00:00:40 1970
Raid Level : raid5
Array Size : 7805958144 (7444.34 GiB 7993.30 GB)
Used Dev Size : 1951489536 (1861.09 GiB 1998.33 GB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Fri Jun 19 17:28:44 2015
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Name : (none):4
UUID : 7927d386:af211243:6adef83d:39460332
Events : 1040

Number Major Minor RaidDevice State
0 8 34 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 2 2 active sync /dev/sdc2
3 8 66 3 active sync /dev/sdd2
5 8 50 4 active sync /dev/sde2
root@fvdw-sta-kirkwood:/ #

[Jocko]

all is fully ok

[cwherbert]

ok, so what do I do now?

how can I find out what file system was used when the array was built?

I just tried mounting again, and it hanged itself up again . ..

fvdw mentioned something with regards to the program only supporting ext3 or xfs, what exactly does that mean?

[cwherbert]

any idea how I could get in contact with "Patzag" as he got his data recovered through a consultant ... maybe he can help me ... I cant lose this data!! :please :please :please :please
:hail :hail :hail :hail

[fvdw]

ok, so what do I do now?

how can I find out what file system was used when the array was built?

I just tried mounting again, and it hanged itself up again . ..

fvdw mentioned something with regards to the program only supporting ext3 or xfs, what exactly does that mean?

It means the file system on the array should be XFS or ext3. I think it will be XFS when you made it using the lacie firmware. It could be that the mount command from busybox has problems to mount such a big file system
Need to look if we can use a separate binary of mount to see if that is able to mount it.
Just a minute

[cwherbert]

some silly ideas:

a) if I take all disks out of the enclosure, and re-insert them, would that do something?

b) if I buy/have the same lacie enclosure and insert the disks in there, will that resolve anything?

[fvdw]

some silly ideas:

a) if I take all disks out of the enclosure, and re-insert them, would that do something?

b) if I buy/have the same lacie enclosure and insert the disks in there, will that resolve anything?

no probably not.

Let try this
Put attached archive in the tftp folder of the fvdw-sl console on your pc running the console
copy it to the 5big2 using telnet client

Code: Select all

cd /
tftp -l mount.tar -r mount.tar -g ip-pc

(replace ip-pc by the actual ip address of the pc running the fvdw-sl console)
it should tell you if the file was uploaded
if so, unpack it

Code: Select all

tar -xvf mount.tar

now try to use the new mount command
you need to use the prefix /usr/sbin before the mount command)

Code: Select all

/usr/sbin/mount ......

---edit---
With the last version 6.0, no need to upload mount manually. Use a new option with fvdw-programs menu :
* run on the telnet window the command: fvdw-sl-programs
(then a menu will appear)
* select "Upload and extract glibc mini and tools"

Jocko