Lacie 5Big2 Failed After Firmware Update

[unlucky1]

No, don't have e2fsck but I do have fsck. Is that the same?

[Jocko]

Yes you can do this command to check your partition :

Code: Select all

 fsck /dev/sdb2 -fv

[unlucky1]

Hmm, failed.

root@(none):/ # fsck /dev/sdb2 -fv
fsck (busybox 1.21.0, 2013-02-04 10:48:06 GMT+1)
fsck: can't read '/etc/fstab': No such file or directory
fsck: fsck.auto: No such file or directory

[Jocko]

try to create this file :

Code: Select all

touch /etc/fstab

[unlucky1]

root@(none):/ # touch /etc/fstab
root@(none):/ # fsck /dev/sdb2 -fv
fsck (busybox 1.21.0, 2013-02-04 10:48:06 GMT+1)
fsck: fsck.auto: No such file or directory
root@(none):/ # touch /etc/fsck.auto
root@(none):/ # fsck /dev/sdb2 -fv
fsck (busybox 1.21.0, 2013-02-04 10:48:06 GMT+1)
fsck: fsck.auto: No such file or directory

I probably put fsck.auto in the wrong place....

[unlucky1]

I do see in sbin fsck.minix if that helps.

[unlucky1]

fsck.minix /dev/sdb2 -fv
fsck.minix: can't open '/dev/sdb2': No such device or address

[fvdw]

attached e2fsck compiled static...

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

[Mijzelf]

So all tools seem to agree that /dev/sdb2 is not present.

Can you have a look at your blockdevices:

Code: Select all

cat /proc/partitions

[unlucky1]

root@(none):/ # cat /proc/partitions
major minor #blocks name

31 0 500 mtdblock0
31 1 4 mtdblock1
8 0 976762584 sdc
8 1 1024 sdc1
8 2 974737408 sdc2
8 3 934 sdc3
8 4 1024 sdc4
8 5 256000 sdc5
8 6 8033 sdc6
8 7 16065 sdc7
8 8 843413 sdc8
8 9 875543 sdc9
8 10 8033 sdc10
8 16 976762584 sdb
8 32 976762584 sda
8 48 976762584 sde
8 64 976762584 sdd
8 65 1024 sdd1
8 66 974737408 sdd2
8 67 934 sdd3
8 68 1024 sdd4
8 69 256000 sdd5
8 70 8033 sdd6
8 71 16065 sdd7
8 72 843413 sdd8
8 73 875543 sdd9
8 74 8033 sdd10


Okay, messing about, I looked at all the disks:

root@(none):/ # fsck.minix /dev/md0 -fv
fsck.minix: lseek(1024): Invalid argument
root@(none):/ # fsck.minix /dev/sda2 -fv
fsck.minix: bad magic number in superblock
root@(none):/ # fsck.minix /dev/sdb2 -fv
fsck.minix: can't open '/dev/sdb2': No such device or address
root@(none):/ # fsck.minix /dev/sdc2 -fv
fsck.minix: can't open '/dev/sdc2': No such device or address
root@(none):/ # fsck.minix /dev/sdd2 -fv
fsck.minix: can't open '/dev/sdd2': No such file or directory
root@(none):/ # fsck.minix /dev/sde2 -fv
fsck.minix: bad magic number in superblock