New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arch recover failure from cifs share #1070
Comments
@danboid |
Hi Vlad! Glad you like the screenshots! :) I'll try that ifconfig command when I get home. I only tried booting the recovery USB and restoring twice but bringing up the network must've failed on both attempts because both auto and manual recovery failed. If the ifconfig command fixes recover, could some code be added to rear somewhere to make bringing up NICs more reliable under Arch? Activating interfaces seems to work OK for Ubuntu. |
Note that during development I had renamed In general see |
Woohoo! I just did my first successful rear recovery and it was Arch on XFS via Samba using the above config. All I had to do was boot the recovery USB in manual recovery mode then run:
I'd like to change this bug report into a feature request / suggestion. There should be no need for me to have to add |
Congrats @danboid to your successful restore!
So maybe try to set USE_DHCLIENT=yes in your /etc/rear/local.conf |
Or |
Hi Vlad I knew there was at least one way to activate DHCP in local.conf but why is it that Ubuntu MATE's auto-restore worked (I was assigned an address) whilst with Arch I had to run dhcp manually? With both OSs I was using DHCP before running I can be certain its not a case of missing software from the recovery disk now. Maybe Ubuntu defaults to USE_DHCLIENT=yes whilst Arch defaults to USE_DHCLIENT=no? |
Might as well close this now. I may open another ticket if there is irregular DHCP behaviour going on when recovering different distros. |
@danboid What I use on my SUSE systems is (in local.conf) SSH_ROOT_PASSWORD="rear" USE_DHCLIENT="yes" which makes network setup via DHCP plus When things in ReaR do not work o.k. for you with If you like to adapt and enhance Relax-and-Recover |
I thought I should give a quick update to say that I gave rear another go with Arch last night using the following local.conf:
Thanks to using I'd like to see my commented config added as an example that comes included with the rear sources because none of the included examples use USB for the recovery device or a samba share as the backup target. I would call the file USB-and-samba-example.conf I should've mentioned it before but the rear man page recommends using a credentials file for using samba shares but I failed to get that to work, hence why I had to give the username and password in the backup options. |
@danboid if you want to add your config to ReaR upstream, easiest way (IMHO) is to create pull request ... |
I tidied up my config a bit, made it more generic, improved the comments and submitted a pull request. |
@danboid Where is the related pull request? (which issue number?) |
@ProBackup-nl |
OUTPUT=USB
USB_DEVICE=/dev/sdb1
BACKUP=NETFS
BACKUP_URL=cifs://192.168.1.4/sys
BACKUP_OPTIONS="username=dan,pass=xxxxxxxxxxxx"
I have Arch x86_64 installed onto a single XFS partition on sda1. I installed rear git from the AUR:
https://aur.archlinux.org/packages/relax-and-recover-git/
Installation went fine but I noticed the rear PKGBUILD doesn't have samba as a dep so I also installed samba as I want to backup and restore to/from a cifs share so I presumed samba would be required. The rear format, mkrescue and mkbackuponly commands all seemed to work fine under Arch so after backing up I formatted my HD.
My recovery USB stick booted OK but when it came to recovery, rear failed using both the manual and auto recovery modes as it seemed to be unable to mount the samba share. Note that this is exactly the same samba share that I managed to recover (mostly) Ubuntu MATE from last week. I have attached screenshots of the errors.
Although I've not properly investigated this yet nor do I really have anything to back up my hypothesis, I suspect this mount error will be caused because either samba isn't being installed onto the recovery USB drive or it isn't getting started successfully in time for the mount command but I'm just guessing.
The text was updated successfully, but these errors were encountered: