LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices



Reply
 
Search this Thread
Old 12-04-2008, 10:57 AM   #1
feltdd
LQ Newbie
 
Registered: May 2006
Posts: 12

Rep: Reputation: Disabled
Fedora 10 installs fine, then on boot, VolGroup00 not found. Raid5


I'm trying to install Fedora 10 86_64 on a 64 bit system with a Dell PERC Raid5 controller. It installs fine, but on bootup it comes back with VolGroup00 not found, other errors, and refuses to boot.

This machine ran FC9_86_64 just fine until we went to bigger disks and tried to reload.

Checking the single DVD from Fedora_86_64 says it tests ok. Tried it twice now. Any hints ?? TIA!
 
Old 12-04-2008, 02:04 PM   #2
spuds
LQ Newbie
 
Registered: Dec 2008
Posts: 2

Rep: Reputation: 1
Same with me on 3Ware RAID 10 configuration

When I installed Fedora 10 I just used the defaults for creating the file system partitions. I didn't check or modify any of the default settings.
 
Old 12-05-2008, 12:39 PM   #3
feltdd
LQ Newbie
 
Registered: May 2006
Posts: 12

Original Poster
Rep: Reputation: Disabled
FC9 loaded and ran fine on the machine (although eth0 is not activating on boot for some reason..) One of the other Forums sent me a work-around, but I lost it. It's modifications of the boot sequence and timings in FC10, and apparently can be done from the rescue disk process. If I find it again, will post it. For now, staying with FC9.
 
Old 12-08-2008, 02:57 PM   #4
spuds
LQ Newbie
 
Registered: Dec 2008
Posts: 2

Rep: Reputation: 1
I figured this out after doing more google searches. Turns out this is a known issue with the scsi initialization not waiting long enough. You have to rebuild initrd with 'mkinitrd' and use the --with=scsi_wait_scan

Boot off the install DVD and go into rescue mode.
Cd the mounted root for the hard drive with new installation. Then do a "chroot" so you are now operating on the installed disk drive.

next run the following command:

mkinitrd -f --with=scsi_wait_scan /boot/initrd-2.6.27.5-117.fc10.x86_64.img 2.6.27.5-117.fc10.x_86_64

This will install a new initrd in /boot.
Now reboot. Should work.

The only issue after this seems to be a bad name resolver library that is causing yum updates to fail because it can't resolve some repository host names. That was fixed by hardcoding some of the mirror sites in /etc/hosts.

... Moving on to other hurdles ...
 
Old 12-22-2008, 10:01 AM   #5
Walt750
LQ Newbie
 
Registered: Jan 2006
Posts: 1

Rep: Reputation: 0
No Need to boot off the Rescue CD

use 'scsi_mod.scan=sync' as an additional item on the kernel boot string.

You can boot into your OS and do the mkinitrd to fix the issue.

Warning: a yum udpdate afterwards caused my system to require another go at this procedure ... so watch your updates ... it will break things.

By the way ... It's all SCSI type cards ...
for example my system was Sata Drives on a 3ware card.
 
Old 01-09-2009, 12:22 PM   #6
mechdude
LQ Newbie
 
Registered: Sep 2008
Posts: 4

Rep: Reputation: 0
Thumbs up

Quote:
Originally Posted by spuds View Post
I figured this out after doing more google searches. Turns out this is a known issue with the scsi initialization not waiting long enough. You have to rebuild initrd with 'mkinitrd' and use the --with=scsi_wait_scan

Boot off the install DVD and go into rescue mode.
Cd the mounted root for the hard drive with new installation. Then do a "chroot" so you are now operating on the installed disk drive.

next run the following command:

mkinitrd -f --with=scsi_wait_scan /boot/initrd-2.6.27.5-117.fc10.x86_64.img 2.6.27.5-117.fc10.x_86_64

This will install a new initrd in /boot.
Now reboot. Should work.

The only issue after this seems to be a bad name resolver library that is causing yum updates to fail because it can't resolve some repository host names. That was fixed by hardcoding some of the mirror sites in /etc/hosts.

... Moving on to other hurdles ...
Thank you very much. It worked for me on a HP Proliant ML150 server.

/sbin/mkinitrd -f --with=raid10 --with=raid456 --with=aacraid --with=scsi_wait_scan /boot/initrd-2.6.27.9-159.fc10.x86_64.img 2.6.27.9-159.fc10.x86_64
 
Old 05-05-2009, 03:36 AM   #7
fcc
LQ Newbie
 
Registered: May 2009
Posts: 1

Rep: Reputation: 0
Thank you. It works on my IBM xSeries 360 too.
 
  


Reply

Tags
fedora 10


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Replaced MB now I get volgroup00 not found Maleki Linux - Newbie 8 10-24-2008 04:47 PM
installs fine, but won't boot. Kernel_Sanders *BSD 3 04-06-2006 01:54 PM
Fedora 3 and 4 installs fine but doesnt boot correctly prob, no clue what to do vtecturbo13 Fedora 10 12-30-2005 10:36 AM
xandros installs fine, fedora won't see hdb? houstoncarl Linux - Newbie 1 09-18-2005 06:21 PM
YDL installs fine but won't boot on 17" Powerbook DannyG Linux - Hardware 0 09-23-2004 12:36 AM


All times are GMT -5. The time now is 05:58 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration