Fedora Linux Support Community & Resources Center
  #31  
Old 30th November 2008, 07:35 PM
Carstijn Offline
Registered User
 
Join Date: Nov 2008
Posts: 2
still a error

Hi all,

I have a 3ware 9650se and used this command:

/sbin/mkinitrd -f --with=scsi_wait_scan --with=3w-9xxx /boot/initrd-2.6.27.5-117.fc10.x86_64.img 2.6.27.5-117.fc10.x86_64

then I rebooted and got a error:

mount: error mounting /dev/root on /sysroot as ext3: no such file or directory sda5

I think the scsi_wait_scan is to short, after the error I get the following message:

sd 4:0:0:0: [sda] Attached SCSI disk
sd 4:0:0:0: attached scsi generic sg1 type 0

someone got a hint?

screen for extra info:

Reply With Quote
  #32  
Old 1st December 2008, 12:50 AM
Philio27 Offline
Registered User
 
Join Date: Nov 2008
Posts: 20
Quote:
Originally Posted by Carstijn View Post
Hi all,

I have a 3ware 9650se and used this command:

/sbin/mkinitrd -f --with=scsi_wait_scan --with=3w-9xxx /boot/initrd-2.6.27.5-117.fc10.x86_64.img 2.6.27.5-117.fc10.x86_64

then I rebooted and got a error:

mount: error mounting /dev/root on /sysroot as ext3: no such file or directory sda5

I think the scsi_wait_scan is to short, after the error I get the following message:

sd 4:0:0:0: [sda] Attached SCSI disk
sd 4:0:0:0: attached scsi generic sg1 type 0

someone got a hint?

screen for extra info:

Weird that worked for me with almost identical card model (I have the 8 port equivalent).
Reply With Quote
  #33  
Old 2nd December 2008, 08:25 AM
hijacker7 Offline
Registered User
 
Join Date: May 2005
Location: Germany
Age: 41
Posts: 9
For 3ware 7506 and Fedora 10 i686:
/sbin/mkinitrd -f --with=scsi_wait_scan --with=3w-xxxx /boot/initrd-2.6.27.5-117.fc10.i686.img 2.6.27.5-117.fc10.i686
Reply With Quote
  #34  
Old 2nd December 2008, 08:21 PM
bonzocs Offline
Registered User
 
Join Date: Dec 2008
Location: Cardiff
Posts: 9
Sorry for the newbie question here, but how can I find out which raid module I am using in order to know what I need to set in the --with flag.

Thanks
Reply With Quote
  #35  
Old 2nd December 2008, 11:32 PM
jzc Offline
Registered User
 
Join Date: Nov 2008
Posts: 16
bonzocs,

Me I just did the /sbin/mkinitrd -f --with=scsi_wait_scan /boot/initrd-2.6.27.5-117.fc10.x86_64.img 2.6.27.5-117.fc10.x86_64 WITHOUT specifying the scsi module because it's ALREADY in the initrd file. Try that.

Jon
Reply With Quote
  #36  
Old 3rd December 2008, 01:37 AM
Insomune Offline
Registered User
 
Join Date: Nov 2008
Location: Gastown, Vancouver, BC
Posts: 42
Thumbs up

Thanks guys, I had to do it the way jcz did it, w/out the driver name listed in the title.

Works now great :o

Set up my VPN as well on VBox, very cool.
Set up my fileshare across Samba, very cool. [My server being the computer serving sourcefiles to all of the workstations and then them writing image sequences back to the server].

My next steps, to set up my FTP
and properly set up my quad port b/c I don't think it's using multiple ip's when multiple workstations write to it...

Lovin' Fedora 10 on my raid card now, no problems 8tb raid 6 ended up giving me 5.1tb after I loaded the filesystem on there... anyways, I'm hoping I'm doing most of it right. I think I am.

Thanks again for the help guys, Phillo, jcz. One step at a time is how I'm approaching it and it's workin' out pretty well.
Reply With Quote
  #37  
