OMV 2.2.13: RAID5 missing after reboot

markus-fried@gmx.de · 23. Juni 2017

Hi guys,

I've got 3 WD SATA drives configured into a RAID5.

Today had a power outage the battery kicked in and shut the server down.

When I restarted later my data volumes were gone.

I can see the RAID5 as clean in the OMV GUI, but the file system on it can't be mounted.

Any idea?

Best Regards

Mark.

tkaiser · 23. Juni 2017

Not that much informtion... what about running a fsck and if this fails restoring latest backup and continue running?

markus-fried@gmx.de · 23. Juni 2017

thanks for you input -I already did a fs check - no errors - it's just that it won't get mounted on startup

When I try to mount the RAID manually I get the following error:

Code

Error #6000:
exception 'OMVException' with message 'Failed to mount 'fefa03a4-f295-4b64-b7ad-49dba9101cc8': mount: can't find /media/fefa03a4-f295-4b64-b7ad-49dba9101cc8 in /etc/fstab or /etc/mtab' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:931
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}

omv-mkconf fstab did not change the situation either.

Mark.

tkaiser · 23. Juni 2017

How do /etc/fstab and output from 'lsblk' look like?

markus-fried@gmx.de · 23. Juni 2017

Code

sudo lsblk
NAME      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda         8:0    0  55,9G  0 disk
├─sda1      8:1    0  53,6G  0 part  /
├─sda2      8:2    0     1K  0 part
└─sda5      8:5    0   2,3G  0 part  [SWAP]
sdb         8:16   0   2,7T  0 disk
└─md127     9:127  0   5,5T  0 raid5
sdc         8:32   0   2,7T  0 disk
└─md127     9:127  0   5,5T  0 raid5
sdd         8:48   0   2,7T  0 disk
└─md127     9:127  0   5,5T  0 raid5
sde         8:64   0   1,8T  0 disk
├─sde1      8:65   0 517,7M  0 part
│ └─md125   9:125  0 517,6M  0 raid1
├─sde2      8:66   0 517,7M  0 part
│ └─md126   9:126  0 517,6M  0 raid1
├─sde3      8:67   0   1,8T  0 part
└─sde4      8:68   0 486,3M  0 part
  └─md124   9:124  0 448,1M  0 raid1

Alles anzeigen

Code

# /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=60a34d84-7808-4f55-b6cf-85085449fa0e /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=cb4bec70-1d91-4d2c-ba5b-8547141de1c8 none            swap    sw              0       0
/dev/sdb1       /media/usb0     auto    rw,user,noauto  0       0
tmpfs           /tmp            tmpfs   defaults        0       0
# >>> [openmediavault]
UUID=9233e731-35e8-44a1-acda-494a8e782c5b /media/9233e731-35e8-44a1-acda-494a8e782c5b ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]

Alles anzeigen

tkaiser · 23. Juni 2017

Silly me, I wanted 'blkid' output but asked for 'lsblk'

At least you need a match between UUIDs in your system and the one in /etc/fstab. But it needs someone else commenting on what's necessary to edit this since I have forgotten everything I ever did with OMV 2 (continued recently with 3.0.65 and above)

markus-fried@gmx.de · 23. Juni 2017

thanks anyway, just in case here is the output of 'blkid'

Code

/dev/sdb: UUID="2925be41-fc40-e814-1ba6-b2a7d48d94eb" UUID_SUB="494a3956-6113-6104-1adf-0e91af53ad43" LABEL="OMV:MasterVault" TYPE="linux_raid_member"
/dev/sdc: UUID="2925be41-fc40-e814-1ba6-b2a7d48d94eb" UUID_SUB="63651409-9fdd-cda6-349b-96d1bb93af37" LABEL="OMV:MasterVault" TYPE="linux_raid_member"
/dev/sde1: UUID="9eee4ce1-8f7b-d9f8-d832-36864d9c359d" TYPE="linux_raid_member"
/dev/md127: LABEL="Data" UUID="fefa03a4-f295-4b64-b7ad-49dba9101cc8" TYPE="ext4"
/dev/md126: UUID="e511463e-3be9-4c93-8f25-43cf50f55803" TYPE="swap"
/dev/md125: UUID="d0a2c22e-0a4f-433c-a63a-5e1f354c50e7" SEC_TYPE="ext2" TYPE="ext3"
/dev/md124: UUID="a9452440-d89a-4ad5-919c-f38efc69a499" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda1: UUID="60a34d84-7808-4f55-b6cf-85085449fa0e" TYPE="ext4"
/dev/sda5: UUID="cb4bec70-1d91-4d2c-ba5b-8547141de1c8" TYPE="swap"
/dev/sdd: UUID="2925be41-fc40-e814-1ba6-b2a7d48d94eb" UUID_SUB="98b93a20-3877-06fe-330b-b0281b25c8c8" LABEL="OMV:MasterVault" TYPE="linux_raid_member"
/dev/sde2: UUID="1b692fd1-0b7d-4871-90ed-caab235dd1c8" TYPE="linux_raid_member"
/dev/sde3: UUID="ab855e11-d4b3-4d1e-8dd8-5487cb6d9518" TYPE="ext4"
/dev/sde4: UUID="6b872a8b-c0d8-ae59-afc0-f6122c5b3870" TYPE="linux_raid_member"

Alles anzeigen

OMV 2.2.13: RAID5 missing after reboot

Jetzt mitmachen!

Tags