Why No Help For Pi 5 with USB 3 SSD Issue Described Under NVMe Thread?

Support and Troubleshooting
1

In a separate thread in this section I describe in detail how I had to move a 2 TB drive from NVMe to USB 3 because umbrelOS 1.0.x doesn’t support NVMe connections.

In that thread I lay out my move to USB 3 which I’m told does work. I don’t feel like duplicating all that description here, but I’d like to understand how some of these “help/troubleshooting” threads get answered in a few minutes to maybe a few hours, and others are completely ignored by Umbrel folks?

Have I ticked someone off? Is the answer to difficult to post? Are folks so swamped with work and the issues so serious that there’s no time to reply?

I have, what is supposed to be, a stock, fully supported hardware stack.

RPi 5 with 8 gb RAM, 64gb Micro Card, 2 TB SSD using USB3…

I’ve installed UmbrelOS 1.0.4 per the published instructions and nothing seems to function as it should. Some response would be appreciated. Please see the last 4 or 5 posts on the “Formatting NVMe M.2 Hardrive (sic)” thread. I’m at the end of my rope.

2

So I’ve tried yet again. Here are the detailed steps I’ve taken.

  1. Reflashed the 64gb Micro SD with Bookworm, installed gparted, wiped the 2 TB SSD mounted via USB3.

  2. Reflashed the 64 gb Micro SD using BalenaEtcher and the most current RPi 5 image for umbrelOS, which is 1.0.4 as I see it. Installed the Micro SD card and booted the Pi 5.

  3. Waited 5 minutes and tried umbrella.local and the IP address in Chrome, with no response.

  4. ssh’d to the IP address, was prompted for a password, and logged in.

  5. Ran df and got the following output…

umbrel@umbrel:~$ df
Filesystem      1K-blocks     Used  Available Use% Mounted on
overlay          50219552    23892   47612212   1% /
tmp               4122880     5088    4117792   1% /run
/dev/mmcblk0p7   50219552    23892   47612212   1% /run/rugpi/mounts/data
/dev/root         3334328  2946436     198200  94% /run/rugpi/mounts/system
/dev/mmcblk0p1     261864     1148     260716   1% /run/rugpi/mounts/config
/dev/mmcblk0p2     130796    61380      69416  47% /boot
devtmpfs             4096        0       4096   0% /dev
tmpfs             4122880        0    4122880   0% /dev/shm
tmpfs                5120        0       5120   0% /run/lock
/dev/sda1      1921680472 11486632 1812504092   1% /mnt/data
tmpfs              824576        0     824576   0% /run/user/1000

This shows the 2 TB drive (/dev/sda1) is mounted at /mnt/data

  1. Ran top to see what’s running and got this…
umbrel@umbrel:~$ top

top - 15:37:32 up 9 min,  1 user,  load average: 1.33, 1.20, 0.68
Tasks: 157 total,   2 running, 155 sleeping,   0 stopped,   0 zombie
%Cpu(s): 28.5 us,  1.9 sy,  0.0 ni, 69.5 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :   8052.5 total,   7371.5 free,    314.6 used,    455.9 buff/cache     
MiB Swap:      0.0 total,      0.0 free,      0.0 used.   7737.9 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                     
   9665 root      20   0  615936  70144  39936 R  20.9   0.9   0:00.63 npm                         
    292 root      20   0  260608  17920  14336 S   0.7   0.2   0:01.05 NetworkManager              
     23 root      20   0       0      0      0 I   0.3   0.0   0:00.53 kworker/1:0-events_freezable
   2444 umbrel    20   0   20768   7328   5120 S   0.3   0.1   0:00.01 sshd                        
   8151 umbrel    20   0    8992   4096   2048 R   0.3   0.0   0:00.14 top                         
      1 root      20   0  168864  10640   7680 S   0.0   0.1   0:03.09 systemd                     
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.00 kthreadd                    
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_workqueue_release      
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-rcu_g             
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-rcu_p             
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-slub_             
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-netns             
      8 root      20   0       0      0      0 I   0.0   0.0   0:00.77 kworker/0:0-events          
      9 root       0 -20       0      0      0 I   0.0   0.0   0:00.15 kworker/0:0H-mmc_complete   
     11 root      20   0       0      0      0 I   0.0   0.0   0:00.64 kworker/u8:0-scsi_tmf_0     
     12 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker/R-mm_pe             
     13 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tasks_kthread           
     14 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tasks_rude_kthread      
     15 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tasks_trace_kthread     
     16 root      20   0       0      0      0 S   0.0   0.0   0:00.05 ksoftirqd/0                 
     17 root      20   0       0      0      0 I   0.0   0.0   0:00.51 rcu_preempt                 
     18 root      rt   0       0      0      0 S   0.0   0.0   0:00.00 migration/0                 
     19 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/0                     
     20 root      20   0       0      0      0 S   0.0   0.0   0:00.00 cpuhp/1                     
     21 root      rt   0       0      0      0 S   0.0   0.0   0:00.00 migration/1

