Lacie 5Big2 Failed After Firmware Update

[unlucky1]

I was doing this for sdb sdc but need to continue for sdd sde??

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

[fvdw]

I was doing this for sdb sdc but need to continue for sdd sde??

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

yes and examine sdc2,sdd2 and sde2 with mdadm

[fvdw]

I find it strange that sdb and sdc have the same diskid

Disk identifier (GUID): 5C7C3386-9367-3C4B-95F2-6B7403CA90CC

[Mijzelf]

@unlucky1: What is the nature of your data?

@fvdw: Do you know what a disk id actually is? Maybe it's something in the MBR. Well, we copied the MBR of sda to 3 of the 4 other disks.

[fvdw]

@fvdw: Do you know what a disk id actually is? Maybe it's something in the MBR. Well, we copied the MBR of sda to 3 of the 4 other disks.

nope but it isn't the same as from sda...
guess its a kind if serial number reported by disk firmware (to my knowledge it is not in the MBR nor in part table info but I could be wrong)

[Mijzelf]

OK, what's the worst? That somehow sdb and sdc are the same physical disk? Do you have 5 disks in your 5big2?

[unlucky1]

Yes, I have 5 physical disks. All the same hardware. The data is a mix of photos and videos and of the documents, many docs and pdfs and presentations from our organization (we run a non-profit org). I'll tell you more by e-mail, you have my e-mail so you can write me (and I don't have yours) but I prefer to keep details off the public view ;)

[unlucky1]

Code: Select all

root@(none):/ # mdadm --examine /dev/sdc2
mdadm: No md superblock detected on /dev/sdc2.
root@(none):/ # mdadm --examine /dev/sdd2
/dev/sdd2:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 4f4a8ea3:4c99b769:e18e6826:872bc27f
           Name : (none):4  (local to host (none))
  Creation Time : Thu Jan  1 00:00:39 1970
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 1949474544 (929.58 GiB 998.13 GB)
     Array Size : 3898947584 (3718.33 GiB 3992.52 GB)
  Used Dev Size : 1949473792 (929.58 GiB 998.13 GB)
   Super Offset : 1949474800 sectors
          State : clean
    Device UUID : 9134e88d:390f3c7e:ae8566b5:7a779902

    Update Time : Tue Jun 18 10:35:58 2013
       Checksum : 71c4a891 - correct
         Events : 51808

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 4
   Array State : AAAAA ('A' == active, '.' == missing)
root@(none):/ # mdadm --examine /dev/sde2
/dev/sde2:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 4f4a8ea3:4c99b769:e18e6826:872bc27f
           Name : (none):4  (local to host (none))
  Creation Time : Thu Jan  1 00:00:39 1970
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 1949474544 (929.58 GiB 998.13 GB)
     Array Size : 3898947584 (3718.33 GiB 3992.52 GB)
  Used Dev Size : 1949473792 (929.58 GiB 998.13 GB)
   Super Offset : 1949474800 sectors
          State : clean
    Device UUID : b7d90b31:1b4b0e9a:c3f998a6:fbe87a36

    Update Time : Tue Jun 18 10:35:58 2013
       Checksum : 55ce6f2e - correct
         Events : 51808

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AAAAA ('A' == active, '.' == missing)


[unlucky1]

I tried sdc twice and it doesn't seem to take like the others....

[fvdw]

about GUId see here http://en.wikipedia.org/wiki/Globally_unique_identifier

and that page mentions this

Certain GUIDs turn up again and again, both intentionally, and otherwise. In a GUID Partition Table (GPT), it's not appropriate for more than one disk to have the same Disk GUID, or for more than one partition to have the same Unique partition GUID, however it is appropriate for multiple partitions to use the same Partition type GUID. So only Linux swap partitions, and all Linux swap partitions on GPT-formatted disks can be counted on to have the GUID 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F, for example.

typically that sdb and sdc having the same GUID are the problem disks...