Sense Key Recovered Error
Even apply patch http://lkml.org/lkml/2010/4/26/335, and try all mpt fusion driver I can find form 3.04.01 to the latest lsi version 4.0.22. But the scsi-sense-problems are even coming sometimes when partitions of the disk are mounted. Sense: ATA pass through information available I've tried upgrading to the newest firmware (1.28.02.00, 05-MAY-2009), but all that changed is that the hex dump was added to the error message. I can shut the kernel up by > making the recovered error processing clause look for 01/00/1D as well > as REQ_QUIET, but it won't affect this problem. http://onlivetalk.com/sense-key/sense-key-medium-error-sense-code-0x73-0x03-macbook-pro.php
This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Scratch that; I could use smartctl all I wanted, but installing smartd promptly floored the entire card (and with it, the machine, since the RAID went away). Log Out Select Your Language English español Deutsch italiano 한국어 français 日本語 português 中文 (中国) русский Customer Portal Products & Services Tools Security Community Infrastructure and Management Cloud Computing Storage JBoss Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log http://superuser.com/questions/652214/what-does-sense-key-recovered-error-mean
Word for a German "Ausflugscafé" - a cafe mainly catering to people taking a walk Is cardinality a well defined function? end_request: I/O error, dev sda, sector 3903551 md: super_written gets error=-5, uptodate=0 RAID1 conf printout: --- wd:1 rd:2 disk 0, wo:0, o:1, dev:sda1 disk 1, wo:1, o:0, dev:sdb1 RAID1 conf printout: Having a problem logging in?
Current Customers and Partners Log in for full access Log In New to Red Hat? Whenever this happens, it appears like all the disks “hiccup” and the kernel loses contact with the controller for a small while. After a couple of hour of googling, the only interesting pointer I've found is there, thanks to grepping the message in the kernel src dir... Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search
Because "e2fsck" just said something like "FILE SYSTEM MODIFIED" as a conclusion (I didn't record the result). View Responses Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups Are you new to LinuxQuestions.org? Sense: Logical unit failed self-configuration [588675.819312] sd 0:0:4:0: [sde] CDB: Read(10): 28 00 00 5a cc b0 00 00 08 00 [588675.826713] end_request: I/O error, dev sde, sector 5950640 [588675.838005] RAID5
We Acted. More over, I can see kernel these output: Code: ata_id: HDIO_GET_IDENTITY failed for '/dev/sdc' ata_id: HDIO_GET_IDENTITY failed for '/dev/sda' ata_id: HDIO_GET_IDENTITY failed for '/dev/sdb' So, do I have to change sdc only > a small number of commands have to work when the disk > is not ready) but you would think accessing metadata > given the disk has spun up once Don't know if I'm just luckier now or what happened...
This tip is not option specific. https://access.redhat.com/solutions/41612 It mounts without a problem and I was able to do an rsync backup to it without any complaints. It could be reproduced easily by running "while true; do smartctl -a /dev/sdd > /dev/null; done". Trying smartctl -d scsi returns an outright failure.
I am suspecting this issue may be mapped to the end devices also. http://onlivetalk.com/sense-key/sense-key-hardware-error-sense-code-0x09-0x01.php What is behavior in that case? Sense: ATA pass through information > available This is a message the kernel prints out on all recovered error returns (except those marked REQ_QUIET). Another annoyance is that the disk must be ready (i.e.
Bug watch updates for Red Hat Bugzilla are disabled. Regards Changed in linux (Ubuntu): status: Expired → Confirmed TGL (tom-gl) wrote on 2011-05-05: #5 Download full text (4.4 KiB) Similar issue here with an USB-3 disk on the USB-2 port It will automatically gather and attach updated debug information to this report. http://onlivetalk.com/sense-key/sense-key-medium-error-sense-code-0x73-0x03-mac.php Browse other questions tagged centos-6 error-logging dmesg or ask your own question.
It might just be our shonky hardware (our hardware in particular is shonky) but I'm beginning to assume that unless md has spat out the disk or it's showing real errors, I can shut the kernel up by >>> making the recovered error processing clause look for 01/00/1D as well >>> as REQ_QUIET, but it won't affect this problem. >> I tried If you have any questions, please contact customer service.
Comment 17 Ken Stailey 2010-07-20 20:08:27 UTC Related bug reports: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/605939 https://bugzilla.redhat.com/show_bug.cgi?id=616572 Comment 18 pipa.tk 2010-10-29 03:30:34 UTC I also use LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS and
We Acted. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. You won't be able to vote or comment. 234Help: "Recovered error" spam in dmesg on new hard drives (self.sysadmin)submitted 3 years ago by bwoscc[_]ffe-onlyMy 2 hard drives (RAID1) in a server went belly-up a month So I check the /var/log/message and lsscsi, there are 2 firmware version in the server, and all sdX error messages loged are version SD17.
Mark as duplicate Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications. If so, can you try with the latest development release of Ubuntu? Please visit this page to clear all LQ-related cookies. Get More Info Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag.
Contact Novell Linux Support for more information on SUSE Linux Enterprise Server and obtaining the fix: http://support.novell.com/linux Workaround These errors may be ignored, they are caused by a software defect and idProduct 0x5106 bcdDevice 0.02 iManufacturer 2 StoreJet Transcend iProduct 3 StoreJet Transcend iSerial 1 S1WFJDZB109753 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 Gunderson