after upgrading omv-backup plugin to 6.05 the hdd does not spindown anymore. Workaround is a reboot after completing backup.
Also selected borgbackup seems not to be executed anymore
after upgrading omv-backup plugin to 6.05 the hdd does not spindown anymore. Workaround is a reboot after completing backup.
Also selected borgbackup seems not to be executed anymore
after upgrading omv-backup plugin to 6.05 the hdd does not spindown anymore.
I'm not sure why the backup plugin would affect hdd spindown. All it does is run a script unless that script is never finishing or not not finishing in the timeframe you expect.
Also selected borgbackup seems not to be executed anymore
Not sure what that means but you aren't giving any info that can help diagnose the problem.
after upgrading omv-backup plugin to 6.05 the hdd does not spindown anymore. Workaround is a reboot after completing backup. Also selected borgbackup seems not to be executed anymore
I'm not sure why the backup plugin would affect hdd spindown. All it does is run a script unless that script is never finishing or not not finishing in the timeframe you expect.
Not sure what that means but you aren't giving any info that can help diagnose the problem.
I've searched the log, but did not find anything relevant. After restoring the 6.04 version of the backup-script the selected borgbackup is executed again and the hdd also spins down again. So there must be a Problem with the 6.05 version. The reason my be, that the backup-script does not finish, but i have no idea how to create some debug-log
i have no idea how to create some debug-log
sudo /usr/sbin/omv-backup
because I have an armbian system my boot-partition is on sdcard, the root partition is on an 1TB SSD with gpt. with omv-backup 6.0.5 an dd of EFI is created. It seems to be, that in my case the backup-script trys to make a dd of the whole SSD (1TB). Thereofore it does not come to an end in an adequate time.
Are you sure the plugin is the problem?
Have you followed my guide to use the new hd-idle rewrite?
I am still running the backup plugin 6.0.4 , yet I have the same issue, but it's caused by hd-idle getting stuck after resuming the system from standby.
I have a WD-Red hdd. this hdd seem to have a problem with hdparm. Therefore I have disabled hdparm and I use hd-idle.
because I have an armbian system my boot-partition is on sdcard, the root partition is on an 1TB SSD with gpt. with omv-backup 6.0.5 an dd of EFI is created. It seems to be, that in my case the backup-script trys to make a dd of the whole SSD (1TB). Thereofore it does not come to an end in an adequate time.
The backup plugin probably won't work on your system. It assume the OS stuff is on the same disk and would look for an esp partition on your SSD because it has a gpt partition table. It would be a pain to support this because it is effectively multiple root devices. Not sure if I want to do that.
The backup plugin probably won't work on your system. It assume the OS stuff is on the same disk and would look for an esp partition on your SSD because it has a gpt partition table. It would be a pain to support this because it is effectively multiple root devices. Not sure if I want to do that.
A couple of quick and dirty fixes:
- ignore the boot partition if boot and system partitions are not on the same drive
- option to disable the EFI/boot partition backup
- ignore the boot partition if boot and system partitions are not on the same drive
The boot partition is very important on arm systems though.
option to disable the EFI/boot partition backup
That would be confusing. People already ask how to use the plugin and the only real setting is backup type. I need to rewrite the plugin to handle these non-standard installs and it complicates using the plugin.
The boot partition is very important on arm systems though.
That would be confusing. People already ask how to use the plugin and the only real setting is backup type. I need to rewrite the plugin to handle these non-standard installs and it complicates using the plugin.
I feel guilty because I am the one who asked for the EFI backup...
Maybe the plugin could scan all disks and backup the partition with the boot flag and formatted FAT32?
Maybe the plugin could scan all disks and backup the partition with the boot flag and formatted FAT32?
Easier said than done. What if there are two?
A couple of quick and dirty fixes:
- ignore the boot partition if boot and system partitions are not on the same drive
- option to disable the EFI/boot partition backup
an option to disable EFI/boot partition backup is perfectly OK for me
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!