- Pi 4 running Bookworm 6.12.25
- Crucial 250GB BX100 SSD (requires 2A power apparently) in ext USB 3.0 enclosure plugged into Tendak USB 3.0 Hub with 5V 3A power supply.
- SSD was imaged from a working Micro SD card using SD Card Copier. This failed a couple of times but eventually worked and resulting SSD partitions look fine and mount ok when booted from Micro SD card.
If I plug the hub into the USB 3 port and try to boot from it it hangs for several minutes at the Welcome splash screen, then a bunch of error messages re failures starting various services, mostly systemd stuff, are output and also:
EXT4-fs error (device sda2): ext4_wait_block_bitmap:582: comm ext4lazyinit: Cannot read block bitmap - block_group = 1392, block_bitmap = 45613056
EXT4-fs error (device sda2): ext4_read_inode_bitmap:201: comm systemd: Cannot read inode bitmap - block_group = 816, inode_bitmap = 26738704
.
.
EXT4-fs error (device sda2): Remounting filesystem read-only
At which point, after several failed boots, I gave up and tried booting with the hub plugged into the Pi's USB 2 port whereupon it came up perfectly and is working just fine.
I saw the post on UAS issues with USB 3.0, but these messages don't look anything like the ones described there. Could this be a UAS issue?
Oh yes, I've also tried the same drive with another unbranded USB 3 hub (using both the same and a different power brick) and another BX100 SSD in another ext case, all without success.
Has anyone seen this problem before or have any suggestions?
- Crucial 250GB BX100 SSD (requires 2A power apparently) in ext USB 3.0 enclosure plugged into Tendak USB 3.0 Hub with 5V 3A power supply.
- SSD was imaged from a working Micro SD card using SD Card Copier. This failed a couple of times but eventually worked and resulting SSD partitions look fine and mount ok when booted from Micro SD card.
If I plug the hub into the USB 3 port and try to boot from it it hangs for several minutes at the Welcome splash screen, then a bunch of error messages re failures starting various services, mostly systemd stuff, are output and also:
EXT4-fs error (device sda2): ext4_wait_block_bitmap:582: comm ext4lazyinit: Cannot read block bitmap - block_group = 1392, block_bitmap = 45613056
EXT4-fs error (device sda2): ext4_read_inode_bitmap:201: comm systemd: Cannot read inode bitmap - block_group = 816, inode_bitmap = 26738704
.
.
EXT4-fs error (device sda2): Remounting filesystem read-only
At which point, after several failed boots, I gave up and tried booting with the hub plugged into the Pi's USB 2 port whereupon it came up perfectly and is working just fine.
I saw the post on UAS issues with USB 3.0, but these messages don't look anything like the ones described there. Could this be a UAS issue?
Oh yes, I've also tried the same drive with another unbranded USB 3 hub (using both the same and a different power brick) and another BX100 SSD in another ext case, all without success.
Has anyone seen this problem before or have any suggestions?
Statistics: Posted by dshan — Tue Jun 17, 2025 3:39 am