[solved]Fresh install with dd - boot stuck to "waiting for root device partuuid"


I'm completely new to openwrt, and I'm trying to install it on a dedicated hardware (custom server handmade).


I'm using a NVMe => Samsung SSD Interne 970 EVO Plus NVMe M.2
and this => Tangxi Carte Adaptateur m.2 NVMe vers USB

to write the openwrt image to the nvme from a debian machine (I only have 1 nvme slot, so I can't plug the nvme directly to the motherboard since the single slot is already used by the nvme with debian)


I've followed this guide => https://openwrt.org/docs/guide-user/installation/openwrt_x86
but I'm facing an issue while booting.

It's stuck at "Waiting for root device PARTUUID=eb3ae1bb-02".

I've read similar topics about this specific issue, but I couldn't find a solution.

Here is the drive before using dd to write the openwrt image

And here is the drive after using dd to write the image

The command I used to write the image is => dd if=openwrt-18.06.1-x86-64-combined-squashfs.img of=/dev/sdX

If you have any idea how I can fix this issue, would be appreciated !

The wiki is outdated when it comes to openwrt version.
You should really install 19.07.7.

If it still fails in 19.07, post back here.

Additional question, is the openwrt supposed to be running from/via the USB-nvme adapter ?

I could imagine the kernel image not having build in support for it.


1 Like

Any outdated information in the wiki should be a stimulation for the community to update it, otherwise it will stay outdated.

1 Like


but I noticed it today, when OP linked to it.

"Problem" is it doesn't contain the dynamic links, as most of the other router pages do, where the link is kept fresh, and always pointing towards the most recent release.

I'll try to fix, if I can figure out how dynamic links work.

It's already the latest img, as you can see from my third screen

This is the image I downloaded and write with the dd command => https://downloads.openwrt.org/releases/19.07.7/targets/x86/64/openwrt-19.07.7-x86-64-combined-squashfs.img.gz

Once the image is written on the NVMe, I'm booting from that NVMe.
I'm not using the adapter to boot, only to copy the image.

Well, you also wrote ...

But ok, so the waiting for boot device ... is when you try to boot from the NVMe the "proper" way ?

Ho my bad, I copy paste the command from the FAQ and forgot to edit the filename...

Yes, I'm booting from the NVMe the "proper" way.

Anyway I've find an other solution and went with the Sophos firewall home edition. Everything is working as I want.

Thank you for the help. You can lock this topic.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.