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
2.5 Can't Mount CIFS #2170
Comments
don't mind the "/root/.cifs" versus "/root/cifs" that was just a typom in creating this ticket, that type doesn't exist within the configuration. Not sure if this is a recovery iso issue, but when I enter mount.cifs : command not found |
I don't use CIFS but "man rear" reads
In general during "rear mkrescue/mkbackup" what is specific Therefore in general it does not work to do "rear mkrescue/mkbackup" Cf. the documentation about "Using Multiple Backups for Relax-and-Recover" at To verify in advance that all what you need to use CIFS during "rear recover" Then One thing that you cannot test with E.g. CIFS needs the
plus some more modules like on my openSUSE Leap 15.0 system:
Fortunately since ReaR 2.5 by default all kernel modules Nevertheless a real "rear recover" verification is still mandatory in any case, |
@chumunga check you rear log file when you run mkbackup to see whether mount.cifs is copied to the rescue image (as it was apparently missing in the recover phase) |
I checked the logs and this was the only trace of cifs,
This was after i add this parameter to the local.conf MODULES=( 'all_modules' ) however in my recovery environment mount.cifs still doesn't show but when i run mount -t cifs -o username=username,password=pass,vers=(1.0, 2.0,3.0) I get a new error message saying the mount is read only and fails to mount. @jsmeix I think I am understanding what your saying, are you implying that the backup location (or backup parameters) determines how my options to how I can recover or what I can do in the recovery options? |
@chumunga
Cf. the section "Fully compatible replacement hardware is needed" in |
sorry been on PTO, thanks for the update. I eventually got this to work by installed 2.4 and RPM-ing the files from centos 7 32bit repository at centos.org |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
2.5-git.0.0.unknwon / 2019-06-21
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
SHMZ release 6.5 Final (i386)
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=ISO
BACKUP=NETFS
BACKUP_PROG=tar
BACKUP_TYPE=incremental
FULLBACKUPDAY="Sat"
FULLBACKUP_OUTDATED_DAYS=5
BACKUP_INTEGRITY_CHECK=1
BACKUP_PROG_CRYPT_ENABLED=1
BACKUP_PROG_CRYPT_KEY=passwordhere
BACKUP_PROG_CRYPT_OPTIONS="/usr/bin/openssl aes-256-cbc -salt -k"
BACKUP_PROG_DECRYPT_OPTIONS="/usr/bin/openssl aes-256-cbc -d -k"
#--- Backup Destination
BACKUP_URL="file:///mnt/S3online"
BACKUP_PROG_EXCLUDE=( '/mnt/S3online/*')
#--- Local Recovery
#BACKUP_URL=192.168.1.100
#BACKUP_OPTIONS="credentials=/root/cifs,vers=1.0"
Horever, for recovery I transfer the file to a network share hence the commented out options at the bottom, i just switch those on and off.
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
PC
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
32
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
BIOS
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
local
Description of the issue (ideally so that others can reproduce it):
When I try run recovery I get mount fail "mount: fs type, bad option, bad supereblock"
in dmesg I get CIFS VFS: No username specified.
I have cifs-utils-4.8.1-19.e16.i686 installed.
I try mounted with just the mount command by it self such as
mount -t cifs -o credentials=/root/cifs,vers=1.0 //192.168.1.100 /mnt/test
i've tried different variation without vers or different vers like 2.0,3.0. Same issue, I am suspecting maybe this is an issue with the recovery disk itself? However I do use 192.168.1.100 file server on my other systems running ReaR version 2.4 without issues.
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
The text was updated successfully, but these errors were encountered: