Fedup 17->18 won't boot, all partitions are GPT
Hi, I did a fedup from F17 to F18 on my work desktop. Now I get an infinite boot loop. Fdisk can't look at the partition table of /dev/sda because it has been coverted to GPT format (who did that?). As near as I can tell, the boot process fails after about 1 page of output near where "/" should be mounted. I can't see the error message because it reboots too quickly. Doing a rescue with an F17 bootable flash drive allows me to at least mount my /boot and / partitions, so I guess F17 understands the GPT conversion. It won't however, recognize the new system to do a boot sector repair. Should I try with an F18 bootable flash drive? Under the F17 debug prompt /dev/sda2 (boot) and /dev/sda4 (root) both give clean fsck checks. I appreciate any suggestions. kind regards, -- Rick Walker -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedup 17->18 won't boot, all partitions are GPT
On 12/07/13 10:20, Rick Walker wrote: I did a fedup from F17 to F18 on my work desktop. Now I get an infinite boot loop. Fdisk can't look at the partition table of /dev/sda because it has been coverted to GPT format (who did that?). As near as I can tell, the boot process fails after about 1 page of output near where "/" should be mounted. I can't see the error message because it reboots too quickly. Doing a rescue with an F17 bootable flash drive allows me to at least mount my /boot and / partitions, so I guess F17 understands the GPT conversion. It won't however, recognize the new system to do a boot sector repair. Should I try with an F18 bootable flash drive? Under the F17 debug prompt /dev/sda2 (boot) and /dev/sda4 (root) both give clean fsck checks. I appreciate any suggestions. When dealing with GPT partition tables, parted is probably the tool you want use as fdisk doesn't understand them. Somebody correct me if I'm wrong, but I think a non UEFI system cannot normally boot directly from a GPT partition, so often in addition to a GPT partition table, an MS-DOS (fdisk style) partition table is created which masks out the rest of the disk as being in use to avoid non-GPT aware software from stomping over your partitions. Providing your bootloader and OS understand GPT, then the system should boot. What does the output of "fdisk -l /dev/sda" show? I would expect it to look something like Device Boot Start End Blocks Id System /dev/sda1 1 625142447 312571223+ ee GPT Compare that to the output of "parted /dev/sda print". Mine for example is: Disk /dev/sda: 320GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 2097kB 1049kB bios_grub 2 2097kB 526MB 524MB ext4 ext4 boot 3 526MB 320GB 320GB lvm -- Ian Chapman. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedup 17->18 won't boot, all partitions are GPT
Hi Ian, > > I did a fedup from F17 to F18 on my work desktop. Now I get an > > infinite boot loop. Fdisk can't look at the partition table of > > /dev/sda because it has been coverted to GPT format (who did that?). Ian Chapman writes: > When dealing with GPT partition tables, parted is probably the tool you > want use as fdisk doesn't understand them. > > What does the output of "fdisk -l /dev/sda" show? I would expect it to > look something like > > Device Boot Start End Blocks Id System > /dev/sda1 1 625142447 312571223+ ee GPT Thanks for the comments, Ian. I checked with parted and have the same disk setup as you. I also can see my old partitions using the "parted /dev/sda print" command. I guess my grub setup got hosed somehow, and the GPT conversion is a red-herring. I'm downloading an F18 live image to try a rescue on the boot setup. An f17 image was unable to cope with the GPT conversion. After saying that it identified and mounted the old root partition (but "may have had some problems"), the mount point was null. Maybe F18 can fix itself. -- Rick Walker -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedup 17->18 won't boot, all partitions are GPT
On Fri, Jul 12, 2013 at 8:39 AM, Rick Walker wrote: > > Hi Ian, > >> > I did a fedup from F17 to F18 on my work desktop. Now I get an >> > infinite boot loop. Fdisk can't look at the partition table of >> > /dev/sda because it has been coverted to GPT format (who did that?). > > Ian Chapman writes: >> When dealing with GPT partition tables, parted is probably the tool you >> want use as fdisk doesn't understand them. >> >> What does the output of "fdisk -l /dev/sda" show? I would expect it to >> look something like >> >> Device Boot Start End Blocks Id System >> /dev/sda1 1 625142447 312571223+ ee GPT > > Thanks for the comments, Ian. I checked with parted and have the > same disk setup as you. I also can see my old partitions using > the "parted /dev/sda print" command. > > I guess my grub setup got hosed somehow, and the GPT conversion is a > red-herring. > > I'm downloading an F18 live image to try a rescue on the boot > setup. An f17 image was unable to cope with the GPT conversion. > After saying that it identified and mounted the old root > partition (but "may have had some problems"), the mount point was > null. Maybe F18 can fix itself. > > -- > Rick Walker > > Didn't parted have an X component once upon a time? Although I have used Linux for a very long time and am quite used to text environments, I love the visual (read lazy) based environments when / if available, considering I agree that text offers an incredible plethora of options over the GUI. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedup 17->18 won't boot, all partitions are GPT
On Thu, Jul 11, 2013 at 7:20 PM, Rick Walker wrote: > > Hi, > > I did a fedup from F17 to F18 on my work desktop. Now I get an infinite > boot loop. Fdisk can't look at the partition table of /dev/sda because > it has been coverted to GPT format (who did that?). > > As near as I can tell, the boot process fails after about 1 page of > output near where "/" should be mounted. I can't see the error message > because it reboots too quickly. > > Doing a rescue with an F17 bootable flash drive allows me to at least > mount my /boot and / partitions, so I guess F17 understands the GPT > conversion. It won't however, recognize the new system to do a boot > sector repair. Should I try with an F18 bootable flash drive? > > Under the F17 debug prompt /dev/sda2 (boot) and /dev/sda4 (root) > both give clean fsck checks. > > I appreciate any suggestions. > > kind regards, > -- > Rick Walker > > > It's not much help, but my solution would be to backup and install F18 from CD / other source, however, there might be a better solution coming from someone with a lot more knowledge. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
