Bug 140245
Summary: | Buffer I/O error on removable SCSI JAZ drive | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marek Kassur <cmarco> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-17 22:51:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marek Kassur
2004-11-21 18:54:52 UTC
After some test I see that haldaemon spin up JAZ drive. I have two USB pen drives, one is 32MB USB 1.1, second is 512MB USB 2.0. I see almost identical error with second one, maybe it's something in SCSI layer ? usb 5-2: new full speed USB device using address 3 scsi3 : SCSI emulation for USB Mass Storage devices Vendor: Model: Rev: Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdb: 64000 512-byte hdwr sectors (33 MB) sdb: Write Protect is off sdb: Mode Sense: 0b 00 00 08 sdb: assuming drive cache: write through sdb: sdb1 Attached scsi removable disk sdb at scsi3, channel 0, id 0, lun 0 USB Mass Storage device found at 3 usb 1-7: new high speed USB device using address 7 scsi5 : SCSI emulation for USB Mass Storage devices Vendor: Model: USB DRIVE Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02 sdc: Unit Not Ready, sense: Current : sense key Unit Attention Additional sense: Not ready to ready change, medium may have changed sdc : READ CAPACITY failed. sdc : status=1, message=00, host=0, driver=08 Current sd: sense key Unit Attention Additional sense: Not ready to ready change, medium may have changed sdc: test WP failed, assume Write Enabled sdc: assuming drive cache: write through sdc: Unit Not Ready, sense: Current : sense key Unit Attention Additional sense: Not ready to ready change, medium may have changed sdc : READ CAPACITY failed. sdc : status=1, message=00, host=0, driver=08 Current sd: sense key Unit Attention Additional sense: Not ready to ready change, medium may have changed sdc: test WP failed, assume Write Enabled sdc: assuming drive cache: write through sdc: Unit Not Ready, sense: Current : sense key Unit Attention Additional sense: Not ready to ready change, medium may have changed sdc : READ CAPACITY failed. sdc : status=1, message=00, host=0, driver=08 Current sd: sense key Unit Attention Additional sense: Not ready to ready change, medium may have changed sdc: test WP failed, assume Write Enabled sdc: assuming drive cache: write through sdc:end_request: I/O error, dev sdc, sector 0 Buffer I/O error on device sdc, logical block 0 Buffer I/O error on device sdc, logical block 0 Buffer I/O error on device sdc, logical block 262143 Buffer I/O error on device sdc, logical block 262143 Buffer I/O error on device sdc, logical block 0 unable to read partition table sdc:<3>Buffer I/O error on device sdc, logical block 0 Buffer I/O error on device sdc, logical block 262143 Buffer I/O error on device sdc, logical block 0 unable to read partition table Attached scsi removable disk sdc at scsi5, channel 0, id 0, lun 0 USB Mass Storage device found at 7 hub 1-0:1.0: connect-debounce failed, port 8 disabled An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. This bug is already fixed in previous kernels, I think 2.6.11. BTW, kernel-2.6.12-1.1372_FC3 failed to boot on this machine (kernel panic), but this is another story. |