public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rick Jansen <rick@rockingstone.nl>
To: Daniel Egger <de@axiros.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DriveReady SeekComplete Error
Date: Fri, 4 Jun 2004 15:53:26 +0200	[thread overview]
Message-ID: <20040604135326.GD1684@web1.rockingstone.nl> (raw)
In-Reply-To: <E0E7D4BA-B62C-11D8-B781-000A958E35DC@axiros.com>

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Fri, Jun 04, 2004 at 03:41:27PM +0200, Daniel Egger wrote:
> This is usually also a bad sign, escpecially if the size is caused
> by the Error Log Structure areas.
> 
> Please send the info of smartctl -v <device>. This should give a
> good indication of whether this is a kernel or a drive problem
> because it will show some of the internal status of the drive.
> 
> Servus,
>       Daniel

I don't think -v is the option you mean:

smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=======> INVALID ARGUMENT TO -v: /dev/hda <======= 
=======> VALID ARGUMENTS ARE:
	help
	9,halfminutes
	9,minutes
	9,seconds
	9,temp
	192,emergencyretractcyclect
	193,loadunload
	194,10xCelsius
	194,unknown
	198,offlinescanuncsectorct
	200,writeerrorcount
	201,detectedtacount
	220,temp
	N,raw8
	N,raw16
	N,raw48
<=======

Use smartctl -h to get a usage summary


-- 
Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-04 13:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04  7:54 DriveReady SeekComplete Error Rick Jansen
2004-06-04  9:02 ` Daniel Egger
2004-06-04  9:38   ` John Bradford
2004-06-04  9:43 ` John Bradford
2004-06-04  9:54   ` Rick Jansen
2004-06-04  9:59     ` Jens Axboe
2004-06-04 10:02       ` Rick Jansen
2004-06-04 10:08         ` Jens Axboe
2004-06-04 13:02           ` Andy Hawkins
2004-06-04 13:41     ` Daniel Egger
2004-06-04 13:53       ` Rick Jansen [this message]
2004-06-04 14:05         ` John Bradford
2004-06-04 14:18           ` Rick Jansen
2004-06-04 19:32             ` Bruce Allen
2004-06-04 14:15         ` Daniel Egger
2004-06-04 14:09     ` John Bradford
  -- strict thread matches above, loose matches on Subject: below --
2004-06-04 10:15 mattia
2004-06-04 10:22 ` Jens Axboe
2004-06-04 11:44   ` Bartlomiej Zolnierkiewicz
2004-06-04 11:56     ` Jens Axboe
2004-06-04 12:15       ` Bartlomiej Zolnierkiewicz
2004-06-04 12:17         ` Jens Axboe
2004-06-04 12:40           ` Bartlomiej Zolnierkiewicz
2004-06-04 21:55           ` Ed Tomlinson
2004-06-04 19:58 ` Eric D. Mudama
2004-06-05 13:48   ` mattia
2004-07-13 12:30 Dhruv Matani
2004-07-13 12:32 ` Dwayne Rightler
     [not found] ` <40F3D4AC.9050407@gardenali.biz>
2004-07-13 14:27   ` Dhruv Matani
2004-07-13 14:29   ` Dhruv Matani
2004-07-13 14:47   ` Dhruv Matani
2004-07-13 15:01     ` Bartlomiej Zolnierkiewicz
2004-07-13 12:44 Piszcz, Justin Michael
2004-07-13 15:57 ` Dwayne Rightler
2004-07-13 17:23 Piszcz, Justin Michael
2004-07-14 20:10 ` Dwayne Rightler
2004-07-15  4:08   ` Dhruv Matani
2004-07-26 14:32   ` Dhruv Matani
2004-07-26 14:51     ` Dwayne Rightler
2004-08-20  3:22   ` Dhruv Matani

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=20040604135326.GD1684@web1.rockingstone.nl \
    --to=rick@rockingstone.nl \
    --cc=de@axiros.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox