Since the last update to 7.3.0-5 (Sandworm) I have run into the following issue (some excerpts from the most recent boots):
Code
Jul 02 17:03:06 openmediavault systemd[1]: dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device: Job dev-disk-by\x2duuidcfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device/start timed out.
Jul 02 17:03:06 openmediavault systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device - /dev/disk/by-uuid/cfd18169-e6ea-469d-9f25-c222a82302a6.
Jul 02 17:03:06 openmediavault systemd[1]: Dependency failed for systemd-fsck@dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.service - File System Check on /dev/disk/by-uuid/cfd18169-e6ea-469d-9f25-c222a8230>
Jul 02 17:03:06 openmediavault systemd[1]: Dependency failed for srv-dev\x2ddisk\x2dby\x2duuid\x2dcfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.mount - /srv/dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6.Code
Jul 02 17:37:38 openmediavault monit[1008]: 'filesystem_srv_dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6' trying to restart
Jul 02 17:37:38 openmediavault monit[1008]: 'mountpoint_srv_dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6' status failed (32) -- /srv/dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6 is not a mountpoint
Jul 02 17:37:38 openmediavault monit[1008]: 'mountpoint_srv_dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6' status failed (32) -- /srv/dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6 is not a mountpoint
Jul 02 17:38:08 openmediavault monit[1008]: Filesystem '/srv/dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6' not mounted
Jul 02 17:38:08 openmediavault monit[1008]: 'filesystem_srv_dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6' unable to read filesystem '/srv/dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6' stateCode
Jul 01 19:32:15 openmediavault systemd[1]: dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device: Job dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device/start timed out.
Jul 01 19:32:15 openmediavault systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device - /dev/disk/by-uuid/cfd18169-e6ea-469d-9f25-c222a82302a6.
Jul 01 19:32:15 openmediavault systemd[1]: Dependency failed for srv-dev\x2ddisk\x2dby\x2duuid\x2dcfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.mount - /srv/dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6.
Jul 01 19:32:15 openmediavault systemd[1]: srv-dev\x2ddisk\x2dby\x2duuid\x2dcfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.mount: Job srv-dev\x2ddisk\x2dby\x2duuid\x2dcfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.mount/start failed with result 'dependency'.
Jul 01 19:32:15 openmediavault systemd[1]: Dependency failed for systemd-fsck@dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.service - File System Check on /dev/disk/by-uuid/cfd18169-e6ea-469d-9f25-c222a82302a6.
Jul 01 19:32:15 openmediavault systemd[1]: systemd-fsck@dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.service: Job systemd-fsck@dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.service/start failed with result 'dependency'.
Jul 01 19:32:15 openmediavault systemd[1]: dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device: Job dev-disk-by\x2duuid-cfd18169\x2de6ea\x2d469d\x2d9f25\x2dc222a82302a6.device/start failed with result 'timeout'.After that in the GUI it displays the filesystem as missing and in "Multiple Devices" the RAID is completely gone. I can work around of this whole issue by doing a manual "mdadm --assemble md0" and adding "x-systemd.automount" to the file system in fstab. After I manually assemble the RAID after booting, only then the NAS does the "I'm done booting"-beep and everything works as normal.
Here's more info for good measure:
cat /proc/mdstat:
Code
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid6 sdb[0] sdh[7] sdg[6] sdf[5] sda[4] sde[3] sdd[2] sdc[1]
35162342400 blocks super 1.2 level 6, 512k chunk, algorithm 2 [8/8] [UUUUUUUU]
bitmap: 0/44 pages [0KB], 65536KB chunkblkid:
Code
/dev/sdf: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="2bb8811d-3565-ce9e-0c5c-9a36ff6e831f" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/nvme0n1p3: UUID="c2c2c343-fef0-4ee5-96fc-b5e4901e994b" TYPE="swap" PARTUUID="2e128110-891d-4b30-8f6f-b19f4d4ab7c1"
/dev/nvme0n1p1: UUID="15F7-854E" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="3d6ce883-d505-4db7-88fc-4c001aacc756"
/dev/nvme0n1p2: UUID="e673257c-ddb1-46db-aa09-1c3441da5663" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2c94ca82-0fd8-424c-9311-a6aa99653faa"
/dev/sdd: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="1f45d37d-8e25-7cec-d1a8-e20a5f28e757" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sdb: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="055af87b-4574-eb63-5f97-146a63b98fda" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sdg: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="5c57ee40-ccd9-d8b5-13fd-72244ef735f1" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sde: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="e54e7e3e-672e-fd76-50e5-e213a93c7af3" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sdc: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="decdb86a-189f-d324-9295-18576fd8b7f5" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sda: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="ca94814e-fc14-47f9-d9d8-e8ff2c900b04" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sdh: UUID="86fc8ff7-cd49-17fc-3f87-4a93f382df33" UUID_SUB="dbf69129-0858-fc77-5fe4-f1dba6216d6a" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/md0: UUID="cfd18169-e6ea-469d-9f25-c222a82302a6" BLOCK_SIZE="4096" TYPE="ext4"fdisk -l | grep "Disk ":
Code
Disk /dev/nvme0n1: 238,47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SK hynix BC711 HFM256GD3JX013N
Disk identifier: 993CCF6F-54B8-4315-9AA7-022C9AA62BF3
Disk /dev/sdb: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0034
Disk /dev/sdc: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0034
Disk /dev/sda: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0034
Disk /dev/sde: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: X316_SMKRE06TA07
Disk /dev/sdd: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000NM0034
Disk /dev/sdg: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: X316_SMKRE06TA07
Disk /dev/sdf: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: X316_SMKRE06TA07
Disk /dev/sdh: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: X316_SMKRE06TA07
Disk /dev/md0: 32,75 TiB, 36006238617600 bytes, 70324684800 sectorscat /etc/mdadm/mdadm.conf:
Code
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# 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/md0 metadata=1.2 name=openmediavault:0 UUID=86fc8ff7:cd4917fc:3f874a93:f382df33
ARRAY /dev/md/0 metadata=1.2 UUID=86fc8ff7:cd4917fc:3f874a93:f382df33 name=openmediavault:0mdadm --detail --scan --verbose:
Code
ARRAY /dev/md/md0 level=raid6 num-devices=8 metadata=1.2 name=openmediavault:0 UUID=86fc8ff7:cd4917fc:3f874a93:f382df33
devices=/dev/sda,/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde,/dev/sdf,/dev/sdg,/dev/sdhcat /etc/fstab:
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).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=e673257c-ddb1-46db-aa09-1c3441da5663 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=15F7-854E /boot/efi vfat umask=0077 0 1
# swap was on /dev/nvme0n1p3 during installation
UUID=c2c2c343-fef0-4ee5-96fc-b5e4901e994b none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/cfd18169-e6ea-469d-9f25-c222a82302a6 /srv/dev-disk-by-uuid-cfd18169-e6ea-469d-9f25-c222a82302a6 ext4 defaults,nofail,noauto,x-systemd.automount,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]Any pointers how to solve this? I could just run "mdadm --assemble md0" via crontab @reboot, but that would be bad practice, no?