I don’t see any http or https deamon running, but I don’t know what umbrel uses so whatever…

  1. Waited 5 more minutes…tried umbrel.local and the IP again with no response.

  2. Ran ss -ltn to see what ports are being watched and get the following…

umbrel@umbrel:~$ ss -ltn
State      Recv-Q     Send-Q         Local Address:Port           Peer Address:Port     Process     
LISTEN     0          128                  0.0.0.0:22                  0.0.0.0:*                    
LISTEN     0          128                     [::]:22                     [::]:*

Obviously no listener for port 80

  1. Walked away for a few as my blood is boiling…came back…pulled the power plug from the RPi 5…waited a minute…powered it back up…

  2. After waiting for a couple of minutes tried browser access to umbrel.local and get the “Welcome to umbrelOS window” so that’s good news, but why didn’t it start up properly the first time I booted? That concerns me…

  3. Create my user name and assign a password, and get to the “Install your first app” panel. Click on the “Settings” icon. See the USB drive showing 5.13 GB / 1.97 TB. Click the “Device Info” link and get “Device Raspberry Pi 5” which is the first time I’ve gotten this far. So good, but again, why didn’t this happen in the previous EXACT SAME SETUP AND PROCESS? Is this OS stable?

  4. Clicked on Bitcoin Node Install, install starts running…gets 99% and sits there…so I wait…and wait…and wait…then get a quickly flashed error about “auth existence check fails”…and am then presented with the “Welcome to umbrelOS” screen so I can set up umbrel…WTF? I already did that!

  5. Click Start again and get the error again…

  6. Reload the browser page and get “This site can’t be reached”.

  7. ssh back to the device, and use the new password I set, and I get logged on.

  8. run a ss -ltn and get the following…

umbrel@umbrel:~$ ss -ltn
State      Recv-Q     Send-Q         Local Address:Port           Peer Address:Port     Process     
LISTEN     0          128                  0.0.0.0:22                  0.0.0.0:*                    
LISTEN     0          4096                 0.0.0.0:2000                0.0.0.0:*                    
LISTEN     0          128                     [::]:22                     [::]:*                    
LISTEN     0          4096                    [::]:2000                   [::]:*

So no port 80, again…

  1. Run df and the 2TB drive still shows it is mounted.

Stop this freaking insane process…

So, I sit here, after probably 20 hours of work spread over many days trying to get a plain RPi 5 set up working, first with NVMe and umbrelOS 1.0. And then buying and waiting for a USB3 enclosure and then trying umbrelOS 1.0.3, and 1.0.4. What does a guy have to do?

3

Here is section of the system log, which clearly shows a fail to initiate the USB drive, although it worked on one of the reboots…

Mar 27 17:49:53 umbrel kernel: scsi host0: uas
Mar 27 17:49:53 umbrel kernel: usb 2-1: USB disconnect, device number 24
Mar 27 17:49:53 umbrel kernel: scsi 0:0:0:0: tag#4 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:49:53 umbrel kernel: scsi 0:0:0:0: tag#4 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:49:53 umbrel umbreld[828]: [server       ] GET /trpc/system.cpuTemperature
Mar 27 17:49:55 umbrel kernel: usb 2-1: new SuperSpeed USB device number 25 using xhci-hcd
Mar 27 17:49:56 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:49:56 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:49:56 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:49:56 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:49:56 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:49:56 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:49:56 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:49:56 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:49:56 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:49:56 umbrel kernel: scsi host0: uas
Mar 27 17:49:56 umbrel kernel: usb 2-1: USB disconnect, device number 25
Mar 27 17:49:56 umbrel kernel: scsi 0:0:0:0: tag#16 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:49:56 umbrel kernel: scsi 0:0:0:0: tag#16 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:49:58 umbrel kernel: usb 2-1: new SuperSpeed USB device number 26 using xhci-hcd
Mar 27 17:49:58 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:49:58 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:49:58 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:49:58 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:49:58 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:49:58 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:49:58 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:49:58 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:49:58 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:49:58 umbrel kernel: scsi host0: uas
Mar 27 17:49:59 umbrel umbreld[828]: [server       ] GET /trpc/system.cpuTemperature
Mar 27 17:49:59 umbrel kernel: usb 2-1: USB disconnect, device number 26
Mar 27 17:49:59 umbrel kernel: scsi 0:0:0:0: tag#12 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:49:59 umbrel kernel: scsi 0:0:0:0: tag#12 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:50:00 umbrel umbreld[828]: [server       ] GET /trpc/system.status
Mar 27 17:50:01 umbrel kernel: usb 2-1: new SuperSpeed USB device number 27 using xhci-hcd
Mar 27 17:50:01 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:50:01 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:50:01 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:50:01 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:50:01 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:50:01 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:01 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:01 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:01 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:01 umbrel kernel: scsi host0: uas
Mar 27 17:50:02 umbrel kernel: usb 2-1: USB disconnect, device number 27
Mar 27 17:50:02 umbrel kernel: scsi 0:0:0:0: tag#16 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:50:02 umbrel kernel: scsi 0:0:0:0: tag#16 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:50:03 umbrel avahi-daemon[208]: Registering new address record for fd33:149f:e073:aa4f:79d6:984f:3e19:154f on end0.*.
Mar 27 17:50:04 umbrel umbreld[828]: [server       ] GET /trpc/system.cpuTemperature
Mar 27 17:50:04 umbrel kernel: usb 2-1: new SuperSpeed USB device number 28 using xhci-hcd
Mar 27 17:50:04 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:50:04 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:50:04 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:50:04 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:50:04 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:50:04 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:04 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:04 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:04 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:04 umbrel kernel: scsi host0: uas
Mar 27 17:50:04 umbrel kernel: usb 2-1: USB disconnect, device number 28
Mar 27 17:50:04 umbrel kernel: scsi 0:0:0:0: tag#0 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:50:04 umbrel kernel: scsi 0:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:50:07 umbrel kernel: usb 2-1: new SuperSpeed USB device number 29 using xhci-hcd
Mar 27 17:50:07 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:50:07 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:50:07 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:50:07 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:50:07 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:50:07 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:07 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:07 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:07 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:07 umbrel kernel: scsi host0: uas
Mar 27 17:50:07 umbrel kernel: usb 2-1: USB disconnect, device number 29
Mar 27 17:50:07 umbrel kernel: scsi 0:0:0:0: tag#20 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:50:07 umbrel kernel: scsi 0:0:0:0: tag#20 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:50:09 umbrel umbreld[828]: [server       ] GET /trpc/system.cpuTemperature
Mar 27 17:50:10 umbrel umbreld[828]: [server       ] GET /trpc/system.checkUpdate
Mar 27 17:50:10 umbrel avahi-daemon[208]: Withdrawing address record for fd33:149f:e073:aa4f:79d6:984f:3e19:154f on end0.
Mar 27 17:50:10 umbrel umbreld[828]: [server       ] GET /trpc/system.status
Mar 27 17:50:10 umbrel kernel: usb 2-1: new SuperSpeed USB device number 30 using xhci-hcd
Mar 27 17:50:10 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:50:10 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:50:10 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:50:10 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:50:10 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:50:10 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:10 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:10 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:10 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:10 umbrel kernel: scsi host0: uas
Mar 27 17:50:10 umbrel kernel: usb 2-1: USB disconnect, device number 30
Mar 27 17:50:10 umbrel kernel: scsi 0:0:0:0: tag#24 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:50:10 umbrel kernel: scsi 0:0:0:0: tag#24 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:50:12 umbrel umbreld[828]: [server       ] GET /assets/device-info-content-2d163e3f.js
Mar 27 17:50:12 umbrel umbreld[828]: [server       ] GET /assets/device-info-afe8521a.js
Mar 27 17:50:12 umbrel umbreld[828]: [server       ] GET /figma-exports/system-pi.svg
Mar 27 17:50:13 umbrel kernel: usb 2-1: new SuperSpeed USB device number 31 using xhci-hcd
Mar 27 17:50:13 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:50:13 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:50:13 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:50:13 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:50:13 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:50:13 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:13 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:13 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:13 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:13 umbrel kernel: scsi host0: uas
Mar 27 17:50:13 umbrel kernel: usb 2-1: USB disconnect, device number 31
Mar 27 17:50:13 umbrel kernel: scsi 0:0:0:0: tag#24 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:50:13 umbrel kernel: scsi 0:0:0:0: tag#24 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:50:14 umbrel umbreld[828]: [server       ] GET /trpc/system.cpuTemperature
Mar 27 17:50:16 umbrel kernel: usb 2-1: new SuperSpeed USB device number 32 using xhci-hcd
Mar 27 17:50:16 umbrel kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
Mar 27 17:50:16 umbrel kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 27 17:50:16 umbrel kernel: usb 2-1: Product: SSK Storage
Mar 27 17:50:16 umbrel kernel: usb 2-1: Manufacturer: SSK
Mar 27 17:50:16 umbrel kernel: usb 2-1: SerialNumber: 012345678923
Mar 27 17:50:16 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:16 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:16 umbrel kernel: usb 2-1: Enable of device-initiated U1 failed.
Mar 27 17:50:16 umbrel kernel: usb 2-1: Enable of device-initiated U2 failed.
Mar 27 17:50:16 umbrel kernel: scsi host0: uas
Mar 27 17:50:16 umbrel kernel: usb 2-1: USB disconnect, device number 32
Mar 27 17:50:16 umbrel kernel: scsi 0:0:0:0: tag#4 uas_zap_pending 0 uas-tag 1 inflight: CMD 
Mar 27 17:50:16 umbrel kernel: scsi 0:0:0:0: tag#4 CDB: opcode=0x12 12 00 00 00 24 00
Mar 27 17:50:17 umbrel umbreld[828]: [server       ] GET /assets/troubleshoot-1e321779.js
Mar 27 17:50:17 umbrel umbreld[828]: [server       ] GET /assets/format-2b6dad33.js
Mar 27 17:50:17 umbrel umbreld[828]: [server       ] GET /trpc/system.logs
Mar 27 17:50:17 umbrel umbreld[828]: [server       ] GET /trpc/system.logs
4

Well, while I wait for someone at Umbrel to lend a hand to the above mess, I decided to wipe the entire system, reinstall the 2 TB NMVe drive using the PCIe hat, reload RaspiOS Bookworm, and boot everything from the NMVe drive and get off the Micro SD card entirely. This took maybe 15 minutes and the RPi 5 is a screaming machine right now. It’s impressive how fast it is when you can boot from a fast, NVMe drive and get off the slow SD card.

I still have hopes that at some point in time UmbrelOS 1.X will be a viable solution, as I really like the integration work the Umbrel Team has done. But until that happens I can do other things with the RPi 5.

Umbrel guys/gals, when you find the time to make the RPi 5 actually work please post and I’ll take a look. I posted on a separate thread asking for users that have a functional RPi 5 based server running to post their hardware set up, but so far, not a single reply…which makes it seem like claiming RPi 5 support is a stretch…but I guess if you’re system is working, you’re off doing other things, and not looking at the support site.

5

This all sounds very similar to what I went through to get Umbrel up and running on RPi5.
Once I put the M.2 NVME into an attached USB 3.0 enclosure and start the install from the very start, it all went well. I have just done the 1.0.4 upgrade after the Blockchain was finished at 100%. That all went really well. So I’m happy with how things have worked out.

The only thing now is getting the NVME into the case with the PI5 and not connected via USB, once they make NVME compatible.

6

So what hardware are you using? I have a different thread asking folks that did get RPi 5 working to post that hardware list. I bought a USB3 enclosure and installed my drive in that, but it’s very flaky and sometimes shows up and sometimes doesn’t, which is/was driving me crazy.

7

I just answered another message you have.
This is mine…
Argon one V3 case.
RPi 5
San Disc 32gb SD card.
Crucial P3 Plus NVME SSD-Mounted in an external case plugged in via the USB 3.0 port on the RPi 5.
This external case is just one I bought from Amazon, nothing special just a cheap one.

I had to start the Umbrel install from the very beginning after many failed attempts.
It is now working well. Only recently got to the 100% Blockchain download and then I done the 1.0.4
update and it is working well.

8

So…it’s the “noting special external case” for the NVMe drive that I’m interested in. The Argon One V3 is for the Pi 5, and that’s not my issues. Which USB3 case did you get?

9

IMG_2013
IMG_20131920×1440 210 KB

IMG_2014
IMG_20141920×1808 330 KB

Just took these now.

10

THANK YOU! I’ll check out the specs and compare with mine. If that enclosure is “slower” that might be the issue…

11

So the main difference I see is the enclosure you have is a USB 3.1 Gen 2 and mine is a USB 3.2 Gen 2. Both way they support 10 gb speeds, but maybe there is an issue with the RPi 5 and USB 3.2. Normally the higher version falls back to the lower version but depending on the hardware drivers in the Umbrel kernel, maybe that’s an issue…I’m still checking, and am not a hardware/driver guy, but maybe…

The RPi 5 says it supports USB 3.0 ports, supporting simultaneous 5Gbps operation. Both of the enclosures we have support 10Gbps, but maybe that different explains why my drive “disappears” and yours doesn’t…

Sure wish the Umbrel guys would chime in…

1 Like
12

I don’t know. Maybe I just got lucky. Hope it works out for you. Sure is frustrating when things don’t go as planned.

13

I’m in the exact same boat as you guys. I haven’t jumped on the USB3 boat yet but would love a shout out from Umbrel to let us know where their, at and to acknowledge that they are working on it.

1 Like
14

I am a non tech user here experiencing a kind of the same issue since I updated to Umbrel OS 1.0. any of my apps is running.
umbrel_umbrel_2024-03-28_06-58.log (188.8 KB)

All the hardware used were following the official suggestions of Umbrel:

  • RPi 5 with official official power source.
  • Crucial Mx500 2.5 SSD 1tb

I’m attaching here my logs in case are useful.

15

I have the same problem here (Hardware: RPi 5, 120gb Micro Card and 1TB SSD using USB3.0).
In my case Hard Disk is not even mounted automatically during the flash-boot.

I’ve tried reinstalling it three times, but it hasn’t worked.

df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         107G   16G   86G  16% /
tmp             4.0G  9.8M  4.0G   1% /run
/dev/mmcblk0p7  107G   16G   86G  16% /run/rugpi/mounts/data
/dev/root       3.2G  2.9G  194M  94% /run/rugpi/mounts/system
/dev/mmcblk0p1  256M   44K  256M   1% /run/rugpi/mounts/config
/dev/mmcblk0p2  128M   60M   69M  47% /boot
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs           4.0G     0  4.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           806M     0  806M   0% /run/user/1000

fdisk -l
Disk /dev/mmcblk0: 119.08 GiB, 127865454592 bytes, 249737216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x71b5877c

