After Upgrade to 4.1.23-1 my mdraid is not mounted etc

    • Resolved
    • OMV 4.x
    • After Upgrade to 4.1.23-1 my mdraid is not mounted etc

      Dear Sir/Madam,

      I just upgraded to 4.1.23-1

      And now my raid does not get mounted, and i cannot change settings on shares etc :

      I get this if i try and edit permissions on a share :

      Error #0:
      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; systemctl restart 'sharedfolders-pgnas2.mount' 2>&1' with exit code '1': A dependency job for sharedfolders-pgnas2.mount failed. See 'journalctl -xe' for details. in /usr/share/php/openmediavault/system/process.inc:182
      Stack trace:
      #0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
      #1 /usr/share/php/openmediavault/system/systemctl.inc(160): OMV\System\SystemCtl->exec('restart', NULL, false)
      #2 /usr/share/openmediavault/engined/module/sharedfolders.inc(66): OMV\System\SystemCtl->restart()
      #3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleSharedfolders->startService()
      #4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusUW...', '/tmp/bgoutputS6...')
      #8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      #9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      #10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      #11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      #12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      #13 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      #14 {main}

      journalctl -xe

      Aug 09 17:43:06 pgnas2 monit[954]: 'mountpoint_srv_dev-disk-by-label-pgnas2' status failed (1) -- /srv/dev-disk-by-label-pgnas2 is not a mountpoint
      Aug 09 17:43:06 pgnas2 monit[954]: 'mountpoint_ssd' status failed (1) -- /ssd is not a mountpoint
      Aug 09 17:43:16 pgnas2 systemd[1]: dev-disk-by\x2dlabel-pgnas2.device: Job dev-disk-by\x2dlabel-pgnas2.device/start timed out.
      Aug 09 17:43:16 pgnas2 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-pgnas2.device.
      -- Subject: Unit dev-disk-by\x2dlabel-pgnas2.device has failed
      -- Defined-By: systemd
      -- Support: debian.org/support
      --
      -- Unit dev-disk-by\x2dlabel-pgnas2.device has failed.
      --
      -- The result is timeout.
      Aug 09 17:43:16 pgnas2 systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/pgnas2.
      -- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-pgnas2.service has failed
      -- Defined-By: systemd
      -- Support: debian.org/support
      --
      -- Unit systemd-fsck@dev-disk-by\x2dlabel-pgnas2.service has failed.
      --
      -- The result is dependency.
      Aug 09 17:43:16 pgnas2 systemd[1]: Dependency failed for /srv/dev-disk-by-label-pgnas2.
      -- Subject: Unit srv-dev\x2ddisk\x2dby\x2dlabel\x2dpgnas2.mount has failed
      -- Defined-By: systemd
      -- Support: debian.org/support
      --
      -- Unit srv-dev\x2ddisk\x2dby\x2dlabel\x2dpgnas2.mount has failed.
      --
      -- The result is dependency.
      Aug 09 17:43:16 pgnas2 systemd[1]: srv-dev\x2ddisk\x2dby\x2dlabel\x2dpgnas2.mount: Job srv-dev\x2ddisk\x2dby\x2dlabel\x2dpgnas2.mount/start failed with result
      Aug 09 17:43:16 pgnas2 systemd[1]: systemd-fsck@dev-disk-by\x2dlabel-pgnas2.service: Job systemd-fsck@dev-disk-by\x2dlabel-pgnas2.service/start failed with res
      Aug 09 17:43:16 pgnas2 systemd[1]: dev-disk-by\x2dlabel-pgnas2.device: Job dev-disk-by\x2dlabel-pgnas2.device/start failed with result 'timeout'.
      Aug 09 17:43:36 pgnas2 monit[954]: 'mountpoint_srv_dev-disk-by-label-pgnas2' status failed (1) -- /srv/dev-disk-by-label-pgnas2 is not a mountpoint
      Aug 09 17:43:36 pgnas2 monit[954]: 'mountpoint_ssd' status failed (1) -- /ssd is not a mountpoint
      Aug 09 17:44:05 pgnas2 proftpd[19007]: 127.0.1.1 (192.168.0.115[192.168.0.115]) - FTP session opened.
      Aug 09 17:44:05 pgnas2 proftpd[19007]: 127.0.1.1 (192.168.0.115[192.168.0.115]) - mod_wrap/1.2.4: using access files: /etc/hosts.allow, /etc/hosts.deny
      Aug 09 17:44:05 pgnas2 proftpd[19007]: 127.0.1.1 (192.168.0.115[192.168.0.115]) - mod_wrap/1.2.4: allowed connection from ::ffff:192.168.0.115
      Aug 09 17:44:05 pgnas2 proftpd[19007]: pam_unix(proftpd:session): session opened for user mrpg by (uid=0)
      Aug 09 17:44:05 pgnas2 proftpd[19007]: 127.0.1.1 (192.168.0.115[192.168.0.115]) - notice: unable to use DefaultRoot '/srv/ftp/' [resolved to '/srv/ftp/']: No s
      Aug 09 17:44:05 pgnas2 proftpd[19007]: 127.0.1.1 (192.168.0.115[192.168.0.115]) - mrpg chdir("/") failed: No such file or directory
      Aug 09 17:44:05 pgnas2 proftpd[19007]: pam_unix(proftpd:session): session closed for user mrpg
      Aug 09 17:44:05 pgnas2 proftpd[19007]: 127.0.1.1 (192.168.0.115[192.168.0.115]) - FTP session closed.
      Aug 09 17:44:06 pgnas2 monit[954]: 'mountpoint_srv_dev-disk-by-label-pgnas2' status failed (1) -- /srv/dev-disk-by-label-pgnas2 is not a mountpoint
      Aug 09 17:44:06 pgnas2 monit[954]: 'mountpoint_ssd' status failed (1) -- /ssd is not a mountpoint
      Aug 09 17:44:36 pgnas2 monit[954]: 'mountpoint_srv_dev-disk-by-label-pgnas2' status failed (1) -- /srv/dev-disk-by-label-pgnas2 is not a mountpoint
      Aug 09 17:44:36 pgnas2 monit[954]: 'mountpoint_ssd' status failed (1) -- /ssd is not a mountpoint

      fdisk -l

      root@pgnas2:/# fdisk -l
      Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 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 /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 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 /dev/sdf: 111.8 GiB, 120034123776 bytes, 234441648 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
      Disklabel type: dos
      Disk identifier: 0xf6eb0bdb

      Device Boot Start End Sectors Size Id Type
      /dev/sdf1 * 2048 226058239 226056192 107.8G 83 Linux
      /dev/sdf2 226060286 234440703 8380418 4G 5 Extended
      /dev/sdf5 226060288 234440703 8380416 4G 82 Linux swap / Solaris

      Partition 2 does not start on physical sector boundary.


      Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 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 /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 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 /dev/sdb: 745.2 GiB, 800166076416 bytes, 1562824368 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
      Disklabel type: gpt
      Disk identifier: 90E8329A-585A-7A4F-B3EC-40383F610EC1

      Device Start End Sectors Size Type
      /dev/sdb1 2048 1562806271 1562804224 745.2G Solaris /usr & Apple ZFS
      /dev/sdb9 1562806272 1562822655 16384 8M Solaris reserved 1


      Disk /dev/md127: 8.2 TiB, 9001374842880 bytes, 17580810240 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 524288 bytes / 1572864 bytes


      Perhaps the label of the disk has changed or something? as i can see /dev/md127 thats where my raid5 is

      i am not sure how to fix this.

      Please help, i will provide any and all further details if needed :

      Bes Regards
      Patric
    • Hi Geaves,

      Many thanks for helping!

      Here are the snippets :

      Source Code

      1. root@pgnas2:/# cat /proc/mdstat
      2. Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
      3. md127 : active (auto-read-only) raid5 sde[3] sdd[2] sda[0] sdc[1]
      4. 8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
      5. bitmap: 0/22 pages [0KB], 65536KB chunk
      6. unused devices: <none>





      Source Code

      1. /dev/sda: UUID="a4eaac6d-09a7-678a-a410-39f545fc8a88" UUID_SUB="829814f6-afe7-cba4-e318-24feaf4234f0" LABEL="pgnas2:Raid5" TYPE="linux_raid_member"
      2. /dev/sdc: UUID="a4eaac6d-09a7-678a-a410-39f545fc8a88" UUID_SUB="d994823b-0bdb-77f3-8536-91fd896168ff" LABEL="pgnas2:Raid5" TYPE="linux_raid_member"
      3. /dev/sdf1: UUID="f53de5f0-6b4f-4e67-9d08-2267ef9542f1" TYPE="ext4" PARTUUID="f6eb0bdb-01"
      4. /dev/sdf5: UUID="db997024-abda-4a75-984e-f8a82430d819" TYPE="swap" PARTUUID="f6eb0bdb-05"
      5. /dev/sde: UUID="a4eaac6d-09a7-678a-a410-39f545fc8a88" UUID_SUB="1f0a97e5-d8b2-7055-daea-5ad2158b81a1" LABEL="pgnas2:Raid5" TYPE="linux_raid_member"
      6. /dev/sdd: UUID="a4eaac6d-09a7-678a-a410-39f545fc8a88" UUID_SUB="754525e4-e931-00ab-35ad-05355e77b4ad" LABEL="pgnas2:Raid5" TYPE="linux_raid_member"
      7. /dev/sdb1: LABEL="ssd" UUID="16055115822611016235" UUID_SUB="16333854279340365342" TYPE="zfs_member" PARTLABEL="zfs-cfaad19e7bf04ac2" PARTUUID="ffcf088a-ea6d-d643-8c7c-6a78625f922c"
      8. /dev/sdb9: PARTUUID="b56e0178-1205-694d-baae-07356e2e412b"

      Source Code

      1. root@pgnas2:/# fdisk -l | grep "Disk "
      2. Partition 2 does not start on physical sector boundary.
      3. Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
      4. Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
      5. Disk /dev/sdf: 111.8 GiB, 120034123776 bytes, 234441648 sectors
      6. Disk identifier: 0xf6eb0bdb
      7. Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
      8. Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
      9. Disk /dev/sdb: 745.2 GiB, 800166076416 bytes, 1562824368 sectors
      10. Disk identifier: 90E8329A-585A-7A4F-B3EC-40383F610EC1
      11. Disk /dev/md127: 8.2 TiB, 9001374842880 bytes, 17580810240 sectors
      Display All

      Source Code

      1. root@pgnas2:/# cat /etc/mdadm/mdadm.conf
      2. # mdadm.conf
      3. #
      4. # Please refer to mdadm.conf(5) for information about this file.
      5. #
      6. # by default, scan all partitions (/proc/partitions) for MD superblocks.
      7. # alternatively, specify devices to scan, using wildcards if desired.
      8. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      9. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      10. # used if no RAID devices are configured.
      11. DEVICE partitions
      12. # auto-create devices with Debian standard permissions
      13. CREATE owner=root group=disk mode=0660 auto=yes
      14. # automatically tag new arrays as belonging to the local system
      15. HOMEHOST <system>
      16. # definitions of existing MD arrays
      17. ARRAY /dev/md/Raid5 metadata=1.2 name=pgnas2:Raid5 UUID=a4eaac6d:09a7678a:a41039f5:45fc8a88
      18. # instruct the monitoring daemon where to send mail alerts
      19. MAILADDR pg@lannywanny.se
      20. MAILFROM rootroot@pgnas2:/#
      Display All

      Source Code

      1. root@pgnas2:/# mdadm --detail --scan --verbose
      2. ARRAY /dev/md/Raid5 level=raid5 num-devices=4 metadata=1.2 name=pgnas2:Raid5 UUID=a4eaac6d:09a7678a:a41039f5:45fc8a88
      3. devices=/dev/sda,/dev/sdc,/dev/sdd,/dev/sde
    • Source Code

      1. root@pgnas2:/# mdadm --readwrite /dev/md127
      2. root@pgnas2:/# cat /proc/mdstat
      3. Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
      4. md127 : active raid5 sde[3] sdd[2] sda[0] sdc[1]
      5. 8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
      6. bitmap: 0/22 pages [0KB], 65536KB chunk
      7. unused devices: <none>
      8. root@pgnas2:/# omv-mkconf mdadm
      9. /usr/share/openmediavault/mkconf/mdadm: 99: [: ARRAY: unexpected operator
      10. update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.5-amd64
      11. update-initramfs: Generating /boot/initrd.img-4.9.0-0.bpo.6-amd64
      12. update-initramfs: Generating /boot/initrd.img-4.9.0-0.bpo.5-amd64
      Display All
      That did not seem to do much.

      still same problem as posted in the thread start.

      and the raid disk is not visible under file systems in omv web gui.

      This bits is where i suspect the problem is? that it cannot find this disk?

      Source Code

      1. journalctl -xe
      2. Aug 09 17:43:06 pgnas2 monit[954]: 'mountpoint_srv_dev-disk-by-label-pgnas2' status failed (1) -- /srv/dev-disk-by-label-pgnas2 is not a mountpoint
      3. Aug 09 17:43:06 pgnas2 monit[954]: 'mountpoint_ssd' status failed (1) -- /ssd is not a mountpoint
      4. Aug 09 17:43:16 pgnas2 systemd[1]: dev-disk-by\x2dlabel-pgnas2.device: Job dev-disk-by\x2dlabel-pgnas2.device/start timed out.
      5. Aug 09 17:43:16 pgnas2 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-pgnas2.device.
      6. -- Subject: Unit dev-disk-by\x2dlabel-pgnas2.device has failed
      7. -- Defined-By: systemd
      8. -- Support: debian.org/support
      9. --
      10. -- Unit dev-disk-by\x2dlabel-pgnas2.device has failed.
      Display All


      Many thanks
      Patric

      The post was edited 1 time, last by mrpg ().

    • ok, mount -a just wont show you any details :

      Source Code

      1. root@pgnas2:~# mount -a
      2. root@pgnas2:~# clear
      3. root@pgnas2:~# cat /etc/fstab
      4. # /etc/fstab: static file system information.
      5. #
      6. # Use 'blkid' to print the universally unique identifier for a
      7. # device; this may be used with UUID= as a more robust way to name devices
      8. # that works even if disks are added and removed. See fstab(5).
      9. #
      10. # <file system> <mount point> <type> <options> <dump> <pass>
      11. # / was on /dev/sda1 during installation
      12. UUID=f53de5f0-6b4f-4e67-9d08-2267ef9542f1 / ext4 errors=remount-ro 0 1
      13. # swap was on /dev/sda5 during installation
      14. UUID=db997024-abda-4a75-984e-f8a82430d819 none swap sw 0 0
      15. tmpfs /tmp tmpfs defaults 0 0
      16. # >>> [openmediavault]
      17. /dev/disk/by-label/pgnas2 /srv/dev-disk-by-label-pgnas2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      18. /srv/dev-disk-by-label-pgnas2/pgnas /export/pgnas2 none bind,nofail 0 0
      19. /ssd/ssd /export/ssd none bind,nofail,_netdev 0 0
      20. # <<< [openmediavault]
      21. root@pgnas2:~#
      Display All
    • Ok the fstab shows no entry for the array, hence it's not mounting not sure if this would resolve it omv-mkconf fstab

      Can't make sense of this either:
      /dev/sdb1: LABEL="ssd" UUID="16055115822611016235" UUID_SUB="16333854279340365342" TYPE="zfs_member" PARTLABEL="zfs-cfaad19e7bf04ac2" PARTUUID="ffcf088a-ea6d-d643-8c7c-6a78625f922c"

      nor the output from journalctl -xe seems to relate to an ssd
      Raid is not a backup! Would you go skydiving without a parachute?
    • Hi,

      I used to have a 3 disk zfs, all three disks died, and i dont know how to clean that up, perhaps thats leftovers from that?.

      i ran :

      Source Code

      1. root@pgnas2:~# omv-mkconf fstab
      2. root@pgnas2:~# mount -av
      3. / : ignored
      4. none : ignored
      5. /tmp : already mounted
      6. /export/pgnas2 : already mounted
      7. /export/ssd : already mounted
      8. root@pgnas2:~#
      and rebooted, no change
    • yeah its still the same issue.

      te md127 is still not mounted, as in these messages, it cant find the disk :

      Source Code

      1. journalctl -xe
      2. Aug 09 17:43:06 pgnas2 monit[954]: 'mountpoint_srv_dev-disk-by-label-pgnas2' status failed (1) -- /srv/dev-disk-by-label-pgnas2 is not a mountpoint
      3. Aug 09 17:43:06 pgnas2 monit[954]: 'mountpoint_ssd' status failed (1) -- /ssd is not a mountpoint
      4. Aug 09 17:43:16 pgnas2 systemd[1]: dev-disk-by\x2dlabel-pgnas2.device: Job dev-disk-by\x2dlabel-pgnas2.device/start timed out.
      5. Aug 09 17:43:16 pgnas2 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-pgnas2.device.
      6. -- Subject: Unit dev-disk-by\x2dlabel-pgnas2.device has failed
      7. -- Defined-By: systemd
      8. -- Support: debian.org/support
      9. --
      10. -- Unit dev-disk-by\x2dlabel-pgnas2.device has failed.
    • Users Online 1

      1 Guest