Another RAID 1 is gone thread

bootleg · 4. Juni 2015

Ok, back again after extensive searches on Google with no results. My problem is this. 4 days ago I went to watch a show that was stored on my OMV machine from my Kodi box. My mysql library didnt come up. After a bit of digging, i found that the array that its on is gone.

Using the mdadm -examine /dev/sd* command, i found that neither disk in the array had it's superblocks. That is completely gone.

Also used the scan and assemble flags with mdadm as well with no luck. Tried moving the drives to the onboard sata ports from the controller card as well. No joy. Any and all guides I have found require that at least one drive have it's superblocks. And since neither of mine have them, am I to assume that it be best to start fresh? Kind of not wanting to lose about 1TB of data that was there.

Also, the mdadm.conf still has it defined there, but i am guessing that doesnt matter since the uid of the array will likely change if the array can be restored.

Please let me know if any command ouptuts need to be posted.

ryecoaaron · 4. Juni 2015

Post the output from the commands in this thread

bootleg · 4. Juni 2015

output of cat /proc/mdstat

Code

root@server:~# cat /proc/mdstat
Personalities : [raid1]
md126 : active raid1 sdb[0] sda[2]
      1953513424 blocks super 1.2 [2/2] [UU]


md127 : active raid1 sdc[0] sdd[2]
      1953513424 blocks super 1.2 [2/2] [UU]


unused devices: <none>

Alles anzeigen

output of blkid

Code

root@server:~# blkid
/dev/sdb: UUID="250a2ff4-ca91-299b-bdf6-1085f73f1eba" UUID_SUB="4717fb1f-a80f-822b-a8d9-a1f84fbfc01e" LABEL="openmediavault:Array1" TYPE="linux_raid_member"
/dev/sda: UUID="250a2ff4-ca91-299b-bdf6-1085f73f1eba" UUID_SUB="1c0fdcbd-c30f-67c6-a736-8219ccdee418" LABEL="openmediavault:Array1" TYPE="linux_raid_member"
/dev/sdc: UUID="e0051b6f-d629-8cea-cea6-530b7af33c9c" UUID_SUB="40a18d80-ae37-3b4c-060a-31d6cd0d7db1" LABEL="openmediavault:Array0" TYPE="linux_raid_member"
/dev/md127: LABEL="array0" UUID="f038462d-c3c2-4aaf-97a8-23357c044f6c" TYPE="ext4"
/dev/md126: LABEL="array1" UUID="9a1aeafe-7406-45a5-890e-56b42d132ba9" TYPE="ext4"
/dev/sdd: UUID="e0051b6f-d629-8cea-cea6-530b7af33c9c" UUID_SUB="d6733487-bfbb-e92d-b365-c79c67e7714c" LABEL="openmediavault:Array0" TYPE="linux_raid_member"
/dev/sde1: UUID="c56914f6-f090-457c-8be4-48a233c53878" TYPE="ext4"
/dev/sde5: UUID="a932d14a-b38f-4c6d-85e2-87b7428e7209" TYPE="swap"
/dev/sdf1: LABEL="dump" UUID="3a3b968b-cbc4-44e6-9419-9ec4d3a0c619" TYPE="ext4"

output of fdisk -l

Code

root@server:~# fdisk -l


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  3907029167  1953514583+  ee  GPT


WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1  3907029167  1953514583+  ee  GPT


WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  3907029167  1953514583+  ee  GPT


Disk /dev/sde: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c9929


   Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *        2048    59895807    29946880   83  Linux
/dev/sde2        59897854    62531583     1316865    5  Extended
/dev/sde5        59897856    62531583     1316864   82  Linux swap / Solaris


WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdf: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1               1   976773167   488386583+  ee  GPT


Disk /dev/sdg: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


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


Disk /dev/sdh: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


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


Disk /dev/md127: 2000.4 GB, 2000397746176 bytes
2 heads, 4 sectors/track, 488378356 cylinders, total 3907026848 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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


Disk /dev/md126: 2000.4 GB, 2000397746176 bytes
2 heads, 4 sectors/track, 488378356 cylinders, total 3907026848 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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

Alles anzeigen

/dev/sdg and /dev/sdh are the two drives within the array that disappeared

Also, using Debian Wheezy with OMV 1.19 on kernel 3.2.0-4-amd64 on a haswell intel celeron g1840 processor and MSI motherboard

edit - mdadm.conf

Code

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# definitions of existing MD arrays
ARRAY /dev/md/Array2 metadata=1.2 name=server:Array2 UUID=1fc3a340:bd87fe94:cdc$
ARRAY /dev/md/openmediavault:Array0 metadata=1.2 spares=1 name=openmediavault:A$
ARRAY /dev/md/openmediavault:Array1 metadata=1.2 name=openmediavault:Array1 UUI$
MAILADDR root
ARRAY /dev/md/Array1 metadata=1.2 UUID=250a2ff4:ca91299b:bdf61085:f73f1eba name$
ARRAY /dev/md/Array0 metadata=1.2 UUID=e0051b6f:d6298cea:cea6530b:7af33c9c name$

Alles anzeigen

ryecoaaron · 4. Juni 2015

What is the output of: cat /etc/mdadm/mdadm.conf

bootleg · 4. Juni 2015

Edited my previous post with that a few minutes before you posted.

bootleg · 6. Juni 2015

Sorry to bump this thread, but I am hoping that anyone has a solution to get at least one of the drives limping so i can retrieve data. Thanks.

Edit - Tried to do a bit more on the diagnostic on one of the drives. Leaving one completely untouched.

Code

root@server:~# e2fsck /dev/sdg1?offset=2048                                             
e2fsck 1.42.5 (29-Jul-2012)                                                             
e2fsck: No such file or directory while trying to open /dev/sdg1                        
Possibly non-existent device?                                                           
root@server:~# e2fsck /dev/sdg?offset=2048                                              
e2fsck 1.42.5 (29-Jul-2012)                                                             
ext2fs_open2: Bad magic number in super-block                                           
e2fsck: Superblock invalid, trying backup blocks...                                     
e2fsck: Bad magic number in super-block while trying to open /dev/sdg                   

The superblock could not be read or does not describe a correct ext2                    
filesystem.  If the device is valid and it really contains an ext2                      
filesystem (and not swap or ufs or something else), then the superblock                 
is corrupt, and you might try running e2fsck with an alternate superblock:              
    e2fsck -b 8193 <device>

Alles anzeigen

Edit 2 - was able to put the drive in a limp mode of sorts. Using the command:

Code

testdisk /dev/sdg

And was able to convert it to a GPT partition to recover all data.

Jetzt mitmachen!