Hi All,
I noticed this in dmesg the other day

hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
ide: failed opcode was: 0xb0

and i have started to get corrupted data off of it. I assume it is dying,
but thought to ask, as its rather new (*Power On Hours* 827) its a maxtor
160gb.

--

blog.transiency.org -- T's Abstract Art Blog
-----------------------------------------
transiency.org/index.php/Transiency/Home -- T's Wiki

On Aug 6, 2007, at 9:56 AM, Sam wrote:

> Hi All,
> I noticed this in dmesg the other day
>
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0xb0
>
> and i have started to get corrupted data off of it. I assume it is
> dying, but thought to ask, as its rather new ( Power On Hours 827)
> its a maxtor 160gb.

Time to file a warranty claim, I'm guessing. Maxtor has their own
test utility, which you might as well download because they'll want
an error code from it before they do an exchange.

On Aug 6, 2007, at 9:56 AM, Sam wrote:

> Hi All,
> I noticed this in dmesg the other day
>
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0xb0
>
> and i have started to get corrupted data off of it. I assume it is
> dying, but thought to ask, as its rather new ( Power On Hours 827)
> its a maxtor 160gb.

Time to file a warranty claim, I'm guessing. Maxtor has their own
test utility, which you might as well download because they'll want
an error code from it before they do an exchange.

On Mon, 6 Aug 2007, David Brodbeck wrote:

>
> On Aug 6, 2007, at 9:56 AM, Sam wrote:
>
>> Hi All,
>> I noticed this in dmesg the other day
>>
>> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>> hda: drive_cmd: error=0x04 { DriveStatusError }
>> ide: failed opcode was: 0xb0
>>
>> and i have started to get corrupted data off of it. I assume it is dying,
>> but thought to ask, as its rather new ( Power On Hours 827) its a maxtor
>> 160gb.
>
> Time to file a warranty claim, I'm guessing. Maxtor has their own test
> utility, which you might as well download because they'll want an error code
> from it before they do an exchange.
>
>

Use smartctl:

smartctl -a /dev/hda

What does this show?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, 6 Aug 2007, Sam wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Justin, here is the output from smartctl -a /dev/hda
>
> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/

Your disk looks OK to me, I have seen Device Status Error in the past as
well but never suffered any ill effects.

Some other things to try:

smartctl -t short /dev/hda # wait 5min
smartclt -l selftest /dev/hda

smartctl -t long /dev/hda # wait 6-120 min
smartclt -l selftest /dev/hda

and/then show smartctl -a output again
if all the tests pass, your disk should be OK




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Justin, here is the output from smartctl -a /dev/hda

smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: MAXTOR STM3160812A
Serial Number: 4LS62YAM
Firmware Version: 3.AAK
User Capacity: 160,041,885,696 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Aug 6 13:50:49 2007 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection:
Enabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test has
ever
been run.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off
supp

ort.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 54) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_

FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 114 095 006 Pre-fail
Always
-

74351205
3 Spin_Up_Time 0x0003 093 092 000 Pre-fail
Always
-

0
4 Start_Stop_Count 0x0032 100 100 020 Old_age
Always
-

72
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
Always
-

0
7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail
Always
-

84026551
9 Power_On_Hours 0x0032 100 100 000 Old_age
Always
-

828
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
Always
-

0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age
Always
-

82
187 Unknown_Attribute 0x0032 100 100 000 Old_age
Always - 0
189 Unknown_Attribute 0x003a 100 100 000 Old_age
Always
-

0
190 Unknown_Attribute 0x0022 065 055 045 Old_age
Always
-

740425763
194 Temperature_Celsius 0x0022 035 045 000 Old_age
Always
-

35 (Lifetime Min/Max 0/11)
195 Hardware_ECC_Recovered 0x001a 056 048 000 Old_age
Always
-

6712323
197 Current_Pending_Sector 0x0012 100 100 000 Old_age
Always
-

0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
Offline
-

0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age
Always
-

26
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age
Offline
-

0
202 TA_Increase_Count 0x0032 100 253 000 Old_age
Always
-

0

SMART Error Log Version: 1
ATA Error Count: 39 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 39 occurred at disk power-on lifetime: 19 hours (0 days + 19 hours)
When the command that caused the error occurred, the device was active or
idle

..

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 00 00 00 e0 00 00:01:02.122 READ DMA EXT
25 00 08 00 00 00 e0 00 00:01:05.759 READ DMA EXT
10 00 3f 00 00 00 e0 00 00:01:05.309 RECALIBRATE [OBS-4]
25 00 08 00 00 00 e0 00 00:01:05.309 READ DMA EXT
25 00 08 00 00 00 e0 00 00:01:04.858 READ DMA EXT

Error 38 occurred at disk power-on lifetime: 19 hours (0 days + 19 hours)
When the command that caused the error occurred, the device was active or
idle

..

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 00 00 00 e0 00 00:01:02.122 READ DMA EXT
10 00 3f 00 00 00 e0 00 00:01:02.091 RECALIBRATE [OBS-4]
25 00 08 00 00 00 e0 00 00:01:05.309 READ DMA EXT
25 00 08 00 00 00 e0 00 00:01:05.309 READ DMA EXT
25 00 08 00 00 00 e0 00 00:01:04.858 READ DMA EXT


Error 37 occurred at disk power-on lifetime: 19 hours (0 days + 19 hours)
When the command that caused the error occurred, the device was active or
idle

..

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 00 00 00 e0 00 00:01:02.122 READ DMA EXT
25 00 08 00 00 00 e0 00 00:01:02.091 READ DMA EXT
25 00 08 00 00 00 e0 00 00:01:02.072 READ DMA EXT
c6 00 10 00 00 00 e0 00 00:01:01.621 SET MULTIPLE MODE
00 00 40 00 00 00 00 06 00:01:04.858 NOP [Abort queued commands]

Error 36 occurred at disk power-on lifetime: 19 hours (0 days + 19 hours)
When the command that caused the error occurred, the device was active or
idle

..

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 00 00 00 e0 00 00:01:02.122 READ DMA EXT
25 00 08 00 00 00 e0 00 00:01:02.091 READ DMA EXT
c6 00 10 00 00 00 e0 00 00:01:02.072 SET MULTIPLE MODE
00 00 40 00 00 00 00 06 00:01:01.621 NOP [Abort queued commands]
ef 03 40 00 00 00 e0 02 00:01:01.171 SET FEATURES [Set transfer
mode]

Error 35 occurred at disk power-on lifetime: 19 hours (0 days + 19 hours)
When the command that caused the error occurred, the device was active or
idle

..

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 00 00 00 e0 00 00:01:02.122 READ DMA EXT
c6 00 10 00 00 00 e0 00 00:01:02.091 SET MULTIPLE MODE
00 00 40 00 00 00 00 06 00:01:02.072 NOP [Abort queued commands]
ef 03 40 00 00 00 e0 02 00:01:01.621 SET FEATURES [Set transfer
mode]
25 00 08 00 00 00 e0 00 00:01:01.171 READ DMA EXT

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA

_of_first_error
# 1 Extended offline Completed without error 00% 812
-
# 2 Extended offline Completed without error 00% 825
-

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Thanks,
Sam


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGt2FyMwtNS8TLpaIRAr3vAKDZJ1lS5mh3nooBO6U42l QX5BXk6wCfXUTL
kFNyy2fRShyO0BVy1vVIcXs=
=vKd7
-----END PGP SIGNATURE-----
On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>
>
> On Mon, 6 Aug 2007, David Brodbeck wrote:
>
> >
> > On Aug 6, 2007, at 9:56 AM, Sam wrote:
> >
> >> Hi All,
> >> I noticed this in dmesg the other day
> >>
> >> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> >> hda: drive_cmd: error=0x04 { DriveStatusError }
> >> ide: failed opcode was: 0xb0
> >>
> >> and i have started to get corrupted data off of it. I assume it is
> dying,
> >> but thought to ask, as its rather new ( Power On Hours 827) its a
> maxtor
> >> 160gb.
> >
> > Time to file a warranty claim, I'm guessing. Maxtor has their own test
> > utility, which you might as well download because they'll want an error
> code
> > from it before they do an exchange.
> >
> >
>
> Use smartctl:
>
> smartctl -a /dev/hda
>
> What does this show?
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>

Justin,
Should I unmount the drive before doing the tests?

Thanks,
Sam

On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>
>
> On Mon, 6 Aug 2007, Sam wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Justin, here is the output from smartctl -a /dev/hda
> >
> > smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce
> Allen
> > Home page is http://smartmontools.sourceforge.net/
>
> Your disk looks OK to me, I have seen Device Status Error in the past as
> well but never suffered any ill effects.
>
> Some other things to try:
>
> smartctl -t short /dev/hda # wait 5min
> smartclt -l selftest /dev/hda
>
> smartctl -t long /dev/hda # wait 6-120 min
> smartclt -l selftest /dev/hda
>
> and/then show smartctl -a output again
> if all the tests pass, your disk should be OK
>
>
>
>

Justin,
Should I unmount the drive before doing the tests?

Thanks,
Sam

On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>
>
> On Mon, 6 Aug 2007, Sam wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Justin, here is the output from smartctl -a /dev/hda
> >
> > smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce
> Allen
> > Home page is http://smartmontools.sourceforge.net/
>
> Your disk looks OK to me, I have seen Device Status Error in the past as
> well but never suffered any ill effects.
>
> Some other things to try:
>
> smartctl -t short /dev/hda # wait 5min
> smartclt -l selftest /dev/hda
>
> smartctl -t long /dev/hda # wait 6-120 min
> smartclt -l selftest /dev/hda
>
> and/then show smartctl -a output again
> if all the tests pass, your disk should be OK
>
>
>
>

No, smart short and long tests are safe, most people run them daily and
weekly without ever unmounting for long periods of time.

Justin.

On Mon, 6 Aug 2007, Sam wrote:

> Justin,
> Should I unmount the drive before doing the tests?
>
> Thanks,
> Sam
>
> On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>>
>>
>>
>> On Mon, 6 Aug 2007, Sam wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Justin, here is the output from smartctl -a /dev/hda
>>>
>>> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce
>> Allen
>>> Home page is http://smartmontools.sourceforge.net/
>>
>> Your disk looks OK to me, I have seen Device Status Error in the past as
>> well but never suffered any ill effects.
>>
>> Some other things to try:
>>
>> smartctl -t short /dev/hda # wait 5min
>> smartclt -l selftest /dev/hda
>>
>> smartctl -t long /dev/hda # wait 6-120 min
>> smartclt -l selftest /dev/hda
>>
>> and/then show smartctl -a output again
>> if all the tests pass, your disk should be OK
>>
>>
>>
>>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Cool, thanks for the information Justin. Hopefully all turns out well.

On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
> No, smart short and long tests are safe, most people run them daily and
> weekly without ever unmounting for long periods of time.
>
> Justin.
>
> On Mon, 6 Aug 2007, Sam wrote:
>
> > Justin,
> > Should I unmount the drive before doing the tests?
> >
> > Thanks,
> > Sam
> >
> > On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> >>
> >>
> >>
> >> On Mon, 6 Aug 2007, Sam wrote:
> >>
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>>
> >>> Justin, here is the output from smartctl -a /dev/hda
> >>>
> >>> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce
> >> Allen
> >>> Home page is http://smartmontools.sourceforge.net/
> >>
> >> Your disk looks OK to me, I have seen Device Status Error in the past
> as
> >> well but never suffered any ill effects.
> >>
> >> Some other things to try:
> >>
> >> smartctl -t short /dev/hda # wait 5min
> >> smartclt -l selftest /dev/hda
> >>
> >> smartctl -t long /dev/hda # wait 6-120 min
> >> smartclt -l selftest /dev/hda
> >>
> >> and/then show smartctl -a output again
> >> if all the tests pass, your disk should be OK
> >>
> >>
> >>
> >>
> >
>

Cool, thanks for the information Justin. Hopefully all turns out well.

On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
> No, smart short and long tests are safe, most people run them daily and
> weekly without ever unmounting for long periods of time.
>
> Justin.
>
> On Mon, 6 Aug 2007, Sam wrote:
>
> > Justin,
> > Should I unmount the drive before doing the tests?
> >
> > Thanks,
> > Sam
> >
> > On 8/6/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> >>
> >>
> >>
> >> On Mon, 6 Aug 2007, Sam wrote:
> >>
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>>
> >>> Justin, here is the output from smartctl -a /dev/hda
> >>>
> >>> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce
> >> Allen
> >>> Home page is http://smartmontools.sourceforge.net/
> >>
> >> Your disk looks OK to me, I have seen Device Status Error in the past
> as
> >> well but never suffered any ill effects.
> >>
> >> Some other things to try:
> >>
> >> smartctl -t short /dev/hda # wait 5min
> >> smartclt -l selftest /dev/hda
> >>
> >> smartctl -t long /dev/hda # wait 6-120 min
> >> smartclt -l selftest /dev/hda
> >>
> >> and/then show smartctl -a output again
> >> if all the tests pass, your disk should be OK
> >>
> >>
> >>
> >>
> >
>

On Mon, Aug 06, 2007 at 10:59:13AM -0700, Sam wrote:
> Justin,
> Should I unmount the drive before doing the tests?
>

