Error Device Sd0
Contents |
2009-06-15 Posts: 3,581 [SOLVED] badblocks ext4 Overview of issue.On boot when a filesystem is being fsck, errors appear:[ 21.638174] sd 2:0:0:0: [sdc] Unhandled sense code buffer i/o error on device logical block [ 21.638180] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08 [ 21.638186] sd buffer i/o error on device sda logical block 0 2:0:0:0: [sdc] Sense Key : 0x3 [current] [ 21.638192] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0 [ 21.638197] sd 2:0:0:0: buffer i/o error on device sdb logical block 0 [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 67 00 00 40 00 [ 21.638210] end_request: critical target error, dev sdc, sector 96469095 [ 21.638289] Buffer I/O error buffer i/o error on device dm-0 on device sdc1, logical block 96469032 [ 21.638351] Buffer I/O error on device sdc1, logical block 96469033 [ 21.638410] Buffer I/O error on device sdc1, logical block 96469034 [ 21.638468] Buffer I/O error on device sdc1, logical block 96469035 [ 21.638525] Buffer I/O error on device sdc1, logical block 96469036 [ 21.638581] Buffer I/O error on device
Kernel: Buffer I/o Error On Device
sdc1, logical block 96469037 [ 21.638639] Buffer I/O error on device sdc1, logical block 96469038 [ 21.638696] Buffer I/O error on device sdc1, logical block 96469039 [ 21.638762] Buffer I/O error on device sdc1, logical block 96469040 [ 21.638820] Buffer I/O error on device sdc1, logical block 96469041 [ 23.551857] sd 2:0:0:0: [sdc] Unhandled sense code [ 23.551863] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08 [ 23.551868] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current] [ 23.551874] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0 [ 23.551878] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 a7 00 00 80 00 [ 23.551890] end_request: critical target error, dev sdc, sector 96469159 [ 24.591795] sd 2:0:0:0: [sdc] Unhandled sense code [ 24.591801] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08 [ 24.591806] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current] [ 24.591811] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0 [ 24.591816] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 8f 00 00 08 00 [ 24.591828] end_request: critical target error, dev sdc, sector 96469135I'm not f
and logging By sch on Dec 07, 2005 One of the questions raised at Tuesday night's BoF was
Buffer I/o Error On Dev Async Page Read
"why are some of the statistics that iostat -E displays buffer io error on device sr0 result in a console message and some do not?" I was sitting in the back buffer i/o error on device logical block 0 with a copy of Mike Kupfer's split ON source tree, and decided to have a look. iostat(1M) is a kstat reader, with some simple processing https://bbs.archlinux.org/viewtopic.php?id=129916 and formatted output. The output function is show_disk_errors() but requires understanding how iostat groups the disks and statistics in its implementation; the code that acquires the device statistics is located in cmd/stat/common/acquire_iodevs.c. Searching for error show that the critical function is acquire_iodev_errors(), and that two classes of kstats contribute to the https://blogs.oracle.com/sch/entry/lisa05_tuesday_device_errors_iostat error output: device_error and iopath_error. The most direct way to see these statistics is to invoke kstat(1M) with these classes. On my laptop, the result for device_error is $ kstat -p -c device_error sderr:0:sd0,err:Device Not Ready 0 sderr:0:sd0,err:Hard Errors 0 sderr:0:sd0,err:Illegal Request 1 sderr:0:sd0,err:Media Error 0 sderr:0:sd0,err:No Device 0 sderr:0:sd0,err:Predictive Failure Analysis 0 sderr:0:sd0,err:Product UJ-832D Revision sderr:0:sd0,err:Recoverable 0 sderr:0:sd0,err:Revision 1.50 sderr:0:sd0,err:Serial No sderr:0:sd0,err:Size 0 sderr:0:sd0,err:Soft Errors 1 sderr:0:sd0,err:Transport Errors 0 sderr:0:sd0,err:Vendor MATSHITA sderr:0:sd0,err:class device_error sderr:0:sd0,err:crtime 76.139658104 sderr:0:sd0,err:snaptime 1857.960128997 (The laptop has no kstats of class iopath_error.) We then look for the creation of the named kstat for each of these strings—invocations of kstat_create() to identify the structure member names associated with each. And then we can look for statements that involve those member names; this leads us to the various SDUPDATEERRSTATS() invocations throughout uts/common/io/scsi/targets/sd.c. The discrepancy between updates and logging arises because the macro, SD_UPDATE_ERRSTATS(), which bumps the counters
Help » Desktop Hardware » USB drive not seen as logical block device [SOLVED] « previous next » Print Pages: [1] Go Down Author Topic: http://www.pclinuxos.com/forum/index.php?topic=108096.0 USB drive not seen as logical block device [SOLVED] (Read 12668 times) Jonesy Sr. Member Posts: 394 USB drive not seen as logical block device [SOLVED] « on: August 13, 2012, 06:06:12 AM » This weeks removeable storage saga continues.This time I have a new 64Gb generic USB pen drive which is not recognized as a logical block device. Either that or the error on system is not able to correctly determine the size of the media.lsusb reports Device/ Vendor ID 0011:7788fdisk -l causes the terminal to freeze.Gparted just scans for devices for ever and I have to close it.Dmesg output, for the device only, shows it is seen as:Code: [Select]usb 4-1.3: New USB device found, idVendor=0011, idProduct=7788
usb 4-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-1.3: error on dev Manufacturer: Generic
usb 4-1.3: SerialNumber: 210F8EF1
usb 4-1.4: new low speed USB device using uhci_hcd and address 6
usb 4-1.4: string descriptor 0 malformed (err = -61), defaulting to 0x0409
But not as a logical block device:Code: [Select]sd 2:0:0:0: [sdb] Unhandled error code
sd 2:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
sd 2:0:0:0: [sdb] CDB: Read(10): 28 00 07 c3 7f f8 00 00 01 00
end_request: I/O error, dev sdb, sector 130252792
Buffer I/O error on device sdb, logical block 16281599
usb 4-1.3: reset full speed USB device using uhci_hcd and address 5
usb 4-1.3: reset full speed USB device using uhci_hcd and address 5
usb 4-1.3: reset full speed USB device using uhci_hcd and address 5
usb 4-1.3: reset full speed USB device using uhci_hcd and address 5
usb 4-1.3: reset full speed USB device using uhci_hcd and address 5
usb 4-1.3: reset full speed USB device using uhci_hcd and address 5
sd 2:0:0:0: [sdb] Unhandled error code
sd 2:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
sd 2:0:0:0: [sdb] CDB: Read(10): 28 00 07 c3 7f f8 00 00 01 00
end_request: I/O error, dev sdb, sector 130252792
The device