Still no progress here - usbbackup does not run, when the USB harddisk is plugged in. Have to trigger all backups manually in the GUI.
Any idea, what's the problem here?
Still no progress here - usbbackup does not run, when the USB harddisk is plugged in. Have to trigger all backups manually in the GUI.
Any idea, what's the problem here?
this is still a thing ?
Yes, it still is.
In OMV 3.0.90, I have got a RAID 5 with three discs, one had to be replaced and the RAID rebuilt, and afterwards, I got that message.
I "fixed" /etc/mdadm/mdadm.conf now manually, hope that works
I've even re-installed the usbbackup-package (before, it was already in the latest version), but it still doesn't autodetect the plugged-in backup disc.
However, when I manually trigger the backup job in the GUI, it works (though it blocks the GUI for a very long time, until the backup is finished)
The backup drive is in good health, I had no problems in mounting it manually (I used /mnt/cdrom as mountpoint).
The last time, I successfully ran usbbackup was in mid january according to my notes. After that I didn't try it any more, so now it's time ![]()
Unplugging and plugging again does not help. Manual mounting, e.g. to /mnt/cdrom does not help, too.
I doubt, re-installing the plugin will help, to me it seems, that the plugin itself or the part in OMV, which it uses, is broken ![]()
Hi,
I just wanted to make my usual backup by just plugging in my USB3-hard drive, but this time, it failed.
I plugged in the disc, and in /var/log/daemon.log, you can read, what happened:
May 14 17:18:05 nas systemd[1]: Found device External_USB_3.0 TOSHIBA_EXT.
May 14 17:18:05 nas systemd[1]: Found device External_USB_3.0 TOSHIBA_EXT.
May 14 17:18:05 nas systemd[1]: Starting Execute the rsync backup jobs when /dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2 is plugged in...
May 14 17:18:06 nas ntfs-3g[3900]: Version 2014.2.15AR.2 integrated FUSE 28
May 14 17:18:06 nas ntfs-3g[3900]: Mounted /dev/sde2 (Read-Write, label "TOSHIBA EXT", NTFS 3.1)
May 14 17:18:06 nas ntfs-3g[3900]: Cmdline options: rw
May 14 17:18:06 nas ntfs-3g[3900]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sde2,blkdev,blksize=4096
May 14 17:18:06 nas ntfs-3g[3900]: Ownership and permissions disabled, configuration type 7
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:07 nas openmediavault-usbbackup-fefe811c9a7804e3c6137d70193f91ea[3896]: ERROR: External storage device </dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2> not mounted!
May 14 17:18:08 nas ntfs-3g[3900]: Unmounting /dev/sde2 (TOSHIBA EXT)
May 14 17:18:08 nas systemd[1]: Started Execute the rsync backup jobs when /dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20160908007094F-0:0-part2 is plugged in.
Any idea, what changed with that plugin (I use the most recent version 3.2.18 on openmediavault 3.0.75.1), so that it doesn't automount the backup USB disk anymore, and so cannot start the rsync backup process?
Thank you very much
Christoph
And an additional question: What's the purpose of the following mail, I get daily on my OMV 3 installation:
Cron <root@nas> test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null [nas.*************]
invoke-rc.d: policy-rc.d denied execution of start.
Of course, I could modify policy-rc.d, and from what I've seen, it seems to be related to sysvinit (which is a bit odd, since Debian 8 uses systemd instead), but without knowing the reason for it, I don't want to ![]()
Thanks
Christoph
Same problem here.
I even switched off the journal on my ext4-RAID-array, but the HDDs never spin down, though there's no data written or read from these disks,
Als MB verwende ich ein AsRock J3710, 4GB RAM, SSD als OS-Harddisk, dazu ein RAID5 mit 3 3TB-Platten.
Die Installation erfolgte über einen USB-Stick, das Image war das 3.0.42 aus dem offiziellen Download, nach der Installation habe ich noch das Repo für die omv-extras installiert und über die Update-Funktion auf die 3.0.43 aktualisiert.
Was auffällig ist, ist, daß in /sbin sowohl der "fake" start-stop-daemon (der ja nichts tut und wohl für die Probleme verantwortlich ist) liegt, als auch der "richtige":
root@nas:~# ls -l /sbin/start*
-rwxr-xr-x 1 root root 94 Okt 7 21:34 /sbin/start-stop-daemon
-rwxr-xr-x 1 root root 32392 Mai 3 00:41 /sbin/start-stop-daemon.REAL
root@nas:~#
Und wenn ich jetzt den "fake" daemon beiseite schiebe und stattdessen einen Symlink auf den /sbin/start-stop-daemon.REAL setze, läuft auf einmal alles!
Hallo,
ich setze gerade ein OMV-System mit der aktuellen Beta 3.0.43 auf, und habe das Problem, daß fast kein Dienst regulär startet, weder nfs noch minidlna, noch smb.
Das Problem scheint daran zu liegen, daß der start-stop-daemon verwendet werden soll, der aber nur ein Dummy ist:
root@nas:/var/log# systemctl status smbd
* smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
Loaded: loaded (/etc/init.d/smbd)
Active: active (exited) since Sat 2016-10-08 22:18:02 CEST; 39min ago
Process: 1252 ExecStart=/etc/init.d/smbd start (code=exited, status=0/SUCCESS)
Oct 08 22:18:02 nas smbd[1252]: Starting SMB/CIFS daemon: smbd
Oct 08 22:18:02 nas smbd[1252]: Warning: Fake start-stop-daemon called, doing nothing.
Oct 08 22:18:02 nas smbd[1252]: .
und laut ps läuft auch kein smb.
Was kann ich tun?
Vielen Dank
Christoph