No need. The tests happen at the drive level, below the level of the
filesystem. When you run the test, it should tell you how long to wait
before you query the drive to get the result.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Aug 06, 2007 at 01:56:41PM -0400, Justin Piszcz wrote:

> Your disk looks OK to me, I have seen Device Status Error in the past as
> well but never suffered any ill effects.

If I recall correctly from the Google study, certain smart errors (don't
remember which) mean the drive will fail, but no smart errors doesn't
mean the drive is safe! The study should be easily found with a Google
search.

The OP should back-up anything important if he hasn't done so yet.

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGt4ahqJyztHCFm9kRAmUiAJ4qMvwAdLGY1yuhU1R0I1 Gax3dbJgCgmkNm
rNjKpa6YN1yJKmO80hOvSDs=
=Ia3w
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yeah it is backed up, I just happen to need to drive to expand my
operations. Would be a pity if it was bad.

No errors tho, in both the short and extended tests.


=== 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 Extended offline Completed without error 00% 830
-
# 2 Short offline Completed without error 00% 829
-
# 3 Extended offline Completed without error 00% 812
-




Thanks,
Sam



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGt4tMMwtNS8TLpaIRAiOFAJ9ZvAznd/GYsh39jX+x7euvnyjYagCfTF5z
nM5/caI6DFuh8SJw4j5+evA=
=5TVm
-----END PGP SIGNATURE-----
On 8/6/07, Andrei Popescu <andreimpopescu@gmail.com> wrote:
>
> On Mon, Aug 06, 2007 at 01:56:41PM -0400, Justin Piszcz wrote:
>
> > Your disk looks OK to me, I have seen Device Status Error in the past as
> > well but never suffered any ill effects.
>
> If I recall correctly from the Google study, certain smart errors (don't
> remember which) mean the drive will fail, but no smart errors doesn't
> mean the drive is safe! The study should be easily found with a Google
> search.
>
> The OP should back-up anything important if he hasn't done so yet.
>
> Regards,
> Andrei
> --
> If you can't explain it simply, you don't understand it well enough.
> (Albert Einstein)
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGt4ahqJyztHCFm9kRAmUiAJ4qMvwAdLGY1yuhU1R0I1 Gax3dbJgCgmkNm
> rNjKpa6YN1yJKmO80hOvSDs=
> =Ia3w
> -----END PGP SIGNATURE-----
>
>

On Mon, Aug 06, 2007 at 01:56:41PM -0400, Justin Piszcz wrote:
>
>
> On Mon, 6 Aug 2007, Sam wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Justin, here is the output from smartctl -a /dev/hda
>>
>> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
>> Home page is http://smartmontools.sourceforge.net/
>
> Your disk looks OK to me, I have seen Device Status Error in the past as
> well but never suffered any ill effects.
I had a drive I just replaced because it kept crashing my machine - had the
exact same errors (the error list at the bottom of the report). I failed on
resync of the raid set it was part off, I ran it for about 3 weeks, before this
started to happen.

>
> Some other things to try:
>
> smartctl -t short /dev/hda # wait 5min
> smartclt -l selftest /dev/hda
>
> smartctl -t long /dev/hda # wait 6-120 min
> smartclt -l selftest /dev/hda
>
> and/then show smartctl -a output again
> if all the tests pass, your disk should be OK
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGt5aIkZz88chpJ2MRAreaAKCgWYBbn7TtCXYq8lct+I Dvq1B/nQCg62I+
NFsdnb9OpKzDyummjrQDgrQ=
=p+cs
-----END PGP SIGNATURE-----

On Mon, 6 Aug 2007, Sam wrote:

> Hi All,
> I noticed this in dmesg the other day
>
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0xb0
>
> and i have started to get corrupted data off of it. I assume it is dying,
> but thought to ask, as its rather new (*Power On Hours* 827) its a maxtor
> 160gb.

Have you tried a new cable? I have had errors in one drive when the real
problem was a failure in the other drive sharing the same cable, so if
there are two drives on the cable, try to run some tests with just one at
a time.

--
George N. White III <aa056@chebucto.ns.ca>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, 6 Aug 2007, Sam wrote:

> Hi All,
> I noticed this in dmesg the other day
>
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0xb0
>
> and i have started to get corrupted data off of it. I assume it is dying,
> but thought to ask, as its rather new (*Power On Hours* 827) its a maxtor
> 160gb.

Have you tried a new cable? I have had errors in one drive when the real
problem was a failure in the other drive sharing the same cable, so if
there are two drives on the cable, try to run some tests with just one at
a time.

--
George N. White III <aa056@chebucto.ns.ca>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org