Fedora SCSI install issues
 

Hi,

I am trying to install Fedora Core 3 on a 1U server. It has 2 SCSI drives. The install finishes fine and recognizes and loads the appropriate Adaptec driver. When the computer is restarted for the first time, it hangs with a kernel panic. The lines above show that the Adaptec driver is not being loaded. What gives. It has been a number of years since installing on SCSI for me. I am about to go to Slackware since I know that it works, but will take longer to setup.

Thanks!!

Dave

Which card? 2940? Can you do a "safe mode" start?

You'll need to interrupt the boot, load the appropriate module and then continue the boot. I don't recall the syntax off the top of my head. What boot loader are you using?

GRUB. I only know LILO.

Dave

I'm giving up on Fedora and going back to Slackware. At least I know it works.

Dave

use lsmod to view loaded modules, should see something for scsi, and there should also be something for your specific driver, but probably not there.

use modprobe 'whatever scsi module name is' ie; modprobe adp2970 (or whatever) to load the module. You can also use insmod.

You may need to drop a driver into the kernels driver directory and re-compile the kernel

Finally, depending on the module, you may need to add module/driver options into /etc/modules.conf

Your initrd isn't loading your scsi module properly, or you aren't using an initrd and scsi isn't built into the kernel.

Strangely, I'm running XP at the moment (almost always in Debian)

....

Now back in debian.

You can (maybe) modify the initrd file by mounting it on a loop device, copy the extra modules there if needed, etc.

Or say screw it and go back to Slack. But buy it - Patrick had some health issues, and could use the $ :)

bb80sc:

There is a kernel panic on boot. Stoopid Fedora disk did not let me create a rescue disk. I remeber a long time ago that I had trouble with booting to SCSI right after install, but I don't really use SCSI anymore.

id10t:
I have always had a subscription to Slack. I started to go this route, then one of the SCSI disks died on me and we do not have anymore matched drives. Oh well, Will try again after some more drives are ordered.

My boss would prefer Fedora/RedHat over Slack. This way when I leave someone else can pickup where I left off. I could have had this machine up and running if I had started with Slackware.

Dave

Same here - GRUB is supposed to be superior, but I like LILO better.

Did you have a previous OS on that system? Did your install go cleanly? Did you get prompted to insert a disk with the proper SCSI drivers? Whos 1U system are you using? I would recommend burning a bootable cd of Knoppix or Mandrake Move. This way, you can 1. see if either of these recognizes the module, 2. If so, then you can mount the device (/dev/sda1?) and monkey around with configs and what not. Both of these will also allow you to use networking services, so you can visit the RedHat site and look for drivers, etc. On POST, you should get a chance to go into your SCSI controller settings, typically ctrl-a, IIRC. Verify the devices, etc. Just some ideas.. Or, you can ship it to me and for a small fee...... :):) Good luck

It is an older Intel setup. The RedHat install go without a hitch. It pre-loads the correct Adaptec driver. I don't really care anymore. RedHat was behind in developing a SATA kernel as well.

I learned Linux from the first version of Patrick's compilation. I still think it is the best, albeit lacking the easy install of some of the other distro's. SW is also great for booting dead systems. It is what I have been using all day. I can mount the volumes without problem with SW.

Slackware goes on when the new drives arrive. I'd rather give my money to Patrick anyday and I do. I don't always upgrade my systems to the new versions, but I enjoy receiving them every six months or so and they look really good all lined up on a shelf. :cool:

I was going to let this thread die, but I think I found the problem. I am using an Intel L440GX chipset. I found a post today that said Fedora has a bug and has problems with the 440 chipset.

Anyway, Slackware works just fine on the 440, so I will still go this route. Thanks for the input.

Dave