Hardware
micon 200mhz p-pro x 2
Adaptec Scsi card
drive 0, id 0 - 9gb seagate
drive 1, id 2 - 4.5gb ibm

When I boot both drives are recognized by the adaptec bios but only drive 0 was picked up by linux (Redhat 7.3) on installation.
I installed on just drive 0 now labeled appropriately /dev/sda.
No when linux boots, it detects both drives on startup but I cannot acess drive 1. I tried fdisk /dev/sdb but it can't find the drive. MS DOS FDISK recognizes both drives.

ideas?

Thanks.

I suppose it's possible that the IBM drive is jumpered to require a signal from the SCSI adapter before it'll spin up. If the Adaptec hasn't been configured to send that signal, you might see the drive listed when the Adaptec initializes but the drive will never be brought online. If you can, power cycle the system (or HW reset it; either one) and press Ctrl-A when the Adaptec banner appears. Check the configuration to see that the start up signal is being sent to the device at ID 2. BTW, which Adaptec adapter are we talking about anyway? If this is an older Adaptec you might have to change a jumper on the board to do this. Not sure why MS-DOS would see the second drive.

The drive does spinup, you can hear it and the contrller is set to spin up the drives. The conroller is an AHA-2940UW with the latest bios.

The 1st drive is UW scsi, the second is older scsi 2 but it is recognized by the controller, and linux too when it checks for scsi devices.

And fdisk /dev/sdb doesn't work? That's just weird.

Does anything under /proc/scsi look amiss?

I have had some really old DEC SCSI-2 2GB drives not work properly on the same model SCSI adapter. Could be a similar problem I guess.

Looks like a disk issue, I couldn't verify the disk with scsi utilites. I replaced it with another disk I had of the same size and it worked.

I do have another question, actually 2.

linux fdisk id's my disk with 553 cylinders and allows a max of 63 sectors/track. The drive docs have it with 5583 cyl and 150 sectors/track. It seems OK and the size is correct. Wierd.

Also, after partition and mkfs i needed to add a mount point.
I added a directory /mnt/newdir and was able to mount the drive but is there a way to mount the drive so it's reflected as just /newdir and not /mnt/newdir like all the other mappings?

thanks

To mount it under /newdir do the following:

mkdir /newdir

Change /etc/fstab to show mountpoint as /newdir

Then you're all set.

dbp

With odd scsi behavior double check termination, I've had windows chug along fine (well slow, but no errors) with a mis terminated scsi bus but linux was having problems until I fixed it.

Good point. The original post was about a aha2940UW. I have one of those and I don't think it alerts you about incorrect termination. If memory serves, the 29160s do during the bus scan at initialization. (Now I remember why I prefer cables with the termination rather than having to jumper that last device. :-) )

Rick