Adaptec Scsi Medium Error
Contents |
log in with your existing support account. Username Password Forgot your username or password? Support Home Answers Ask a Question Your Account Account Overview Support History Account Settings Notifications When a Verify or Low Level Format is attempted on the hard drive, adaptec scsi cable it responds with some error codes. Answer ID 170 | Published 04/27/1999 08:54 AM | Updated adaptec scsi adapter 11/20/2011 09:05 PM When the SCSI Disk Utility is used to format or verify a hard drive, an Unexpected SCSI Command Failure is returned with
Adaptec Usb Scsi
a lot of error information. What does this mean? This information applies to the following Operating System(s): - This information is not operating system specific These errors indicate that SCSI Select encountered a problem with the disk drive or media.
Adaptec 2940 Scsi
Normally some of the following information is displayed: SCSI target ID of the device SCSI CDB Sent (e.g., 03 xx xx....., 04 xx xx indicating the command sent) Host Adapter Status (e.g., 00h No host adapter error - this means that the status of the host adapter is good - no error reported by the host adapter) Target Status (e.g., 02h Check Condition) Sense key (e.g., 03h-Medium error) Common Sense Key errors: 02h--Not ready - Media is not ready to format. Drive adaptec scsi card 39160 may not be up to speed. 03h--Medium error - Disk media may be defective. Attempt to format and then verify again. 04h--Hardware error - If the drive is not spinning up, the disk is probably defective. Try setting the jumper on the drive to spin up at power on. 05h--Illegal Request - Rare, usually indicates firmware issues or the vendor does not allow format. 06h--Unit attention - The unit may be write protected. Check jumper configuration. Disable write protect or Unit Attention jumper. Sense Codes and Sense Code Qualifiers are usually vendor specific: Typical: Error code (hex) Description Byte 12 Byte 13 00 00 No additional information is supplied 01 00 There is no index/sector signal 02 00 There is no seek complete signal 03 00 A write fault occurred 04 00 The drive is not ready and the cause is not reportable 04 01 The drive is not ready, but it is in the process of becoming ready 04 02 The drive is not ready; it is waiting for the initializing command 04 03 The drive is not ready; human intervention is required 04 04 The drive is not ready; the format routine is in process 05 00 The drive does not respond when it is selected 06 00 Track 0 was not found 07 00 More than one drive is selected at a time 08 00 There was a drive communication failure 08 01 A drive communication time-out occurred
Links Notable Members Current Visitors Recent Activity New Profile Posts Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this
Adaptec Scsi Card 29160
forum only Display results as threads More... Recent Posts Menu Log in adaptec scsi card 39320a or Sign up [H]ard|Forum Forums > [H]ard|Ware > SSDs & Data Storage > SCSI trouble Discussion in 'SSDs & Data adaptec scsi card 29160lp Storage' started by mzungu, Sep 10, 2008. Sep 10, 2008 #1 mzungu n00bie Messages: 4 Joined: May 19, 2008 I have no experience with SCSI drives, other then what i have learned http://ask.adaptec.com/app/answers/detail/a_id/170/~/when-a-verify-or-low-level-format-is-attempted-on-the-hard-drive,-it-responds in the last couple of days on Google, so ive come here as my last resort, here is my issue The SCSI Controller and Hard Drive show up in the device manager, but the HD will not show up in Disk Management there is only 1 SCSI drive and its jumpers are set for the 0 slot or whatever its called, also i have the https://hardforum.com/threads/scsi-trouble.1344794/ latest driver update for the controller its running on a win2k (new install), Adaptec card 29320LP Ultra 320 SCSI, Seagate SCSI drive only reason i need to do this is recover data off the drive, i just need a second opinion before i declare the battle over, thanks for anyhelp mzungu, Sep 10, 2008 mzungu, Sep 10, 2008 #1 Sep 10, 2008 #2 sabregen [H]ardForum Junkie Messages: 16,153 Joined: Jun 6, 2005 the adaptec card should have a controller BIOS that asks for a key combination to be pressed to access it. I believe with Adaptec that it is CTRL + A, but check the POST messages for confirmation. Once inside the controller's BIOS, go to SCSI Disk Utilities, and scan the SCIS Bus. If the drive has the jumpers set to 0, it should show up as ID 0 on the bus scan. If it doesn't then power off the system, check your cables, terminator (you'll need one), and ID jumpers are making good physical contact, and retry the system boot. If it still doesn't see the drive, you could check whether the drive is spinning or not by removin
Sep 13, 2013 Messages: 135 Thanks Received: 5 Trophy Points: 21 Location: Bogotá, Colombia I'm running badblocks https://forums.freenas.org/index.php?threads/scsi-sense-medium-error-unrecovered-read-error.20515/ on a bunch of 12 drives prior to putting them into https://ubuntuforums.org/showthread.php?t=1165166 service. Three had already failed SMART self testing so badblocks errors were expected, and duly received, from those. One actually disconnected itself, is that usual for some type of errors? One other disk, which had pass the self testing, started giving errors after 26 adaptec scsi hours (one pass of a badblocks test on these 4TB drives is about 8 hours, iirc), and is producing messages such as these about twice per minute, though the error count is not increasing: Code:Apr 27 19:15:08 freenas kernel: (da4:mps0:0:4:0): READ(16). CDB: 88 00 00 00 00 01 cf 06 db 00 00 00 01 adaptec scsi card 00 00 00 Apr 27 19:15:08 freenas kernel: (da4:mps0:0:4:0): CAM status: SCSI Status Error Apr 27 19:15:08 freenas kernel: (da4:mps0:0:4:0): SCSI status: Check Condition Apr 27 19:15:08 freenas kernel: (da4:mps0:0:4:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Apr 27 19:15:08 freenas kernel: (da4:mps0:0:4:0): Info: 0x1cf06db77 Apr 27 19:15:08 freenas kernel: (da4:mps0:0:4:0): Error 5, Unretryable error Apr 27 19:15:41 freenas kernel: (da4:mps0:0:4:0): READ(16). CDB: 88 00 00 00 00 01 cf 06 e0 00 00 00 01 00 00 00 Apr 27 19:15:41 freenas kernel: (da4:mps0:0:4:0): CAM status: SCSI Status Error Apr 27 19:15:41 freenas kernel: (da4:mps0:0:4:0): SCSI status: Check Condition Apr 27 19:15:41 freenas kernel: (da4:mps0:0:4:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Apr 27 19:15:41 freenas kernel: (da4:mps0:0:4:0): Info: 0x1cf06e0e0 Apr 27 19:15:41 freenas kernel: (da4:mps0:0:4:0): Error 5, Unretryable error Have I really got a FOURTH bad disk? Anything else I should check? Because that would make 4 out of 12 bad and I thought 3 was pretty unlikely... IanWo
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] SCSI DDS tape fails "Medium error" and "error on write filemark" Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 3 of 3 Thread: SCSI DDS tape fails "Medium error" and "error on write filemark" Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 20th, 2009 #1 henrylaw View Profile View Forum Posts Private Message Just Give Me the Beans! Join Date May 2009 Beans 47 SCSI DDS tape fails "Medium error" and "error on write filemark" I'm trying to get an HP DDS2 tape to work with my Ubuntu 8.04 desktop system. I've tried various combinations of tar and dd but on every occasion I get things like this (this is a dd example but it's the same all the time)henry@saturn:~$ sudo dd if=lr.txt of=/dev/st0 obs=512 dd: writing to `/dev/st0': Input/output error dd: closing output file `/dev/st0': Input/output error... associated with log entries like this:[16743.478185] st0: Sense Key : Medium Error [deferred] [16743.478200] st0: Add. Sense: Sequential positioning error [16775.895007] st0: Sense Key : Medium Error [deferred] [16775.895022] st0: Add. Sense: Sequential positioning error [16775.895033] st0: Error on write filemark.I've tried three tape drives, two SCSI adapter cards and three different cables, using both device-internal termination (one of the drives does that) and also a separate terminator on the cable;