Issues with NAS and Rescuezilla Version 2.0

[Anonymous]

Hi there,

first of all I seriously wanna thank you for that amazing piece of Software.

I got issues with the newest Version of Rescuezilla setting a correct path for my NAS on my Fritzbox 6591 (using Linux Mint 20). I sucessfully managed to create an Image with the previous version before, but under Version 2.0 Rescuezilla simply wont accept the path to the location that worked perfectly with the previous version. I can exclude that there are any faults from my side, I tried it with the exact same path, Username and Password that worked in the previous version and I also tried many other ways, but it simply fails all the time, telling me something about fstab.

Are there any possibilities to make it work in that version or circumstances that I have to take into account?

Thank you very much and greetings from Germany!

[Rescuezilla]

Hi Anonymous,

What is the error message?

Some network shares may not support the default SMB 3.1.1 protocol that is now default in Rescuezilla v2.0. For such network shares you may need to enter '2.1' or even '1.0' in the version field.

Rescuezilla v2.0 was a full rewrite from scratch. I have tested connecting to a Linux-based SMB/CIFS network share and didn't have any issues, but I am sure there could be legitimate SMB/CIFS authentication combinations which Rescuezilla v2.0 might not be handling correctly.

I recommend making sure the fields have the correct UNC path (eg "\\fileserver\johnsmith") and username/password. Since you're connecting to a Linux-based NAS, it is often worth switching all backslashes in the UNC path to forward slashes, as a quick check if any backslashes are being incorrectly interpreted by the client or server as an escape character.

[Anonymous]

Hi Rescuezilla,

thank you very much for your quick reply.

I apologize for not mentioning the error message of Rescuezilla 2.0 in the first posting. I filled all the fields that worked with the previous Version of 2.0 (my path is \MY-ROUTER-IP\fritzbox), I filled my Username and Password, set the Domain to WORKGROUP and also set the right Version (my Fritzbox still only supports Version 1.0). But I also tried to set the Version to 2.1 and left the Version field blank.

MY-ROUTER-IP in the path is a placeholder here for my real Router IP.

The error-message I receive is the following:

Failed to run command: mount.cifs \\MY-ROUTER-IP\fritzbox /mnt/backup -o 
credentials=/tmp/tmpvisf9wusversion=1.0
error 2 (No such file or directory) opening credential file /tmp/-
tmpvisf9wusversion=1.0
If the device is shared on a network, make sure that the username and password are correct. Then try again!

(Edit by Rescuezilla: Fix the quoting of the message above so that the double backslash correctly renders)

I can assure that my username and password are absolutely correct, it works fine for the previous version of Rescuezilla too!I also tried switching the backlashes in the UNC path to forward slashes with the same result.

I also re-checked the situation in the previous Version of Rescuezilla 2.0 and it works all fine there with the path \MY-ROUTER-IP\fritzbox my Username and Password, the Domain and Version 1.0. After setting that, Rescuezilla leads me to a next window then where I am able to select the directory to save the image.

Its not a big deal if a solution for me cant be found here cause I got the older version of Rescuezilla and creating Backups there just works fine, but it is strange to me somehow.

[Rescuezilla]

What version of Rescuezilla worked fine for you? Because v1.0.6/v1.0.6.1 64-bit are based on Ubuntu 20.04 just like Rescuezilla v2.0.

If you were running any of the Rescuezilla 32-bit builds then you were using a version based on Ubuntu 18.04 which has an older version of the SMB/CIFS client called cifs-utils which could exhibit different behavior.

By the way, I am not sure the reason for the "visf9wus" characters. It might be worth confirming the behavior when Rescuezilla has booted into the English language.

Its not a big deal if a solution for me cant be found here cause I got the older version of Rescuezilla and creating Backups there just works fine, but it is strange to me somehow.

Your issue may affect other people. I'm happy to investigate the issue for as long as it takes. I definitely want to understand and resolve the issues when users prefer an older version of Rescuezilla.

[Anonymous]

Hi Rescuezilla,

Version 1.0.6.1 works perfectly fine for me.

And both versions are on 64-bit. I dont know if this could be problematic, but I put Rescuezilla 2.0 in Ventoy alongside some other Linux Distros, that is a tool to create Multi-Boot USB Sticks. Version 1.0.6.1 is completely alone on another USB-Stick. I think my next step will be to download Version 2.0 again and install it also alone on an USB-Stick and retry it that way, just to make sure that this is not a problem caused by Ventoy.

I will also retry it in English Language and will keep you updated here in that direction.

[Rescuezilla]

OHHHH. I see the error now: "error 2 (No such file or directory) opening credential file".

It's literally running the command mount.cifs \\MY-ROUTER-IP\fritzbox /mnt/backup -o credentials=/tmp/tmpvisf9wusversion=1.0

The credentials file should have a comma. This is a bug in Rescuezilla v2.0 (which was a complete rewrite in a new programming language).

Sorry about that, I will fix it for Rescuezilla v2.1: https://github.com/rescuezilla/rescuezilla/issues/140

Thanks for the report!

[Rescuezilla]

The ability to specify the version field for SMB/CIFS network share folders has been fixed in Rescuezilla v2.1.

[Anonymous]

Hi Rescuezilla,

first of all sorry for my late reply.

I`m happy to report that I tested Version 2.1 now and everything works like a charm again - thank you so much for fixing that! :-)

I`d also like to express a great Thank you for that awesome piece of Software - as a learning Linux-User who completely switched from Windows a couple of months ago, your Software was the very first I was able to create a Backup with without any major Error-Messages and I got a good feeling in case of an emergency. :-)

I also noticed the possibility to support the project over Patreon and I` planning to make an adjustment shortly. ;-)

Thank you very much for your kind assistance, have the best possible Christmas and New Year 2021 under these difficult global circumstances and please: Stay healthy!

Best regards from Germany! :-)

[Rescuezilla]

Thanks for the kind words! I'm glad specifying the version field of SMB/CIFS network share folders now works again!

The real test of any backup software is its ability to successfully and reliably restore the images. I've tried to test everything as much as I can (very time consuming) but I am still always worried I've missed something. I am planning on automating the testing in the future. Side note: I'm also a bit worried that I didn't make clear enough how limited the new "Image Explorer" beta functionality currently is.

I have done more work on Rescuezilla in the past few months than I planned to, so I am hoping to go back to my previous 4-6 month release cycle and not make any new releases until *after April 2021*. I won't offended if any Patreon supporters decide to lower their contribution tier (or cancel their pledge entirely) given the expected gap before next release.

Stay safe! Let me know if you have any issues!