Dear Jim:<br><br>Please forgive me for not responding sooner. I began this reply the day you sent me the message and got sidetracked.<br><br>Thank you again for your lengthy, well thought out, consistent and technically<br>
sound response!<br><br>I apologize if my responses were not clear. I beg you for great forgiveness.<br><br>Again, all me methods I've used and you've suggested have been taken
<br>because I've been under the assumption that anaconda saw remnants<br>of past lvm or raid devices based upon the docs in the installation guide<br>and I believe in the release notes.<br><br>I thoroughly read the article at
<a href="http://www.issociate.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">www.issociate.de</a>. I found a slew of pointers<br>which I can possibly use in the future and I tried to use some of the mdadm
<br>command suggested there. however, since there are no physical partitions associated
<br>with the raid device /dev/md0 mdadm will not operate on that device. Moreover<br>the partitions originally associated with the device have been deleted.<br><br>I've run find on my udev directories looking for "md" but nothing appeared relative
<br>to raid devices.<br><br>I have also noticed a complete md0 tree located in /sys/block/md0 and I suspect
<br>that anaconda might be reading that and thinking that an raid device exists.<br><br>re: the 4GB split on files.<br>I'm assuming that was mentioned with the intent to burn to a DVD.<br>I don't have a DVD burner nor a CD burner on my linux box. My cd
<br>burner died a while back and I'm only using a CD reader. I only have<br>a CD burner on an older windows box.<br><br>Thanks for the info regarding the incremental label naming of paritions, i.e. /usr1 etc.<br><br>
Re: the reference to the f7-updates.img.<br>it apparently found it across the net when I specified it<br>on the command line since anaconda prompted me for the IP address<br>of this local machine along with the gateway and dns which were both my local
<br>router. I'm assuming that since I didn't receive an error after that that<br>the f7-updates.img file was used but I'm only guessing.<br><br>Again please forgive me. The fstab I included in the previous e-mail did not have label
<br>references for partitions on drive /dev/hdc or /dev/hdd even though partition labels<br>do exist for all parititions.<br><br>Well, I changed the physical device references for all partitions on /dev/hdc and /dev/hdd,
<br>neither of which have any OS software, and voila! I rebooted with the rescue<br>CD and I eventually received the install / upgrade window! Hmm. I think<br>there should be some mention in anaconda as an informational message
<br>or as an error message flagging that as a potential "non-install" issue.<br><br>The upgrade continued from there until it reached the selinux-policy-targeted rpm<br>at which point it appeared to have stalled. I checked the drive light and apparently
<br>there was disk activity and I assumed that selinux-policy-targeted was changing file<br>attributes or assembling policies for selinux, so I waited. I was tempted to do<br>a hard reset but I resisted. 1 1/2 hours had already passed and the install was
<br>not finished yet. More than 2 hours later and the install finally finished. The machine<br>rebooted and I received an error, in that it couldn't find my F7 install. So I rebooted<br>again and explicitly selected the F7 option from the grub boot menu (there was only
<br>one other entry, that of the FC6) and the F7 boot continued from there. I was then<br>presented from pirut with over 975 upgrade packages. So I spent most of Sunday<br>wading through those. I'm now checking through the package manager to ensure
<br>check for other installs. I still have to wade through my rpm list for legacy fc6 rpms<br>that F7 didn't remove.<br><br>Thanks very much for your help.<br><br>Regards,<br>Lou<br><br><br><div><span class="gmail_quote">
On 6/7/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>> Dear Jim:<br>
>
<br>> Please forgive me for NOT including fstab. I thought I had but I did<br>> not. Since I am currently not at my machine and "out of the<br>> building" I cannot upload my fstab, however, I can asure you that all
<br>> devices referenced in fstab are labeled as well as any partition on<br>> the disk.<br><br>I think that you sent it before. I remember all of the d# entries. It<br>might be good to use e2label and add meaningful labels to the
<br>mountpoints, evwn if you use d and the number. That way if there is some<br>change in the future affecting device naming, you will be one step safer.</blockquote><div><br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
><br>> I still see remnants of raid, i.e. /dev/md0 continues to be created<br>> upon reboot. I was #fedora irc yesterday speaking with someone who<br>> seem quite knowledgeable about these issue and he suggested to comment
<br>> out the template reference to the md device in<br>> /dev/makedev.d/01linux-2.6.??? /dev/md0 was recreated upon reboot<br>> again.<br><br>Sorry, I misunderstood you. I thought the md device was gone after
<br>
running the gauntlet of disk management utilities.<br><br>This link briefly talks about some md management and udev. I only see<br>topics which may clear up what raid is doing.<br><br><a href="http://www.issociate.de/board/post/429713/removed_disk_&&_md-device.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.issociate.de/board/post/429713/removed_disk_&&_md-device.html</a><br><br><br>The next article sounds informative to familiarize one regarding raid. I<br>will probably read the article in depth. There has to be some clue as to
<br>how to prevent the md0 at zero byte from lingering around the disk.<br><br><br>><br>> re: the confusing in the installer. I thought about that when I saw<br>> the FC6 had labeled /boot as /boot1 and /usr as /usr1 so I relabeled
<br>> those /boot1->/boot and /usr1->/boot and nada. Didn't fix it.<br><br>Usually that happens if you have another installation on the same<br>computer. I have had several /1, /boot1 entries on my multi-version
<br>Fedora computers. As you found out, only the references to whatever it<br>is called matters. If I use e2label, I usually label using a variety of<br>names.<br><br><br><br>><br>> /etc/fstab<br>><br>> <snip>
<br>><br>> LABEL=/ / ext3 defaults 1 1<br>>LABEL=/boot /boot ext3 defaults 1 2<br> devpts /dev/pts devpts gid=5,mode=620 0 0
<br>>tmpfs /dev/shm tmpfs defaults 0 0<br>>LABEL=/home /home ext3 defaults 1 2<br>>proc /proc proc defaults 0 0<br>
>sysfs /sys sysfs defaults 0 0
<br>>LABEL=/usr /usr ext3 defaults 1 2<br>>LABEL=SWAP-hda5 swap swap defaults 0 0<br>><br>> /dev/hdc1 /mnt/d1 ext3 defaults 0 0
<br> >/dev/hdc2 /mnt/d2 ext3 defaults 0 0<br>>/dev/hdc3 /mnt/d3 ext3 defaults 0 0<br>>/dev/hdd1 /mnt/d4 ext3 defaults 0 0<br>>/dev/hdd2 /mnt/d5 ext3 defaults 0 0
<br> >/dev/hdd3 /mnt/d6 ext3 defaults 0 0<br>>/dev/hdd4 /mnt/d7 ext3 defaults 0 0<br>><br>> </snip><br>><br>><br>> I just tried the f7-updates.img
using: linux<br>> updates=http:/people.redhat.com/clumens/f7-updates.img<br>><br>> and anaconda prompted for local ip and appeared to retrieve the<br>> image.<br>><br>> However, that apparently didn't fix the problem. After it searched
<br>> for previous releases I received the "Partition Type" screen with no<br>> screen to select the type of install, i.e. install or upgrade.<br><br>I was not sure if your problem would be fixed by the updated image.
<br>Briefly reading the explanation on how to use the updated image it seems<br>you launch the DVD and choose the additional updates selection. I was<br>thinking that it was just a boot disk which would ask for file location.
<br><br>><br>> I'm at my wits end. I'm attempting to move /etc /home /usr/local<br>> /var/www but thinking that might have to reformat but I don't know if<br>> I have the space to move the files.
<br>
<br>Someone mentioned tarring up the information, splitting them into 4 GB<br>files awhile back or something along those lines.<br><br>><br>> Any other ideas? Ideas about removing that /dev/md0 device?<br><br>The installer anaconda incorporates disk druid which I believe you could
<br>remove the raid element. I don't know if you could remove the md and not<br>mess up your system by the installer going on after the disk information<br>is saved or not. I assume the installer will go ahead and overwrite or
<br>copy to the same locations.<br><br>Regarding ideas to gt rid of raid, I have no ideas other than just don't<br>do Raid in the first place. A David Gilmour song come to mind. "No Way<br>out" .. (In for good)
<br><br>><br>> Any help would be appreciated.<br>><br>> Thanks again. Regards, Lou<br>><br>><br>> - What about you labels in fstab? would they confuse the installer?<br>> Are they LABEL references or device references?
<br>><br><br>The /dev/hdc# and /dev/hdd# entries could confuse the installer.<br><br>I would backup important information and then try a yum upgrade to FC7.<br>I did one and it worked out OK to allow what used to work to still work
<br>after upgrade. I dd not need to reconfigure the system.<br><br>Maybe someone familiar with raid will chime in. I seem to remember<br>something on the test list being discussed regarding a command to issue<br>to get rid of raid. You might ask on the test ist or search the archive
<br>for information.<br><a href="http://www.google.com/search?hl=en&q=site%3Awww.redhat.com%2Farchives%2Ffedora-test-list+raid&btnG=Search" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.google.com/search?hl=en&q=site%3Awww.redhat.com%2Farchives%2Ffedora-test-list+raid&btnG=Search
</a><br><br>Jim<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>