USB Backup configuration survived all OMV upgrades except to v3. However, when I plug in the disk there are several beeps. Is there anything I can do to restore configuration?
USB Backup configuration lost after upgrade to OMV3
-
- OMV 3.x
- rutra80
-
-
Tried to recreate configuration but when I try to run a backup it errors:
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
ERROR: External storage device '/dev/disk/by-id/usb-ST2000LM_003_HN-M201RAD_FF2000FF00F377F9FFA02859-0:0-part1' not mounted!And when I try to unmount the drive:
Error #0:exception 'OMV\Config\DatabaseException' with message 'The XPath query '//system/fstab/mntent[dir='/media/4CF0796AF0795AE2']' does not return the requested number of 1 object(s).' in /usr/share/php/openmediavault/config/database.inc:172Stack trace:#0 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(964): OMV\Config\Database->getByFilter('conf.system.fil...', Array, 1)#1 [internal function]: OMVRpcServiceFileSystemMgmt->umount(Array, Array)#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)#3 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('umount', Array, Array)#4 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('FileSystemMgmt', 'umount', Array, Array, 1)#5 {main} -
I guess I'll just restore that trainwreck v3 "upgrade" to v2 from a backup
-
Looks like the upgrade didn't finish. What is the output of: dpkg -l | grep openm
-
Code
ii openmediavault 3.0.59 all Open network attached storage solution ii openmediavault-cups 3.1.1 all OpenMediaVault CUPS (network printer server) plugin. ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-minidlna 3.3.4 all OpenMediaVault miniDLNA (DLNA server) plugin ii openmediavault-omvextrasorg 3.4.14 all OMV-Extras.org Package Repositories for OpenMediaVault ii openmediavault-usbbackup 3.2.12 all OpenMediaVault USB/eSATA backup plugin
-
What is the output of:
cat /etc/fstab
omv-showkey mntentDo you have a desktop environment installed?
-
Code
Alles anzeigen# /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> proc /proc proc defaults 0 0 # / was on /dev/sda1 during installation UUID=dc0f364d-0d5d-4b70-b0d8-fe230571b296 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=71f3a1ec-2130-408b-860e-027cccfeda90 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # /dev/sda1 /media/usb0 auto rw,user,noauto 0 0 UUID=055b500e-ffb0-4058-b3f8-6a6bdd5ff65b /media/usb0 auto rw,user,noauto 0 0 /dev/sda2 /media/usb1 auto rw,user,noauto 0 0 /dev/sda5 /media/usb2 auto rw,user,noauto 0 0 tmpfs /tmp tmpfs defaults 0 0 # >>> [openmediavault] UUID=055b500e-ffb0-4058-b3f8-6a6bdd5ff65b /media/055b500e-ffb0-4058-b3f8-6a6bdd5ff65b ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2 # <<< [openmediavault]
Code
Alles anzeigen<mntent> <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid> <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname> <dir>/xxx/yyy/zzz</dir> <type>ext2|ext3|ext4|xfs|jfs|iso9660|udf</type> <opts></opts> <freq>0</freq> <passno>0|1|2</passno> </mntent> <mntent> <uuid>076512a7-0d5a-4392-9c99-a4c7ba9742cf</uuid> <fsname>055b500e-ffb0-4058-b3f8-6a6bdd5ff65b</fsname> <dir>/media/055b500e-ffb0-4058-b3f8-6a6bdd5ff65b</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>0</hidden> </mntent>
There's no desktop environment.
-
Do you have two data drives? Is one or both usb? Post the output of blkid
-
Code
/dev/sda1: UUID="055b500e-ffb0-4058-b3f8-6a6bdd5ff65b" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="c7efbca5-2022-4c97-90fa-f41ae65ccf27" /dev/sdb1: UUID="dc0f364d-0d5d-4b70-b0d8-fe230571b296" TYPE="ext4" PARTUUID="000852cf-01" /dev/sdb5: UUID="71f3a1ec-2130-408b-860e-027cccfeda90" TYPE="swap" PARTUUID="000852cf-05"
One SATA data drive, one USB system drive, one USB backup drive.
-
UUID=055b500e-ffb0-4058-b3f8-6a6bdd5ff65b /media/usb0 auto rw,user,noauto 0 0
/dev/sda2 /media/usb1 auto rw,user,noauto 0 0
/dev/sda5 /media/usb2 auto rw,user,noauto 0 0You need to remove these lines especially the first. When you added the first one, it is already added by OMV.
-
Ehh, thank you R2 but it turns out there's more problems, several tabs throw out errors, notifications don't work etc.
-
There are threads about the common upgrade errors. You probably aren't running into any that haven't already been solved.
-
Ultimately I reverted to flawlessly working v2.1, perhaps I'll try v3 upgrade some time later when it's more unfailing.
-
perhaps I'll try v3 upgrade some time later when it's more unfailing.
Strange. The problems I noticed were problems introduced from things you changed. Just because they worked with OMV 2.x does not mean OMV is the problem. There is huge difference between Debian 7 (OMV 2.x) and Debian (OMV 3.x).
-
But I didn't change anything. It's a vanilla OMV with MiniDLNA and CUPS only, nothing was ever changed behind the curtains except for fixing stuff borked by upgrades. I'm using 3.2 kernel in OMV v2 and it is working great.
v3 upgrade breaks just too many things here to make manual fixing worthwhile when v2 works so good.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!