Where Did It Go? A Re-Post
Mercury Morris
mercury.morris at gmail.com
Wed Aug 1 18:22:55 UTC 2007
Mikkel wrote:
> What log messages do you get when you insert a disk in the drive
> after booting without one? Also, what does /proc/scsi/scsi list the
> drive as? From what you are reporting, it does not sounds like it is
> being detected as a removable hard drive.
There are no log messages when the disk is inserted. I agree that
the device is not being detected as a removable drive. And I would
go further by saying that the device is not detected at all, except
for the case when a disk is inserted BEFORE the system is booted.
Here are the lines from the command, cat /proc/scsi/scsi, basically
all blanks. The other scsi devices have vendor information included.
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 05
> I do not have an IDE ZIP drive handy to test with. On the USB ZIP
> drive, I get this after inserting a disk:
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Spinning up disk....ready
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] 196608 512-byte
> hardware sectors (101 MB)
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Write Protect is off
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Assuming drive cache:
> write through
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] 196608 512-byte
> hardware sectors (101 MB)
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Write Protect is off
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Assuming drive cache:
> write through
> Jul 31 17:44:47 asus kernel: sdb: sdb4
>
> I would expect something like that when a disk is inserted in an IDE
> ZIP drive as well. If not, you could try to re-scan the SCSI bus the
> ZIP drive is on. There is a script to do this at
> http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh-1.25 but I have
> not had to use it. If you try it, let us know how it works. If it
> lets you mount the drive, it should give the developers the clues
> needed to fix the problem.
I ran the script that you pointed to (above). The output follows this
paragraph. I believe the lines for "scsi1" are the lines of interest.
The script was run twice, first with no disk in the drive, then after
a disk had been inserted. There was no difference between the two,
and the mount command failed, as well.
----- rescan-scsi-bus.sh output -----
[root at estreet ~]# ./rescan-scsi-bus.sh-1.25
Host adapter 0 (<NULL>) found.
Host adapter 1 (pata_amd) found.
Host adapter 2 (pata_amd) found.
Scanning SCSI subsystem for new devices
Scanning host 0 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: 3ware Model: Logical Disk 0 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: 3ware Model: Logical Disk 0 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning for device 0 0 1 0 ...
OLD: Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: 3ware Model: Logical Disk 1 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 1 0 ...
OLD: Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: 3ware Model: Logical Disk 1 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning for device 0 0 2 0 ...
OLD: Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: 3ware Model: Logical Disk 2 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 2 0 ...
OLD: Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: 3ware Model: Logical Disk 2 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning for device 0 0 3 0 ...
OLD: Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: 3ware Model: Logical Disk 3 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 3 0 ...
OLD: Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: 3ware Model: Logical Disk 3 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning host 1 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 05
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 05
Scanning host 2 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: DVD RW DRU-710A Rev: BY01
Type: CD-ROM ANSI SCSI revision: 05
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: DVD RW DRU-710A Rev: BY01
Type: CD-ROM ANSI SCSI revision: 05
0 new device(s) found.
0 device(s) removed.
I would like to submit all of this information to the developers.
As Andy suggested, I will go ahead and try to interest the folks
at Fedora's Bugzilla. I think it's a kernel problem, mostly because
I have been reading some of the kerneltrap traffic where one
discussion about the ide-scsi module might just indicate where
the trouble started. But, I don't particularly want to join the
kernel mailinglist, so I'll go the Bugzilla route.
Thanks, Mikkel, for taking an interest and pointing out the places
to look and the rescan-scsi-bus.sh script.
--
MM
More information about the users
mailing list