Your NVME is the same as mine, Crucial P3 Plus 2tb, mounted in an enclosure and connected via USB 3.0. The case I’m using is an Argon One V3 for the RPi5.
I’ll check out the specs on your enclosure…I suspect that my enclosure might be the culprit. It might be a speed issue and the UmbrelOS kernel can’t keep up with the speed. When I reformatted everything and went back to Bookworm I configured the kernel to use Gen 3 speeds and the NVMe drive works very fast. But it the kernel in UmbrelOS is using older drives there may be a timing issue that causes the USB3 based device to drop out. Just don’t know…
Right now I have no idea when they’ll push 1.1, how stable it will be, or if it will support NVMe boot (No Micro SD card). I just went back to Bookworm and booting from NVMe (which is VERY fast compared to micro SD slot), and installed Bitcoin Core directly. It took about 18 hours for the block chain to download and sync, but it’s running just fine (low CPU usage, reasonable network consumption) so I will have to be completely convinced of stability and usability to try UmbrelOS 1.1. And I don’t feel like re-downloading the entire blockchain again, so if there’s not a decent way to move what I have over, that’s another hurdle…
I really fell for the fancy marketing BS for 1.0, and assumed that the “production release” would be an actual solution that actually supported RPi 5 fully. Sadly, that isn’t the case. No timing info on when NVMe support will be released. No actual online docs on the OS/environment that end users can work with. No theory of operation or architectural overview so users can understand how it’s put together so they can trouble shoot. No real access to the underlying OS (via terminal) or understanding on how to install or build things, or do break fix. I guess they just expect users to use the “store”, and post questions to the community. That seems like a real tough way to release a software “environment” and is doing nothing but creating all kinds of “feedback” that I’m sure they don’t need right now. As a software developer/system manager for over 40 years, I’d hate to be the developer who is also the help desk and troubleshooter, and who is developing and doing break fix at the same time. Oh well…
Harsh? If I’m being that then I apologize. I don’t think that pointing out legitimate issues is particularly harsh, but what do I know…it’s certainly not my intent. I would much prefer to buy the Umbrel team a beer and have a good conversation…
I actually think I’m just discussing facts, simple facts. And I’m not angry at all, just disappointed. Simple transparency would have resolved this issue. I pity the person that finds the new UmbrelOS release page, happily downloads and tries to install, and then finds out no NVMe, and flaky USB 3 enclose support.
As I just posted on a different response to a different thread…just be transparent about what is actually supported. And I really do hope they’re able to resolve the issues; I’m sure it’s not fun to do hard development and end user support and break fix, all at the same time…