Posts by chudak

    ryecoaaron

    I actually was able on the second try to successful restore the system

    Steps:

    - run Backup plugin

    - gzip -d backup-omv-30-Jun-2020_14-57-39.ddfull.gz

    - sudo pishrink.sh -v backup-omv-30-Jun-2020_14-57-39.ddfull.img backup-omv-30-Jun-2020_14-57-39.ddfull-shrunk.img

    - used Etcher to restore shrunk file


    But had the same thought you described "Since you are backing a live OS, it is possible that some things may not be perfect"


    How do you do manage that with crontab dd ? Do you stop services and then run dd?

    Please share script if possible.

    gderf

    So I took output of dd backup file backup-omv-26-Jun-2020_12-07-45.ddful (~65GB) as was produced by the BackUp plugin (option dd full disk - use dd to clone the entire drive to a compressed image file.)


    Used pishrink https://github.com/Drewsif/PiShrink and shrunk it to size 3.5GB and used Etcher to burn on to the SD card.

    While in general I was able to boot up and log into OMV, I saw SMB and DLNA services as red.

    So assuming it did not quite work as expected.


    Question - is the dd full back up suppose to and was tested to restore fully operational backups ?


    Or I am missing something here.

    I have two drives on my network

    One connected to my Ubuntu server and another to the newly built OMV R Pi NAS 3tb and 5tb.


    I am considering to connect both drives to the OMV NAS and looking for practical pros and cons.


    Thx in advance !!

    Got a new SD card, installed a fresh R OS/OMV and restore the files by comparing.


    1. in ./openmediavault/config.xml

    removed all <interfaces> section that related to wifi/wlan0

    added instead `eth0`


    2. in ./collectd/collectd.conf.d/interface.conf

    removed `wlan0` line


    3. in ./netplan/ dir, removed 30-openmediavault-wlan0.yaml file and replaced with 20-openmediavault-eth0.yaml


    R Pi - boots up and all seems to be OK, except OMV on login throws error


    Error #0:

    OMV\Rpc\Exception: Failed to connect to socket: Connection refused in /usr/share/php/openmediavault/rpc/rpc.inc:141

    Stack trace:

    #0 /var/www/openmediavault/rpc/session.inc(56): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)

    #1 [internal function]: OMVRpcServiceSession->login(Array, Array)

    #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)

    #4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)

    #5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()

    #6 {main}


    And fixed some errors in XML formatting etc. omg ! OMV :)

    I got a warning email from my OMV :


    "The following users are locked/banned or are candidates for too many failed login attempts:
    Login Failures Latest failure From
    root 1 06/26/20 09:05:28 unknown
    You can reset their counters and unlock them via the omv-firstaid command." and was playing with ``


    and was playing with `omv-firstaid` and tried modify WiFi network setting and I think unintentionally made my R Pi unable to connect via Ethernet wire ;(


    I don't have an access to the console but can made modification to the file system by removing a SD card and inserting it to Ubuntu box.


    Can someone point me n what file and what changes must be done ?

    I suspect it's in `/etc/openmediavault/config.xml`


    I see latest modified files as :


    sudo find . -printf '%T+ %p\n' | sort -r | head

    2020-06-27+09:07:40.8181073420 ./dhcp

    2020-06-27+09:04:50.5133100770 ./network

    2020-06-27+08:45:08.4235809220 ./openmediavault

    2020-06-27+08:11:31.7970906700 ./netplan/30-openmediavault-wlan0.yaml

    2020-06-27+08:11:31.7970906700 ./netplan

    2020-06-27+08:11:31.7370918730 ./netplan/10-openmediavault-default.yaml

    2020-06-27+08:11:01.9376890610 ./hosts

    2020-06-27+08:10:43.4480595990 ./collectd/collectd.conf.d/interface.conf

    2020-06-27+08:10:43.4480595990 ./collectd/collectd.conf.d

    2020-06-27+08:10:38.6981547890 ./openmediavault/config.xml




    Thanks in advance!

    As I have said before and elsewhere, making the backup is the easy part. The harder part is performing the restore and what most users seem to be be looking for are instructions for that part.


    But of course, those who have no experience in the shell are going to be at a huge disadvantage, and the forum might get bogged down with Introduction to Linux 101 questions.


    OBTW, the restore can be done without using the shell. It's just a few mouse clicks in Linux Mint (or any of the other distros, even the Live CD ones) to decompress a compressed image file (if needed) and write it out to an attached disk that will become the replacement OMV system disk.


    I get it. I am looking for what other people are using and open for any successful details to try out and document findings afterwards.