Fedora: scsi cdrom drives me crazy
Dave Andruczyk
djandruczyk at yahoo.com
Mon Oct 3 14:31:05 EDT 2005
--- Scott Fleming <nflug at afourthdimension.com> wrote:
> Thank you in advance for your help with this.
>
> SCSI termination is correct - all drives are recognized after I run
> modprobe in /etc/rc.local
>
> cat /proc/scsi/scsi:
>
> Attached devices:
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: IBM-PCCO Model: DDRS-34560W !# Rev: S97B
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: IBM-PCCO Model: DDRS-34560W !# Rev: S97B
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 03 Lun: 00
> Vendor: IBM-PCCO Model: DDRS-34560W !# Rev: S97B
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 05 Lun: 00
> Vendor: IBM Model: CDRM00203 !K Rev: BZ26
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
> Vendor: MDI Model: LaserBank 1300D Rev: 1027
> Type: Sequential-Access ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
> Vendor: TEXEL Model: CD-ROM DM-XX28 Rev: 3.05
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 01 Lun: 00
> Vendor: TEXEL Model: CD-ROM DM-XX28 Rev: 3.05
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 02 Lun: 00
> Vendor: TEXEL Model: CD-ROM DM-XX28 Rev: 3.05
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 03 Lun: 00
> Vendor: TEXEL Model: CD-ROM DM-XX28 Rev: 3.05
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 04 Lun: 00
> Vendor: TEXEL Model: CD-ROM DM-XX28 Rev: 3.05
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 05 Lun: 00
> Vendor: TEXEL Model: CD-ROM DM-XX28 Rev: 3.05
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 06 Lun: 00
> Vendor: TEXEL Model: CD-ROM DM-XX28 Rev: 3.05
> Type: CD-ROM ANSI SCSI revision: 02
>
>
> I can manually mount drives 1-4. Drives 5,6,7 report an error, stating
> unknown device. Yet, they're recognized in the above.
>
> I'm looking to be able to see them listed in the disk management tool,
> which they aren't when FC boots.
>
> Perhaps I'm running modprobe at the wrong point in the boot sequence?
> Currently, I have it running in the etc/rc.local file: (should the be
> done somewhere else?)
>
> #!/bin/sh
> #
> # This script will be executed *after* all the other init scripts.
> # You can put your own initialization stuff in here if you don't
> # want to do the full Sys V style init stuff.
>
> touch /var/lock/subsys/local
>
> # load the scsi card driver
> modprobe aha152x aha152x=0x140,10,7
>
> #mount the dumb-ass cdroms
> mount -t is09660 -r /dev/scd1 /mnt/scd1
> mount -t is09660 -r /dev/scd2 /mnt/scd2
> mount -t is09660 -r /dev/scd3 /mnt/scd3
> mount -t is09660 -r /dev/scd4 /mnt/scd4
> mount -t is09660 -r /dev/scd5 /mnt/scd5
> mount -t is09660 -r /dev/scd6 /mnt/scd6
> mount -t is09660 -r /dev/scd7 /mnt/scd7
>
> The drives are not mounting.
>
> Help!
OK, On my system (Gentoo 2005.1) there are not /dev/scd* devices (2.6.13
kernel, UDEV enabled), there are however /dev/sr* (which correspond to the
SCSI cdrom's)
after booting check /dev/ to see if /dev/scd* exists, same wiht /dev/sr* if
the sr ones exist but not the scd's then just adjust your mount lines in
/etc/rc.d/rc.local. I though that redhat DID have some init module to
manually load kernel modules (like your AHA1542 module and the cdrom and sr_mod
modules) I donno what redhat calls it as I dropped that distro years ago after
suffering way too much RPM hell.
Dave J. Andruczyk
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
More information about the nflug
mailing list