Old 3rd December 2008, 02:59 AM
cornelius785 Offline
Registered User
 
Join Date: Mar 2008
Posts: 17
I've also encountered this problem. In my case, the boot partition is /dev/sda1 and the main partition (with /bin, /home, /etc and so on) is /dev/VolGroup00/LogVol01. In order to remake the initrd file, I think I should do:

su
mkdir -p /mnt/sysroot
mount /dev/VolGroup00/LogVol01 /mnt/sysroot
mount /dev/sda1 /mnt/sysroot/boot
chroot /mnt/sysroot
/sbin/mkinitrd -f --with=scsi_wait_scan --with=aacraid /boot/initrd-2.6.27.5-117.fc10.x86_64.img 2.6.27.5-117.fc10.x86_64

Does this look correct? Is there anything I should be concerned about when doing this? I don't want to make more problems for myself.

Also, will I have to do something similar every time the kernel is upgraded? Since this appears to affect all computers with scsi, has this been documented somewhere (besides on the Fedora forums) so others are made aware of this before install/upgrade, along with the solution?
Reply With Quote
  #38  
Old 3rd December 2008, 06:56 AM
jzc Offline
Registered User
 
Join Date: Nov 2008
Posts: 16
Quote:
Originally Posted by cornelius785 View Post
/sbin/mkinitrd -f --with=scsi_wait_scan --with=aacraid /boot/initrd-2.6.27.5-117.fc10.x86_64.img 2.6.27.5-117.fc10.x86_64
cornelius785,

Do it without the --with=aacraid and the reason why is becuase the module is already in the initrd file. This is the way that I fixed the problem. Good luck.

jzc
Reply With Quote
  #39  
Old 3rd December 2008, 07:05 AM
jzc Offline
Registered User
 
Join Date: Nov 2008
Posts: 16
Google hits...

Peoples,

I just did a '"fedora 10" scsi boot' google query and this thread is NUMBER ONE on the results... seems a lot of people are hitting this thread. Already over two thousand views.

Jon
Reply With Quote
  #40  
Old 3rd December 2008, 02:00 PM
Sauron Offline
Registered User
 
Join Date: Jan 2005
Posts: 258
Yep, appears to be a common problem, this thread fixed it for me (just finished upgrading FC9 to FC10 and ran into the exact same issue, 3ware 7000 series card).
Thanks!

Just had a random question: Say someone had this issue but needs the PAE kernel, what command line would they use to build a PAE initrd?

Last edited by Sauron; 3rd December 2008 at 02:15 PM.
Reply With Quote
  #41  
Old 3rd December 2008, 04:04 PM
cdhgold Offline
Registered User
 
Join Date: Aug 2008
Posts: 6
I'm getting this same error using a LSI Logic scsi raid card when the system boots it load both the megaraid driver and megraid-mbox driver

anyone know which one to pass to the /sbin/mkinitrd -f --with=scsi_wait_scan --with=<insert driver here> /boot/initrd-2.6.27.5-117.fc10.i686.img 2.6.27.5-117.fc10.i686 command?

I tried it without the driver as jzc suggested with no luck
Reply With Quote
  #42  
Old 3rd December 2008, 07:59 PM
cornelius785 Offline
Registered User
 
Join Date: Mar 2008
Posts: 17
After trying the proposed solution, I had a few possible problems. When I run mkinitrd, it displays:

resolveDevice: device spec expected
resolveDevice: device spec expected
cp: cannot stat '/usr/lib/plymouth/test.so': No such file or directory
cp: cannot stat '/usr/lib/plymouth/details.so': No such file or directory

and the file is created. Upon reboot, it shows:

Loading /lib/kbd/keymaps/i386/qwerty/us.map
could not start boot splash: no such device

and stops there.

I'm guessing the two outputs are related since plymouth has something to do with the boot sequence (based from google). Should mkinitrd be looking in /usr/lib64, or similar? Does anyone have any possible solutions to this? Searching isn't returning anything of real use.
Reply With Quote
  #43  
Old 4th December 2008, 12:16 AM
jzc Offline
Registered User
 
