OMV is labelling one hard disk twice. How To repair?

    • OMV 2.x
    • Resolved
    • OMV is labelling one hard disk twice. How To repair?

      I had initial issues with my openmediavault system because for some reason, one of my hard disks went missing. This disk was in a JBOD linked to the server via a USB3 connector.
      To avoid the issue I ran the following procedure: unix.stackexchange.com/questio…ting-usb-sticks-on-debian
      After this I noticed that the system was double labelling disks as in the attached example:
      root@omv:~# blkid -o list
      device fs_type label mount point UUID
      -------------------------------------------------------------------------------------------------------------------------------------------------------
      /dev/sda1 ext4 Gen1610T0004 /media/usb3 95af425e-7c51-4539-ad8f-c67966f3b5fb
      /dev/sdi1 ext4 2Hornetek1 /media/0fdb085d-2371-4cc6-86f1-0f98e7e3721a 0fdb085d-2371-4cc6-86f1-0f98e7e3721a
      /dev/sdj1 ntfs Z800Backup /media/01D175003DF87D40 01D175003DF87D40
      /dev/sdf1 ntfs PassportHDD /media/usb0 01D05435239BD740
      /dev/sdg1 ntfs MyBook500GB /media/usb1 3E027FB3027F6F31
      /dev/sdh1 ntfs PassportVMS (not mounted) F474B7AA74B76DCC
      /dev/sdb1 ntfs My Passport /media/54D8D96AD8D94ABE 54D8D96AD8D94ABE
      /dev/sdc1 ntfs HPZ800Backup /media/F474B7AA74B76DCC F474B7AA74B76DCC
      /dev/sdd1 ext4 Gen1610T0003 /media/67e677e1-50a3-4be4-b273-abff7a70cd56 67e677e1-50a3-4be4-b273-abff7a70cd56
      /dev/sde1 vfat VID /media/usb2 55BA-8E92
      /dev/sdk1 ext4 2Hornetek2 /media/6f1b1b52-a404-4bb7-a249-382b25b75801 6f1b1b52-a404-4bb7-a249-382b25b75801
      /dev/sdo1 ext4 Gen1610T0002 /media/4ffe7ed7-6381-421c-bc93-1bec6448ee37 4ffe7ed7-6381-421c-bc93-1bec6448ee37
      /dev/sdm1 ext4 Horntekk2 /media/b0e1c7dc-56ad-48ca-a980-e59231da4036 b0e1c7dc-56ad-48ca-a980-e59231da4036
      /dev/sdn1 ext4 Gen1610T0004 /media/8bfc6a26-2a16-416a-92ca-ae9a579ddff6 8bfc6a26-2a16-416a-92ca-ae9a579ddff6
      /dev/sdl1 ext4 Horntekk3 /media/db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9 db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9
      /dev/sdp1 ext4 Gen1610T0001 /media/7e4d9949-1d15-42de-ae4b-35721e8c3702 7e4d9949-1d15-42de-ae4b-35721e8c3702
      /dev/sdq1 ext4 Gen1610T0003 /media/c41de965-ebea-4229-a2b0-e514be69bf67 c41de965-ebea-4229-a2b0-e514be69bf67
      /dev/sdr1 ext4 Horntekk3 / f3655cd5-176c-41c4-b271-2b7172b67d58
      /dev/sda5 swap (not mounted) 1c72916d-09d9-43a2-b5a3-49f284e0a578
      /dev/sdd5 swap (not mounted) 9dac56c3-a385-4a51-bc97-5f1f75e513a5
      /dev/sdr5 swap <swap> 25550420-645b-4e41-a8e2-32b41d07a757
      /dev/sdt1 ext4 Horntekk4 /media/c6dce86b-f3ee-4251-b33a-d76a8f95707d c6dce86b-f3ee-4251-b33a-d76a8f95707d
      root@omv:~#

      As you can see Gen1610T0004 is occuring twice when it should occur only once. According to my previous records, there should only be one of this. How can I correct it?
      if I run this I get:

      Source Code

      1. root@omv:~# blkid -U 8bfc6a26-2a16-416a-92ca-ae9a579ddff6
      2. /dev/sdn1

      And this gives me:

      Source Code

      1. root@omv:~# blkid -U 95af425e-7c51-4539-ad8f-c67966f3b5fb
      2. /dev/sda1

      Either this one hard disk is being mounted twice or there is a problem.

      Source Code

      1. root@omv:~# blkid -L Gen1610T0004
      2. /dev/sdn1

      I know from previous interrogations that /dev/sda1 is
      Disk /dev/sda: 32.0 GB, 32015679488 bytes
      255 heads, 63 sectors/track, 3892 cylinders, total 62530624 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: 0x000db286

      Device Boot Start End Blocks Id System
      /dev/sda1 * 2048 59891711 29944832 83 Linux
      /dev/sda2 59893758 62529535 1317889 5 Extended
      /dev/sda5 59893760 62529535 1317888 82 Linux swap / Solaris
      Note: sector size is 4096 (not 512)

      I have deleted the scripts I initiated in http automount and ran omv-mkconf fstab but I still get no repair.
      Can anyone help repair the damage I did my system?
      My fstab is as follows:
      root@omv:~# 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/sde1 during installation
      UUID=f3655cd5-176c-41c4-b271-2b7172b67d58 / ext4 errors=remount-ro 0 1
      # swap was on /dev/sde5 during installation
      UUID=25550420-645b-4e41-a8e2-32b41d07a757 none swap sw 0 0
      /dev/sdf1 /media/usb0 auto rw,user,noauto 0 0
      /dev/sdg1 /media/usb1 auto rw,user,noauto 0 0
      /dev/sdg2 /media/usb2 auto rw,user,noauto 0 0
      /dev/sdg5 /media/usb3 auto rw,user,noauto 0 0
      # >>> [openmediavault]
      UUID=8bfc6a26-2a16-416a-92ca-ae9a579ddff6 /media/8bfc6a26-2a16-416a-92ca-ae9a579ddff6 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=4ffe7ed7-6381-421c-bc93-1bec6448ee37 /media/4ffe7ed7-6381-421c-bc93-1bec6448ee37 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=7e4d9949-1d15-42de-ae4b-35721e8c3702 /media/7e4d9949-1d15-42de-ae4b-35721e8c3702 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=c41de965-ebea-4229-a2b0-e514be69bf67 /media/c41de965-ebea-4229-a2b0-e514be69bf67 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=c6dce86b-f3ee-4251-b33a-d76a8f95707d /media/c6dce86b-f3ee-4251-b33a-d76a8f95707d ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=b0e1c7dc-56ad-48ca-a980-e59231da4036 /media/b0e1c7dc-56ad-48ca-a980-e59231da4036 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9 /media/db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=6f1b1b52-a404-4bb7-a249-382b25b75801 /media/6f1b1b52-a404-4bb7-a249-382b25b75801 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=0fdb085d-2371-4cc6-86f1-0f98e7e3721a /media/0fdb085d-2371-4cc6-86f1-0f98e7e3721a ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=67e677e1-50a3-4be4-b273-abff7a70cd56 /media/67e677e1-50a3-4be4-b273-abff7a70cd56 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      UUID=b0f7900f-891b-47a4-b1ab-2956e09300ee /media/b0f7900f-891b-47a4-b1ab-2956e09300ee ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
      /dev/disk/by-uuid/54D8D96AD8D94ABE /media/54D8D96AD8D94ABE ntfs defaults,nofail 0 2
      /dev/disk/by-uuid/01D05435239BD740 /media/01D05435239BD740 ntfs defaults,nofail 0 2
      /dev/disk/by-uuid/01D175003DF87D40 /media/01D175003DF87D40 ntfs defaults,nofail 0 2
      /dev/disk/by-uuid/F474B7AA74B76DCC /media/F474B7AA74B76DCC ntfs defaults,nofail 0 2
      # <<< [openmediavault]


      The config xml and the automount process are attached

      One other variable I should mention is that during booting I get a pause and a request to run a maintenance shell which is kind of difficult since all I can run is fsck which always exits with an e2fsck 8 error.
      I have googled to find out what else to do but the advice to run fsck is e2fsck is tempered by the responses from the system that running fsck on a GPT system is not recommended.
      I'm kind of stuck. Can anyone help?
      Files
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220
    • subzero79 wrote:

      Why don't you undo all the configurations you did?
      autofs shouldbe used in only certain cases. I suspect you haven't deleted your udev rules and that's why youre getting double entries.

      I have deleted all the rules. I followed the process exactly and removed each script but what I have not done is rebooted the server itself.
      I will do that now and report back.

      I rebooted the server and then ssh into it and ran blkid -o list and got this: Now Gen1016T0003 is being counted twice. Should I delete the relevant sections of configuration.xml in the hope that fstab will rebuild?

      ​root@omv:~# blkid -o list
      device fs_type label mount point UUID
      -------------------------------------------------------------------------------------------------------------------------------------------
      /dev/sda1 ext4 Gen1610T0004 (in use) 95af425e-7c51-4539-ad8f-c67966f3b5fb
      /dev/sdi1 ext4 2Hornetek1 /media/0fdb085d-2371-4cc6-86f1-0f98e7e3721a 0fdb085d-2371-4cc6-86f1-0f98e7e3721a
      /dev/sdj1 ntfs Z800Backup /media/01D175003DF87D40 01D175003DF87D40
      /dev/sdf1 ntfs PassportHDD /media/usb0 01D05435239BD740
      /dev/sdg1 ntfs MyBook500GB /media/usb1 3E027FB3027F6F31
      /dev/sdh1 ntfs PassportVMS /media/F474B7AA74B76DCC F474B7AA74B76DCC
      /dev/sdb1 ntfs My Passport /media/54D8D96AD8D94ABE 54D8D96AD8D94ABE
      /dev/sdc1 ntfs HPZ800Backup (not mounted) F474B7AA74B76DCC
      /dev/sdd1 ext4 Gen1610T0003 /media/67e677e1-50a3-4be4-b273-abff7a70cd56 67e677e1-50a3-4be4-b273-abff7a70cd56
      /dev/sde1 vfat VID /media/usb2 55BA-8E92
      /dev/sdk1 ext4 Horntekk4 /media/c6dce86b-f3ee-4251-b33a-d76a8f95707d c6dce86b-f3ee-4251-b33a-d76a8f95707d
      /dev/sdo1 ext4 Gen1610T0004 /media/8bfc6a26-2a16-416a-92ca-ae9a579ddff6 8bfc6a26-2a16-416a-92ca-ae9a579ddff6
      /dev/sdm1 ext4 Horntekk3 /media/db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9 db5d0e3c-b56f-4e00-9f7d-a2965c3bc1b9
      /dev/sdl1 ext4 2Hornetek2 /media/6f1b1b52-a404-4bb7-a249-382b25b75801 6f1b1b52-a404-4bb7-a249-382b25b75801
      /dev/sdp1 ext4 Gen1610T0002 /media/4ffe7ed7-6381-421c-bc93-1bec6448ee37 4ffe7ed7-6381-421c-bc93-1bec6448ee37
      /dev/sdq1 ext4 Gen1610T0001 /media/7e4d9949-1d15-42de-ae4b-35721e8c3702 7e4d9949-1d15-42de-ae4b-35721e8c3702
      /dev/sdr1 ext4 Gen1610T0003 /media/c41de965-ebea-4229-a2b0-e514be69bf67 c41de965-ebea-4229-a2b0-e514be69bf67
      /dev/sda5 swap (not mounted) 1c72916d-09d9-43a2-b5a3-49f284e0a578
      /dev/sdd5 swap (not mounted) 9dac56c3-a385-4a51-bc97-5f1f75e513a5
      /dev/sds1 ext4 / f3655cd5-176c-41c4-b271-2b7172b67d58
      /dev/sds5 swap <swap> 25550420-645b-4e41-a8e2-32b41d07a757


      Although omv reports the hdd situation accurately except that it is now reporting a communication failure. sigh!
      I have donated. have you?
      OMV 2.2 running on HP Gen 8 G1610T server, 16GB RAM + Xeon E3-1220

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