Hello,
I have removed/replaced some harddrives (using part of them now as RAID).
Even though I have afterwards removed the entries of those drives in the webgui, I still get
fsck.ext4: Unable to resolve 'UUID=bafe12a7-c795-46d3-9804-5e27bf357596'
fsck.ext4: Unable to resolve 'UUID=d74b4e1b-6e8e-4c19-b823-0d9bb688f0f5'
fsck.ext4: Unable to resolve 'UUID=1bb45a3e-0a3a-48a7-b979-b2e193be5e85'
when I boot.
Does anybody know how to get rid of this?
Thank you!
Regards, Tomte.
Allways remove them via the webgui. You need to remove shares and shared folders first before you can unmount them in the GUI.
You now have to remove the entries in /etc/openmediavault/config.xml manually.
Greetings
David
Hello,
thank you for the quick answer!!
However, this file does not exist. It is probably the file
/etc/openmediavault/config.xml
In this file, I delete the blocks like:
<mntent>
<uuid>5db4407b-f8c0-4879-8274-852f3c7307fd</uuid>
<fsname>bafe12a7-c795-46d3-9804-5e27bf357596</fsname>
<dir>/media/bafe12a7-c795-46d3-9804-5e27bf357596</dir>
<type>ext4</type>
<opts>defaults,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aq$
<freq>0</freq>
<passno>2</passno>
</mntent>
Right?
Can something go wrong if I delete too many/the wrong ones? I am a bit confused, that uuid and fsname are not the same?!?
Regards, Tomte
Yep, sorry, just wrote it from the memory...
Yes you need to remove these blocks. Of course you need to remove the right ones!
Greetings
David
uuid is a unique xml id. fsname is unique mount point name. They won't be the same.
If you use the blkid command it will give you a list of the current filesystems on your OMV. That should help you to make sure you don't delete the wrong ones.
I corrected David's post. You are correct it it the /etc/openmediavault/config.xml that has to be edited. Backup this file before you edit it.
cd /etc/openmediavault
cp config.xml config.bak1
Be careful editing the config.xml. Also, if the deleted filesystems were still used by any services there may be some remnants of the filesystems in any services that you used them in within the config.xml. So you may have make some corrections in other sections too. Rule of thumb is to always remove filesystems via the web-gui. If they cannot be removed they are still being used by some service.
If you make a mistake and need a do over just do this:
cd /etc/openmediavault
cp config.bak1 config.xml
Viel Glu"ck!!
Hello,
thank you for the explanations!
I have removed the above mentioned sections, however, I still get the fsck-error messages during start up.
So I am missing other entries to be removed?
Regards, Tomte.
PS: If I had known, I would have removed the Gui entries first, of course. But I cannot reinstall the drives I removed. I would rather reinstall OMV.
How should I have known?
You need to remove the entries from /etc/fstab as well.
Hello,
thank you for supporting me so much.
I am not there, yet:
I have an NFS share which drive does not exist anymore.
When I try to delete it, I get:
Failed to get configuration (xpath=//services/nfs/shares/share[uuid='999aadba-a1aa-4695-a861-5cd08e9d35c2'])And under "freigegebene Ordner", I can not delete the abandoned entry (greyed).
What can I do?
Regards, Tomte.
You need to remove that entry from /etc/openmediavault/config.xml and /etc/fstab as well.
Well, I can not find the above name uuid in any of these ...
So what can I do/should I remove?
I forgot to tell you /etc/exports
Thanks a lot to all who supported me! I finally managed all.
I had to delete some depenencies, before I could delete the shared folders ...
Regards, Tomte!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!