Join Date: Nov 2008
Posts: 16
Quote:
Originally Posted by cornelius785 View Post
After trying the proposed solution, I had a few possible problems. When I run mkinitrd, it displays:

resolveDevice: device spec expected
resolveDevice: device spec expected
cp: cannot stat '/usr/lib/plymouth/test.so': No such file or directory
cp: cannot stat '/usr/lib/plymouth/details.so': No such file or directory

and the file is created.
Hmmm.... did you chroot to the system? with the rescue image?

Jon
Reply With Quote
  #44  
Old 4th December 2008, 12:20 AM
jzc Offline
Registered User
 
Join Date: Nov 2008
Posts: 16
Quote:
Originally Posted by Sauron View Post
Just had a random question: Say someone had this issue but needs the PAE kernel, what command line would they use to build a PAE initrd?
I would imagine it be something like /sbin/mkinitrd -f --with=scsi_wait_scan /boot/initrd-2.6.27.5-117.fc10.i686.PAE.img 2.6.27.5-117.fc10.i686.PAE. Boot the rescue system, cd to the /boot directory and look there for the names.

Jzc
Reply With Quote
  #45  
Old 4th December 2008, 02:56 AM
cornelius785 Offline
Registered User
 
Join Date: Mar 2008
Posts: 17
I did do the chroot command. As for the 'plymouth' issue, it is looking in the wrong location (/usr/lib as opposed to /usr/lib64). How do point mkinitrd look in /usr/lib64 as opposed to /usr/lib? I suppose there is the creation of a symbolic link, but I'm unsure if that would hurt. I've edited /usr/sbin/plymouth-set-default-plugin (by forcing the libdir to become /usr/lib64), which also didn't work. I don't have the experience to make sense of /sbin/mkinitrd 's content to figure out what specifically is causing the 'resolveDevice: device spec expected'.

Apparently this --with=scsi_wait_scan issue has been known for several months and apparently hasn't been truly fixed, see this link for details: https://bugzilla.redhat.com/show_bug.cgi?id=454663 (July), https://bugzilla.redhat.com/show_bug.cgi?id=429937 (similar problem in Fedora 9, January). I find it really interesting that this issue has a multi-month history in bugzilla. It also sound like some people wanted to block the release of fedora 10, see https://bugzilla.redhat.com/show_bug.cgi?id=466607#c25 .

I've also discovered this: https://bugzilla.redhat.com/show_bug.cgi?id=466607#c47 and a few comments down. In a nutshell, edit /sbin/mkinitrd change wait_for_scsi="no" to wait_for_scsi="yes" OR create/edit /etc/sysconfig/mkinitrd and have MODULES="scsi_wait_scan" in it. My guess is that this will also solve the problem, but since initrd files are generated per kernel, it'll also ensure that scsi_wait_scan is there without having to do this manual creation of the initrd file, which I assume is done whenever. I hope the last sentence is correct, if not, please correct me. I for one, don't want to do this every time the kernel is upgraded. I did mkinitrd with -v and no --with=scsi_wait_scan and it appears the module is being loaded into the initrd file. I hope this provides a permanent solution.
Reply With Quote
Reply

Tags
boot, fedora 10, hangs, scsi

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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 On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
aacraid trouble (SCSI hang up?) barakuda Servers & Networking 3 11th January 2010 03:02 PM
Hang: Installing F9 i386 on old AMD-K6 CPU laptop rweed Installation, Upgrades and Live Media 16 3rd September 2008 09:44 PM
Fedora 8 hang on boot Tintinosio Installation, Upgrades and Live Media 3 12th November 2007 09:31 PM
Hang at loading SCSI driver.... BlackBear Installation, Upgrades and Live Media 0 24th September 2005 07:57 AM
GRUB or LILO boot to SCSI drive in SCSI system w/ IDE card mkl838 Installation, Upgrades and Live Media 0 6th March 2005 06:44 AM


Current GMT-time: 12:12 (Monday, 21-04-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat