On Wed, 23 Apr 2003, David van Hoose wrote:
> I included ppa and scsi in my kernel since I have a parallel port
> zipdrive. Problem I am having is that it keeps scanning the drive for
> too much too often. Anytime I mount/unmount, plug/unplug USB and
> firewire devices, or at random times, I get the following messages on my
> console and in my messages file.
Was the zip drive recognized as removable?
>
> Apr 23 11:41:35 aeon kernel: sda : READ CAPACITY failed.
> Apr 23 11:41:35 aeon kernel: sda : status = 1, message = 00, host = 0,
> driver = 08
> Apr 23 11:41:35 aeon kernel: Current sd00:00: sns = 70 2
> Apr 23 11:41:35 aeon kernel: ASC=3a ASCQ= 0
> Apr 23 11:41:35 aeon kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00
> 0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0xff
> 0xfe 0x01 0x00 0x00 0x00 0x00
> Apr 23 11:41:35 aeon kernel: sda : block size assumed to be 512 bytes,
> disk size 1GB.
> Apr 23 11:41:35 aeon kernel: sda: Write Protect is off
> Apr 23 11:41:35 aeon kernel: sda: I/O error: dev 08:00, sector 0
> Apr 23 11:41:35 aeon kernel: I/O error: dev 08:00, sector 0
> Apr 23 11:41:35 aeon kernel: unable to read partition table
> Apr 23 11:41:35 aeon kernel: Device not ready. Make sure there is a
> disc in the drive.
>
> This gets really annoying, but I like to use my zipdrive.
> Let me know if more information is needed.
>
> Thanks,
> David
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
bill davidsen <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
Bill Davidsen wrote:
> On Wed, 23 Apr 2003, David van Hoose wrote:
>
>>I included ppa and scsi in my kernel since I have a parallel port
>>zipdrive. Problem I am having is that it keeps scanning the drive for
>>too much too often. Anytime I mount/unmount, plug/unplug USB and
>>firewire devices, or at random times, I get the following messages on my
>>console and in my messages file.
>
> Was the zip drive recognized as removable?
Yes it was. Below is the snip-it from my dmesg. That is also where the
first error appears. Though it is different in subsequent with the last
line as can be seen in the quoted message fragment just below this part.
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
ppa: Version 2.07 (for Linux 2.4.x)
ppa: Found device at ID 6, Attempting to use EPP 32 bit
ppa: Communication established with ID 6 using EPP 32 bit
scsi1 : Iomega VPI0 (ppa) interface
Vendor: IOMEGA Model: ZIP 100 Rev: D.09
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 6, lun 0
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sense key Not Ready
Additional sense indicates Medium not present
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
unable to read partition table
>>Apr 23 11:41:35 aeon kernel: sda : READ CAPACITY failed.
>>Apr 23 11:41:35 aeon kernel: sda : status = 1, message = 00, host = 0,
>>driver = 08
>>Apr 23 11:41:35 aeon kernel: Current sd00:00: sns = 70 2
>>Apr 23 11:41:35 aeon kernel: ASC=3a ASCQ= 0
>>Apr 23 11:41:35 aeon kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00
>>0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0xff
>>0xfe 0x01 0x00 0x00 0x00 0x00
>>Apr 23 11:41:35 aeon kernel: sda : block size assumed to be 512 bytes,
>>disk size 1GB.
>>Apr 23 11:41:35 aeon kernel: sda: Write Protect is off
>>Apr 23 11:41:35 aeon kernel: sda: I/O error: dev 08:00, sector 0
>>Apr 23 11:41:35 aeon kernel: I/O error: dev 08:00, sector 0
>>Apr 23 11:41:35 aeon kernel: unable to read partition table
>>Apr 23 11:41:35 aeon kernel: Device not ready. Make sure there is a
>>disc in the drive.
>>
>>This gets really annoying, but I like to use my zipdrive.
>>Let me know if more information is needed.
It works nice under 2.5.x, but gives the sda error 5+ times just during
boot under 2.4.x. I wonder if someone forgot to backport all or some
patches.
Thanks,
David
Bill Davidsen wrote:
> On Wed, 23 Apr 2003, David van Hoose wrote:
>>Apr 23 11:41:35 aeon kernel: sda : READ CAPACITY failed.
>>Apr 23 11:41:35 aeon kernel: sda : status = 1, message = 00, host = 0,
>>driver = 08
>>Apr 23 11:41:35 aeon kernel: Current sd00:00: sns = 70 2
>>Apr 23 11:41:35 aeon kernel: ASC=3a ASCQ= 0
>>Apr 23 11:41:35 aeon kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00
>>0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0xff
>>0xfe 0x01 0x00 0x00 0x00 0x00
>>Apr 23 11:41:35 aeon kernel: sda : block size assumed to be 512 bytes,
>>disk size 1GB.
>>Apr 23 11:41:35 aeon kernel: sda: Write Protect is off
>>Apr 23 11:41:35 aeon kernel: sda: I/O error: dev 08:00, sector 0
>>Apr 23 11:41:35 aeon kernel: I/O error: dev 08:00, sector 0
>>Apr 23 11:41:35 aeon kernel: unable to read partition table
>>Apr 23 11:41:35 aeon kernel: Device not ready. Make sure there is a
>>disc in the drive.
I added more SCSI logging support so the below is better info than the
above. Sorry. Forgot the logging when I posted this. I knew it looked
extra weird.
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sense key Not Ready
Additional sense indicates Medium not present
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: Write Protect is off
sda: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
unable to read partition table
Device not ready. Make sure there is a disc in the drive.
Hope this helps more.
Thanks,
David