search for: ascq

...; vendorId: 10de deviceId: 03ec subVendorId: 1849 subDeviceId: 03ec pciType: 1 pcidom: 0 pcibus: 0 pcidev: 6 pcifn: 0 ------- dmesg -------- astFailedSense=0x03 } ide: failed opcode was: unknown ATAPI device hdb: Error: Medium error -- (Sense key=0x03) (reserved error code) -- (asc=0x02, ascq=0x00) The failed "Read 10" packet command was: "28 00 00 00 34 e7 00 00 20 00 00 00 00 00 00 00 " end_request: I/O error, dev hdb, sector 54172 hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } hdb: media error (bad sector): error=0x34 { AbortedCo...

...; vendorId: 10de deviceId: 03ec subVendorId: 1849 subDeviceId: 03ec pciType: 1 pcidom: 0 pcibus: 0 pcidev: 6 pcifn: 0 ------- dmesg -------- astFailedSense=0x03 } ide: failed opcode was: unknown ATAPI device hdb: Error: Medium error -- (Sense key=0x03) (reserved error code) -- (asc=0x02, ascq=0x00) The failed "Read 10" packet command was: "28 00 00 00 34 e7 00 00 20 00 00 00 00 00 00 00 " end_request: I/O error, dev hdb, sector 54172 hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } hdb: media error (bad sector): error=0x34 { AbortedCo...

...Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Vendor: SEAGATE Serial Number: 9946626576 Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Sense Key: Unit Attention Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] ASC: 0x29 (power on occurred), ASCQ: 0x1, FRU: 0x1 Jul 8 20:12:59 fortress scsi: [ID 107833 kern.warning] WARNING: / sbus at 1f,0/SUNW,fas at 2,8800000/sd at 6,0 (sd19): Jul 8 20:12:59 fortress Error for Command: write(10) Error Level: Retryable Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Request...

...ted Block: 1380679073 Error Block: 1380679073 Aug 16 13:14:16 nas-hz-02 scsi: Vendor: DELL Serial Number: Aug 16 13:14:16 nas-hz-02 scsi: Sense Key: Unit Attention Aug 16 13:14:16 nas-hz-02 scsi: ASC: 0x29 (device internal reset), ASCQ: 0x4, FRU: 0x0 Aug 16 13:14:16 nas-hz-02 scsi: WARNING: /scsi_vhci/disk at g60026b900053aa180000029e4b8f0d61 (sd41): Aug 16 13:14:16 nas-hz-02 Error for Command: write(10) Error Level: Retryable Aug 16 13:14:16 nas-hz-02 scsi: Requested Block: 1380679072 Error Block: 13...

...ed around the md''s for volume management. I currently am running 3 domUs, each with LVM backed vbd''s. This server has been up for nearly a month. I am getting these types of kernel messages: ata4: status=0x50 { DriveReady SeekComplete } sdc: Current: sense key=0x0 ASC=0x0 ASCQ=0x0 ata2: status=0x50 { DriveReady SeekComplete } sdb: Current: sense key=0x0 ASC=0x0 ASCQ=0x0 ata1: status=0x50 { DriveReady SeekComplete } sda: Current: sense key=0x0 ASC=0x0 ASCQ=0x0 ata4: status=0x50 { DriveReady SeekComplete } sdc: Current: sense key=0x0 ASC=0x0 ASCQ=0x0 ata2: stat...

...port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f irq 16 at device 0.0 on pci2 atapci0: [ITHREAD] ata2: <ATA channel 0> on atapci0 ata2: [ITHREAD] acd0: DVDR <HL-DT-STDVD-RAM GH22LP20/1.02> at ata2-master UDMA66 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata2 bus 0 target 0 lun 0 cd0: <HL-DT-ST DVD-RAM GH22LP20 1.02> Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x0...

Hi, I get these below information. Please help me understand about "SMART Health Status: FAILURE PREDICTION THRESHOLD EXCEEDED: ascq=0x5 [asc=5d, ascq=5]" and what does that error mean. Does it mean that the SAS disk 0 is failing and has serious issues and needs to be replaced and also do i need to run health status test with different options/flags or switches. /usr/sbin/smartctl -d megaraid,0 -a /dev/sda smartctl 5.42 20...

...73 > Error Block: 1380679073 > > Aug 16 13:14:16 nas-hz-02 scsi: Vendor: DELL > Serial Number: > > Aug 16 13:14:16 nas-hz-02 scsi: Sense Key: Unit Attention > > Aug 16 13:14:16 nas-hz-02 scsi: ASC: 0x29 (device internal > reset), ASCQ: 0x4, FRU: 0x0 > > Aug 16 13:14:16 nas-hz-02 scsi: WARNING: > /scsi_vhci/disk at g60026b900053aa180000029e4b8f0d61 (sd41): > > Aug 16 13:14:16 nas-hz-02 Error for Command: write(10) > Error Level: Retryable > > Aug 16 13:14:16 nas-hz-02 scsi: Requested Block:...

...ine, for example with either ''vlc dvd:///dev/acd0@2'' or ''mplayer dvd://2'' I wonder whether the problem is related to the FAILURE line in dmesg: acd0: DVDR <MATSHITADVD-RAM UJ-852S/1.01> at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: <MATSHITA DVD-RAM UJ-852S 1.01> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Adding ''device at...

James, patch 1 fixes scanning of LUNs whose number is greater than 255. QEMU passes a max_lun of 16383 (because it uses SAM numbering) but in Linux it must become 32768 (because LUNs above 255 are "relocated" to 16640). Patch 2 is a resubmission of the patch for online resizing of virtio-scsi LUNs, which needs to be rebased. LUNs above 255 now work for all of scanning, hotplug,

