Also, change the same long string name between the single quotes in the grub search command that sets the root variable to "UUI" (or whatever) as well. Do this for each grub boot menu option (there were 3 menuentry locations in my grub.cfg file). In the file, change the default root-live:LABEL= setting of "CentOS-7-x86_64-LiveKDE-1511" (or whatever the super long label string name is) to "UUI" (or whatever your USB disk/device drive label string is).
I saved a copy of it first in, in case I messed something up. I suspect you can change it to whatever you want at this point (up to 11 characters), but I just left mine as "UUI".įor CentOS 7 and grub2, open the USB drive from within the Windows File Explorer, go to the EFI/BOOT directory, and edit the grub.cfg file. The USB disk/device label is in the text box at the top of the General tab. To see what your drive label setting should be, once the UUI (and probably UNetbootin?) program finishes formatting & writing your ISO image to the USB drive from Windows, open "This PC" (Windows 10 - used to be "My Computer" on older Windows), right click your USB drive, and select Properties on the context menu. So the fix is to find out what the label is for the Live USB drive you build in Windows, then open the final USB drive when UUI finishes building it in Windows and edit the grub config files with NotePad (doesn't screw up the DOS/Linux newlines), to rename the appropriate label name strings from the long "CentOS*" string to simply "UUI", or whatever label your USB drive happens to be. Everytime I used UUI, it put this label on the USB device.
I didn't look at the UUI source, but I'm guessing if the label is longer than 11 characters, it simply labels the USB drive "UUI" instead when it writes the ISO image file to it. Since the Windows ISO utilities format the USB drive as a FAT32 partition, and since FAT32 in Windows only allows a disk label of 11 characters max, the really long default disk labels assumed by the utility and used in the grub config files ("CentOS-6.7-x86_64-LiveDVD" and "CentOS-7-x86_64-LiveKDE-1511") are way too long to fit. For CentOS 6, the EFI/boot/boot圆4.conf and nf files were messed up. So for the CentOS 7 ISO image, it was writing a screwed up EFI/BOOT/grub.cfg file on the USB drive. Turns out UUI (and also UNetbooin I'll bet - although I never went back to it and checked) labels the FAT32 formatted USB drive with a label that does not match the label it uses on the kernel command in the grub/grub2 config files.
CENTOS ISO TO USB WINDOWS 10 WINDOWS 10
I ended up getting both the CentOS 6 & 7 ISO images to burn to a USB drive (2 separate ones) from Windows 10 using the UUI utility from pendrivelinux. localhost systemd: Received SIGRTMIN+21 from PID 402 (plymouthd). localhost systemd: Starting Dracut Emergency Shell. localhost dracut-initqueue: Warning: /dev/mapper/live-rw does not exist localhost dracut-initqueue: Warning: /dev/disk/by-label/CentOS-7-x86_64-LiveKDE-1511 does not exist localhost systemd: Received SIGRTMIN+20 from PID 402 (plymouthd). localhost dracut-initqueue: Warning: Could not boot. But at least CentOS 7 gave me the very nice emergency shell prompt to poke around, run "blkid" to see my actual /sdb1 USB disk label, mount my USB drive, and dump the rdsosreport.txt file and the redirected output of journalctl to it for later easy reading in Windows.Ĭode: Select all localhost dracut-initqueue: Warning: dracut-initqueue timeout - starting timeout scripts It crashed during boot as well, with the following messages. Sticking with the UUI Windows app, I tried the latest CentOS 7 LiveKDE ISO next. I saw lots of posts and problems similar to this over the past few years related to CentOS, Fedora, Debian and Ubuntu, tried the various fixes for disabling SELinux, BIOS changes (secure boot, UEFI settings), etc., again - nothing. Pid: 1, comm: init Not tainted 2.6.86_64 #1ĭrm_kms_helper: panic occured, switching back to text console Code: Select all Kernel panic - not syncing: Attempted to kill init!
0 kommentar(er)
