Skip to content

cmdline.txt failing to get updated UUID #187

@fjmartin1966

Description

@fjmartin1966

I'm running a couple of Pi 5's with the Debian 12. Install is very new and all packages are up to date. After cloning the cloned MicroSD Card would not boot. Mounting the drive and examining them with blkid of sda and a cat of fstab and cmdline.txt on the mounted drives showed that cmdline.txt was not getting updated correctly with the newly assigned drive UUIDs. Examination of the rpi-clone script showed that the script was attempting to update /boot/cmdline.txt but that is deprecated and the location is now /boot/firmware/cmdline.txt. I updated the script on my Pis and it is now properly updating cmdline.txt and the cloned drives now boot. I'm guessing the script will need to add a check for either release version to determine the path for older vs newer deployments. Either that or if the older releases do not have a /boot/firmware directory then a decision could be make in the script whether to use /boot/cmdline.txt and .boot or /boot/firmware/cmdline.txt and .boot

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://allstarlink.org"
SUPPORT_URL="https://community.allstarlink.org"
BUG_REPORT_URL="https://github.com/AllStarLink/asl3-pi-appliance/"
VARIANT="AllStarLink System Manager"
VARIANT_ID="AllStarLink"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions