Restoring software RAID5 in new system/won't mount.

GTvert90 · 6. Juli 2015

I upgraded hardware and went to the latest OMV 2.1 as well.

I have 3 4TB drives set up in RAID5, I put them in the new system went under raid management and created a new raid.

Code

Version : 1.2
  Creation Time : Sun Jul  5 22:34:21 2015
     Raid Level : raid5
     Array Size : 7813774336 (7451.80 GiB 8001.30 GB)
  Used Dev Size : 3906887168 (3725.90 GiB 4000.65 GB)
   Raid Devices : 3
  Total Devices : 3
    Persistence : Superblock is persistent


    Update Time : Mon Jul  6 08:30:27 2015
          State : active
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0


         Layout : left-symmetric
     Chunk Size : 512K


           Name : openmediavault:media  (local to host openmediavault)
           UUID : b040ce6c:ce3b7d0b:0a44acd3:cdf43ca8
         Events : 123


    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8       32        1      active sync   /dev/sdc
       2       8       48        2      active sync   /dev/sdd

Alles anzeigen

Under file systems I have device /dev/md0 with label Media^P-M-;^D Under total and unused I have n/a mounted no referenced no and online.

I go to mount it and get

Zitat

Failed to mount 'de05ecdc-41bc-41dc-ab98-dc4d7b1f0e6d': mount: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

Code

Error #6000:
exception 'OMVException' with message 'Failed to mount 'de05ecdc-41bc-41dc-ab98-dc4d7b1f0e6d': mount: wrong fs type, bad option, bad superblock on /dev/md0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:921
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
#4 {main}

Alles anzeigen

Not really sure where to go from here. There is or was still data on the drives.. it is backed up so losing it isn't a big deal.

Here is the commands the message suggested trying

Code

root@openmediavault:~# dmesg | tail
[18089.750120] perf interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[35914.563852] md: md0: resync done.
[35915.064050] RAID conf printout:
[35915.064056]  --- level:5 rd:3 wd:3
[35915.064059]  disk 0, o:1, dev:sdb
[35915.064061]  disk 1, o:1, dev:sdc
[35915.064063]  disk 2, o:1, dev:sdd
[36542.587535] EXT4-fs (md0): Couldn't mount because of unsupported optional features (1fd00001)
[36800.133077] EXT4-fs (md0): Couldn't mount because of unsupported optional features (1fd00001)
[38793.746888] EXT4-fs (md0): Couldn't mount because of unsupported optional features (1fd00001)
root@openmediavault:~#

Alles anzeigen

If you need any more info let me know thanks

GTvert90 · 6. Juli 2015

could the plugin have not assembled the RAID in the right order? https://forums.gentoo.org/viewtopic-t-899364-start-0.html

GTvert90 · 6. Juli 2015

here is cat /proc/mdstat

Code

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdd[2] sdc[1] sdb[0]
      7813774336 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

and fdisk -l

Code

root@openmediavault:~# fdisk -l


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


Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 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


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 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: 0x0006c35d


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048   224860159   112429056   83  Linux
/dev/sda2       224862206   234440703     4789249    5  Extended
/dev/sda5       224862208   234440703     4789248   82  Linux swap / Solaris


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


Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 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


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


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


Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 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


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/md0: 8001.3 GB, 8001304920064 bytes
2 heads, 4 sectors/track, 1953443584 cylinders, total 15627548672 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000


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

Alles anzeigen

GTvert90 · 6. Juli 2015

would different drives being issued different names be the issue?
/dev/sdb
/dev/sdc
/dev/sdd

they aren't in the same order as they were with the old hardware setup. could that be it?

ryecoaaron · 6. Juli 2015

uuid is used so device name is not a problem. What is the output of blkid

GTvert90 · 6. Juli 2015

Code

root@openmediavault:~# blkid
/dev/sda5: UUID="3bf9239d-5341-40f6-9374-fd96ec1037b3" TYPE="swap"
/dev/sda1: UUID="247bba48-e673-420c-a4f0-3a121a8bc234" TYPE="ext4"
/dev/sdb: UUID="b040ce6c-ce3b-7d0b-0a44-acd3cdf43ca8" UUID_SUB="4f4d6744-78dc-ca63-ac9b-18f4369ad2b2" LABEL="openmediavault:media" TYPE="linux_raid_member"
/dev/sdd: UUID="b040ce6c-ce3b-7d0b-0a44-acd3cdf43ca8" UUID_SUB="c0732d07-6f8e-9041-9de8-c19474e41b6e" LABEL="openmediavault:media" TYPE="linux_raid_member"
/dev/md0: LABEL="Media^P-M-;^D" UUID="de05ecdc-41bc-41dc-ab98-dc4d7b1f0e6d" EXT_JOURNAL="00000500-0000-0000-0000-00000010c8fd" TYPE="ext4"
/dev/sdc: UUID="b040ce6c-ce3b-7d0b-0a44-acd3cdf43ca8" UUID_SUB="a8cb6cba-f5e4-3328-45c5-f49d7db65f79" LABEL="openmediavault:media" TYPE="linux_raid_member"
root@openmediavault:~#

GTvert90 · 6. Juli 2015

Zitat von ryecoaaron

uuid is used so device name is not a problem. What is the output of blkid

thanks btw you always seem to bail me out

ryecoaaron · 6. Juli 2015

Your label seems corrupt but maybe not. Never seen the EXT_JOURNAL line in blkid. What does the following tell you: fsck.ext4 -f /dev/md0

GTvert90 · 6. Juli 2015

Code

root@openmediavault:~# fsck.ext4 -f /dev/md0e2fsck 1.42.5 (29-Jul-2012)fsck.ext4: Filesystem revision too high while trying to open /dev/md0The filesystem revision is apparently too high for this version of e2fsck.(Or the filesystem superblock is corrupt)The superblock could not be read or does not describe a correct ext2filesystem. If the device is valid and it really contains an ext2filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock:e2fsck -b 8193 <device>

ryecoaaron · 6. Juli 2015

I would boot the latest systemrescuecd on the system and try the fsck again.

GTvert90 · 6. Juli 2015

anything specific I'm doing in there? which rescue cd? its been a while since ive used one

GTvert90 · 6. Juli 2015

nevermind its systemrescuecd I'm an idiot.

Anyway boot into that run fsck.ext4 -f /dev/md0 ? Anythingelse? or if its corrupt it will help me fix it?

ryecoaaron · 6. Juli 2015

It might not be md0. cat /proc/mdstat will tell you what to use. If it is corrupt, systemrescuecd should have new enough utils to fix. Not sure why omv's tools aren't.

GTvert90 · 6. Juli 2015

gotcha. thanks. Do you think the data is still there? Like I said its still backed up so its not really a big deal.

ryecoaaron · 6. Juli 2015

I think there is about a 25% chance it is still there. Not a good feeling because of the label and newer utils error. Been wrong plenty of times before though

GTvert90 · 6. Juli 2015

Zitat von ryecoaaron

I think there is about a 25% chance it is still there. Not a good feeling because of the label and newer utils error. Been wrong plenty of times before though

on rescuesystemcd... I did fdisk -l and it shows no raid just my 3 data drives my system drive and my flash drive..

ryecoaaron · 7. Juli 2015

I would wipe the three drives then.

GTvert90 · 7. Juli 2015

Zitat von ryecoaaron

I would wipe the three drives then.

I forgot about that.. probably would have done that a long time ago.. Wiped and resycing now.. hopefully it works this time it sucks wasting 8 hours to let it sync just to have it corrupt

GTvert90 · 7. Juli 2015

So trying to figure out what might have gone wrong. Was it possibly because it was never unmounted with the old setup? I simply shut down removed the drives and through them into the new box.

ryecoaaron · 7. Juli 2015

I've seen a lot of weird things with mdadm raid lately that I can't explain.

Jetzt mitmachen!