All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: David Greaves <david@dgreaves.com>
Cc: Linux-ide <linux-ide@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>,
	Nicolas.Mailhot@LaPoste.net, Jens Axboe <axboe@suse.de>,
	Christopher Smith <csmith@nighthawkrad.net>,
	Erik Slagter <erik@slagter.name>,
	hahn@physics.mcmaster.ca, mlaks@verizon.net,
	Soeren Sonnenburg <kernel@nn7.de>,
	mlaks@verizononline.net,
	smartmontools-support@lists.sourceforge.net
Subject: Re: SMART on SATA reporting errors? (was Re: regarding bug #5914 - fs corruption on SATA)
Date: Tue, 07 Feb 2006 14:30:32 -0500	[thread overview]
Message-ID: <43E8F558.4040002@pobox.com> (raw)
In-Reply-To: <43E8E85F.5000905@dgreaves.com>

David Greaves wrote:
> This is a followon to the email below.
> 
> Basically, it seems some SMART commands produce unexpected errrors.
> 
> My Debian smartd config has "-o on" and "-S on" for every drive so it
> puts out lots of errors every time I boot.
> 
> I did a little investigation and I see that when I do:
> # smartctl -o on -data /dev/sdb
> smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
> 
> === START OF ENABLE/DISABLE COMMANDS SECTION ===
> Error SMART Disable Automatic Offline failed: Input/output error
> Smartctl: SMART Disable Automatic Offline Failed.
> 
> (Which is fine if the drive doesn't support it.)
> 
> I unexpectedly get this in dmesg:
> 
> ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata2: status=0x51 { DriveReady SeekComplete Error }
> ata2: error=0x04 { DriveStatusError }
> ata2: no sense translation for status: 0x51
> ata2: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata2: status=0x51 { DriveReady SeekComplete Error }
> ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata2: status=0x51 { DriveReady SeekComplete Error }
> ata2: error=0x04 { DriveStatusError }
> ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata2: status=0x51 { DriveReady SeekComplete Error }
> ata2: error=0x04 { DriveStatusError }
> ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> ata2: status=0x51 { DriveReady SeekComplete Error }
> ata2: error=0x04 { DriveStatusError }


All of your commands are missing "-d ata"

	Jeff



  reply	other threads:[~2006-02-07 19:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26  5:50 regarding bug #5914 - fs corruption on SATA Tejun Heo
2006-01-26  5:51 ` Tejun Heo
2006-01-26  9:14   ` Nicolas Mailhot
2006-01-26  9:21     ` Jens Axboe
2006-01-26 10:01       ` Nicolas Mailhot
     [not found]       ` <5840.192.54.193.25.1138269692.squirrel@rousalka.dyndns.org>
2006-01-26 21:04         ` Nicolas Mailhot
2006-01-27  8:13           ` Jens Axboe
2006-01-27  8:53             ` Nicolas Mailhot
2006-01-27  9:10               ` Jens Axboe
2006-01-27  9:20                 ` Jens Axboe
2006-01-27  9:27                   ` Nicolas Mailhot
2006-01-27  9:46                   ` Bartlomiej Zolnierkiewicz
2006-01-27  9:50                     ` Jens Axboe
2006-01-27 19:37                       ` Nicolas Mailhot
2006-01-27 23:54                         ` Nicolas Mailhot
2006-01-30 15:08                           ` Jens Axboe
2006-01-30 23:33                             ` Nicolas Mailhot
2006-01-31  7:26                               ` Jens Axboe
2006-01-31  8:39                                 ` Nicolas Mailhot
2006-01-31  8:47                                   ` Jens Axboe
2006-01-31 22:54                                     ` Nicolas Mailhot
2006-01-27 12:12             ` Ric Wheeler
2006-01-27 12:23               ` Jens Axboe
2006-01-26  9:18 ` Jens Axboe
2006-01-26 14:11   ` Bartlomiej Zolnierkiewicz
2006-01-26 14:27     ` Jens Axboe
2006-01-26 16:41 ` David Greaves
2006-01-26 16:58   ` Jeff Garzik
2006-01-26 17:15     ` David Greaves
2006-02-07 18:35       ` SMART on SATA reporting errors? (was Re: regarding bug #5914 - fs corruption on SATA) David Greaves
2006-02-07 19:30         ` Jeff Garzik [this message]
2006-02-08  7:21           ` David Greaves
2006-01-26 17:20     ` regarding bug #5914 - fs corruption on SATA Soeren Sonnenburg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E8F558.4040002@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Nicolas.Mailhot@LaPoste.net \
    --cc=axboe@suse.de \
    --cc=csmith@nighthawkrad.net \
    --cc=david@dgreaves.com \
    --cc=erik@slagter.name \
    --cc=hahn@physics.mcmaster.ca \
    --cc=htejun@gmail.com \
    --cc=kernel@nn7.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=mlaks@verizon.net \
    --cc=mlaks@verizononline.net \
    --cc=smartmontools-support@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.