Enclosure Services Checksum Error
Contents |
Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & Software Colloquium Linux hardware error enclosure services checksum error Kung Fu Windows Technical Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's
Checksum Error In The Encrypted File Winrar
Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom checksum error windows 7 The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries Dell 2950 Enclosure checksum errors - should I be worried? 9 posts Barmaglot Ars Tribunus Angusticlavius et Subscriptor Tribus: Israel Registered: Jan 18, 2006Posts: 9368
Checksum Error Fix
Posted: Tue May 31, 2011 6:42 am Dell PowerEdge 2950 III, PERC6/i, 2x144GB SAS drives in RAID1 used only for booting ESX 4.1. For a while now, it's been logging the following message once every few days:Unexpected sense. SCSI sense data: Sense key: 4 Sense code: 35 Sense qualifier: 5: Enclosure 0:0 Controller 0, Connector 0Going by this wiki article, this refers to "Hardware Error - enclosure services checksum error". Both Server Administrator and IT Assistant classify checksum error witcher 3 this as 'severity:normal'. Server is out of warranty so I can't contact Dell. 102 days of uptime since last time the system was patched, no signs of instability of any kind, but I'm still sort of worried. sryan2k1 Ars Legatus Legionis et Subscriptor Tribus: Ann Arbor, MI Registered: Nov 28, 2002Posts: 34238 Posted: Tue May 31, 2011 9:04 am Quote:Server is out of warranty so I can't contact Dell.Actually for enterprise equipment they will do the best to help you out short of dispatching parts, they will even suggest some rather....out of the normal fixes since it's already out of warranty. Barmaglot Ars Tribunus Angusticlavius et Subscriptor Tribus: Israel Registered: Jan 18, 2006Posts: 9368 Posted: Tue May 31, 2011 9:13 am Hmmm, not in my experience - maybe for huge customers? I guess it won't hurt to try to call them tomorrow, but I'm not holding my breath. Nevarre Ars Legatus Legionis Tribus: Steam:Nevarre12 Registered: Aug 19, 2003Posts: 19271 Posted: Tue May 31, 2011 6:25 pm At least domestically, the support side is perpetual, the warranty is not. They'll tell you what's what and how to fix it if need be-- you just don't get the parts for free anymore.The quality of the service may differ based on your organization, but it should still be present. forky Ars Tribunus Militum et Subscriptor Registered: Aug 24, 2003Posts: 1811 Posted: T
you quickly. I am interested in fun and interesting work opportunities. You may view my resume in PDF or Word format. I have removed my address and my
Checksum Error On Boot
phone number. Please send me an email if you need to get in touch
Checksum Error Wireshark
with me. SCSI Sense Codes a command is issued a command completes if command completes with a CHECK CONDITION status: checksum error zip sense data is returned in the same I_T_L_Q nexus transaction as CHECK CONDITION after sense data is returned, it is usually cleared, except: it is associated with a unit attention condition AND UA_INTLCK_CTRL field http://arstechnica.com/civis/viewtopic.php?t=1146267 contains either 10b or 11b Steps to decoding sense data: check the sense key. this provides basic information about the error check the additional sense length. this tells how many more bytes of info check asc & ascq. this provides detailed info about the error check SKSV bit (sense key specific valid). 1 (set) = there is more detail in bytes 15 - 17
Sense Codes Sense Key Name http://richgoldstein.net/KB/Scsi/scsi_sense_codes.html Description 0h No Sense Indicates there is no specific Sense Key information to be reported for the disc drive. This would be the case for a successful command or when the ILI bit is one. 1h Recovered Error Indicates the last command completed successfully with some recovery action performed by the disc drive. When multiple recovered errors occur, the last error that occurred is reported by the additional sense bytes. Note: For some Mode settings, the last command may have terminated before completing. 2h Not Ready Indicates the logical unit addressed cannot be accessed. Operator intervention may be required to correct this condition. 3h Medium Error Indicates the command terminated with a non-recovered error condition, probably caused by a flaw in the medium or an error in the recorded data. 4h Hardware Error Indicates the disc drive detected a nonrecoverable hardware failure while performing the command or during a self test. This includes SCSI interface parity error, controller failure or device failure. 5h Illegal Request Indicates an illegal parameter in the command descriptor block or in the additional parameters supplied as data for some commands (Format Unit, Mode Select, and so forth). If the disc drive detects an invalid parameter in the Command Descriptor Block, it shall termisorted by: [ date ] [ thread ] [ subject ] [ author ] Thanks guys... I have forwarded the comments from Scott to the Dell and hope for the best.... Thank you again..... VJ On Thu, Nov https://lists.freebsd.org/pipermail/freebsd-questions/2008-November/186416.html 13, 2008 at 2:51 PM, Scott Long