Description of problem: Incorrect detection of partition information, and subsequently wants to partition the fedora core 6, erasing it, rather than upgrading it. Additionally, seems to get through to the partition screen if you click retry, then has a further error. Version-Release number of selected component (if applicable): rawhide 2007-04-17 08:31 pxeboot ftp install How reproducible: yes: hp compaq nx6320 Steps to Reproduce: 1. boot from network pxeboot 2. ftp method Actual results: I need to redo to get actual message... Expected results: Should detect existing working operating partition info from the disk, and offer to upgrade. Additional info:
Created attachment 152809 [details] commonly requested info {bug 229704}
Created attachment 152811 [details] hp compaq nx6320 sata disk fc6 lspci
Created attachment 152812 [details] hp compaq nx6320 sata disk fc6 lspcmcia
Created attachment 152813 [details] hp compaq nx6320 sata disk fc6 dmesg
The message is: Warning The partition table on device sda was unreadable. To create new partition it must be initialized, causing the loss of ALL DATA on this drive. This operation will override any previous isntallation choices about which drives to ignore. Would you like to initialize this drive, erasing ALL DATA ? No {default- thankgod} Yes. --- click No Searching for fedora core installations back to warning dialog Click No Create custom layout | next dialog: No Drives Found An error has occurred - no valid device were found on which to create new file systems. Please check your hardware for the cause of this problem. === This second message should be more like: ~"we have a bug that meant anaconda could not detect and mount the /dev/sda device. Please submit a bug report at bugzilla.redhat.com" This is a fedora core 6 system. The partitions are ntfs fat32 boot, extended, root swap etc. The NTFS partition was downsized with a circa 2006 gparted.
Created attachment 152820 [details] hp compaq nx6320 sata disk f devel lspci
Created attachment 152821 [details] hp compaq nx6320 sata disk f devel dmesg
Can you try again with loglevel=debug as a boot parameter? Attach /tmp/anaconda.log to this bug report.
Created attachment 152882 [details] with loglevel=debug as a boot parameter? Attach /tmp/anaconda.log with loglevel=debug boot param on a side note: the rescue cd set to ftp install fails as well (cant mount the downloaded img), but that may be a separate issue.
This is odd. I cannot reproduce the problem here. Can you try passing the 'nodmraid' boot option to the installer and see if the problem persists?
Created attachment 153071 [details] rescue iso installer wants to initialize disk, same failure {nodmraid not set} 2007-04-19 release 2! -rw-r--r-- 1 root root 103387136 Apr 19 14:21 FC-development-i386-rescuecd.iso -rw-r--r-- 1 root root 5779339 Apr 19 14:19 initrd.img -rw-r--r-- 1 root root 270 Apr 19 14:19 README -rw-r--r-- 1 root root 75 Apr 19 14:21 SHA1SUM -rw-r--r-- 1 root root 1919988 Apr 19 14:19 vmlinuz
Created attachment 153072 [details] installer log with: loglevel=debug nodmraid The nodmraid parameter does not make any difference to the issue.
Created attachment 153073 [details] fdisk -l
Created attachment 153074 [details] lsmod both the logs are from vt2 when installer has excepted.
Didn't realise I needed to comment to unset need info...
Cna you provide what parted thinks the disk looks like? Since that's almost certainly where the problem lies
Created attachment 153845 [details] parted | fdisk -l | fdisc /dev/sda x Notice that fdisk is happy about the partition scheme, and it is what is actually used for this dual boot winxp+fc6 machine. The original winxp ntfs partition was shrunk with gparted, and the other partitions created. There is no other visible side effect from parted from not liking it.
Created attachment 153846 [details] dd sda first 1024 bytes
I've created your partition layout exactly as you specify both by hand and by using the dd image you provided. In rawhide (soon to F-8), parted is not showing any errors when reading this disk label. The partitions are all detected and appear in anaconda just fine. I'm marking this as a dupe of bug #229745 because it appears to be the exact same problem. I patched parted to fix that bug and that's what I'm using here to try to reproduce your problem. *** This bug has been marked as a duplicate of 229745 ***