Migrate from Raspberry Pi 4 to Raspberry Pi 5

Support and Troubleshooting
21 
/dev/mmcblk0p7: LABEL="data" UUID="27529bd0-67c7-434c-b750-796850ce40f4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="555d3053-07"
/dev/mmcblk0p5: LABEL="system-a" UUID="968add47-b2cc-4c79-9d98-866792e4e234" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="555d3053-05"
/dev/mmcblk0p3: PARTUUID="555d3053-03"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="CONFIG" LABEL="CONFIG" UUID="05FD-7483" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="555d3053-01"
/dev/mmcblk0p6: PARTUUID="555d3053-06"
/dev/mmcblk0p2: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT-A" LABEL="BOOT-A" UUID="0600-32B4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="555d3053-02"

the drive is a Sandisk Extreme Portable SSD model sdssde61-1t00

trying the other ports now

22

Im useing 2tb samsung 879 qvo ssd and serbrent USB 3.0 to 2.5-Inch SATA Adapter. Logs:

umbrel@umbrel:~$ sudo blkid
[sudo] password for umbrel:
/dev/mmcblk0p7: LABEL=“data” UUID=“de7e7dbb-97f0-462b-be1d-49793760cb15” BLOCK_SIZE=“4096” TYPE=“ext4” PARTUUID=“7c411514-07”
/dev/mmcblk0p5: LABEL=“system-a” UUID=“968add47-b2cc-4c79-9d98-866792e4e234” BLOCK_SIZE=“4096” TYPE=“ext4” PARTUUID=“7c411514-05”
/dev/mmcblk0p1: SEC_TYPE=“msdos” LABEL_FATBOOT=“CONFIG” LABEL=“CONFIG” UUID=“05FD-7483” BLOCK_SIZE=“512” TYPE=“vfat” PARTUUID=“7c411514-01”
/dev/mmcblk0p2: SEC_TYPE=“msdos” LABEL_FATBOOT=“BOOT-A” LABEL=“BOOT-A” UUID=“0600-32B4” BLOCK_SIZE=“512” TYPE=“vfat” PARTUUID=“7c411514-02”
/dev/mmcblk0p3: PARTUUID=“7c411514-03”
/dev/mmcblk0p6: PARTUUID=“7c411514-06”

23

nope using my pi4 official charger. i can put more power through and see if thats the issue, didn’t actually account for that. thanks for bringing it up.

i tried both blue usb3 ports with the same result. going to try to put more power through the rpi5 to see if thats the issue.

edit
used a 60w usb c charger and im getting the same logs

1 Like
24

So to confirm @boroghor @Merlin you are both using a Pi 5 but not with the official Pi 5 power supply, is that correct?

Are you able to try with the official PSUs? We get a lot of issues with nonstandard PSUs, even if they are rated high.

25

yep thats correct. I will get my hands on an official rpi 5 charger and report back. thanks for the quick quick replies!

1 Like
26

Of course, no problem!

27

Correct. I should be getting the official one delivered Tuesday then i will try again.

Edit: i got the official pi power supply and it all works. thank you for your time in helping troubleshooting.

1 Like
28

I have make the Upgrade vom Pi 4 to Pi 5, but it dosnt work. I have become this failure:
image

No matter what I click, I’m fromof this message.

@lukechilds I can give you the protocol via privat chat. I have use the original pi 5 charger.

29

I have restart the Pi, now it works. Sometimes you just can’t be so impatient :rofl:

30

Does this work with an nvme hat? I have a 4 TB nvme in this hat but I can’t get it to boot from the drive no matter what I do. Ended up wiping the drive in an attempt to get this to work but it doesn’t. Not happy.

31

Its not supported yet. I think somone said they are working on it. Do you want the nvme as the app and profile drive or as a boot drive to replace the sd csrd?

32

I nee it to replace the mSD card as it’s only booting from and using that as the primary storage I have 3.8 something GB left.

33

No. Not at this point, despite the “it supports RPi 5” claim. One of the major benefits of moving from RPi4 to RPi5 was the addition of the NVMe port that allows significantly faster storage access and the ability to boot from NVMe storage. When I saw that Umbrel would support RPi5 in the 1.0 release (with no caveats) a reasonable person could assume that it included the new features of the RPi. Sadly, that isn’t true.

They’re saying that support for NVMe is a “high priority” and will be out in release 1.1. But there is no information on the timing of that. I’ve asked about timing on that release but no one is providing an answer. Going from 0.5.4 (June 2023) to 1.0.3 (March 2024) took around 9 months, so I doubt 1.1 will be out any time soon.

So I’ve reluctantly ordered a USB3 enclosure for my 2TB drive, and will reluctantly try using that set up. I completely understand that this is community supported software, but they had to know 1.0 wasn’t supporting NVMe from the start so it’s disappointing that there wasn’t more information shared about the (still listed) “Now available for Umbrel Home, Raspberry Pi 4, and Raspberry Pi 5.” capabilities without any caveats on the Pi 5 and NVMe.

A detailed “supports the following tech” list would be a more transparent way to inform users…

1 Like
34

When you ran this on the pi4 you didnt have have a usb ssd?

35

my psu just got here and the drive is being found. no issues with the migration from a pi4 to pi5 so far, need to test some things but everything looks fine. thanks for the support and the new update!

36

Are you using the NVMe base hat?

37

nope umbrel booting off sd and data on a usb ssd

38

I thought all had gone well but then I restarted the Pi 5 and now i am being taken to the create an new account page rather than being able to sign in :frowning:

1 Like
39

Is the new account stored on the sd card as opposed to the SSD? When I initially attempted to upgrade I re-flashed the micro SD card and had this same error thinking that it had wiped everything on my hard drive but it actually just made a new account on the 16 GB sd card I’m using.

So upon further inspection the data that was supposed to be on the SSD was intact and no data was lost it just looked lost because of an issue with the new OS at the time was 1.0.0. Since then I attempted to install Umbrel 1 on the SSD using rsync but it hasn’t worked when trying to make umbrel bootable from the SSD via NVMe HAT.

40

Worked perfectly! :grinning: