Posts by h3dkandi

  • Is there a guide to in place upgrade?

    I succeeded in restoring from backup and precoded with the release upgrade again


    Some hand picked errors during installation here.


    Should I be worried? Should I do something? Should I restore from backup and only think about migrating by full reinstall? :(
    Full terminal log


    Inside the browser UI I am greeted by message saying there are pending changes for :

    • apt
    • avahi
    • collectd
    • cron
    • hdparm
    • hostname
    • hosts
    • monit
    • nfs
    • nginx
    • postfix
    • proftpd
    • rsyncd
    • samba
    • smartmontools
    • systemd-logind
    • systemd-networkd
    • watchdog


    When I tired to apply them an errors occur - log copied from UI

  • Is there a guide to in place upgrade?

    What is you definition of "well"?


    I replaced couple of files that had 'conflicts' during install with the package owner version and not mine. More importantly it ended with errors:





    Should I continue with the fix5to6upgrade script?

  • Is there a guide to in place upgrade?

    I am in dire need of help.


    So.. I did hit ctrl-c mid sudo omv-release-upgrade:

    I wanted to copy a warning that poped up just in case I need it later :

    Code
    dpkg: warning: unable to delete old directory '/var/www/openmediavault/js/omv/util': Directory not empty
dpkg: warning: unable to delete old directory '/usr/lib/systemd/system-sleep': Directory not empty


    Stopping the update logs the following with a list of the affected packages after it:

    Code
    W: --force-yes is deprecated, use one of the options starting with --allow instead.
W: Operation was interrupted before it could finish
W: APT had planned for dpkg to do more than it reported back (628 vs 2759).

    How bad is it can I 'resume' it some how by rerunning the command or something?


    More log info


    Even if I can resume in some way would the update be guaranteed as if everything went ok the first try? Is it overall better to restoring my backup and then do a clean release upgrade?

  • CRON-APT error, not sure how to clear it

    I have the same error apt clean did not help. If i do apt update from CLI I have extra option to accept the change


    Quote

    E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'

    N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

    Do you want to accept these changes and continue updating from this repository? [y/N]


    Should I accept the change?

  • OMV Backup plugin w/ Borg method - can't restore

    Yup making a live system clone with borgupdates is too advanced for me. For some reason it doesn't work their documentation says this should be the command

    Code
    borg create --read-special repo::hostname-disk $DISK -e "/dev"

    Where $DISK is I suppose my physical device lets say /dev/sda . I did try /dev/sda1 which where / is mounted with similar result. I exclude at least /dev because documentation says we might get into infinite loop if we try to back up /dev/zero with --read-special.


    I will just stick to fsarchive for auto live back up. And from time to time I will make manual off-line back up using USBimager.


    PS.

    Quote from auanasgheps

    Borg/the plugin backs up the root file system, which you can specify if not detected automatically

    FYI I did check out the source code and omv-backup plugin with option borg has the root hard coded in it. It will always back up only / directory. It will not care even if someone manually sets root dir form the plugin web interface.

  • OMV Backup plugin w/ Borg method - can't restore

    Quote from auanasgheps

    Fsarchiver is great in this case because it is actually made to backup a file system to a compressed archive.

    Borg is designed for normal file backup


    Quote from crashtest

    For SD-cards, it's easier to simply clone them

    Well I will looking into that. I will test making a full disk image with borg. If it works it could be added as a back up option.


    BTW I did test fsarchiever and it works perfectly. I will use it if borg doesn't pin out. Thank you ryecoaaron for making it so easy to back up and restore.

  • OMV Backup plugin w/ Borg method - can't restore

    I am using omv on a rpie. The system is installed on a SD

    I decided to try out borg. Simulating a scenario where my SD card dies.

    My boot is a separate partition and it seems that borg doesn't back up those files. I was wondering if it is the same for you?

    Code
    borg list borgbackup/::backup-omv-08-Nov-2020_00-59-19 boot

    When I tried to list the files in the boot dir it shows no files. Don't I need them to restore my /boot?


    Seeing that you are running a VM I saw some info in borg documentation check it. Dunno how relevant that is.


    I will try fsarchiever and maybe use that.