Lacie 5Big2 Failed After Firmware Update

[fvdw]

Okay, now you're really scaring me.

can imagine, however if i give that command on my nwsp2 that has 8 partitions I get the same output as you. Lets see what Mijzelf says

[Mijzelf]

it was a gpt partition table

I know. But it should fit in the first 10k, right?

further he didn't wrote to sdd why is there the partition table changed ?

Due to the device name mangling in the kernel:

Code: Select all

8 0 976762584 sdc
8 16 976762584 sdb

It seems only the name is changed, not the minor. I guess /dev/sdc defines minor 32, so the copy actually used sda as source.

I suppose this means that the device nodes on Lacie firmware are created dynamically, else the name mangling makes no sense. How does your software do that? The name mangling did solve some problem, didn't it?

@unlucky1, you really honour your nick. But don't panic, earlier in this thread you dumped the contents of the partition table, so it is possible to recreate it.

[fvdw]

the kernel uses a disk map (same as lacie kernel), so sda is always the disk in slot1, sdb is the disk in slot2 and so on

[unlucky1]

I swear if you two help me out of this I'll honor you both with some sort of repayment! I'm really worried!

[fvdw]

to see what has been assigned as sda and so on you could do

Code: Select all

dmesg | grep sd

[unlucky1]

root@(none):/ # dmesg | grep sd
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=PRO_KW cap=gpt,lba64
[ 21.501620] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 24.813471] sd 0:1:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 24.829937] sd 0:1:0:0: [sdc] Write Protect is off
[ 24.834741] sd 0:1:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 24.834832] sd 0:1:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 24.844720] sd 0:2:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 24.861763] sd 0:2:0:0: [sdb] Write Protect is off
[ 24.866742] sd 0:2:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 24.866842] sd 0:2:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 24.876496] sd 0:3:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 24.884743] sd 0:3:0:0: [sda] Write Protect is off
[ 24.889515] sd 0:3:0:0: [sda] Mode Sense: 00 3a 00 00
[ 24.890345] sd 0:3:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 24.902194] sdc: unknown partition table
[ 24.906944] sd 0:1:0:0: [sdc] Attached SCSI disk
[ 24.912512] sdb: unknown partition table
[ 24.917229] sd 0:2:0:0: [sdb] Attached SCSI disk
[ 24.951615] sda: unknown partition table
[ 24.956315] sd 0:3:0:0: [sda] Attached SCSI disk
[ 27.383435] sd 1:1:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 27.399841] sd 1:1:0:0: [sde] Write Protect is off
[ 27.404729] sd 1:1:0:0: [sde] Mode Sense: 00 3a 00 00
[ 27.404826] sd 1:1:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 27.414618] sd 1:2:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 27.422949] sd 1:2:0:0: [sdd] Write Protect is off
[ 27.428098] sd 1:2:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 27.428192] sd 1:2:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 27.474521] sde: unknown partition table
[ 27.479209] sd 1:1:0:0: [sde] Attached SCSI disk
[ 27.486471] sdd: unknown partition table
[ 27.491137] sd 1:2:0:0: [sdd] Attached SCSI disk

[Mijzelf]

@fvdw: Yes, the name changes.

Code: Select all

8 32 976762584 sda

But the minor is 32, which is /dev/sdc in each statically populated /dev.

@unlucky: Of course we'll help. You don't need to swear for that.

Code: Select all

2 4048896 1953523711 929.6 GiB 0700 primary

You can use parted (yes?, fvdw?) to create a partition starting at 4048896 on sda. (Don't worry to do it wrong. A partition table is only administrative, in the first few kB of the disk. Your data won't be touched.)
Assuming that is the only partition you create, then try a

Code: Select all

mdadm --examine /dev/sda1

[unlucky1]

I have all these flashbacks of lost disks to partition failures! i probably could have saved them but didn't know better and the company support was always brusque and terse ending in fdisk. Here's mdadm:

root@(none):/ # mdadm --examine /dev/sda1
mdadm: cannot open /dev/sda1: No such device or address

[Mijzelf]

Did you already create the partition with parted? mdadm will show if the offset is right.

[fvdw]

@mijzelf
this is the disk map in the kernel

Code: Select all

static struct lacie_disk net5big_v2_disks[] = {
        {
                .host_no = 0,
                .channel = 3,
                .id      = 0,
                .letter  = 'a',
        },
        {
                .host_no = 0,
                .channel = 2,
                .id      = 0,
                .letter  = 'b',
        },
        {
                .host_no = 0,
                .channel = 1,
                .id      = 0,
                .letter  = 'c',
        },
        {
                .host_no = 1,
                .channel = 2,
                .id      = 0,
                .letter  = 'd',
        },
        {
                .host_no = 1,
                .channel = 1,
                .id      = 0,
                .letter  = 'e',
        },
};

so the kernel has assigned the right disk names to disks.
But you are right the minor doesn't fit, indeed normally 32 is sdc :scratch

No gparted ins not in the standalone kernel but gdisk is, think he can use that ?