asked on fedora won't boot after install to 3ware 9550sx-12 controller
I have a 64bit machine with two 3ware 9550sx-12 raid controllers. Each raid card has 12 750GB disks attached that are setup as 6.82TB raid 5 with hotspare. I installed fedora 10 and it has the drivers for the controller, so that went smoothly, but when i reboot, the system doesn't seem to recognize where to boot from. I just get a blinking curser.
During the install of fedora 10, I created a 10GB partion on the first controllers raid for the OS, formatted it jfs and the install went fine. Then rebooted, and just got the blinking curser. So it seems like the system does not recognize where to boot from.
Any suggestions? I tried a couple things like booting to rescue mode and editing grub.conf, but it doesn't seem like it ever gets to grub.
During the install of fedora 10, I created a 10GB partion on the first controllers raid for the OS, formatted it jfs and the install went fine. Then rebooted, and just got the blinking curser. So it seems like the system does not recognize where to boot from.
Any suggestions? I tried a couple things like booting to rescue mode and editing grub.conf, but it doesn't seem like it ever gets to grub.
LinuxLinux Distributions
Last Comment
jcwells120
ASKER
I'm more of a windows admin, but i'm switching to linux so i'm a bit green on some stuff. I found some things on the net, but so far nothing has worked.
https://bugzilla.redhat.com/show_bug.cgi?id=466607#c57
I modified the MODULES var in /sbin/mkinitrd to:
MODULES="scsi_wait_scan"
I changed line 69 in my /sbin/mkinitrd from
wait_for_scsi="no"
to
wait_for_scsi="yes"
and ran this
mkinitrd -v -f /boot/initrd-2.6.27.5-117.
I also edited grub.conf on the kernel line and added this:
scsi_mod.scan=sync
I don't have any logs, since it doesn't boot up, but the mkinitrd had some output I could post
https://bugzilla.redhat.com/show_bug.cgi?id=466607#c57
I modified the MODULES var in /sbin/mkinitrd to:
MODULES="scsi_wait_scan"
I changed line 69 in my /sbin/mkinitrd from
wait_for_scsi="no"
to
wait_for_scsi="yes"
and ran this
mkinitrd -v -f /boot/initrd-2.6.27.5-117.
I also edited grub.conf on the kernel line and added this:
scsi_mod.scan=sync
I don't have any logs, since it doesn't boot up, but the mkinitrd had some output I could post
ASKER
here's the attachment with the log file from mkinitrd
mkinitrd.log
mkinitrd.log
does the grub.conf use the correct initrd?
When I need to recreate modules I usually just add them into the /etc/modprobe.conf file; (mine is below)
alias scsi_hostadapter sata_sil24
alias eth0 sky2
alias eth1 forcedeth
alias scsi_hostadapter1 aic7xxx
alias scsi_hostadapter2 sata_nv
...and then run the mkinitrd and make sure my grub.conf uses the correct initrd file.
From your log file it looks like the driver is there, I don't have the card myself so cant be 100% sure!
Does the boot hang at a specific point? Can you get a screen pic?
When I need to recreate modules I usually just add them into the /etc/modprobe.conf file; (mine is below)
alias scsi_hostadapter sata_sil24
alias eth0 sky2
alias eth1 forcedeth
alias scsi_hostadapter1 aic7xxx
alias scsi_hostadapter2 sata_nv
...and then run the mkinitrd and make sure my grub.conf uses the correct initrd file.
From your log file it looks like the driver is there, I don't have the card myself so cant be 100% sure!
Does the boot hang at a specific point? Can you get a screen pic?
ASKER
yes grub.conf uses the correct initrd.
I don't have a /etc/modprobe.conf file in fedora 10. I know that the drivers are built in because I didn't have any problem installing the system on the raid. F10 recognized the 3ware 9550sx controller and raid.
I would give you a screen pic, but there's nothing to give, since the boot process never even begins. not one single word, just a flashing cursor.
I don't have a /etc/modprobe.conf file in fedora 10. I know that the drivers are built in because I didn't have any problem installing the system on the raid. F10 recognized the 3ware 9550sx controller and raid.
I would give you a screen pic, but there's nothing to give, since the boot process never even begins. not one single word, just a flashing cursor.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
After re reading your question I should have guessed earlier...
ASKER
ok...sorry I'm not getting back to you very quickly. I'm overloaded with other duties here at work. Anyway, I tried running grub-install /dev/sda1 but it didn't fix the problem. I think we're on the right track, so maybe I'm not doing it right. During the installation, I choose to install grub on the first partition of sda instead of the default location, which was the MBR of sda. This is a new install, so I can reinstall or whatever it takes to make this work.
I might need to find time to study grub in depth, but currently, I'm trying to keep up with other things, so sorry if I don't get back quicker.
Let me know if you have any more suggestions, and thanks!
I might need to find time to study grub in depth, but currently, I'm trying to keep up with other things, so sorry if I don't get back quicker.
Let me know if you have any more suggestions, and thanks!
grub-install /dev/sda would be the right command, sda1 is the partition.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
It's a shame you didnt stick with it, I'm sure the grub install on the whole disk would have sorted it out.
That said, it seems you wernt happy with the way the system was installed in the first place and there is nothing more annoying than using a system that doesnt have the setup you wanted and your just not happy with.
Would have also been nice to have more points ;-)
That said, it seems you wernt happy with the way the system was installed in the first place and there is nothing more annoying than using a system that doesnt have the setup you wanted and your just not happy with.
Would have also been nice to have more points ;-)
ASKER
is there is a way for me to give you more points? I'm fine with that if there's a way.
Thanks a bunch jools!
Thanks a bunch jools!
You may have to boot rescue mode and recreate the initrd making sure the drivers are listed in the modprobe.conf file.
Do you have any errors or diagnostic info you can post?