Skip to content
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

Closed
andyzle opened this issue Apr 23, 2024 · 5 comments
Closed

No UUID updated in /boot/cmdline.txt & /etc/fstab #751

andyzle opened this issue Apr 23, 2024 · 5 comments
Assignees
Labels
question Some question about raspiBackup

Comments

@andyzle
Copy link

andyzle commented Apr 23, 2024

Using a fully new 32 GB USB 3.2 stick to restore from NAS to Raspberry 3 (/dev/sdb2) I got following error message:

--- RBK0184I: Rootpartitionscheck gestartet.
!!! RBK0208W: Es konnte keine UUID in /boot/cmdline.txt für root= erneuert werden. Das Backup könnte nicht starten.
!!! RBK0208W: Es konnte keine UUID in /etc/fstab für / erneuert werden. Das Backup könnte nicht starten.
!!! RBK0208W: Es konnte keine UUID in /etc/fstab für /boot erneuert werden. Das Backup könnte nicht starten.

Unfortunately with sudo blkid following output:

/dev/sda1: LABEL="BOOT" UUID="74C7-F23F" TYPE="vfat" PARTUUID="479560c9-01"
/dev/sda2: UUID="756282ab-fa72-42b4-89c6-68520dd02704" TYPE="ext4" PARTUUID="479560c9-02"
/dev/sdb1: LABEL="BOOT" UUID="74C7-F23F" TYPE="vfat"
/dev/sdb2: UUID="9504312d-fbe4-4944-9db6-8b546e3adda3" TYPE="ext4"

=> 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.

@framps
Copy link
Owner

framps commented Apr 23, 2024

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?

@andyzle
Copy link
Author

andyzle commented Apr 24, 2024

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.

@framps
Copy link
Owner

framps commented Apr 24, 2024

That's the contents of /etc/fstab in the backup:

20240423-180210 DBG 6959:              --- proc            /proc           proc    defaults          0       0
20240423-180210 DBG 6959:              --- /dev/sda1  /boot           vfat    defaults          0       2
20240423-180210 DBG 6959:              --- /dev/sda2  /               ext4    defaults,noatime  0       1

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.

I've avoided so far because I think I have to reconfigure some raspiBackup.conf parameters.

Any raspiBackup upgrade doesn't modify any configuration options. New options will be added but that's it.
If for some reasons you have to look up the old config options: You have a backup with the old raspiBackup release and there you will have all options before you upgraded 😉

@andyzle
Copy link
Author

andyzle commented Apr 25, 2024

Just ignore the warning.

Thank you for checking my log and your advice.

Any raspiBackup upgrade doesn't modify any configuration options.

I will promptly upgrade.

@framps framps self-assigned this Apr 25, 2024
@framps framps added the question Some question about raspiBackup label Apr 25, 2024
@andyzle andyzle closed this as completed Apr 25, 2024
@framps
Copy link
Owner

framps commented Apr 27, 2024

Fix merged into master and published

framps added a commit that referenced this issue Apr 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Some question about raspiBackup
Projects
None yet
Development

No branches or pull requests

2 participants