Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8082

Troubleshooting • Re: RPi5 seems to be ignoring my boot order.

$
0
0
Alright, here is the blkid output

Code:

/dev/mmcblk0p2: LABEL="SHARE" UUID="2a464d79-2e8d-44e7-8701-5343950e124e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="36ebfde2-02"/dev/mmcblk0p1: LABEL_FATBOOT="BATOCERA" LABEL="BATOCERA" UUID="1A46-E361" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="36ebfde2-01"/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"/dev/sda2: LABEL="SHARE" UUID="4671822f-7cef-4a1a-a523-d8bfb76ccc11" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="7dd54b41-02"/dev/sda1: LABEL_FATBOOT="BATOCERA" LABEL="BATOCERA" UUID="1A46-E361" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="7dd54b41-01"
Both boot partitions have the same label, as do both root partitions. If you're using the label for the boot that will confuse matters.

Also, in your cmdline.txt you've got

Code:

dev=LABEL=BATOCERA
I don't recognise that "dev=" directive. The usual option is to specify the root (not boot) partition with "root=" and Raspberry Pi OS usually uses "root=PARTUUID=xxxxxxxx=02".

In your case, as the root partition isn't being specified, I can only guess that your system is using some default value, maybe "/dev/mmcblk0p2" which would be the SD card.

I suggest changing the cmdline.txt in your HDD boot partition to

Code:

console=tty3 loglevel=3 elevator=deadline vt.global_cursor_default=0 logo.nologo root=PARTUUID=7dd54b41-02 rootwait fastboot noswap
and the one on your SD card to

Code:

console=tty3 loglevel=3 elevator=deadline vt.global_cursor_default=0 logo.nologo root=PARTUUID=36ebfde2-02 rootwait fastboot noswap
The /etc/fstab file on each device may need updating as well, but this should sort the device used for the boot.

Statistics: Posted by rpdom — Wed Feb 19, 2025 7:53 am



Viewing all articles
Browse latest Browse all 8082

Trending Articles