Device         Boot    Start       End   Sectors   Size Id Type
/dev/mmcblk0p1          8192    532479    524288   256M  c W95 FAT32 (LBA)
/dev/mmcblk0p2        532480    794623    262144   128M  c W95 FAT32 (LBA)
/dev/mmcblk0p3        794624   1056767    262144   128M  c W95 FAT32 (LBA)
/dev/mmcblk0p4       1056768 249737215 248680448 118.6G  5 Extended
/dev/mmcblk0p5       1064960  11550719  10485760     5G 83 Linux
/dev/mmcblk0p6      11558912  22044671  10485760     5G 83 Linux
/dev/mmcblk0p7      22052864 249737215 227684352 108.6G 83 Linux
The backup GPT table is corrupt, but the primary appears OK, so that will be used.


Disk /dev/sda: 976.56 GiB, 1048576000000 bytes, 2048000000 sectors
Disk model: SSD 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 01D6269B-46F8-4FB3-A636-17779BBF5AB2

Device     Start        End    Sectors   Size Type
/dev/sda1   2048 2047997951 2047995904 976.6G Linux filesystem

The dumb panel it’s showing a wrong size:

CleanShot 2024-03-28 at 20.52.14@2x
CleanShot 2024-03-28 at 20.52.14@2x1920×1155 70.9 KB

16

Just a thought. Is the problem with NVMe just in the OS image or in the Umbrel UI? Why not just use Umbrel OS on Rasp/Debian/Ubuntu so that you get full hardware support for NVMe? The curl script works on RPi too.

I thought about getting an Umbrel Home but decided to just stick to the 11th-gen Core i7 NUC that I have laying around. It’s faster and has more memory…but I’ll have to wait for however they’re going to deliver Umbrel OS in April for it.

Honestly, I don’t understand why the company couldn’t just stick to a single base operating system. Raspberry Pi’s can run Debian, Ubuntu, Fedora, Arch, and the like (I use a PiKVM which uses Arch as their base OS image - and it’s NOT FORKED). Having one OS image for all x86 and another for ARMv8 with the RPi bootloader from the same OS platform would make a lot more sense than having separate ones for each. What is so special about UmbrelOS 1.x for Umbrel Home over any generic x86 computer?? Why even bother with a custom OS for Umbrel Home at all if all that the Umbrel server components require is a functioning Debian or Ubuntu OS image? Why not just use a build service to build an Ubuntu or Debian image using the same script requirements as the generic Linux Umbrel install? I really hate when companies make a forked OS image for a piece of hardware, but then don’t want to bother with upkeep on it. Let the platform vendor do that if you’re not willing to rebase your downstream fork! Is this all just so that you can reversion it with a shiny “1.0” moniker? I. HATE. THIS. REASONING. If they just kept it on the the base OS repo, they wouldn’t have to do the extra work to recompile all the OS support packages.

I honestly don’t get why they didn’t just use one of the atomic OS systems for this, like openSUSE Micro OS or something similar. Extremely lightweight with simple updates, and they have a build service too. Every app is a container. Updates for the OS are automatic with auto-fallback for an error, but it can be controlled by the user too. Plus, it’s easy to release an OS image for installation because of the build service. Practically any hardware that is supported by the Linux kernel in that base OS could install the software, and yet the application software vendor doesn’t even have to deal with any compatibility headaches.

1 Like
17

My issue was solved with the following commands:

Thanks for sharing those logs, and apologies for the delayed response.

It appears this current issue is related to docker- can you please try the following steps:

  1. Open a terminal window on your computer. On macOS, you can open the Terminal app that’s installed by default on every Mac. On Windows, you can open Command Prompt or the PowerShell app.
  2. Type in the following command ssh -t umbrel@umbrel.local and press the Enter key
  3. Run the following commands one-by-one

sudo systemctl stop umbrel

sudo systemctl stop docker docker.socket

sudo bash -c "rm -rf /var/lib/docker/*"

sudo systemctl start docker docker.socket

sudo systemctl start umbrel > Thanks for sharing those logs, and apologies for the delayed response.

1 Like