Yes, kind of. If you remove the SD card and mount it in another device you can then modify the config.txt file on the BOOT-A volume. You need to add a line at the end that says “dtparam=spi=on” no quotes. Save, reinsert the SD card and boot up. You might need to run the LCD setup again, you’ll get the same errors but it will work.
Currently the only screens working are the DATE/TIME and Storage. Think the others will need to be modified for the changes made in the Umbrel 1.0 update. I might get around to tinkering with this later on but for now at least I have the screen working and not just a plain white display.
Hey everyone, thanks for your patience, I really appreciate you bearing with us. We have a new image that includes a fix for the Raspberry Pi 4 sometimes not detecting USB storage. For any affected users, can you please:
It may take a minute or two to complete the first boot. After that, you’ll be able to access your Umbrel again at http://umbrel.local
To reiterate, your data is totally safe, no data was lost from your umbrelOS 0.5 install. The Pi was just not detecting the storage drive. With the new OS image your storage will be detected reliably on every boot and all your previous data and apps will be available again.
One thing to note is that if you hit this issue previously after installing 1.0 and you then created a new account, that account existed on the SDcard not your USB storage. Updating to the latest fix will mean your previous data on external storage will be correctly detected and used instead of the new account you setup on your SDcard. So if you created a new password during signup, make sure to use your previous umbrelOS 0.5 password after this update.
Let us know how you get on!
Also one more note, some users have reported Lightning Node takes a while to come back online after applying the fix. Nothing is wrong, it’s just rescanning the blocks since it was last online and can take up to an hour. If you think something else is up feel free to let us know and we can take a look at your logs to confirm.
Hey @MadMacks I replied to your post in the other thread. We don’t have NVMe support on Pi 5 right now but it’s high on our list of priorities. Happy to reach out to you if you’d like early access to beta test it once it’s ready.
Ok. Thx for the response. Understand you’re very busy, and really appreciate the hard work you’re doing…just bummed cause I’ve been sitting on the new hardware waiting for 1.0 and was/am frustrated to have the install fail yesterday when I tried to install on the new hardware…oh well.
Not sure what your timing is for RPi 5 with NVMe support but feel free to let me know when/if you have a test release. I’m setting up a new Bitcoin/Lighting node so I haven’t lost any existing functionality.
I’m already half way threw the four days of re-downloading the blockchain so it’s a little late for a fix for me. I have already formated my SSD so I have to just start over.
@lukechilds
Good morning,
When installing version 1.0.1 on a respberry Pi4 when rebooting, asks to enter the 2FA code, but when entering it does not work. An idea ?
The installation process you outline creates different results from the past.
With umbrel 1.0 (on a raspbi4) it created another partition for BOOT, as well as two additional partitions on the microSD card. As a result I couldn’t get WIFI to work… couldn’t validate that it even started up.
Reverted back to prior version and no additional partitions, added wma file and it worked first time.
It’s still important you reflash your sdcard to update because the bug that causes the USB SSD storage is intermittent and can affect you at any future boot. The bug is now resolved in the new 1.0.1 image.
Thanks for the new image. New realization. The web interface starts. New user and PW had to be created. No old APPS, after installing Bitcoin as the first APP it starts at 0%? How can Chain and LND still be saved? It was always said that everything was safe on SSD… After another reboot, the web interface no longer starts…
.
The new SDcard partitioning scheme allows us to ship OTA updates for entire OS images so we can do much more reliable updates moving forward from 1.0. The previous update system was much more difficult to work with.
We’ll be adding official WiFi support from the umbrelOS UI very soon.
@tgm3d your data should still be available on your SSD. Are you able to DM me some live chat contact details like Telegram so I can help debug this with you?
my raspi5 is ready.
Flashed with balenaetcher, sd-card in and Bitcoin Node installed.
Two days for 100 % sync.
Runs very smooth and all is fine for me.
As I’ve thought about the NVMe drive issue, it occurs to me that the best solution would be to allow RPi 5 to boot directly from the NVMe drive and skip the Micro card altogether. The NVMe drives are orders of magnitude faster than Micro SD cards, so allowing both RPi 4 and RPi 5 devices to boot UmbreOS 1.X directly from an “external” drive (USB based or NVMe based) would improve overall performance. Maybe that can be the targeted solution?
I’ve ordered a USB3 to NVMe case to house my Crucial 2 TB M.2/NVMe drive so I assume when that shows up I can get things working…but that means I lose I/O speed by moving off the PCIe bus and going thru the USB controller. And, if there is a fix for NVMe and I move the SSD back to the PCIe bus I assume I’ll have to rebuild the server and reload/download the entire block-chain. Waiting, hopefully, for a solution, reasonably soon…
