Lacie 5Big2 Failed After Firmware Update

[unlucky1]

Hi!

Okay, got in via telnet and based on what I found on the plugout.net site, I tried and got this:

root@(none):/ # gdisk /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

From there I'm too scared to hack around and screw something up. Please help.

Sincerely,
-pete.

[unlucky1]

Command (? for help): p
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9494FBD4-D888-4E97-B46D-50DB2575279A
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 30146 sectors (14.7 MiB)

Number Start (sector) End (sector) Size Code Name
1 4036608 4038655 1024.0 KiB 0700 primary
2 4048896 1953523711 929.6 GiB 0700 primary
3 4040704 4042571 934.0 KiB 0700 primary
4 4044800 4046848 1.0 MiB 0700 primary
5 2048 514047 250.0 MiB 0700 primary
6 530432 546497 7.8 MiB 0700 primary
7 546816 578945 15.7 MiB 0700 primary
8 579584 2266409 823.6 MiB 0700 primary
9 2267136 4018221 855.0 MiB 0700 primary
10 4020224 4036289 7.8 MiB 0700 primary

[fvdw]

at least it has the righjt partition structure
what you should do next is
Make a mountpoint for partition sda2 (that is the patition constaining data), mount that partion and see what is in there
for example like this (in telnet)

Code: Select all

mkdir /sda2
mount /dev/sda2 /sda2

ls -al /sda2

The last command will give a directory listing

[unlucky1]

I get this:

root@(none):/ # mount /dev/sda2 /sda2
mount: mounting /dev/sda2 on /sda2 failed: Invalid argument

Am I missing something?

[unlucky1]

No matter what I try to mount (sda, sda3, etc.) all give the same fail :(

[unlucky1]

Maybe this helps?

root@(none):/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 121602 976762583+ ee EFI GPT

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 121602 976762583+ ee EFI GPT

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 121602 976762583+ ee EFI GPT

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 1 121602 976762583+ ee EFI GPT

[unlucky1]

Uh oh, I don't like dmesg:

[ 26.232757] sd 1:1:0:0: [sde] Attached SCSI disk
[ 26.273943] sdd: sdd1 sdd2 sdd3 sdd4 sdd5 sdd6 sdd7 sdd8 sdd9 sdd10
[ 26.282686] sd 1:2:0:0: [sdd] Attached SCSI disk
[ 26.287546] Freeing init memory: 2152K
[ 26.309967] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 28.154461] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 28.164410] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 39.028213] eth0: no IPv6 routers present
[ 5196.443996] UDF-fs: No partition found (1)
[ 5212.723804] UDF-fs: No partition found (1)
[ 5239.373797] UDF-fs: No partition found (1)
[ 5286.273661] UDF-fs: No partition found (1)
[ 5377.013859] UDF-fs: No partition found (1)
[ 5665.454151] UDF-fs: No partition found (1)
[ 5670.133745] UDF-fs: No partition found (1)
[ 5715.563998] UDF-fs: No partition found (1)
[ 5830.394750] UDF-fs: No partition found (1)
[ 6002.514224] attempt to access beyond end of device
[ 6002.519019] sdc1: rw=0, want=2052, limit=2048
[ 6002.525934] UDF-fs: No partition found (1)
[ 6767.383338] UDF-fs: No partition found (1)
root@(none):/ #

[Mijzelf]

The 5Big2 has it's data partition on a raid array. So you'll have to assemble it to be able to mount it. Don't know if the tools are included in your environment though.

The command is

Code: Select all

mdadm --assemble /dev/md0 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2

and after that you should be able to mount /dev/md0.

[unlucky1]

Crap. Mdadm not found.

[unlucky1]

Any ideas?