For all people having problems with it, execute the following via CLI
omv-mkconf fstab
Then either reboot or execute
mount -a
to remount your hard disks.
Greetings
David
For all people having problems with it, execute the following via CLI
omv-mkconf fstab
Then either reboot or execute
mount -a
to remount your hard disks.
Greetings
David
I have tested both my OMV boxes and I have always this error:
Failed
to mount 'cecc979d-ee30-428e-aa84-826260112a19': mount: can't find
/media/cecc979d-ee30-428e-aa84-826260112a19 in /etc/fstab or /etc/mtab
Error
#6000:
exception 'OMVException' with message 'Failed to mount
'cecc979d-ee30-428e-aa84-826260112a19': mount: can't find
/media/cecc979d-ee30-428e-aa84-826260112a19 in /etc/fstab or /etc/mtab'
in /usr/share/openmediavault/engined/module/fstab.inc:90
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/config.inc(206):
OMVModuleFsTab->startService()
#1 [internal function]: OMVRpcServiceConfig->applyChanges(Array,
Array)
#2 /usr/share/php/openmediavault/rpcservice.inc(125):
call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpcservice.inc(158):
OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
#4 /usr/share/openmediavault/engined/rpc/config.inc(224):
OMVRpcServiceAbstract->callMethodBg('applyChanges', Array, Array)
#5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array,
Array)
#6 /usr/share/php/openmediavault/rpcservice.inc(125):
call_user_func_array(Array, Array)
#7 /usr/share/php/openmediavault/rpc.inc(79):
OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
#8 /usr/sbin/omv-engined(501): OMVRpc::exec('Config', 'applyChangesBg',
Array, Array, 1)
#9 {main}
Alles anzeigen
I tested both my machines:
omv-mkconf fstab + reboot -> error
omv-mkconf fstab + mount -a -> error
omv-mkconf fstab + reboot + mount -a -> error
The only way to mount my two backup hard drives is booting the machines with Parted Magic.
Edit: Modified directly the fstab file adding this string:
UUID=cecc979d-ee30-428e-aa84-826260112a19 /media/cecc979d-ee30-428e-aa84-826260112a19 ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group
Now the hard drive is mounted
please update to the latest 1.0.26 and run omv-mkconf fstab afterwards
Had a look in your config.xml:
Please check if this works:
edit your config.xml and change the "hidden"-tag in this section for your drive: (config/system/fstab)
<mntent>
<uuid>fd600278-4f40-4e34-8681-f03ba410bc9e</uuid>
<fsname>cecc979d-ee30-428e-aa84-826260112a19</fsname>
<dir>/media/cecc979d-ee30-428e-aa84-826260112a19</dir>
<type>ext4</type>
<opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>1</hidden>
</mntent>
from "1" to
run omv-mkconf fstab, reboot and it should be there
Edit: Its too early in the morning and I have misread your post...
Greetings
David
Thank you very much, now I have understood the problem (at least on my own machines, I don't know if there is a bug in OMV).
To reproduce the problem on my systems:
- connect external hard drive.
- on the webgui -> Storage -> File Systems
- push the button "Mount"
- push the button "Unmount" (in config.xml the section of the unmounted hard drive disappears)
- push (again) the button "Mount" (in config.xml the section of the unmounted hard drive reappears with "hidden" = 1)
After pushing the "Mount" button I have the error message.
If I edit che config.xml changing the "hidden" value from 1 to 0 then I can push the yellow "Apply" button without the error message. Now the hard drive is mounted correctly.
Thanks again Solo.
Hello,
The release 1.27.1 solve this bug for me.
Sorry for my english... i'm french user.
Welcome @alexdaums
Thx for reporting.
We understand you anyway You can also put your french text throuhg the google translator if you have problems.
hi guys,
thanks !
I've done the suggested operations :
run "omv-mkconf fstab", reboot
it does work fine
(fyi, if it can help : I had done the upgrade to 1.0.27 and it didnt solve the issue)
have a good evening all !
Chris, also from France
Installed OMV 1.0.x and updated, attached storage and everything working like a champ. Thanks for all the assistance!
Cheers,
Frenetic
Ive got alos problem with my file disk not being able to get mounted.
i had todo da clean install since upgrading bricked the system.
ive deatached the file disk and did the install , shutdown the system reattached it like in the Guide.
but now i cant mount it, under the webinterface i see it in Physical Disk /dev/sdb
but in filesystems i see only /dev/sda
the onyl thing i can click there is create if i do that and look on the devices i see the HDD, but he wants to format what i ofc dont want so i cancelled it
Tryd the suggested stuff here in this thread nothing worked.
omv-mkconf fstab - does nothing
mount -a -does nothing
blkid
/dev/sda1: UUID="f74f8db3-e7a4-4f1e-96c9-d46382dd84d6" TYPE="ext4"
/dev/sda5: UUID="a992585e-22eb-41c0-b095-88bbe36f57b5" TYPE="swap"
/dev/sdb1: UUID="6J2l3M-QKk5-xK3A-47Xe-Sl1d-oVcS-B04e4q" TYPE="LVM2_member" <------ that i want to mount
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/sda1 during installation
UUID=f74f8db3-e7a4-4f1e-96c9-d46382dd84d6 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=a992585e-22eb-41c0-b095-88bbe36f57b5 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
tmpfs /tmp tmpfs defaults 0 0
# >>> [openmediavault]
# <<< [openmediavault]
media
/media# ls -al
insgesamt 12
drwxr-xr-x 3 root root 4096 Sep 10 19:18 .
drwxr-xr-x 24 root root 4096 Nov 1 01:44 ..
lrwxrwxrwx 1 root root 6 Nov 1 00:31 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 Nov 1 00:31 cdrom0
/dev/mapper# ls -al
insgesamt 0
drwxr-xr-x 2 root root 80 Nov 1 02:00 .
drwxr-xr-x 15 root root 3160 Nov 1 02:00 ..
crw------T 1 root root 10, 236 Nov 1 02:00 control
lrwxrwxrwx 1 root root 7 Nov 1 02:00 space1-space1 -> ../dm-0 <- space1-space1 is that HDD
Version 1.0.29
Do this and then reboot:
omv-mkconf fstab
omv-mkconf fstab - does nothing
mount -a -does nothing
If it does not throw an error, the command was successful.
If it does not throw an error, the command was successful.
This is so confusing for people from the windows world where they expect to get a successfull message.
Greetings
David
i mean it does nothing that it still not working and ofc i did a reboot
so i redid the command and rebooted now i get a kernel panic on boot
http://www.suckmypic.net/5qNwaegA.png
ive got the feeling the upgrade killed something on that disk
Alles anzeigeni mean it does nothing that it still not working and ofc i did a reboot
so i redid the command and rebooted now i get a kernel panic on boot
http://www.suckmypic.net/5qNwaegA.png
ive got the feeling the upgrade killed something on that disk
That says it's unable to mount the root filesystem. What is your OS drive? Have you tried just doing a clean install?
Hi the OS drive is /dev/sda mount i want the /dev/sdb
this error happend after doing the omv-mkconf fstab and reboot
this is a clean install of 1.0
when i reboot agn its working but still the sdb is not mountable
so i redid the command omv-mkconf fstab and reboot
this time it boot up but still the drive is not under Storage - filesystems i can only choose it when i click on create
ive got the feeling the filesystem is broken on that drive...
Hi!
I've got the same problem as posted above: I can mount FS on CLI (but then can't add shared folder as the "Volume" dropdown is empty.. ), but not on Web. I get the error:
Error #6000:
exception 'OMVException' with message 'Failed to mount 'abd590d7-a0c7-433d-a990-6100d28fbea7': mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
' in /usr/share/openmediavault/engined/module/fstab.inc:90
I've posted on another thread with same issue:
OMV 1.0.29 Partition mount problem
I was running 0.5.x version, and have to get 1.0.29 running as smooth
Solved !!!
see OMV 1.0.29 Partition mount problem
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!