Can't boot: UUID does not match

224 views
Skip to first unread message

Kévin Poirot

unread,
Sep 11, 2014, 4:56:12 PM9/11/14
to coreo...@googlegroups.com
I installed CoreOS from Qemu (my only way to install OS on my dedicated server). So in rescue mode (Ubuntu 12 launched via PXE), I launched Qemu :

qemu-system-x86_64 -no-kvm -hda /dev/sda -cdrom linux-live-cd-with-kernel-3-14.iso -boot d -vnc :0

Then I launched the install script :

./coreos-install -d /dev/sda -C stable -c cloud-config.yaml


Now, when I use Qemu, everything works fine
qemu-system-x86_64 -no-kvm -hda /dev/sda -boot d -vnc :0
but when I reboot the server to directly start on CoreOS, I get some errors and the system won't boot
Warning: /dev/disk/by-label/ROOT does not exist
Warning: /dev/disk/bypartuuid/7130c94a-213a-4e5a-8e26-6ccce9662f132 does not exist
Warning: /dev/disk/bypartuuid/e03dd35c-7c2d-4a47-b3fe-27f15780a57c does not exist

With another OS, I would modify /etc/fstab with correct UUID but CoreOS/Systemd seems to automatically generate fstab on each boot.

How can I resolve this boot problem ?

Thanks in advance.
correct_uuid.png
uuid_mismatch.png

Michael Marineau

unread,
Sep 11, 2014, 5:06:30 PM9/11/14
to Kévin Poirot, coreos-user
Hm, perhaps we do not include the driver for your disk controller.
Could you post the output of 'lspci -nn' when booting from your rescue
mode or the CoreOS ISO?
> --
> You received this message because you are subscribed to the Google Groups
> "CoreOS User" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to coreos-user...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Kévin Poirot

unread,
Sep 11, 2014, 6:04:43 PM9/11/14
to coreo...@googlegroups.com, hellsl...@gmail.com
Output of 'lspci -nn' from the rescue mode :

root@195-154-99-26:~# lspci -nn

00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX800 Host Bridge [1106:0353] (rev 14)
00:00.1 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Error Reporting [1106:1353]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Host Bus Control [1106:2353]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. VX800 PCI to PCI Bridge [1106:3353]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Power Management Control [1106:4353]
00:00.5 PIC [0800]: VIA Technologies, Inc. VX800/VX820 APIC and Central Traffic Control [1106:5353]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Scratch Registers [1106:6353]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 North-South Module Interface Control [1106:7353]
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. VX800/VX820 Chrome 9 HC3 Integrated Graphics [1106:1122] (rev 11)
00:02.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:c353]
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:e353]
00:03.1 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:f353]
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VX800 Serial ATA and EIDE Controller [1106:5324]
00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.4 USB controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VX800/VX820 Bus Control and Power Management [1106:8353]
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VX8xx South-North Module Interface Control [1106:a353]
00:13.0 PCI bridge [0604]: VIA Technologies, Inc. VX855/VX875 PCI to PCI Bridge [1106:b353]
02:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
03:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]

I added a screenshot for the output from Qemu.
qemu_lspci.png

Michael Marineau

unread,
Sep 12, 2014, 1:35:01 PM9/12/14
to Kévin Poirot, coreos-user
Yup, the driver for that controller is not currently enabled in our kernels:

# CONFIG_PATA_VIA is not set

Will look into adding that soon but for now you'll have to stick with
QEMU I suppose.

Michael Marineau

unread,
Sep 12, 2014, 1:54:14 PM9/12/14
to Kévin Poirot, coreos-user

Kévin Poirot

unread,
Sep 12, 2014, 2:10:44 PM9/12/14
to coreo...@googlegroups.com, hellsl...@gmail.com
Thank you very much for the help and the pull request.
Reply all
Reply to author
Forward
0 new messages