uefi images: "error: no such device: root."

Bug #1726476 reported by dann frazier
This bug affects 21 people
Affects Status Importance Assigned to Milestone

Bug Description

I noticed when booting an arm64/artful image, I've started seeing the error:

error: no suitable video mode found.
error: no such device: root.

Press any key to continue...

The "no suitable video mode found" error has always been there, but the "no such device: root." and "Press any key to continue..." messages appear to be new. Obviously, having to press a key to continue would be a real problem for a cloud environment - but, the boot does appear to continue w/o a key press anyway.

tags: added: id-5a4bb46b3dc58d69b9c536c1
Dan Watkins (oddbloke)
Changed in cloud-images:
importance: Undecided → Low
Revision history for this message
dann frazier (dannf) wrote :
summary: - arm64: "error: no such device: root."
+ uefi images: "error: no such device: root."
Revision history for this message
dann frazier (dannf) wrote :

changed bug title, since this isn't an ARM-specific issue

Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

Has anyone found a way to workaround this problem?

Revision history for this message
dann frazier (dannf) wrote :

The problem is apparently "only cosmetic", since the boot proceeds anyway, but it really would be nice to fix as it impacts both x86 and ARM uefi images.

Revision history for this message
Robert C Jennings (rcj) wrote :

It is cosmetic but there is work to address this. Work was blocked on release since we were too close to GA. The change will impact all cloud-images so this requires extensive testing, so I do not have an ETA for a fix.

tags: added: id-5a9731fa5c97ee0a1462180a
Revision history for this message
Gerry Boland (gerboland) wrote :

I've encountered this too, tracked it down to a problem in the root filesystem's grub.cfg, it contains the line

 search --no-floppy --fs-uuid --set=root

which is incorrect - there should be a UUID appended to this line. Since there isn't, grub tries to find a device with uuid "root" which fails, and it complains.

Revision history for this message
evilhamsterman (evilhamsterman) wrote :

To expand on the previous comment, the issue can be resolved post boot by running update-grub which will fill out the missing values on the search line. It appears the build process is either not running update-grub or it is using a default grub template that is missing the appropriate data.

tags: added: id-5d12500579ebd95c1b52ecb8
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This is strictly an image build issue; livecd-rootfs diverts all of grub-probe in the divert_grub() function, but it really should only do this for 30_os-prober.

We already run update-grub correctly; the issue is that some of these calls may happen with grub-probe diverted in such a way that the grub.cfg will get mangled a bit, dropping the right path for the search command used to find the root.

Revision history for this message
dann frazier (dannf) wrote :

I saw this pop up again in a lxd --vm demo yesterday - any chance we can get it addressed this cycle? :) Happy to help w/ the testing where possible..

Changed in cloud-images:
status: New → Confirmed
Revision history for this message
fraser addison (fraseraddison) wrote :

When I set admin_pass: <password> in coud meta file it disapeared. This is a local run in kvm.

Revision history for this message
Dion Bosschieter (dionbosschieter) wrote :

I also experience this using the bionic cloudinit image:


To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.