Can't mount newly created RAID 5

fitur · 8. Januar 2016

Hi guys,
I just came back to OMV from using Win Server 2012 for a while. I am really looking forward to using your NAS solution again, once I get it to work.
This little project started tuesday evening, when I first noticed one of my WD Green 3TB disks had one of its SATA connectors broken. I was in tears, trying to figure out if I can fix the plastic piece of shit that fell off the god damn disk.

Since wednesday, I've tried to stuff my other three disks into a RAID 5. Each time it's finished syncing, I try to mount it and I end up getting an error message reading the following:

Failed to mount '43312270-ea1d-4006-9aa5-b7c33547663e': 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

Error #6000:
exception 'OMVException' with message 'Failed to mount '43312270-ea1d-4006-9aa5-b7c33547663e': 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/module/fstab.inc:90
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/config.inc(206): OMVModuleFsTab->startService()
#1 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
#4 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(899): OMVRpc::exec('Config', 'applyChanges', Array, Array)
#5 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#6 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#7 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
#8 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
#9 {main}

This has happened each time I've re-created the RAID. This is the procedure: Install OMV, wipe data disks, create RAID, wait for it to finish, mount md0 filesystem, rinse and repeat.

What is wrong with my filesystem and how can I fix it?
Thanks and have a nice weekend!

fitur · 8. Januar 2016

So, I found a similar thread where a few requests of command output was posted.

root@Rufus:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdc[2] sdb[1] sda[0]
5860270080 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

unused devices: <none>

root@Rufus:~# blkid
/dev/sdd1: UUID="4311d1c8-9fa1-4d65-8d9f-cb3f60a6eff1" TYPE="ext4"
/dev/sdd5: UUID="ef58893d-0243-4400-ba8f-35074f75eb33" TYPE="swap"
/dev/sda: UUID="6d1f41a1-8f40-cb4c-1822-92207613df0c" UUID_SUB="82d469d9-64a2-5026-39d1-c42ecb187abf" LABEL="Rufus:Djingis" TYPE="linux_raid_member"
/dev/sdb: UUID="6d1f41a1-8f40-cb4c-1822-92207613df0c" UUID_SUB="5203b7ef-6069-4840-1966-7cf9c20d3fca" LABEL="Rufus:Djingis" TYPE="linux_raid_member"
/dev/sdc: UUID="6d1f41a1-8f40-cb4c-1822-92207613df0c" UUID_SUB="1e643951-7a49-6a58-7d07-68940cd168d2" LABEL="Rufus:Djingis" TYPE="linux_raid_member"
/dev/md0: LABEL="Pool" UUID="43312270-ea1d-4006-9aa5-b7c33547663e" EXT_JOURNAL="00000500-0000-0000-0000-000000109982" TYPE="ext4"

root@Rufus:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=4311d1c8-9fa1-4d65-8d9f-cb3f60a6eff1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=ef58893d-0243-4400-ba8f-35074f75eb33 none swap sw 0 0
/dev/sdb1 /media/usb0 auto rw,user,noauto 0 0
# >>> [openmediavault]
UUID=43312270-ea1d-4006-9aa5-b7c33547663e /media/43312270-ea1d-4006-9aa5-b7c33547663e ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]

root@Rufus:~# mount /dev/md0
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

Not sure what other info might be required

fitur · 8. Januar 2016

Tried Ryecoaaron's option:

Code

dd if=/dev/zero of=/dev/md0 bs=512 count=10000
mkfs.ext4 /dev/md0

and then
mount /dev/md0

I had to delete the missing md0 FS in the OMV GUI but then, after a refresh, I could see the new FS and mount it.
BLKID now shows no EXT_JOURNAL information and the FS has no label. Is this something I have to/can add?

ryecoaaron · 8. Januar 2016

A filesystem doesn't have to have a label but you can change it with e2label /dev/md0 "newlabel". Post the output of: dumpe2fs -h /dev/md0

fitur · 8. Januar 2016

That worked perfectly. Thanks!

root@Rufus:~# dumpe2fs -h /dev/md0
dumpe2fs 1.42.5 (29-Jul-2012)
Filesystem volume name: Djingis
Last mounted on: /media/c009fc86-0e28-48f0-be5a-14cf27259570
Filesystem UUID: c009fc86-0e28-48f0-be5a-14cf27259570
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 183136256
Block count: 1465067520
Reserved block count: 73253376
Free blocks: 1453461948
Free inodes: 183135943
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 674
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 4096
Inode blocks per group: 256
RAID stride: 128
RAID stripe width: 256
Flex block group size: 16
Filesystem created: Fri Jan 8 10:10:37 2016
Last mount time: Fri Jan 8 13:23:39 2016
Last write time: Fri Jan 8 13:54:15 2016
Mount count: 2
Maximum mount count: -1
Last checked: Fri Jan 8 10:10:37 2016
Check interval: 0 (<none>)
Lifetime writes: 17 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 4879cbd9-d8f4-4fc4-afc7-af0b09edff9d
Journal backup: inode blocks
Journalfunktioner: journal_incompat_revoke
Journalstorlek: 128M
Journallängd: 32768
Journalsekvens: 0x00000787
Journalstart: 1

