Slackware 10.2 doesn't boot from SCSI hdd
 

Hi!

I've just downloaded Slackware 10.2 and tried to install it on my server. I have a SCSI drive installed, so I chose scsi.s image during installation.

All worked well, I was able to partition the drive, choose the swap and / partitions,packages to be installed and in the end I was asked to reboot the PC in order to start using Slackware. My problem is that after the server reboots, nothing happens.

Seeing this problem, I've decided to restart with the Slack installation disk in the CD drive. At the prompt I've entered the cfdisk command and I got an error that there is no drive and I don't have nothing to open.

This is kind of strange as I was able to install slack on the drive.

Does anyone have any ideea about this?

Thank you!
All the best from Zoli

Does your BIOS still detect the drive?

Yes it does, but when it comes to the part where the OS should be loaded nothing happens. Maybe I need to chose another image at the installation first steps (scsi1.s,scsi2.s, etc.).

What I suggest is you get a new kernel (2.6) that is good with SCSI devices.

Slackware 10.2 defaults to 2.4 kernel, not good with SCSI Devices.


The following link might have the answer to your question:

http://www.bitbenderforums.com/vb22/...?postid=311808

Indeed this is a great article. I will try that as soon as I get home and post the result here tommorow.

Thank you!

You can run cfdisk on a scsi HD if you have first selected a scsi kernel from the 1st Slack install cd to boot with. I've used the adaptec kernel before with good results.
Once I had the scsi kernel loaded then I could run cfdisk.

#cfdisk /dev/sda

The obvious choice is to use the same kernel as the installer was running. This worked because you were able to install :p

You can boot the installation disk again and go into the installation dialog (there might be a quicker way but I can't think of it at the moment) and choose the installer kernel (vmlinuz-2.4.31). Once this stuff gets copied to /boot change your lilo.conf to point to the new kernel (actually you should check and see if you already have this before you install anything further- it could be in /boot) and you should be fine.