Greetings.
Something that might be of interest to you. NOT a problem for me, just
in case you might think I'm complaining :-)
My ISP (Hughes.net) consistently dumps your postings to the fedora list
into the spam folder. Presumably they are using some third-party
filtering service, although I have no idea which. SpamAssassin thinks
the emails are just fine, needless to say.
I'm attaching the as-received copy of this for the headers.
Regards.
On 10/12/2008 02:33:59 PM, Wolfgang S. Rupprecht wrote:
>
> I have a head scratcher here. I was trying to swap motherboards on a
> clean F9 x86_64 install. The system was updated to the current yum
> levels before the mobo swap. Attempting to boot got me through grub,
> but when it came time to mount the root FS for the first time it told
> me that the Volume Group couldn't be found. This is a disk that
> boots
> f9 without any problems on the old motherboard. Booting with a
> rescue
> disk on the new motherboard I can see and mount the Volume Group just
> fine. I'm at a loss why the rescue disk can see the volume group,
> but
> the normal boot sequence can't.
>
> This is on the x86_64 mobo that runs F9 just fine if I temporarily
> install a scratch disk and install F9 on that. It is just the f9
> disk
> that was installed by the old mobo that gives problems. Weird. Can
> anyone shed some light on this puzzler?
>
> -wolfgang
> --
> Wolfgang S. Rupprecht http://www.full-steam.org/
> (ipv6-only)
> You may need to config 6to4 to see the above pages.
>
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/
> MailingListGuidelines
>
--- Begin Message ---
I have a head scratcher here. I was trying to swap motherboards on a
clean F9 x86_64 install. The system was updated to the current yum
levels before the mobo swap. Attempting to boot got me through grub,
but when it came time to mount the root FS for the first time it told
me that the Volume Group couldn't be found. This is a disk that boots
f9 without any problems on the old motherboard. Booting with a rescue
disk on the new motherboard I can see and mount the Volume Group just
fine. I'm at a loss why the rescue disk can see the volume group, but
the normal boot sequence can't.
This is on the x86_64 mobo that runs F9 just fine if I temporarily
install a scratch disk and install F9 on that. It is just the f9 disk
that was installed by the old mobo that gives problems. Weird. Can
anyone shed some light on this puzzler?
-wolfgang
--
Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only)
You may need to config 6to4 to see the above pages.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--- End Message ---
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
