Hi
With Imager I imaged (to recommanded default Trixie arm64) a 500GB SSD that I plugged in a free sata port of my desktop. Previously this SSD hosted buster partitions boot, rootfs, home and swap. I think boot was not user as another boot partition was on a 8G SDCard.
At the time of imaging I left the sdcard in the desktop computer thinking Imager would ask something about it but it didn't.
So I plugged the SSD in my USB adapter to the Pi but I get a boot loop roughly each 1/4h. In between I have the "Welcome to the Raspberry Pi Desktop" splash screen. On very first boot I had these errors:Before that the Pi was booting fine but I could not upgrade to Trixie and I was highly discouraged to try any in place upgrade. The documentation says the Pi can boot from USB. When I first installed raspbian Buster, a SDCard was required. So I did not plugged back the card in the reader.
Also I remember in my first times with Raspbian I had to add a ~quirk~ to have the SSD to boot at decent speed, maybe in some file in the SDCard and perhaps also say some PARTUUID partition label to point to rootfs in the SSD probably.
A new partition is called bootfs instead of boot previously.
So please now what should I do ? Is Pi4B compatible with Trixie and Imager?
Thank you
With Imager I imaged (to recommanded default Trixie arm64) a 500GB SSD that I plugged in a free sata port of my desktop. Previously this SSD hosted buster partitions boot, rootfs, home and swap. I think boot was not user as another boot partition was on a 8G SDCard.
At the time of imaging I left the sdcard in the desktop computer thinking Imager would ask something about it but it didn't.
So I plugged the SSD in my USB adapter to the Pi but I get a boot loop roughly each 1/4h. In between I have the "Welcome to the Raspberry Pi Desktop" splash screen. On very first boot I had these errors:
Code:
pci_bus 0000:01: supply vpcie3v3 not found, using dummy regulatorpci_bus 0000:01: supply vpcie3v3aux not found, using dummy regulatorpci_bus 0000:01: supply vpcie12v not found, using dummy regulatorsd 0:0:0:0 [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)[ 130.305707] I/O error, dev sda, sector 1065088 op Ox0:(READ) flags 0x80700 phys_seq 1 prio class 2[ 130.305882] I/O error, dev sda, sector 17408 op Ox0:(READ) flags 0x80700 phys_seq 1 prio class 2I/O error, dev sda, sector 1065088 op Ox0:(READ) flags 0x80700 phys_seq 1 prio class 2I/O error, dev sda, sector 17408 op Ox0:(READ) flags 0x80700 phys_seq 1 prio class 2[ 161.146083] I/O error, dev sda, sector 1065088 op Ox0:(READ) flags 0x80700 phys_seq 27 prio class 2[ 161.146245] I/O error, dev sda, sector 12598304 op Ox0:(READ) flags 0x80700 phys_seq 28 prio class 2I/O error, dev sda, sector 1065088 op Ox0:(READ) flags 0x80700 phys_seq 27 prio class 2I/O error, dev sda, sector 12598304 op Ox0:(READ) flags 0x80700 phys_seq 28 prio class 2Timed out while waiting for udev queue to empty.[ 202.513709] I/O error, dev sda, sector 1064960 op Ox0:(READ) flags 0x80700 phys_seq 1 prio class 2I/O error, dev sda, sector 1064960 op Ox0:(READ) flags 0x80700 phys_seq 1 prio class 2e2fsck 1.47.2 (1-jan-2025)rootfs: clean 130407/360448 files, 1269154/1441792 blocks_Also I remember in my first times with Raspbian I had to add a ~quirk~ to have the SSD to boot at decent speed, maybe in some file in the SDCard and perhaps also say some PARTUUID partition label to point to rootfs in the SSD probably.
A new partition is called bootfs instead of boot previously.
So please now what should I do ? Is Pi4B compatible with Trixie and Imager?
Thank you
Statistics: Posted by SyncBerry — Sat Jan 24, 2026 8:46 pm