ryecoaaron · 8. Januar 2016

That looks good. You should be ok now.

alexanderryan4 · 14. April 2021

Zitat von fitur
Tried Ryecoaaron's option:
Code
dd if=/dev/zero of=/dev/md0 bs=512 count=10000
mkfs.ext4 /dev/md0
and then
mount /dev/md0

I had to delete the missing md0 FS in the OMV GUI but then, after a refresh, I could see the new FS and mount it.
BLKID now shows no EXT_JOURNAL information and the FS has no label. Is this something I have to/can add?

God bless you. I know it's been a few years since this thread but this still works and just helped me a whole lot!

uzurka · 7. April 2023

Zitat von fitur
Tried Ryecoaaron's option:
Code
dd if=/dev/zero of=/dev/md0 bs=512 count=10000
mkfs.ext4 /dev/md0
and then
mount /dev/md0

I had to delete the missing md0 FS in the OMV GUI but then, after a refresh, I could see the new FS and mount it.
BLKID now shows no EXT_JOURNAL information and the FS has no label. Is this something I have to/can add?

Still working like a charm today !
Got a similar error while mounting a RAID5 :

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian:
----------
          ID: create_filesystem_mountpoint_64e33e77-7b87-40db-af96-8364cda99a01
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_64e33e77-7b87-40db-af96-8364cda99a01 for file /etc/fstab was charged by text
     Started: 15:02:03.681148
    Duration: 1.999 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_64e33e77-7b87-40db-af96-8364cda99a01
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-ef98bdcd-8caf-4f50-8b66-be3bd9255946
      Result: True
     Comment: Target was already mounted
     Started: 15:02:03.683885
    Duration: 115.387 ms
     Changes:
              ----------
              umount:
                  Forced remount because options (user_xattr) changed
----------
          ID: create_filesystem_mountpoint_3ca5d879-5d0e-49ea-8a22-4c15e21ee962
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_3ca5d879-5d0e-49ea-8a22-4c15e21ee962 for file /etc/fstab was charged by text
     Started: 15:02:03.799557
    Duration: 1.516 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_3ca5d879-5d0e-49ea-8a22-4c15e21ee962
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-4ab831bb-40be-4c57-acd2-ff1671e99a13
      Result: True
     Comment: Target was already mounted
     Started: 15:02:03.801221
    Duration: 74.465 ms
     Changes:
              ----------
              umount:
                  Forced remount because options (user_xattr) changed
----------
          ID: create_filesystem_mountpoint_19a6a5dc-1efe-4e2a-91e1-834a8ee12bf5
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_19a6a5dc-1efe-4e2a-91e1-834a8ee12bf5 for file /etc/fstab was charged by text
     Started: 15:02:03.875981
    Duration: 1.961 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_19a6a5dc-1efe-4e2a-91e1-834a8ee12bf5
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-35606c9e-bf0f-4af4-9f25-c7e6b36e2a44
      Result: False
     Comment: mount: /srv/dev-disk-by-uuid-35606c9e-bf0f-4af4-9f25-c7e6b36e2a44: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error.
     Started: 15:02:03.878078
    Duration: 50.344 ms
     Changes:
----------
          ID: append_fstab_entries
    Function: file.blockreplace
        Name: /etc/fstab
      Result: True
     Comment: Changes were made
     Started: 15:02:03.932470
    Duration: 9.821 ms
     Changes:
              ----------
              diff:
                  ---
                  +++
                  @@ -17,4 +17,5 @@
                   # >>> [openmediavault]
                   /dev/disk/by-uuid/ef98bdcd-8caf-4f50-8b66-be3bd9255946        /srv/dev-disk-by-uuid-ef98bdcd-8caf-4f50-8b66-be3bd9255946    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
                   /dev/disk/by-uuid/4ab831bb-40be-4c57-acd2-ff1671e99a13        /srv/dev-disk-by-uuid-4ab831bb-40be-4c57-acd2-ff1671e99a13    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
                  +/dev/disk/by-uuid/35606c9e-bf0f-4af4-9f25-c7e6b36e2a44        /srv/dev-disk-by-uuid-35606c9e-bf0f-4af4-9f25-c7e6b36e2a44    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
                   # <<< [openmediavault]

Summary for debian
------------
Succeeded: 6 (changed=3)
Failed:    1
------------
Total states run:     7
Total run time: 255.493 ms

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian:
----------
          ID: create_filesystem_mountpoint_64e33e77-7b87-40db-af96-8364cda99a01
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_64e33e77-7b87-40db-af96-8364cda99a01 for file /etc/fstab was charged by text
     Started: 15:02:03.681148
    Duration: 1.999 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_64e33e77-7b87-40db-af96-8364cda99a01
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-ef98bdcd-8caf-4f50-8b66-be3bd9255946
      Result: True
     Comment: Target was already mounted
     Started: 15:02:03.683885
    Duration: 115.387 ms
     Changes:
              ----------
              umount:
                  Forced remount because options (user_xattr) changed
----------
          ID: create_filesystem_mountpoint_3ca5d879-5d0e-49ea-8a22-4c15e21ee962
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_3ca5d879-5d0e-49ea-8a22-4c15e21ee962 for file /etc/fstab was charged by text
     Started: 15:02:03.799557
    Duration: 1.516 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_3ca5d879-5d0e-49ea-8a22-4c15e21ee962
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-4ab831bb-40be-4c57-acd2-ff1671e99a13
      Result: True
     Comment: Target was already mounted
     Started: 15:02:03.801221
    Duration: 74.465 ms
     Changes:
              ----------
              umount:
                  Forced remount because options (user_xattr) changed
----------
          ID: create_filesystem_mountpoint_19a6a5dc-1efe-4e2a-91e1-834a8ee12bf5
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_19a6a5dc-1efe-4e2a-91e1-834a8ee12bf5 for file /etc/fstab was charged by text
     Started: 15:02:03.875981
    Duration: 1.961 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_19a6a5dc-1efe-4e2a-91e1-834a8ee12bf5
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-35606c9e-bf0f-4af4-9f25-c7e6b36e2a44
      Result: False
     Comment: mount: /srv/dev-disk-by-uuid-35606c9e-bf0f-4af4-9f25-c7e6b36e2a44: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error.
     Started: 15:02:03.878078
    Duration: 50.344 ms
     Changes:
----------
          ID: append_fstab_entries
    Function: file.blockreplace
        Name: /etc/fstab
      Result: True
     Comment: Changes were made
     Started: 15:02:03.932470
    Duration: 9.821 ms
     Changes:
              ----------
              diff:
                  ---
                  +++
                  @@ -17,4 +17,5 @@
                   # >>> [openmediavault]
                   /dev/disk/by-uuid/ef98bdcd-8caf-4f50-8b66-be3bd9255946        /srv/dev-disk-by-uuid-ef98bdcd-8caf-4f50-8b66-be3bd9255946    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
                   /dev/disk/by-uuid/4ab831bb-40be-4c57-acd2-ff1671e99a13        /srv/dev-disk-by-uuid-4ab831bb-40be-4c57-acd2-ff1671e99a13    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
                  +/dev/disk/by-uuid/35606c9e-bf0f-4af4-9f25-c7e6b36e2a44        /srv/dev-disk-by-uuid-35606c9e-bf0f-4af4-9f25-c7e6b36e2a44    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
                   # <<< [openmediavault]

Summary for debian
------------
Succeeded: 6 (changed=3)
Failed:    1
------------
Total states run:     7
Total run time: 255.493 ms in /usr/share/php/openmediavault/system/process.inc:220
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(174): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuswK...', '/tmp/bgoutputuY...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(195): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Alles anzeigen

This 2 commands worked like a charm !

wreckit27 · 29. April 2024

Zitat von fitur
Tried Ryecoaaron's option:
Code
dd if=/dev/zero of=/dev/md0 bs=512 count=10000
mkfs.ext4 /dev/md0
and then
mount /dev/md0

I had to delete the missing md0 FS in the OMV GUI but then, after a refresh, I could see the new FS and mount it.
BLKID now shows no EXT_JOURNAL information and the FS has no label. Is this something I have to/can add?

Chiming in from the future here. Setup my first RAID5 with the OMV GUI and hadn't been able to mount it. I kept seeing `Structure needs cleaning` whenever I try to mount the filesystem. Googling the error didn't help.

Finally I decided to just search the situation I encountered (RAID5 not mounting) and found this thread. The 2 lines of code from Ryecoaaron worked like magic!

I'm very grateful for the fix but can anyone explain what actually goes on and why this issue seem to happen occassionally?

Can't mount newly created RAID 5

Jetzt mitmachen!

Tags