Thank's Jim for responding to my post.<br><br>Please forgive me for not posting details sooner.<br><br>In the interim I've done a number of things none of which were successful<br>in getting F7 to prompt for and install or upgrade options.
<br><br>I did some more fiddiling with both parted and fdisk. I also noticed some<br>unusual behaviour between the two programs. I printed the parition<br>table an noticed that /dev/hdd4 was displayed with an ID of 0 which indicates
<br>empty. However, i seem to recall that last year when I was fiddiing with software<br>raid that /dev/hdd4, the extended parition, contained hdd5 and hdd6 which were used to test <br>software raid. So I added another primary parition on /dev/hdd4 to clear that entry or
<br>any remnants of old info from the software raid. I ran sfdisk -l and no more reports of<br>/dev/md0. <br><br>However, that didn't solve the problem. I still do not see any screen prompting me<br>for and install or upgrade after I received the Searching for installation or before the "Partition Type" screen.
<br><br>This morning I upgraded 29 rpms on FC6 including the kernel which I thought might help<br>the situation. Nada. I've attempted to remove the /dev/md0 device by deleting it via rm.<br>Of course it was deleted however, upon reboot the device was again present.
<br><br>I checked to see if the two daemons associated with the mdadm package, mdmonitor and mdrdp(sp?), are running and they are off.<br><br>The instructions you included in your post only removes the "physical" drive or partition
<br>from the raid array denoted by /dev/md<num>. I checked the docs and mdadm doesn't<br>include any method for deleting a raid array. (maybe I missed something.)<br><br>I found something yesterday in that mdadm has "misc" commands one of which is
<br>a zero superblock on an attached raid parition. Another individual was having<br>similar problems as I had described and apparently he used that to completely<br>zero the superblock and anaconda presented the upgrade screen which he did
<br>not receive prior to these raid remnants.<br><br>Unfortunately, I had deleted those two old partitions, as well as the extended partition<br>and then just added a primary fourth partition on the /dev/hdd drive, again assuming
<br>that the software raid/lvm remnants were causing the problem. However, since<br>partition 4,5 and 6 no longer exist mdadm will no longer work on those paritions.<br><br>I then used gpart to see if it would detect deleted partitions. Nada.
<br><br>Any other ideas as to what to do.<br><br>Thank you.<br><br>Regards,<br>Lou Spironello<br><br><br>I've included more config files and output below.
<br><br>/boot/grub/grub.conf<br><snip><br><br>default=0<br>timeout=5<br>splashimage=(hd0,0)/grub/splash.xpm.gz<br>hiddenmenu<br>#title Fedora Core (
2.6.20-1.2944.fc6xen)<br># root (hd0,0)<br># kernel /xen.gz-
2.6.20-1.2944.fc6<br># module /vmlinuz-2.6.20-1.2944.fc6xen ro root=LABEL=/ rhgb quiet max_loop=16<br># module /initrd-2.6.20-1.2944.fc6xen.img<br>title Fedora Core (2.6.18-1.2798.fc6)<br> root (hd0,0)
<br>
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/ rhgb quiet max_loop=16<br> initrd /initrd-2.6.18-1.2798.fc6.img<br><br></snip><br>==========<br># sfdisk -l<br><br>
<snip><br>
<br>Disk /dev/hda: 19929 cylinders, 255 heads, 63 sectors/track<br>Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0<br><br> Device Boot Start End #cyls #blocks Id System<br>/dev/hda1 * 0+ 24 25- 200781 83 Linux
<br>/dev/hda2 25 6086 6062 48693015 83 Linux<br>/dev/hda3 6087 12166 6080 48837600 83 Linux<br>/dev/hda4 12167 19928 7762 62348265 5 Extended<br>/dev/hda5 12167+ 12410 244- 1959898+ 82 Linux swap / Solaris
<br>/dev/hda6 12411+ 19928 7518- 60388303+ 83 Linux<br><br>Disk /dev/hdc: 116301 cylinders, 16 heads, 63 sectors/track<br>Units = cylinders of 516096 bytes, blocks of 1024 bytes, counting from 0<br><br> Device Boot Start End #cyls #blocks Id System
<br>/dev/hdc1 0+ 40634 40635- 20480008+ 83 Linux<br>/dev/hdc2 40635 81269 40635 20480040 83 Linux<br>/dev/hdc3 81270 116300 35031 17655624 83 Linux<br>/dev/hdc4 0 - 0 0 0 Empty
<br><br>Disk /dev/hdd: 238216 cylinders, 16 heads, 63 sectors/track<br>Units = cylinders of 516096 bytes, blocks of 1024 bytes, counting from 0<br><br> Device Boot Start End #cyls #blocks Id System<br>/dev/hdd1 0+ 194 195- 98248+ 83 Linux
<br>/dev/hdd2 195 116452 116258 58594032 83 Linux<br>/dev/hdd3 116453 209265 92813 46777752 83 Linux<br>/dev/hdd4 209266 238215 28950 14590800 83 Linux<br></snip><br>
==========<br>
# blkid<br>
<br>
<snip><br># blkid<br>/dev/hdb: LABEL="rescue Disc" TYPE="iso9660" <br>/dev/hdd3: LABEL="hdd3" UUID="218acaa4-4778-4a9b-be33-18f3b3646396" SEC_TYPE="ext2" TYPE="ext3"
<br>/dev/hdd2: LABEL="hdd2" UUID="f28f151c-5963-48be-8281-1b674094c428" SEC_TYPE="ext2" TYPE="ext3" <br>/dev/hdd1: LABEL="hdd1" UUID="df29a431-ec30-4114-8202-035b0f6f3114" SEC_TYPE="ext2" TYPE="ext3"
<br>/dev/hdc3: LABEL="hdc3" UUID="b54505bd-c8c3-401a-8708-c72b38552bb8" SEC_TYPE="ext2" TYPE="ext3" <br>/dev/hdc1: LABEL="hdc1" UUID="d81d7541-80cf-404d-bc0d-21fda2473752" SEC_TYPE="ext2" TYPE="ext3"
<br>/dev/hdc2: LABEL="hdc2" UUID="424d61f6-c4e9-43cb-bbf8-51eb38eea3b5" SEC_TYPE="ext2" TYPE="ext3" <br>/dev/hda6: LABEL="/home" UUID="9122da36-fcf9-482c-978e-14219f46d0ac" SEC_TYPE="ext2" TYPE="ext3"
<br>/dev/hda5: LABEL="SWAP-hda5" TYPE="swap" <br>/dev/hda3: LABEL="/usr" UUID="7bdfe636-fa05-4b00-8e64-1a7ca3cb41a9" SEC_TYPE="ext2" TYPE="ext3" <br>/dev/hda2: LABEL="/" UUID="38e17b63-7a70-4d26-9b7c-e5cdda9064a1" SEC_TYPE="ext2" TYPE="ext3"
<br>/dev/hda1: LABEL="/boot" UUID="d24b169a-8d91-4e9c-9821-205ac9cf0b42" SEC_TYPE="ext2" TYPE="ext3" <br>/dev/hdd4: LABEL="hdd4" UUID="c11b4d0e-b30a-492b-9303-982513fa7c38" SEC_TYPE="ext2" TYPE="ext3"
<br></snip><br><br><br><div><span class="gmail_quote">On 6/4/07, <b class="gmail_sendername">Jim Cornette</b> <<a href="mailto:fc-cornette@insight.rr.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
fc-cornette@insight.rr.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Lou Spironello wrote:<br>> -----BEGIN PGP SIGNED MESSAGE-----<br>> Hash: SHA1<br>><br>> Jim Cornette wrote:<br>>> Lou Spironello wrote:<br>>>> Thanks Jim for the idea.<br>>>><br>>>> Did that and still no option to install/upgrade, or detection of
<br>>>> fc6 before the partition screen.<br>>>><br>>>> Regards, Lou<br>>>><br>>>><br>>> Could it be that for some reason the installer does not encounter a<br>>> fedora-release package so it refuses to upgrade the system. This
<br>>> happened to me once and no upgrade option was provided.<br>>><br>>><br>>> So check your installation for upgrade and verify that<br>>> fedora-release is installed. If it is installed and verifies, it
<br>>> must be something to do with not recognizing your hard disk, so<br>>> back to the hunt.<br>>><br>>> Jim<br>>><br>> Parted shows the culprit at the bottom:<br>><br>> (parted) print devices
<br>> /dev/hda (164GB)<br>> /dev/hdc (60.0GB)<br>> /dev/hdd (123GB)<br>> /dev/md0 (0.00B)<br><br>I'm not familiar with setting up raid or removing raid. Would rm<br>/dev/md0 remove the raid information from the disk? Or could you choose
<br>the md0 device using the select feature of parted?<br><br>I'm curious and this is not at all recommended advice.<br><br>Jim<br><br><br>Excerpt from info parted:<br><br>2.4.15 select<br>-------------<br><br> -- Command: select DEVICE
<br> Selects the device, DEVICE, for Parted to edit. The device can be<br> a Linux hard disk device, a partition, a software RAID device or<br> LVM logical volume.<br><br> Example:<br><br> (parted) select /dev/hdb
<br><br>--<br>fedora-list mailing list<br><a href="mailto:fedora-list@redhat.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">fedora-list@redhat.com</a><br>To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://www.redhat.com/mailman/listinfo/fedora-list
</a><br></blockquote></div><br>