On Fri, Jul 12, 2013 at 8:39 AM, Rick Walker <walker@xxxxxxxxxxxxxx> 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 <packages@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx 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
