Hi! I’m a long-time Arch user and… already tired of getting it work on RPi 5b without any issues. That’s why i moved to Manjaro at first but… it’s not that good at all. Decided to try EOS and yup, that’s it. I’m getting older and lazy Simplicity is more than welcome and i’ve found it on EOS.
Installed it without issues on my 128 GB Samsung SDcard. Decided to give it a try and install on NVMe thanks to Waveshare HAT and… bang! It doesn’t boot due to “htree_dirblock_to_tree error reading directory block”. Other words… NVMe disk is down.
I can recover it by whiping all partitions. It’s not broken (checked). It’s almost new (checked). Manjaro ARM and PiOS works (checked).
Ps. Are there any openbox/labwc users? If so… i’m home
The official power supply (27 Watts) will power the RPi 5 itself. But to allow head room for extra USB loads, etc. I recommend the Canakit 45 Watt power supply or the official RPi 47 Watt power supply.
Yeah i asked that because it is possible that the OP is using a phone charger etc. You never know. When such I/O issues arise, most of the time the cause is about power. I don’t know anything about those “hats” to be honest. I could not understand what was meant by “Manjaro ARM and PiOS works (checked).”
Does that mean other operating systems work on that nvme drive and hat but EOS doesn’t? If that is the case, maybe it is a “kernel” issue.
By the way, in RPI forum RPI people always say the official charger is enough for any type of load connected to the Pi. But i don’t know if they include the external hats and all that stuff to the picture when they say that. Maybe not.
Ok, so a bit more details:
It’s Raspberry Pi 5 B - 8 GB RAM Rev 1.1
Official 27 W power supply that works ok so far
My NVMe disk is: SSD M.2 Samsung 2230 PCIe x4 Gen4 NVMe 128GB MZ-9L41280 PM9B1 - one of those easy to get OEM disks. Bought it brand new only for RPi.
What those it mean checked with OS?. Simply already got installed PiOS and Manjaro on it. I do not like PiOS so been using it for few weeks only, and Manjaro for few months. No issues even if i got hosted some server apps on it with docker.
Wanted to go with plain Arch as this is my main distro since i remember on all the computers. That’s where problems started. Thouhgt “Ok, i’m to tired to prepare everything from scratch this time. Let’s try EOS.”
And from SDcard it works great. Much better performance than i.e. Manjaro. I use Gnome as my daily but also like to rice a bit with openbox (labwc nowaydays as Wayland is my choice).
No labwc was used on EOS so far.
Will check rpi-update after installing PiOS once again and let you know how does it behave.
Thank you for such a quick replies!
EDIT
Ok, installed once again PiOS on SD, and updated bootloader. Then installed PiOS on NVMe once again to check if everything is ok as it always was. System crashes and after reboot gives ext-4 errors on boot. Just like with Arch or EOS. Already ordered second NVMe (RPi dedicated) to find if this is an disk issue. Shouldn’t be as health checks are ok.
If you have something like this you could try out your NVME on USB 3.0. If that works, then the hat would likely be the culprit.
I have two RPi 5 with 8 GB RAM, one RPi 5 with 16 GB RAM, and a RPi 500 Plus.
I run all three RPi 5 with a NVME in a USB 3 enclosure. Of course the RPi 500 Plus is running on the internal NVME. With my use case, I can see a slight speed improvement with the 500 Plus but it’s not that great.
If other operating systems are working on the very same setup but EOS isn’t, i would say it is probably about kernel (drivers). It is possible that Manjaro and RPIOS have some kernel tweaks already in place to adapt the system to RPI but i would think EOS also has those. Or maybe not?
Dunno if that’s the case, as PiOS started to hang too, but… I’ve managed to see EOS setup initialization from NVMe this time (and that’s all). Disk speed looks ok (a bit more than 800 MB/s).
Even saw arch linux login prompt in cli. Still PiOS is the only one i can boot from NVMe but it hangs too after few minutes.
Wiped disk (using wipefs and dd), created plain ext4, copied massive files at once (almost 50 GB) and it works without issues. Problm occurse only when i try to install os on it.
Ok, solved it the most obvious way i couldn’t even expect it will work.
Flashed stock bootloader via Pi Imager and… that helped. No additional parameters no config edition was needed. Just that simple thing. Dumb me
@Pudge@Sam_Fisher thank you for your help and patience. Everything works like a charm now.
Still don’t knkw what it was but as i alteady bought second NVMe it’s probably time to check another HAT and also… buy another Pi to test different setup. Besides work this little fella is getting more and more as my daily driver.
Simplicity is more than welcome and i’ve found it on EOS.
I hope you enjoy your time here.