[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problem with SATA disk, difference between standard kernel and Debian kernel



On Thu, Dec 11, 2008 at 01:37:57PM +1100, Alex Samad wrote:

> have you tried smartctl -H <device> and smartctl -t short|long
> <device>

Yes, there doesn't seem to be anything unusual:


cat:/home/lee# smartctl -H /dev/sdb
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

cat:/home/lee# smartctl -t short /dev/sdb
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Wed Dec 10 23:53:43 2008

Use smartctl -X to abort test.
cat:/home/lee# smartctl -l selftest /dev/sdb
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      9158         -


I've started a long test, but it says it'll take about two hours. I'll
let you know the result.


BTW, what is this value for lifetime hours? It's the same value as
"smartctl -A" reports for "Power_On_Hours", but /sda has 9663 and /sdb
has 9158. Both values would have to be identical if they represent
what their name suggests: These disks have always been powered or
turned off at the same time, with no exceptions. Their actual "power
on hours" are identical, if not to the second, the at least to the
minute. There's no way they could differ by 500 hours. --- Digging in
my mails turned up that they were probably bought in April 2006; they
have been used until June 2007 and then not been used until about this
month. That makes for about 9.5k hours.


cat:/home/lee# smartctl -A /dev/sda
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  9 Power_On_Hours          0x0032   226   226   000    Old_age   Always       -       9663
cat:/home/lee# smartctl -A /dev/sdb
  9 Power_On_Hours          0x0032   227   227   000    Old_age   Always       -       9158


> tried changing the cable ?

Yes, I'm using different cables that came with the new board. The old
board (Asus A8N-SLI with an AMD64-4000) had a totally different
chipset as well:


0000:00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)


The kernel version was 2.6.16.2 when the disks were new, using the
sata_nv (or nv_sata) module.

The new board is a Gigabyte GA-P35-DS3L with a 3GHz Intel
Dual-Core. And the AMD was actually a bit faster, if you consider the
CPU alone ...


Anyway, if it's a software problem, it's probably not the module for
the particular controller but something else. That people with all
kinds of different hardware have this problem supports this theory.

Hm, and I haven't seen anyone using Debian reporting it ... Is there
anybody here who has seen it?


-- 
"Don't let them, daddy. Don't let the stars run down."
http://adin.dyndns.org/adin/TheLastQ.htm


Reply to: