Firstly, thank you for the ongoing support for the RV2.
I'm encountering an issue with the top M.2 slot. While I can boot from it, as soon as the prompt appears, an ext4 error is thrown, the root filesystem is mounted read-only, and the system fails to complete the login process.
Interestingly, when I move the same disk to the bottom M.2 slot, everything works perfectly.
To further investigate, I wiped the NVMe drive, created an empty ext4 partition, and booted from an SD card.
Here are the results:
Bottom Slot (Works as expected):
The disk can be mounted and used without issues.
Passes multiple `fio` write and read tests.
Top Slot (Fails to mount):
Unable to mount the disk:
root@orangepirv2:~# mount /dev/nvme0n1p1 /mnt/test
mount: /mnt/test: can't read superblock on /dev/nvme0n1p1.
dmesg(1) may have more information after failed mount system call.
I've checked the dmesg logs, and the only noticeable difference is that when the disk is in the bottom slot (and working), there are more Bluetooth-related lines. Does this indicate that the lines for that slot are used by multiple systems, or am I on the wrong track?
Here are the relevant dmesg logs for both scenarios:
Booting from SD, NVMe disk in top M.2 slot:
Booting from SD, NVMe disk in bottom M.2 slot:
Any insights or suggestions would be greatly appreciated.