James, patch 1 fixes scanning of LUNs whose number is greater than 255. QEMU passes a max_lun of 16383 (because it uses SAM numbering) but in Linux it must become 32768 (because LUNs above 255 are "relocated" to 16640). Patch 2 is a resubmission of the patch for online resizing of virtio-scsi LUNs, which needs to be rebased. LUNs above 255 now work for all of scanning, hotplug,

Hi all, First, I''ll say my intent is not to spam a bunch of lists, but after posting to opensolaris-discuss I had someone communicate with me offline that these lists would possibly be a better place to start. So here we are. For those on all three lists, sorry for the repetition. Second, this message is meant to solicit help in diagnosing the issue described below. Any hints on

...0 Aug 2 14:46:06 exodus scsi: [ID 107833 kern.notice] Vendor: ATA Serial Number: Aug 2 14:46:06 exodus scsi: [ID 107833 kern.notice] Sense Key: Illegal_Request Aug 2 14:46:06 exodus scsi: [ID 107833 kern.notice] ASC: 0x20 (invalid command operation code), ASCQ: 0x0, FRU: 0x0 Aug 2 14:46:06 exodus scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci1043,8239 at 5/disk at 0,0 (sd0): Aug 2 14:46:06 exodus Error for Command: log_sense Error Level: Informational Aug 2 14:46:06 exodus scsi: [ID 107833 kern.notice] Requested Block: 0...

...or: ATA Serial Number: Nov 8 03:58:22 mondo4 scsi: [ID 107833 kern.notice] Sense Key: Unit Attention Nov 8 03:58:22 mondo4 scsi: [ID 107833 kern.notice] Sense Key: Unit Attention Nov 8 03:58:22 mondo4 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0 Nov 8 03:58:22 mondo4 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0 Nov 8 04:13:59 mondo4 scsi: [ID 107833 kern.notice] Requested Block: 1450487074 Error Block: 1450487074 Nov 8 04:13:59 mondo4 scsi: [ID...

...gives me following error : [370517.203926] sd 0:0:15:0: [sdo] Device not ready [370517.203930] sd 0:0:15:0: [sdo]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [370517.203935] sd 0:0:15:0: [sdo]  Sense Key : Not Ready [current] [370517.203940] sd 0:0:15:0: [sdo]  ASC=0x4 <<vendor>> ASCQ=0xf2 [370517.203946] sd 0:0:15:0: [sdo] CDB: Write(10): 2a 00 00 00 6a 00 00 00 80 00 [370517.203955] end_request: I/O error, dev sdo, sector 27136 [370517.204236] sd 0:0:15:0: [sdo] Device not ready [370517.204240] sd 0:0:15:0: [sdo]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [370517.204244]...

I got an email from smartd yesterday with the following error: SMART Health Status: SERVO IMPENDING FAILURE SEEK ERROR RATE TOO HIGH [asc=5d,ascq=43] I understand this means the drive is probably going to fail. This device is /dev/sda and is part of /dev/mapper/VolGroup00-LogVol00 Is it possible to replace the single failing drive and if so, what would be the steps so that data isn't lost. TIA for any guidance. Mike

...thus require high disk usage i get this error in dom0''s dmesg: ATA: abnormal status 0xD0 on port 0x9F7 ATA: abnormal status 0xD0 on port 0x9F7 ATA: abnormal status 0xD0 on port 0x9F7 ata1: command 0x35 timeout, stat 0xd0 host_stat 0x20 ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00 ata1: status=0xd0 { Busy } sd 0:0:0:0: SCSI error: return code = 0x8000002 sda: Current: sense key: Aborted Command Additional sense: Scsi parity error end_request: I/O error, dev sda, sector 118401022 And the filesystem automatically is mounted with read-only. You can help-me? Bru...

...g then worked fine. As far as I know it was using UDMA33. That's what the BIOS said it was using anyway. With FreeBSD 4.8 I use "hw.ata.atapi_dma=1" at boot. This then tells me it is using UDMA33. Unfortunately, I then often get this: acd0: READ_BIG - HARDWARE ERROR asc=0x08 ascq=0x03 error=0x00 I think this means a DMA error. (PS why not say what it is?) If I use atacontrol to downgrade to WDMA2, it works flawlessly (though somewhat slower than it does in UDMA33 mode). So, was 4.5 setting my hardware to WDMA2 when I thought it was doing UDMA33? Has 4.8 introduced bugs...

...Block: 5301376 Error Block: 5301376 Jul 7 22:35:04 merope scsi: Vendor: ATA Serial Number: CVEM849300BM Jul 7 22:35:04 merope scsi: Sense Key: Unit Attention Jul 7 22:35:04 merope scsi: ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0 Jul 7 22:35:09 merope scsi: WARNING: /pci at 0,0/pci10de,375 at f/pci1000,3150 at 0/sd at f,0 (sd32): Jul 7 22:35:09 merope Error for Command: write(10) Error Level: Retryable Jul 7 22:35:09 merope scsi: Requested Block: 5315248 Error Block: 531...

...humper2 scsi: [ID 107833 kern.notice] Vendor: ATA Serial Number: WD-WCAP Aug 11 18:20:52 thumper2 scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention Aug 11 18:20:52 thumper2 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0 Along whit these messages there are a lot of this messages: Aug 11 18:20:51 thumper2 scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,2690 at 1c/pci1000,3140 at 0 (mpt1): Aug 11 18:20:51 thumper2 Log info 0x31123000 received for target 5. Aug 11 18:20:51 thumper2 scsi_...