Ata1 Status 0x51 Driveready Seekcomplete Error
Contents |
Technology - unRAID Server Community » Deprecated » unRAID Server 4.5 [No new topics] » status=0x51 { DriveReady SeekComplete Error } « previous next » Send this topic Print Pages: [1] Go Down Author Topic: drive_cmd status 0x51 driveready seekcomplete error status=0x51 { DriveReady SeekComplete Error } (Read 2287 times) eroz Hero Member Posts: 753
Hdc Drive_cmd Status 0x51 Driveready Seekcomplete Error
status=0x51 { DriveReady SeekComplete Error } « on: October 23, 2010, 12:10:02 PM » I added the AOC-SASLP-MV8 card and 2 new drives, Seagate 2TB 5900rpm which I flashed the firmware to cc35 and a Samung 1TB F3. I didn't change any bios settings anywhere. I started to preclear these 2 drives and I noticed this error repeating, Oct 23 13:50:20 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00Oct 23 13:50:20 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error }Oct 23 13:50:20 Tower kernel: ata1: error=0x04 { DriveStatusError }Any help determining what is wrong is greatly appreciated.http://pastebin.com/Fv3ZwLuk Report to moderator Logged MB - AsRock z170 Extreme7+; CPU - Intel i7-6700k; 16GB of RAM; Controller - Supermicro AOC-SASLP-MV8 & M1015Drives 1 - 6TB ST6000DX000 (parity); 2 - 6TB ST6000DX000; 1 - 4TB WD40EFRX; 3 - 3TB WD30EFRX; 2 - 3TB ST3000DM001; 1 - 2TB HDS5C3020ALA632; 2 - 240GB CT240BX200SSD1 CACHE POOL) eroz Hero Member Posts: 753 Re: status=0x51 { DriveReady SeekComplete Error } « Reply #1 on: October 24, 2010, 01:33:32 PM » The Preclear script finished on the Samsung and it came up with no smart report since the drive had it disabled. Followed the advice, smartctl -s on /dev/sdb to turn it on. Running preclear on the samsung drive again. Now I notice the errors are gone but a new one has surfaced.QuoteOct 24 15:28:20 Tower ata_id[4378]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'Oct 24 15:28:20 Tower ata_id[4393]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'Oct 24 15:29:21 Tower ata_id[4756]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'Oct 24 15:29:22 Tower ata_id[4773]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'Oct 24 15:30:24 Tower ata_id[5181]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'Oct 24 15:30:24 Tower ata_id[5196]: HDIO_GET_IDENTITY failed for '/dev/block/8:32' This error only seems to appear when I open the unmenu webpage.From searching on the site, it seems I do not have anything to worry about this message. Report to moderator Logged MB - AsRock z170 Extreme7+; CPU - Intel i7-6700k; 16GB of RAM; Controller - Supermicro AOC-SASLP-MV8 & M1015Drives 1 - 6TB ST6000DX000 (parity); 2 - 6TB ST6000DX000; 1 - 4TB WD40EFRX; 3 - 3TB WD30EFRX; 2 - 3TB ST3000DM001; 1 - 2TB HDS5C3020ALA632
12:28:22 +0200 Message-id: <200603101228.22512.duncangareth@yahoo.co.uk> Reply-to: debian-user@lists.debian.org In-reply-to: <3afbacad0603100152n8a7cad7kd77beddaa30f5b39@mail.gmail.com> References: <3afbacad0603100152n8a7cad7kd77beddaa30f5b39@mail.gmail.com> On Friday, 10 March 2006 11:52, Jim MacBaine wrote: > Hello, > > one of my hard drives seems to be dying. To me as a layman this looks > as if the disk should be returned to the shop where I bought it. Is > this right? > > ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04 > ata1: status=0x51 { DriveReady SeekComplete Error } > ata1: error=0x40 { UncorrectableError } > ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04 > ata1: status=0x51 { DriveReady SeekComplete Error } > ata1: error=0x40 { http://lime-technology.com/forum/index.php?topic=8441.0 UncorrectableError } > ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04 > ata1: status=0x51 { DriveReady SeekComplete Error } > ata1: error=0x40 { UncorrectableError } > ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04 > ata1: status=0x51 { DriveReady SeekComplete Error } > ata1: error=0x40 { UncorrectableError } > ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04 > ata1: status=0x51 { DriveReady SeekComplete Error https://lists.debian.org/debian-user/2006/03/msg01005.html } > ata1: error=0x40 { UncorrectableError } > sd 0:0:0:0: SCSI error: return code = 0x8000002 > sda: Current: sense key=0x3 > ASC=0x11 ASCQ=0x4 > end_request: I/O error, dev sda, sector 145661514 > > It is a Seagate Barracuda 7200.8 SATA drive with 200 GB capacity and > a member of a raid5 md device. > > Shouldn't the md driver kick mark this drive as faulty and kick it out > of the array? After I noticed the error in the syslog, I had to mark > it faulty manually with mdadm. > > Regards, > Jim Since it's a Seagate you're in luck, because they have a carry-in warranty replacement policy. I have seen these kinds of errors before, shortly before my Barracuda died a tragic death. It is most likely to be the drive. Get it swapped out. cheers Duncan ___________________________________________________________ Yahoo! Photos ? NEW, now offering a quality print service from just 8p a photo http://uk.photos.yahoo.com Reply to: debian-user@lists.debian.org Duncan Anderson (on-list) Duncan Anderson (off-list) References: Hard disk failure? From: "Jim MacBaine"
] [ thread ] [ subject ] [ author ] Hello, I https://www.redhat.com/archives/redhat-list/2005-September/013638.html habe a problem using my HP-xw6200 workstation on Red Hat AS4u1. Often when I try to access files the disk seems to be idle a http://mybookworld.wikidot.com/forum/t-37543/worrisome-error-messages-about-the-hard-drive-badcrc nd also everything is "blocked". You cannot work anymore and need to wait for some time. The performance also is very slow on th status 0x51 e harddisk(s). Here are the errors in /var/log/messages: Sep 13 07:59:36 desperado kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Sep 13 07:59:36 desperado kernel: ata1: error=0x40 { UncorrectableError } Sep 13 07:59:40 desperado kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Sep 13 07:59:40 desperado kernel: ata1: error=0x40 status 0x51 driveready { UncorrectableError } Sep 13 07:59:44 desperado kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Sep 13 07:59:44 desperado kernel: ata1: error=0x40 { UncorrectableError } Sep 13 07:59:50 desperado kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Sep 13 07:59:50 desperado kernel: ata1: error=0x40 { UncorrectableError } Anyhow the harddisk(s) seem to be ok!? But it gives me the feeling that either there is a strong sata problem with RHAS4u1 or th ere is a hardware problem. Kind regards, Harald -- --- Harald Pfaender mailto:pharald at gmx.de ICQ: 121699468 GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl Previous message: postgresql with linux enterprise 4 Next message: How to build one binary for all Redhat systems? Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the redhat-list mailing list
Links Browse Recent changes List all pages Page Calendar Site members FAQs How do I join? What is a Wiki? How can I edit pages? Site Manager Page tags automatic book community digital dvd edition files forum ftp home ipkg irc kernel links login my mybook mybooklive mybookworld nas optware php repair rescue ssh sync unison webdav western world Add a new page Worrisome error messages about the hard drive(BadCRC) Forum » Forum / My Book World Edition (blue rings) » Worrisome error messages about the hard drive(BadCRC) Started by: Frido Date: 26 Jan 2008 09:05 Number of posts: 5 RSS: New posts Summary: Error messages in messages log from dmesg show BadCRC errors. Unfold All Fold All More Options Edit Title & Description Stickness Lock Thread Move Thread Fold Worrisome error messages about the hard drive(BadCRC) Frido 26 Jan 2008 09:05 I broke out my new MBWE from the package, set it up, enabled ssh and done nothing else since then except trying to back up some files. As I was making my first Big transfer, suddenly I see Timeout from my nautilus. I inspect MBWE and see that except for ping the device is unresponsive. I reboot it by disconnecting from the power and disregard it, hopefully, as a fluke. It happened 3 more times since then. Then stopped for now. I've started going over logs and dmesg. I noticed the following errors, which look partly worrisome. Jan 2518:55:49 MyBookWorld user.err kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00 Jan 2518:55:49 MyBookWorld user.warn kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Jan 2518:55:49 MyBookWorld user.warn kernel: ata1: error=0x84 { DriveStatusError BadCRC } Jan 2518:55:52 MyBookWorld user.err kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00 Jan 2518:55:52 MyBookWorld user.warn kernel: ata1: status=0x51 { DriveReady SeekComplete Error } I'm more worried about the BadCRC one than anything else there to be honest. I haven't found yet any satisfying Google answers as most only showed up about DriveStatusError without BadCRC. Anyone got a clue what's the meaning of it? I know what a Bad CRC is in general, and it