[5075] in linux-scsi channel archive
Re: Cd-Rom noticed,detected, but now???
daemon@ATHENA.MIT.EDU (Stuart Felenstein)
Mon Nov 9 13:16:59 1998
Date: Mon, 09 Nov 1998 05:20:09 -0600
From: Stuart Felenstein <stuartf@dimensional.com>
To: carguin@iname.com, linux-scsi@vger.rutgers.edu
carguin@iname.com wrote:
> Anyway, /dev/sr0 should be a block device with major number 11, minor
> number 0.
>
> Then you'll want to modify your /etc/fstab. Just copy the /dev/cdrom line,
> and change it to /dev/sr0 and the mount point to /mnt/cdrom2 (or whatever
> you want). Then you can do a "mount /mnt/cdrom2" and it'll work fine.
>
After doing a mknod /dev/sr0 b 11 0 (think that's correct), I checked the /dev for
sr0, sure enough there. I rebooted (not sure how to get the system to read fstab
while up). Anyway I did a mount /mnt/cdrom2 , which seemed to hang for a bit .
Then a series of scanning scsi messages (sorry , couldn't provide log) there were
four total scan related lines, 3 which were referencing scsi id: 4, which is the
disk my filesystem resides on. Then the last with a scan reference to scsi id: 3,
the cd-rom I want to access. The a timeout , another round of "trying harder" ,
timout , then /mnt/cdrom2 doesn't exist. Any retries met with immediate failure
bypassing any scanning and directly to /mnt/cdrom2 doesn't exist.
I moved the entry in /etc/fstab up under the sda1-7 thinking that would help. It
didn't. I'm wondering if having the cdrom on a scsi device higher then the cd-rom
is causing the conflict and ultimately the timeout.
Just to mention in case of possible importance. The scsi chain is as follows,
id3: cd-rom, id4: Iomega Jaz disk (Linux Filesystem)sda , id5: Iomega Zip,
recognized as sdb, id6: Akai Sampler (generic scsi device) and id7: host (Adaptec
2940UU) No problems accessing the Zipdrive.
Thanks
Stuart
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
