Jump to content

Not booting to system on NVMe


robnielsen

Recommended Posts

I'm struggling to get my Orange Pi 5 to boot to NVMe with Armbian 23.02 Bullseye CLI. With armbian-install I picked:

 

4 Boot from MTD Flash - system on SATA, USB or NVMe

 

then install to /dev/nvme0n1p1, followed by updating the bootloader on mtdbblock0, and then powering off.

 

When I remove the SD drive, and reboot. The console remains blank. When I insert the SD drive, and reboot again, the system comes up, and I can mount /dev/nvme0n1p1:

 

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            7.7G     0  7.7G   0% /dev
tmpfs           1.6G  9.6M  1.6G   1% /run
/dev/mmcblk1p2   30G  2.0G   27G   7% /
tmpfs           7.7G     0  7.7G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.7G     0  7.7G   0% /tmp
/dev/mmcblk1p1  256M  150M  106M  59% /boot
/dev/zram1       49M  4.1M   41M  10% /var/log
tmpfs           1.6G     0  1.6G   0% /run/user/1000
/dev/nvme0n1p1  234G  1.7G  221G   1% /mnt

 

/dev/nvme0n1p1 looks like it's a clone of /

 

Any ideas/suggestions?
 

Edited by robnielsen
more details
Link to comment
Share on other sites

I was able to get my Orange Pi 5 to boot to NVMe. I used https://jamesachambers.com/orange-pi-5-ssd-boot-guide/ as an example.

 

Deleted partition on NVMe

gdisk /dev/nvme0n1

 

Copied SD card to NVMD

cat /dev/mmcblk1 > /dev/nvme0n1

 

Powered off the Orange Pi 5, removed the SD card and then powered it back on and it booted from the NVMe. I then resized the filesystem

 /usr/lib/armbian/armbian-resize-filesystem start

 

Now I have:

$ df -H
Filesystem      Size  Used Avail Use% Mounted on
udev            8.3G     0  8.3G   0% /dev
tmpfs           1.7G   10M  1.7G   1% /run
/dev/nvme0n1p2  254G  5.7G  245G   3% /
tmpfs           8.3G     0  8.3G   0% /dev/shm
tmpfs           5.3M  4.1k  5.3M   1% /run/lock
tmpfs           8.3G     0  8.3G   0% /tmp
/dev/nvme0n1p1  269M  158M  111M  59% /boot
/dev/zram1       51M  4.8M   43M  11% /var/log
tmpfs           1.7G     0  1.7G   0% /run/user/1000

$ mount | grep /dev/n
/dev/nvme0n1p2 on / type ext4 (rw,noatime,errors=remount-ro,commit=600)
/dev/nvme0n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=936,iocharset=utf8,shortname=mixed,errors=remount-ro)
/dev/nvme0n1p2 on /var/log.hdd type ext4 (rw,noatime,errors=remount-ro,commit=600)


 

Link to comment
Share on other sites

I have used the simple way( prompted by etho201):

1. Using the balenaetcher write the same armbian image to a microSd and to a nvme m.2 SSD too.

2. Put the  microSd and the nvme SSD into your orange pi 5.

3. Turn on, load from microSd, start armbian-config, install updates and after that defreeze kernel upgrades.

4. At the same place (armbian-config) write the bootloader on spi MTD, shutdown and remove microSd.

5. Turn on again and load from nvme SSD.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines