Not able to delete missing Filesystem Entrys

    • OMV 0.5
    • Resolved
    • Not able to delete missing Filesystem Entrys

      Good Morning from Germany,

      since working on it to make the external Backup run i have some serious problems and still no solution for it.
      It seems that i´m not the only one who ever had the same problem like this how to remove devices in filesystems

      Prehistory:

      I had Problems formating the external HDD (now done, ext4, 4 TB). With this i also deleted on of my NAS Drives (2 x 4TB in Mirror) that was my fault !!! thank God, the Mirror was working and i had at least acccess to my Data, so i could backup them to the external HDD. I formated the deleted NAS HDD (ext4) and tried to run the Rebuild using the WebGUI, this didn´t work (don´t know why) so i tried it again using mdadm this worked.. at least until the next reboot of the hole system. With all this the system created the first wrong Filesystem entry. after the restart i could see my still working Mirror drive and a new drive (the other new formated Mirror drive). I tried to rebuild again with mdadm this worked.. until the next reboot. I started to read the forum and found the above Thread. So i modified the fstab and config.xml (reboot the system) and now i have to missing drives in the filesystem and i´m still not able to delete this both entrys. I also can see my still working Drive and the other one (didn´t not try to rebuild again) I can not see / find any wrong entry anymore within the fstab and config.xml.

      Now.....

      i would like to delete this two wrong entrys and make the Mirror run again.

      Someone any idea ???
      Asus Z97M-Plus / Intel Core i5 / 16 GB RAM / System: 120 GB Intel SSD / RAID 1 - 2 x 4 TB Seagate ST4000VN000 / USB Backup HDD - Seagate Backup Plus Desktop STCA4000200

      OMV - Arrakis
    • In 0.5 there is no relationship between shares and hard disks, thus you're unable to delete it via the GUI. You have to manually delete it from /etc/openmediavault/config.xml including all shares and service entrys that relate to the missing disk.

      In 1.0 you can remove it from the GUI.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Hi David,

      i dont see any relation / connection (in the config.xml) between the unknown devices and the existing shares connected to the drives which are still working. What about if i´m upgrading to 1.0 right now ? Would i be able to delete them over the GUI after the Upgrade ?
      by the way... "deleting the shares" you mean.. just the pathes in the config.xml ? if not, i´m going to lose all my data right if i really delete them or not ?
      What about the unsuccessfully rebuild ? Is this happening because of the unknown devices in the filesystem ?

      Greetings

      Andre
      Asus Z97M-Plus / Intel Core i5 / 16 GB RAM / System: 120 GB Intel SSD / RAID 1 - 2 x 4 TB Seagate ST4000VN000 / USB Backup HDD - Seagate Backup Plus Desktop STCA4000200

      OMV - Arrakis
    • Sunseeker wrote:

      by the way... "deleting the shares" you mean.. just the pathes in the config.xml ? if not, i´m going to lose all my data right if i really delete them or not ?


      I'm only speaking about the entrys in the config.xml for the already MISSING hdd.

      Sunseeker wrote:

      What about the unsuccessfully rebuild ? Is this happening because of the unknown devices in the filesystem ?


      Doubtfull.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Ok, thanks.. i will try to delete them in the config.xml
      What about the update to 1.0 ?
      Can you confirm that i really have to delete this hole part ?

      Source Code

      1. <hdparm>
      2. <uuid>c978a35b-5ff5-48e3-b046-58b3fa184e44</uuid>
      3. <devicefile>/dev/disk/by-id/wwn-0x5000c50065785d25</devicefile>
      4. <apm>0</apm>
      5. <aam>0</aam>
      6. <spindowntime>0</spindowntime>
      7. <writecache>1</writecache>
      8. </hdparm>
      9. <hdparm>
      10. <uuid>09871b71-c552-4e23-8ae0-152d55c61cdc</uuid>
      11. <devicefile>/dev/disk/by-id/wwn-0x5000c5006577d795</devicefile>
      12. <apm>0</apm>
      13. <aam>0</aam>
      14. <spindowntime>0</spindowntime>
      15. <writecache>1</writecache>
      16. </hdparm>
      17. <hdparm>
      18. <uuid>ca9b2d70-10f6-44aa-b3f4-3fbf5cd5e6d7</uuid>
      19. <devicefile>/dev/disk/by-id/wwn-0x500000e0404539ea</devicefile>
      20. <apm>0</apm>
      21. <aam>0</aam>
      22. <spindowntime>0</spindowntime>
      23. <writecache>1</writecache>
      24. </hdparm>
      25. <hdparm>
      26. <uuid>b1ce4338-e935-4353-a9ad-2b2f1d6142bf</uuid>
      27. <devicefile>/dev/disk/by-id/usb-Seagate_Backup+_Desk_NA5KJCN4-0:0</devicefile>
      28. <apm>0</apm>
      29. <aam>0</aam>
      30. <spindowntime>0</spindowntime>
      31. <writecache>1</writecache>
      32. </hdparm>
      33. </storage>
      34. <fstab>
      35. <!--
      36. <mntent>
      37. <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
      38. <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
      39. <dir>/xxx/yyy/zzz</dir>
      40. <type>ext2|ext3|ext4|xfs|jfs|iso9660|udf</type>
      41. <opts></opts>
      42. <freq>0</freq>
      43. <passno>0|1|2</passno>
      44. </mntent>
      45. -->
      46. <mntent>
      47. <uuid>cf6517f5-4182-42cc-9206-e479d27d9bdb</uuid>
      48. <fsname>9a697230-e889-41ac-b396-c2b0302cfcb3</fsname>
      49. <dir>/media/9a697230-e889-41ac-b396-c2b0302cfcb3</dir>
      50. <type>ext4</type>
      51. <opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts>
      52. <freq>0</freq>
      53. <passno>2</passno>
      54. </mntent>
      55. <mntent>
      56. <uuid>52bc6b6c-e5f4-483e-bcd5-79dfe32d6f27</uuid>
      57. <fsname>9bc8e9da-199b-fed6-ca5a-89ca7c4eea01</fsname>
      58. <dir>/media/9bc8e9da-199b-fed6-ca5a-89ca7c4eea01</dir>
      59. <type>ext4</type>
      60. <opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts>
      61. <freq>0</freq>
      62. <passno>2</passno>
      63. </mntent>
      64. <mntent>
      65. <uuid>4e26c656-dbad-40b3-b177-b3585add7505</uuid>
      66. <fsname>48dfcc30-f863-4bb2-90dd-46adc44e8214</fsname>
      67. <dir>/media/48dfcc30-f863-4bb2-90dd-46adc44e8214</dir>
      68. <type>ext4</type>
      69. <opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts>
      70. <freq>0</freq>
      71. <passno>2</passno>
      72. </mntent>
      73. </fstab>
      74. <shares>
      75. <!--
      76. <sharedfolder>
      77. <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
      78. <name>xxx</name>
      79. <comment>xxx</comment>
      80. <mntentref>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</mntentref>
      81. <reldirpath>xxx</reldirpath>
      82. <privileges>
      83. <privilege>
      84. <type>user|group</type>
      85. <name>xxx</name>
      86. <perms>0 = no permission|5 = read and execute|7 = read, write and execute</perms>
      87. </privilege>
      88. </privileges>
      89. </sharedfolder>
      90. -->
      91. <sharedfolder>
      92. <uuid>9298e7c4-1e18-4728-ae58-2c42f23008f5</uuid>
      93. <name>User</name>
      94. <comment></comment>
      95. <mntentref>cf6517f5-4182-42cc-9206-e479d27d9bdb</mntentref>
      96. <reldirpath>User/</reldirpath>
      97. <privileges></privileges>
      98. </sharedfolder>
      99. <sharedfolder>
      100. <uuid>dabcd14c-49b0-420e-8606-7f867ed49ff3</uuid>
      101. <name>TimeMachine</name>
      102. <comment></comment>
      103. <mntentref>cf6517f5-4182-42cc-9206-e479d27d9bdb</mntentref>
      104. <reldirpath>TimeMachine/</reldirpath>
      105. <privileges>
      106. <privilege>
      107. <type>user</type>
      108. <name>Andre</name>
      109. <perms>7</perms>
      110. </privilege>
      Display All

      Thanks

      Andre
      Asus Z97M-Plus / Intel Core i5 / 16 GB RAM / System: 120 GB Intel SSD / RAID 1 - 2 x 4 TB Seagate ST4000VN000 / USB Backup HDD - Seagate Backup Plus Desktop STCA4000200

      OMV - Arrakis

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

    • I have deleted every entry related to shares and services.

      after restarting the system i have still this both missing entrys in the filesystem

      Any idea ?
      Asus Z97M-Plus / Intel Core i5 / 16 GB RAM / System: 120 GB Intel SSD / RAID 1 - 2 x 4 TB Seagate ST4000VN000 / USB Backup HDD - Seagate Backup Plus Desktop STCA4000200

      OMV - Arrakis
    • Did you remove the entry for the harddisk/filesystem too?

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Good Morning,

      well.... this still exists: can you mark the part which i have to delete as well please.

      Thanks

      Source Code

      1. <filesystem>
      2. <!--
      3. <quota>
      4. <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
      5. <fsuuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx</fsuuid>
      6. <usrquota>
      7. <name>xxx</name>
      8. <bsoftlimit>0</bsoftlimit>
      9. <bhardlimit>xxx</bhardlimit>
      10. <isoftlimit>0</isoftlimit>
      11. <ihardlimit>0</ihardlimit>
      12. </usrquota>
      13. <usrquota>
      14. ...
      15. </usrquota>
      16. <grpquota>
      17. <name>xxx</name>
      18. <bsoftlimit>0</bsoftlimit>
      19. <bhardlimit>xxx</bhardlimit>
      20. <isoftlimit>0</isoftlimit>
      21. <ihardlimit>0</ihardlimit>
      22. </grpquota>
      23. <grpquota>
      24. ...
      25. </grpquota>
      26. </quota>
      27. <quota>
      28. ...
      29. </quota>
      30. -->
      31. </filesystem>
      32. <hdparm>
      33. <uuid>c978a35b-5ff5-48e3-b046-58b3fa184e44</uuid>
      34. <devicefile>/dev/disk/by-id/wwn-0x5000c50065785d25</devicefile>
      35. <apm>0</apm>
      36. <aam>0</aam>
      37. <spindowntime>0</spindowntime>
      38. <writecache>1</writecache>
      39. </hdparm>
      40. <hdparm>
      41. <uuid>09871b71-c552-4e23-8ae0-152d55c61cdc</uuid>
      42. <devicefile>/dev/disk/by-id/wwn-0x5000c5006577d795</devicefile>
      43. <apm>0</apm>
      44. <aam>0</aam>
      45. <spindowntime>0</spindowntime>
      46. <writecache>1</writecache>
      47. </hdparm>
      48. <hdparm>
      49. <uuid>ca9b2d70-10f6-44aa-b3f4-3fbf5cd5e6d7</uuid>
      50. <devicefile>/dev/disk/by-id/wwn-0x500000e0404539ea</devicefile>
      51. <apm>0</apm>
      52. <aam>0</aam>
      53. <spindowntime>0</spindowntime>
      54. <writecache>1</writecache>
      55. </hdparm>
      56. <hdparm>
      57. <uuid>b1ce4338-e935-4353-a9ad-2b2f1d6142bf</uuid>
      58. <devicefile>/dev/disk/by-id/usb-Seagate_Backup+_Desk_NA5KJCN4-0:0</devicefile>
      59. <apm>0</apm>
      60. <aam>0</aam>
      61. <spindowntime>0</spindowntime>
      62. <writecache>1</writecache>
      63. </hdparm>
      64. </storage>
      65. <fstab>
      66. <!--
      67. <mntent>
      68. <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
      69. <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
      70. <dir>/xxx/yyy/zzz</dir>
      71. <type>ext2|ext3|ext4|xfs|jfs|iso9660|udf</type>
      72. <opts></opts>
      73. <freq>0</freq>
      74. <passno>0|1|2</passno>
      75. </mntent>
      76. -->
      77. <mntent>
      78. <uuid>cf6517f5-4182-42cc-9206-e479d27d9bdb</uuid>
      79. <fsname>9a697230-e889-41ac-b396-c2b0302cfcb3</fsname>
      80. <dir>/media/9a697230-e889-41ac-b396-c2b0302cfcb3</dir>
      81. <type>ext4</type>
      82. <opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts>
      83. <freq>0</freq>
      84. <passno>2</passno>
      85. </mntent>
      86. <mntent>
      87. <uuid>52bc6b6c-e5f4-483e-bcd5-79dfe32d6f27</uuid>
      88. <fsname>9bc8e9da-199b-fed6-ca5a-89ca7c4eea01</fsname>
      89. <dir>/media/9bc8e9da-199b-fed6-ca5a-89ca7c4eea01</dir>
      90. <type>ext4</type>
      91. <opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts>
      92. <freq>0</freq>
      93. <passno>2</passno>
      94. </mntent>
      95. <mntent>
      96. <uuid>4e26c656-dbad-40b3-b177-b3585add7505</uuid>
      97. <fsname>48dfcc30-f863-4bb2-90dd-46adc44e8214</fsname>
      98. <dir>/media/48dfcc30-f863-4bb2-90dd-46adc44e8214</dir>
      99. <type>ext4</type>
      100. <opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts>
      101. <freq>0</freq>
      102. <passno>2</passno>
      103. </mntent>
      104. </fstab>
      105. <shares>
      Display All

      Asus Z97M-Plus / Intel Core i5 / 16 GB RAM / System: 120 GB Intel SSD / RAID 1 - 2 x 4 TB Seagate ST4000VN000 / USB Backup HDD - Seagate Backup Plus Desktop STCA4000200

      OMV - Arrakis

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

    • Sunseeker, I did not read above but always make a backup of important files before you edit:

      mkdir /scratch
      cp /etc/openmediavault/config.xml /scratch

      or you can simply make a .bk file in current location

      cd /etc/openmediavault
      cp config.xml config.bk

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

    • Good Morning everybody,

      problem solved !!! thread can be closed...

      I have installed a fresh wheezy and Kralizec on top. Now i´m a Kralizec Beta User !

      Greetings and have a nice day... thanks for your support :)
      Asus Z97M-Plus / Intel Core i5 / 16 GB RAM / System: 120 GB Intel SSD / RAID 1 - 2 x 4 TB Seagate ST4000VN000 / USB Backup HDD - Seagate Backup Plus Desktop STCA4000200

      OMV - Arrakis
    • Been here twice now ;) Loving OMV on RPi3b+! Can't wait for a true gigabit ethernet USB 3 product. Anyway, USB 2 with WiFi working very well for now. Point is that I am a long time, experienced, Windows operator but relatively new to Linux (happy with DOS prompt so comfortable with SSH cmd). Guess what, I've messed this up twice too. I have, however, made a simple workaround for windows users.

      1) Whoops, got the order wrong
      2) Shutdown OMV
      3) Attach drive unit (my case a 4 bay USB 3 Orico) to Windows PC
      4) Install and run Minitool Partition Wizard (free)
      5) Find the messed up drive, delete all partitions and format to NTFS
      6) Attach drive unit back onto OMV box and switch on
      7) Edit /etc/openmediavault/config.xml (I used Notepad++ with Filezilla) whilst looking at your erroneous entries and watch them go
      8 Wipe clean NTFS drive to EXT4
      9) Profit

      So now I want the experienced Linux wonders to let me know why I'm going to cease humanity's existence through this method (that's nearly happened before with some of my workarounds!). Many thanks....looking forward to learning so much on here, some superb contributors on this forum!!
    • You have to delete your own posts. Use Edit (lower right), click on More Options, and check "Move this post to trash".
      Good backup takes the "drama" out of computing
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
      2nd Data Backup: OMV 3.0.99, R-PI 2B, 16GB boot, 4TB WD USB MyPassport - direct connect (no hub)