cant upgrade F13 to F14

Jim Cromie jim.cromie at gmail.com
Thu Dec 9 16:40:44 UTC 2010


Anaconda is telling me I have a dirty partition, and to reboot cleanly,
which Ive done several times.  The broken aspect here is that
anaconda is complaining about /dev/sda1, which is the Dell Utility
partition, which should *not* be involved.

heres the partition table of the drive holding currrent F13 install

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf0000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           6       48163+  de  Dell Utility
/dev/sda2   *           7        1271    10156032    7  HPFS/NTFS
/dev/sda3            1271       62450   491423744    7  HPFS/NTFS
/dev/sda4           62450      121602   475132928    5  Extended
/dev/sda5           62451       62514      512000   83  Linux
/dev/sda6           62514      121602   474618880   8e  Linux LVM


Is this prob due to boot flag on sda2 ?
Grub has no problem booting sda2 or sda5

title Fedora (2.6.34.7-63.fc13.x86_64)
root (hd0,4)
kernel /vmlinuz-2.6.34.7-63.fc13.x86_64 ro root=/dev/mapper/vg_groucho-l
v_root rd_LVM_LV=vg_groucho/lv_root rd_LVM_LV=vg_groucho/lv_swap rd_NO_LUKS
rd_N
O_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc
KEYTABL
E=us rhgb quiet
initrd /initramfs-2.6.34.7-63.fc13.x86_64.img

title Windows 7
rootnoverify (hd0,1)
chainloader +1


Given that the problem is supposedly with the Dell Utility partition,
I regard this as a reportable bug in anaconda.
Concur ?
Any workarounds ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20101209/31691f01/attachment.html 


More information about the users mailing list