Failed to start "Generate new UUID for disk" after PXE boot with install to disk #1091
Comments
hmm, thanks for the report, we'll need to repro this and figure out why sgdisk is getting this error. |
I'm getting this on a brand new Kingston 240GB SSD after doing
I tried installs with both stable and beta. |
I also found the discussion coreos-install: backup gpt table is not at the end of the disk && partitions? in the CoreOS Dev group. It looks like that could be related, since I get the same warning message after installing. |
I eventually got CoreOS to boot:
|
I have the same issue with 835.12.0. Previously, I installed a Ubuntu 15.10 on the computer. Does it have anything to with the GPT? I'm not sure. I fixed it by run |
@heqian I had the same issue, But I was installing after Windows 7. Your suggestion fixed issue for me, Thank you! |
parted -> print -> fix -> boot into usr a worked for me. Thanks! |
I can repro this in the qemu image with the following: sudo dd if=/dev/urandom of=/dev/vda bs=512 count=1 seek=$(($(sudo blockdev --getsz /dev/vda) - 1))
sudo sgdisk --disk-guid=R /dev/vda Despite sgdisk insisting that it's "regenerating backup header from main header", it doesn't actually regenerate the backup header. |
Here is a boot with the above patch:
|
Dear all,
after sucessfully booting into Coreos (alpha (935.0.0), beta (899.5.0) or stable (835.11.0)) via PXE, I install with
coreos-install -d /dev/sda -c local-coreos-config.yml.
The installed OCZ-AGILITY3 SSD gets partitioned into sda1..4, sda6..7 and sda9. Perfect.
During the first initial boot, I receive an
Failed to
Generate new UUID for disk... 0-0000-0000-0000-000000001
. It does not matter which channel I have used. PXE is not an issue, as the same occurs after booting via USB or CD-ROM.The boot process finds the devices OCZ-AGILITY3 USR-A and ROOT and successfully checks the file system. It will reach target "Local File Systems". All partitions and file systems have
valid UUIDs. Are the UUIDs generated during startup again?
And from here it goes south and ends up in an emergency shell.
Attached you find the rdsosreport.txt recovered after fumbling around with ways to get it of the system:
rdsosreport.txt
Any hints or ideas are welcome.
Cheers
Carsten
The text was updated successfully, but these errors were encountered: