Hi Thagrol,
No, all are standard RPi OS kernels, with correct checksum after the download.
After doing a cross-check, by
- putting the SD-card with the 6.6.42-v8-16k+ image from the faulty RPi 5 into another RPi 4 mounting of the portable SSD was no problem,
- putting a SD-card with an updated bookworm RPi OS (kernel image 6.6.31+rpt-rpi-v8) from a working and mounting RPi 4 into this RPi 5 resulted in the same mounting error with this portable SSD.
Though, my conclusion for the moment would be a hardware failure of this RPi 5, but other mountings, like USB-stick or USB-HDD ext4 formatted on this RPi 5 went all well.
Ok, scsi host0 with the stick is: usb-storage 3-1:1.0, were as with the HDD it is again: uas, as with the portable SSD.
Is there a different hardware requirement for an attached ext4 filesystem in regard to an f2fs filesystem on the same USB 3 port?
No, all are standard RPi OS kernels, with correct checksum after the download.
After doing a cross-check, by
- putting the SD-card with the 6.6.42-v8-16k+ image from the faulty RPi 5 into another RPi 4 mounting of the portable SSD was no problem,
- putting a SD-card with an updated bookworm RPi OS (kernel image 6.6.31+rpt-rpi-v8) from a working and mounting RPi 4 into this RPi 5 resulted in the same mounting error with this portable SSD.
Though, my conclusion for the moment would be a hardware failure of this RPi 5, but other mountings, like USB-stick or USB-HDD ext4 formatted on this RPi 5 went all well.
Ok, scsi host0 with the stick is: usb-storage 3-1:1.0, were as with the HDD it is again: uas, as with the portable SSD.
Is there a different hardware requirement for an attached ext4 filesystem in regard to an f2fs filesystem on the same USB 3 port?
Statistics: Posted by accfR — Sat Aug 10, 2024 8:07 pm