Lacie 5Big2 Failed After Firmware Update

[Mijzelf]

WAIT!

/edit: I suddenly had a vague remembrance that parted also puts a filesystem on the partition. But gdisk sounds more lowlevel, and safe.

Yes, I suppose gdisk will suffice. unlucky1 only needs to start the partition on a certain sector, I suppose gdisk can do?

[unlucky1]

Are you asking me to do something with parted? I'm hear awaiting instructions :?

[fvdw]

as said parted is not in the kernel, so you can not use it.

@mijzelf, yes gdisk can set start and end sector of a partition

but why is sda not coupled to the right bock device node ?

[Mijzelf]

@unlucky1: gdisk /dev/sda
o (Create new GPT)
n (Create new partition)
2 (partition number)
4048896 (start sector)
<enter> (until the end of the disk)
<enter> (Don't care about type)
w (write table and exit)

Then:
cat /proc/partitions
should show the partition,
mdadm /dev/sda2
should tell it's a raid member.

@fvdw: Don't know. I suppose the table only assigns a name, and the minor is still assigned by the sequence of detection.

[unlucky1]

Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N):

We sure :( ?!

[Mijzelf]

As said, it's only administrative. 'Deleting a partition' is like removing a direction sign to a city. The city is still there, you might only have problems to find it.

But in this case you already posted a map of your disk. So, yes, sure.

[unlucky1]

Here you go:

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

31 0 500 mtdblock0
31 1 4 mtdblock1
8 0 976762584 sdc
8 2 974738119 sdc2
8 16 976762584 sdb
8 32 976762584 sda
8 48 976762584 sde
8 64 976762584 sdd
root@(none):/ # mdadm /dev/sda2
/dev/sda2: is not an md array

[unlucky1]

Hmmm, and this:

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

But sdc2 IS there. I see it:

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

31 0 500 mtdblock0
31 1 4 mtdblock1
8 0 976762584 sdc
8 2 974738119 sdc2
8 16 976762584 sdb
8 32 976762584 sda
8 48 976762584 sde
8 64 976762584 sdd

[Mijzelf]

root@(none):/ # mdadm /dev/sda2
/dev/sda2: is not an md array

Ah, sorry, I meant
mdadm --examine /dev/sda2

[Mijzelf]

cannot open /dev/sdc2: No such device or address

But sdc2 IS there. I see it:

Yes, that was what fvdw and I were talking about. The kernel has a different idea about what sdc is than 'the userland'. That is also the reason the 'dd' operation failed.
What sdc is for the kernel, is sda in userland.