-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
No UUID updated in /boot/cmdline.txt & /etc/fstab #751
Comments
You use an old release of raspiBackup. Current release is 0.6.9.1 😉 Maybe an update makes sense 😄 Anyhow: Would you please provide the debug log of the restore? |
Debug log: 20240423_raspiBackup.log Regarding raspiBackup release: had no restore problems in the past with the current setup - but sure, if the new USB device is the root cause I would try the new release. I've avoided so far because I think I have to reconfigure some raspiBackup.conf parameters. |
That's the contents of /etc/fstab in the backup:
As you can see there is no UUID used but the old deprecated /dev/sd way used in Jessie. So there is no way to update the UUIDs because there don't exist any 😉 Just ignore the warning.
Any raspiBackup upgrade doesn't modify any configuration options. New options will be added but that's it. |
Thank you for checking my log and your advice.
I will promptly upgrade. |
Fix merged into master and published |
Using a fully new 32 GB USB 3.2 stick to restore from NAS to Raspberry 3 (/dev/sdb2) I got following error message:
Unfortunately with sudo blkid following output:
=> sdb is the restore USB storage - I have no info about PARTUUID to manually adapt /boot/cmdline.txt and /etc/fstab.
Any ideas?
Environment:
Raspberry with raspbian 8 (jessie)
raspiBackup.sh V0.6.6
no changes of version (OS, raspiBackup) since last successful restore.
The text was updated successfully, but these errors were encountered: