Re: Hardware upgrade -> Volume Group "VolGroup00" not found. [SOLVED]
Richard Shaw wrote: > On Sun, Mar 8, 2009 at 10:11 AM, Mikkel L. Ellertson >>> >> Well, you can edit the rules by hand. But it is just as easy to >> delete them. Udev will the re-create them on boot for the new >> hardware. The first NIC it finds will be eth0, the first CD/DVD with >> be cdrom and cdrom0, etc... >> >> Mikkel > > Well since we're talking about a tool that doesn't exist yet, maybe > the yet to exist program hw-preupgrade could just clear all the system > specific rules out as a standard practice? > > Richard > It would be easy enough to do. rm /etc/udev/rules.d/*-persistent-*.rules Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found. [SOLVED]
On Sun, Mar 8, 2009 at 10:11 AM, Mikkel L. Ellertson wrote: > Richard Shaw wrote: >> On Sun, Mar 8, 2009 at 9:49 AM, Mikkel L. Ellertson >> wrote: >>> Richard Shaw wrote: Some other thoughts about hardware upgrades: Both machines I upgraded the ethernet changed to "eth1" but I'm not sure where to get rid of the old settings but it's working so I may leave it alone. >>> Udev keeps tract of some hardware. It is mainly so things like >>> network interfaces and CD/DVD drives retain the same label when you >>> add new hardware. (It is a pain when you add another NIC, and it >>> becomes eth0...) You can fix it by deleting the >>> *-persistent-*.rules. For NICs, it is 70-persistent-net.rules. >>> Unless you transfered CD/DVD drives with the hard drives, you are >>> going to find that the CD/DVD symlinks are wrong as well. >>> Maybe there could be some sort of hardware upgrade helper to help with this process? It could install itself on your system as a rescue image to help walk you though the process like preupgrade but for hardware. >>> That sounds like a good idea. Maybe an option in the rescue mode to >>> rebuild the initrd image. Also a command in /sbin to delete the >>> persistent rules... >>> >>> Mikkel >> >> Thanks, I forgot about that. I had a similar thing happen when I >> upgraded DVD burners and completely forgot about udev rules. Hmm... >> along with a hw version of preupgrade maybe a udev device editor would >> be nice too? >> >> Richard >> > Well, you can edit the rules by hand. But it is just as easy to > delete them. Udev will the re-create them on boot for the new > hardware. The first NIC it finds will be eth0, the first CD/DVD with > be cdrom and cdrom0, etc... > > Mikkel Well since we're talking about a tool that doesn't exist yet, maybe the yet to exist program hw-preupgrade could just clear all the system specific rules out as a standard practice? Richard -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found. [SOLVED]
Richard Shaw wrote: > On Sun, Mar 8, 2009 at 9:49 AM, Mikkel L. Ellertson > wrote: >> Richard Shaw wrote: >>> Some other thoughts about hardware upgrades: >>> >>> Both machines I upgraded the ethernet changed to "eth1" but I'm not >>> sure where to get rid of the old settings but it's working so I may >>> leave it alone. >>> >> Udev keeps tract of some hardware. It is mainly so things like >> network interfaces and CD/DVD drives retain the same label when you >> add new hardware. (It is a pain when you add another NIC, and it >> becomes eth0...) You can fix it by deleting the >> *-persistent-*.rules. For NICs, it is 70-persistent-net.rules. >> Unless you transfered CD/DVD drives with the hard drives, you are >> going to find that the CD/DVD symlinks are wrong as well. >> >>> Maybe there could be some sort of hardware upgrade helper to help with >>> this process? It could install itself on your system as a rescue image >>> to help walk you though the process like preupgrade but for hardware. >>> >> That sounds like a good idea. Maybe an option in the rescue mode to >> rebuild the initrd image. Also a command in /sbin to delete the >> persistent rules... >> >> Mikkel > > Thanks, I forgot about that. I had a similar thing happen when I > upgraded DVD burners and completely forgot about udev rules. Hmm... > along with a hw version of preupgrade maybe a udev device editor would > be nice too? > > Richard > Well, you can edit the rules by hand. But it is just as easy to delete them. Udev will the re-create them on boot for the new hardware. The first NIC it finds will be eth0, the first CD/DVD with be cdrom and cdrom0, etc... Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found. [SOLVED]
On Sun, Mar 8, 2009 at 9:49 AM, Mikkel L. Ellertson wrote: > Richard Shaw wrote: >> >> Some other thoughts about hardware upgrades: >> >> Both machines I upgraded the ethernet changed to "eth1" but I'm not >> sure where to get rid of the old settings but it's working so I may >> leave it alone. >> > Udev keeps tract of some hardware. It is mainly so things like > network interfaces and CD/DVD drives retain the same label when you > add new hardware. (It is a pain when you add another NIC, and it > becomes eth0...) You can fix it by deleting the > *-persistent-*.rules. For NICs, it is 70-persistent-net.rules. > Unless you transfered CD/DVD drives with the hard drives, you are > going to find that the CD/DVD symlinks are wrong as well. > >> Maybe there could be some sort of hardware upgrade helper to help with >> this process? It could install itself on your system as a rescue image >> to help walk you though the process like preupgrade but for hardware. >> > That sounds like a good idea. Maybe an option in the rescue mode to > rebuild the initrd image. Also a command in /sbin to delete the > persistent rules... > > Mikkel Thanks, I forgot about that. I had a similar thing happen when I upgraded DVD burners and completely forgot about udev rules. Hmm... along with a hw version of preupgrade maybe a udev device editor would be nice too? Richard -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found. [SOLVED]
Richard Shaw wrote: > > Some other thoughts about hardware upgrades: > > Both machines I upgraded the ethernet changed to "eth1" but I'm not > sure where to get rid of the old settings but it's working so I may > leave it alone. > Udev keeps tract of some hardware. It is mainly so things like network interfaces and CD/DVD drives retain the same label when you add new hardware. (It is a pain when you add another NIC, and it becomes eth0...) You can fix it by deleting the *-persistent-*.rules. For NICs, it is 70-persistent-net.rules. Unless you transfered CD/DVD drives with the hard drives, you are going to find that the CD/DVD symlinks are wrong as well. > Maybe there could be some sort of hardware upgrade helper to help with > this process? It could install itself on your system as a rescue image > to help walk you though the process like preupgrade but for hardware. > That sounds like a good idea. Maybe an option in the rescue mode to rebuild the initrd image. Also a command in /sbin to delete the persistent rules... Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found. [SOLVED]
On Thu, Mar 5, 2009 at 10:23 PM, Richard Shaw wrote: > This is the second time this has happened to me. The first time was > after a hardware upgrade on the computer I'm using right now, however, > it was an F8 system so instead of preupgrade I decided a fresh install > was in order, no big deal. > > This time it's with my Myth Box running F10 and if I don't fix this > quickly the wife is going to kill me. Why does a hardware change (new > MB) cause this problem? Shouldn't it be able to find the volume group > regardless? > > In my previous situation a livecd could find the volume group but the > installed system could not and I suspect the same will happen this > time but I am creating a livecd just to be sure. > > Any troubleshooting ideas? > > Thanks, > Richard > > Old System: > AMD Sempron 64 3100+ > Cheap nForce3 MB > > New(er) system: > AMD Athlon X2 5200+ > Gigabyte AMD 770 chipset. MB Ok, the initrd was the culprit as both Mikkel and I suspected even though I still don't know why the initrd I copied from my working system which had identical hardware specs didn't work. If you ever need to rebuild an initrd from a broken system using a rescue disk or livecd/usb system there are a couple of things you need to do before you can successfully build an initrd from a chroot environment. The plain chroot environment does not map things like /dev /sys /proc which mkinitrd depends on. I'm not sure if every one of these steps is absolutely needed but it worked for me. Also, I'm going to break the steps down a lot for those that find their way here from google. 1. Boot livecd/usb system (rescue boot from an install CD/DVD should work as well). 2. Open terminal or console and run "su" for root. 3. Mount your root partition or logical volume (in my case VolGroup00/LogVol00) 3a. cd /mnt 3b. mkdir sysimage 3c. mount /dev/VolGroup00/LogVol00 ./sysroot 4. Mount your boot partition: (In my case /dev/sdb1) 4a. mount /dev/sdb1 ./sysroot/boot All the above I already knew, here is where it got interesting (and frustrating getting to this point): 5. Mount w/ bind the /dev from your rescue system to your problem system 5a. mount --bind /dev ./sysroot/dev 6. Go into the chroot environment 6a. chroot sysroot 7. Mount /proc and /sys 7a. mount /proc 7b. mount /sys 8. Now we should be ready to run mkinitrd 8a. cd /boot 8b. mkinitrd -v -f initrd-$(kver).img $(kver) # where $(kver) is the full kernel name (i.e. 2.6.27.19-170.2.35.fc10_x86_64) or something like that Make sure you update grub.conf if you use an initrd name that's not already setup in it. Some other thoughts about hardware upgrades: Both machines I upgraded the ethernet changed to "eth1" but I'm not sure where to get rid of the old settings but it's working so I may leave it alone. Maybe there could be some sort of hardware upgrade helper to help with this process? It could install itself on your system as a rescue image to help walk you though the process like preupgrade but for hardware. Richard -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found.
On Fri, Mar 6, 2009 at 10:22 AM, Richard Shaw wrote: > On Fri, Mar 6, 2009 at 8:37 AM, Mikkel L. Ellertson > wrote: >> Richard Shaw wrote: >>> >>> Hmm. I saw some responses like that, however, my current liveusb >>> is i386 and the install is x86_64. I tried bascially a full copy of my >>> working system's /boot which was actually used to boot on THAT >>> hardware until yesterday and it had the same issue. >>> >>> i.e. New HW -> My Desktop, My old Desktop HW -> MythBox. >>> >>> So the initrd I copied over to it was actually used to boot on that >>> very same hardware. >>> >>> I'll have to re download F10 x86_64 as I had to delete it for space a >>> while ago. I'll try mkinitrd but I have some doubts, unless someone >>> can find fault with copying over a working /boot (which was used on >>> that specific hardware previously). >>> >>> Thanks, >>> Richard >>> >> Grub loads the kernel and initrd from /boot using the BIOS, and the >> turns control over to the kernel. So the fact that the kernel loads >> from /boot does not say anything about the initrd having the drivers >> to access the hard drive. >> >> Mikkel > > Well, maybe I didn't explain what I did good enough. I copied all the > files from My desktop computer's /boot to the /boot of the problem > machine. Those boot files are the EXACT same boot files (including the > initrd) used until yesterday to successfully boot the problem machine. > > Basically I did a roll down hardware upgrade. I got new desktop > hardware (but kept my HD) and pushed my old desktop HW to the MythBox > (but kept the same HD). So the hard drives have effectively stayed > stationary while all the other hardware changed. By copying the /boot > from my desktop HD to my Myth HD I'm effectively using the same boot > files (kernel, initrd, etc) that were used to successfully boot the > machine only a day ago. > > That being said I have the 64bit live cd downloading at home now and > will try mkinitrd this evening. Ok, almost there... I don't seem to be able to get mkinitrd to work. I tried "mkinitrd -v -f initrd-2.6.27.16 2.6.27.16" and I didn't get any output either on the screen or in a created file. In desparation, after doing a chroot I tried yum erase/install the kernel. It borked GRUB which I've been able to fix for the most part. It still dumps me to the GRUB> prompt but I can root (hd0,0), configfile /grub/grub.conf and it will try to boot. I think doing the yum kernel install in a chroot enviornment somehow borked plymouth too. I get all the standard kernel output but it pauses at something like "loading keymap /some/dir/us/somefile.map" and just sits. When I don't remove "rhgb", I get some error about not being able to find the images or something like that which I presume is plymouth trying to do a full graphical boot. It looks like I've fixed it being able to find my volume group but caused a few more problems in the process. Any ideas? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found.
On Fri, Mar 6, 2009 at 8:37 AM, Mikkel L. Ellertson wrote: > Richard Shaw wrote: >> >> Hmm. I saw some responses like that, however, my current liveusb >> is i386 and the install is x86_64. I tried bascially a full copy of my >> working system's /boot which was actually used to boot on THAT >> hardware until yesterday and it had the same issue. >> >> i.e. New HW -> My Desktop, My old Desktop HW -> MythBox. >> >> So the initrd I copied over to it was actually used to boot on that >> very same hardware. >> >> I'll have to re download F10 x86_64 as I had to delete it for space a >> while ago. I'll try mkinitrd but I have some doubts, unless someone >> can find fault with copying over a working /boot (which was used on >> that specific hardware previously). >> >> Thanks, >> Richard >> > Grub loads the kernel and initrd from /boot using the BIOS, and the > turns control over to the kernel. So the fact that the kernel loads > from /boot does not say anything about the initrd having the drivers > to access the hard drive. > > Mikkel Well, maybe I didn't explain what I did good enough. I copied all the files from My desktop computer's /boot to the /boot of the problem machine. Those boot files are the EXACT same boot files (including the initrd) used until yesterday to successfully boot the problem machine. Basically I did a roll down hardware upgrade. I got new desktop hardware (but kept my HD) and pushed my old desktop HW to the MythBox (but kept the same HD). So the hard drives have effectively stayed stationary while all the other hardware changed. By copying the /boot from my desktop HD to my Myth HD I'm effectively using the same boot files (kernel, initrd, etc) that were used to successfully boot the machine only a day ago. That being said I have the 64bit live cd downloading at home now and will try mkinitrd this evening. Richard -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found.
Richard Shaw wrote: > > Hmm. I saw some responses like that, however, my current liveusb > is i386 and the install is x86_64. I tried bascially a full copy of my > working system's /boot which was actually used to boot on THAT > hardware until yesterday and it had the same issue. > > i.e. New HW -> My Desktop, My old Desktop HW -> MythBox. > > So the initrd I copied over to it was actually used to boot on that > very same hardware. > > I'll have to re download F10 x86_64 as I had to delete it for space a > while ago. I'll try mkinitrd but I have some doubts, unless someone > can find fault with copying over a working /boot (which was used on > that specific hardware previously). > > Thanks, > Richard > Grub loads the kernel and initrd from /boot using the BIOS, and the turns control over to the kernel. So the fact that the kernel loads from /boot does not say anything about the initrd having the drivers to access the hard drive. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found.
On Fri, Mar 6, 2009 at 6:29 AM, Mikkel L. Ellertson wrote: > Richard Shaw wrote: >> This is the second time this has happened to me. The first time was >> after a hardware upgrade on the computer I'm using right now, however, >> it was an F8 system so instead of preupgrade I decided a fresh install >> was in order, no big deal. >> >> This time it's with my Myth Box running F10 and if I don't fix this >> quickly the wife is going to kill me. Why does a hardware change (new >> MB) cause this problem? Shouldn't it be able to find the volume group >> regardless? >> >> In my previous situation a livecd could find the volume group but the >> installed system could not and I suspect the same will happen this >> time but I am creating a livecd just to be sure. >> >> Any troubleshooting ideas? >> >> Thanks, >> Richard >> >> Old System: >> AMD Sempron 64 3100+ >> Cheap nForce3 MB >> >> New(er) system: >> AMD Athlon X2 5200+ >> Gigabyte AMD 770 chipset. MB >> > Chances are, your disk controller changed with the change of > motherboards. This has been covered a couple of times on this list. > > The fix is fairly simple - build a new initrd with the drivers for > the new motherboard. You can do this by booting with the install > media and using the rescue mode. Then chroot to the mounted root > directory, and run mkinitrd. > > Mikkel Hmm. I saw some responses like that, however, my current liveusb is i386 and the install is x86_64. I tried bascially a full copy of my working system's /boot which was actually used to boot on THAT hardware until yesterday and it had the same issue. i.e. New HW -> My Desktop, My old Desktop HW -> MythBox. So the initrd I copied over to it was actually used to boot on that very same hardware. I'll have to re download F10 x86_64 as I had to delete it for space a while ago. I'll try mkinitrd but I have some doubts, unless someone can find fault with copying over a working /boot (which was used on that specific hardware previously). Thanks, Richard -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found.
Richard Shaw wrote: > This is the second time this has happened to me. The first time was > after a hardware upgrade on the computer I'm using right now, however, > it was an F8 system so instead of preupgrade I decided a fresh install > was in order, no big deal. > > This time it's with my Myth Box running F10 and if I don't fix this > quickly the wife is going to kill me. Why does a hardware change (new > MB) cause this problem? Shouldn't it be able to find the volume group > regardless? > > In my previous situation a livecd could find the volume group but the > installed system could not and I suspect the same will happen this > time but I am creating a livecd just to be sure. > > Any troubleshooting ideas? > > Thanks, > Richard > > Old System: > AMD Sempron 64 3100+ > Cheap nForce3 MB > > New(er) system: > AMD Athlon X2 5200+ > Gigabyte AMD 770 chipset. MB > Chances are, your disk controller changed with the change of motherboards. This has been covered a couple of times on this list. The fix is fairly simple - build a new initrd with the drivers for the new motherboard. You can do this by booting with the install media and using the rescue mode. Then chroot to the mounted root directory, and run mkinitrd. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hardware upgrade -> Volume Group "VolGroup00" not found.
On Thu, Mar 5, 2009 at 9:23 PM, Richard Shaw wrote: > This is the second time this has happened to me. The first time was > after a hardware upgrade on the computer I'm using right now, however, > it was an F8 system so instead of preupgrade I decided a fresh install > was in order, no big deal. > > This time it's with my Myth Box running F10 and if I don't fix this > quickly the wife is going to kill me. Why does a hardware change (new > MB) cause this problem? Shouldn't it be able to find the volume group > regardless? > > In my previous situation a livecd could find the volume group but the > installed system could not and I suspect the same will happen this > time but I am creating a livecd just to be sure. > > Any troubleshooting ideas? > > Thanks, > Richard > > Old System: > AMD Sempron 64 3100+ > Cheap nForce3 MB > > New(er) system: > AMD Athlon X2 5200+ > Gigabyte AMD 770 chipset. MB > Ok, after 3 hours of troubleshooting this I'm about ready to throw in the towel. It is beyond me why a hardware swap would cause this. Some additional strangeness When I use the liveusb none of the lvm commands have any problems finding anything. I'm able to mount, read, write, everything. When I boot, nothing in my grub.conf specifies VolGroup00, in fact it's referenced by UUID. So if the initrd can't find VolGroup00, then how does it know what's it's called? This is infuriating! Not only is this the second time I've had this problem but I REALLY don't want to rebuild my mythtv box from scratch. Richard -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Hardware upgrade -> Volume Group "VolGroup00" not found.
This is the second time this has happened to me. The first time was after a hardware upgrade on the computer I'm using right now, however, it was an F8 system so instead of preupgrade I decided a fresh install was in order, no big deal. This time it's with my Myth Box running F10 and if I don't fix this quickly the wife is going to kill me. Why does a hardware change (new MB) cause this problem? Shouldn't it be able to find the volume group regardless? In my previous situation a livecd could find the volume group but the installed system could not and I suspect the same will happen this time but I am creating a livecd just to be sure. Any troubleshooting ideas? Thanks, Richard Old System: AMD Sempron 64 3100+ Cheap nForce3 MB New(er) system: AMD Athlon X2 5200+ Gigabyte AMD 770 chipset. MB -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
Timothy Murphy wrote, On 12/13/2008 10:37 AM: Braden McDaniel wrote: I'm probably out of my depth, but what happens if you boot with Knoppix or some other Linux CD, and say "sudo vgchange -a y" ? I don't have a live CD handy; but doing that from rescue mode didn't seem to have any effect. Of course, by the time I'm in rescue mode, the filesystems have been located and mounted under /mnt/sysimage. If any of the logical volumes weren't marked as available, they wouldn't be locatable during rescue, would they? As I said, I'm not sure if I am talking sense, but my impression is that "vchange -a y" will tell you what LVM volumes can be found, and make "available" any that are not already available. I found during a long saga preupgrading from F-9 to F-10 on a SCSI machine that for some reason my LVM partitions were not found at one point, and vgchange brought them to light. Actually, I have had a few problems with LVM during system upgrades, and have reluctantly decided to withdraw from the LVM world. The advantages are greatly outweighed by the disadvantages, in my case. If "vchange -a y" does not do it, IIRC I had to a "vgscan -v" and then "vchange -a y VOLNAME" that vgscan showed. Unless a person is running a >1 PB monster drive or a system where they play about with VMs and new file systems, I have decided that the trouble in maintenance modes completely outweighs any benefit of LVM. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
On Fri, 2008-12-12 at 15:06 -0600, Richard Shaw wrote:
> On Fri, Dec 12, 2008 at 1:41 PM, Stephen Berg (Contractor)
> wrote:
> > Braden McDaniel wrote:
> >>
> >> Quoting "Joseph L. Casale" :
> >>
> >>>> After installing F10 and rebooting, I get "Volgroup00 not found".
> >>>>
> >>>> I installed F10 over an existing Fedora installation. (I did not
> >>>> perform an upgrade.) I can boot to rescue mode and things seem to be
> >>>> mounted okay under /mnt/sysimage. What can I do to fix this?
> >>>
> >>> Bad initrd maybe? What storage controller are you using? You might boot
> >>> to the rescue disc and regenerate it adding a --with={module_name}...
> >>
> >> It's a 3ware 9550SXU-4LP.
> >>
> >> What module name do I need?
> >>
> > Probably 3w_9xxx, that's the module I see running on a system with a 3Ware
> > 9500S 8 port SATA RAID adapter.
> >
>
> I had the same problem but with a MB/CPU swapout. I ended up just
> installing from scratch. Wasn't a bid deal since I have a separate
> home partition (which is not in an LVM). It was kind of frustrating
> though. Like the OP, rescue found the volume group fine. Nothing
> special on my end just onboard SATA (AMD 770) on the new computer and
> nForce4 SATA on the old.
A clean install is how I got here. :-/
Well, "clean install" doesn't include completely recreating the LVM
group; I *really* don't want to do that.
The fact that the volumes are accessible in rescue mode suggests to me
that there's no fundamental compatibility problem; rather, I think
something's just not getting loaded at the right time. I've filed this
bug on the issue:
http://bugzilla.redhat.com/show_bug.cgi?id=476337
I'm not sure if it should be against mkinitrd or kernel (or something
else); for the moment it's filed against the first.
I decided to try the upgrade route instead. I did a clean install of
Fedora 9; then did a yum upgrade to 10. Unfortunately, I have exactly
the same problem. But this time, there's a left over kernel from Fedora
9 that I can boot to. Booting to this kernel works; though it's not
without its (unrelated) side effects.
--
Braden McDaniel e-mail:
<http://endoframe.com>Jabber:
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
Braden McDaniel wrote: >> I'm probably out of my depth, >> but what happens if you boot with Knoppix or some other Linux CD, >> and say "sudo vgchange -a y" ? > > I don't have a live CD handy; but doing that from rescue mode didn't > seem to have any effect. Of course, by the time I'm in rescue mode, > the filesystems have been located and mounted under /mnt/sysimage. If > any of the logical volumes weren't marked as available, they wouldn't > be locatable during rescue, would they? As I said, I'm not sure if I am talking sense, but my impression is that "vchange -a y" will tell you what LVM volumes can be found, and make "available" any that are not already available. I found during a long saga preupgrading from F-9 to F-10 on a SCSI machine that for some reason my LVM partitions were not found at one point, and vgchange brought them to light. Actually, I have had a few problems with LVM during system upgrades, and have reluctantly decided to withdraw from the LVM world. The advantages are greatly outweighed by the disadvantages, in my case. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
Quoting Timothy Murphy : Braden McDaniel wrote: After installing F10 and rebooting, I get "Volgroup00 not found". I installed F10 over an existing Fedora installation. (I did not perform an upgrade.) I can boot to rescue mode and things seem to be mounted okay under /mnt/sysimage. What can I do to fix this? I'm probably out of my depth, but what happens if you boot with Knoppix or some other Linux CD, and say "sudo vgchange -a y" ? I don't have a live CD handy; but doing that from rescue mode didn't seem to have any effect. Of course, by the time I'm in rescue mode, the filesystems have been located and mounted under /mnt/sysimage. If any of the logical volumes weren't marked as available, they wouldn't be locatable during rescue, would they? -- Braden McDaniel e-mail: <http://endoframe.com>Jabber: -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
Quoting "Stephen Berg (Contractor)" :
Braden McDaniel wrote:
Quoting "Joseph L. Casale" :
After installing F10 and rebooting, I get "Volgroup00 not found".
I installed F10 over an existing Fedora installation. (I did not
perform an upgrade.) I can boot to rescue mode and things seem to be
mounted okay under /mnt/sysimage. What can I do to fix this?
Bad initrd maybe? What storage controller are you using? You might boot
to the rescue disc and regenerate it adding a --with={module_name}...
It's a 3ware 9550SXU-4LP.
What module name do I need?
Probably 3w_9xxx, that's the module I see running on a system with a
3Ware 9500S 8 port SATA RAID adapter.
Yes, that's the module name. But using mkinitrd as described doesn't help.
I've tried doing a yum update to latest from rescue mode and then
running mkinitrd again; that didn't seem to help, either.
This was working with Fedora 9. I did a yum upgrade to Fedora 10 and
it was still working at that point. But a few things were a bit wonky;
so I figured I'd do a fresh install from DVD. Bad idea, I guess. :-/
Any other suggestions for how to fix this?
--
Braden McDaniel e-mail:
<http://endoframe.com>Jabber:
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
--- On Fri, 12/12/08, Timothy Murphy wrote: > From: Timothy Murphy > Subject: Re: Volgroup00 not found > To: fedora-list@redhat.com > Date: Friday, December 12, 2008, 5:42 PM > Braden McDaniel wrote: > > > After installing F10 and rebooting, I get > "Volgroup00 not found". > > > > I installed F10 over an existing Fedora installation. > (I did not > > perform an upgrade.) I can boot to rescue mode and > things seem to be > > mounted okay under /mnt/sysimage. What can I do to fix > this? > > I'm probably out of my depth, > but what happens if you boot with Knoppix or some other > Linux CD, > and say "sudo vgchange -a y" ? > > > > > -- For some reason or another, I see a similar message on rawhide. I poweroff manually, Then restart/start up machine normally and it boots. But it says /dev/mapper/Volgroup01 not found, and then it changes the 01 to 00 on the subsequent boot and it works. So maybe he can see if it boots or not that way. Regards, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
Braden McDaniel wrote: > After installing F10 and rebooting, I get "Volgroup00 not found". > > I installed F10 over an existing Fedora installation. (I did not > perform an upgrade.) I can boot to rescue mode and things seem to be > mounted okay under /mnt/sysimage. What can I do to fix this? I'm probably out of my depth, but what happens if you boot with Knoppix or some other Linux CD, and say "sudo vgchange -a y" ? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
On Fri, Dec 12, 2008 at 1:41 PM, Stephen Berg (Contractor)
wrote:
> Braden McDaniel wrote:
>>
>> Quoting "Joseph L. Casale" :
>>
>>>> After installing F10 and rebooting, I get "Volgroup00 not found".
>>>>
>>>> I installed F10 over an existing Fedora installation. (I did not
>>>> perform an upgrade.) I can boot to rescue mode and things seem to be
>>>> mounted okay under /mnt/sysimage. What can I do to fix this?
>>>
>>> Bad initrd maybe? What storage controller are you using? You might boot
>>> to the rescue disc and regenerate it adding a --with={module_name}...
>>
>> It's a 3ware 9550SXU-4LP.
>>
>> What module name do I need?
>>
> Probably 3w_9xxx, that's the module I see running on a system with a 3Ware
> 9500S 8 port SATA RAID adapter.
>
I had the same problem but with a MB/CPU swapout. I ended up just
installing from scratch. Wasn't a bid deal since I have a separate
home partition (which is not in an LVM). It was kind of frustrating
though. Like the OP, rescue found the volume group fine. Nothing
special on my end just onboard SATA (AMD 770) on the new computer and
nForce4 SATA on the old.
Richard
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Volgroup00 not found
Braden McDaniel wrote:
Quoting "Joseph L. Casale" :
After installing F10 and rebooting, I get "Volgroup00 not found".
I installed F10 over an existing Fedora installation. (I did not
perform an upgrade.) I can boot to rescue mode and things seem to be
mounted okay under /mnt/sysimage. What can I do to fix this?
Bad initrd maybe? What storage controller are you using? You might boot
to the rescue disc and regenerate it adding a --with={module_name}...
It's a 3ware 9550SXU-4LP.
What module name do I need?
Probably 3w_9xxx, that's the module I see running on a system with a
3Ware 9500S 8 port SATA RAID adapter.
--
Stephen Berg
Systems Administrator
NRL Code: 7321
Office: 228-688-5738
stephen.berg@nrlssc.navy.mil
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: Volgroup00 not found
>It's a 3ware 9550SXU-4LP. > >What module name do I need? Off the top of my head I dunno, but an lsmod while in rescue should point you along as you need to be there to get it done anyway. jlc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: Volgroup00 not found
Quoting "Joseph L. Casale" :
After installing F10 and rebooting, I get "Volgroup00 not found".
I installed F10 over an existing Fedora installation. (I did not
perform an upgrade.) I can boot to rescue mode and things seem to be
mounted okay under /mnt/sysimage. What can I do to fix this?
Bad initrd maybe? What storage controller are you using? You might boot
to the rescue disc and regenerate it adding a --with={module_name}...
It's a 3ware 9550SXU-4LP.
What module name do I need?
--
Braden McDaniel e-mail:
<http://endoframe.com>Jabber:
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: Volgroup00 not found
>After installing F10 and rebooting, I get "Volgroup00 not found".
>
>I installed F10 over an existing Fedora installation. (I did not
>perform an upgrade.) I can boot to rescue mode and things seem to be
>mounted okay under /mnt/sysimage. What can I do to fix this?
Bad initrd maybe? What storage controller are you using? You might boot
to the rescue disc and regenerate it adding a --with={module_name}...
jlc
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Volgroup00 not found
After installing F10 and rebooting, I get "Volgroup00 not found". I installed F10 over an existing Fedora installation. (I did not perform an upgrade.) I can boot to rescue mode and things seem to be mounted okay under /mnt/sysimage. What can I do to fix this? -- Braden McDaniel e-mail: <http://endoframe.com>Jabber: -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update FC9: VolGroup00 not found
To reply to myself to the error after FC9 upgrade: > After rebooting, everything looks fine, but then I get > "/dev/VolGroup00/LogVol00" not found. While tracking this error down, it is necessary to change in the automatically generated initrd (after cpio-extracting it): < mount /sysroot > mount -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00 /sysroot and < switchroot > switchroot /sysroot And cpio the initrd again. This is only necessary on one of my machines with a VIA mainboard and IDE disks. I guess this could be a hardware specific bug? I'll report it. Daniel -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Update FC9: VolGroup00 not found
Hallo, I just did a yum upgrade from FC 6 to FC 9 and did all steps described in [1]. On the FC 6 install, there was a LVM active with root partition on /dev/VolGroup00/LogVol00. By mistake, I ran grub-install /dev/hda before booting. After rebooting, everything looks fine, but then I get "/dev/VolGroup00/LogVol00" not found. So I checked the initrd file built by the kernel rpm and there is no dm_mod required for LVM included. I ran mkinitrd from a Knoppix system and then the generated initrd looked fine when I extracted its contents. The dm_mod is now included, but the problem still exists. I guess there's no problem with grub, but it is scary because in the yum Upgrade FAQ they say "LVM Volume names are not affected." My question is, the change to libata from FC 6 to FC 7 should not consider my LVM-only installation, should it? What else can I do to get a working initrd? Regards, Daniel [1] http://fedoraproject.org/wiki/YumUpgradeFaq#Fedora_Core_6_-.3E_Fedora_7 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
