Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #215310 > unrolled thread

Re: Signs of hard drive failure?

Started byGreg Wooledge <wooledg@eeg.ccf.org>
First post2019-10-21 15:40 +0200
Last post2019-10-22 21:20 +0200
Articles 8 — 6 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Signs of hard drive failure? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-10-21 15:40 +0200
    Re: Signs of hard drive failure? Renato Gallo <renato@aster-lab.com> - 2019-10-22 11:10 +0200
    Re: Signs of hard drive failure? elvis <elvis@dogonfire.com> - 2019-10-22 11:30 +0200
      Re: Signs of hard drive failure? David Wright <deblis@lionunicorn.co.uk> - 2019-10-22 17:00 +0200
        Re: Signs of hard drive failure? elvis <elvis@dogonfire.com> - 2019-10-22 23:20 +0200
          Re: Signs of hard drive failure? Christopher David Howie <me@chrishowie.com> - 2019-10-23 01:00 +0200
    Re: Signs of hard drive failure? Christopher David Howie <me@chrishowie.com> - 2019-10-22 19:40 +0200
    Re: Signs of hard drive failure? Bob Weber <bobrweber@gmail.com> - 2019-10-22 21:20 +0200

#215310 — Re: Signs of hard drive failure?

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-10-21 15:40 +0200
SubjectRe: Signs of hard drive failure?
Message-ID<yTG4F-2V8-3@gated-at.bofh.it>
On Sun, Oct 20, 2019 at 10:21:20PM -0400, Ken Heard wrote:
> #! /bin/bash
> CURPWD=$PWD
> cd /home/ken
> tar -czf /media/fde/backups/kfinancescurrent.tgz --wildcards\
> - --exclude-from=docs/tarlists/kfinancesarchive.lst docs/01-kens/Finances
> cd $CURPWD

What happens if cd /home/ken fails?  Suddenly your tar command is
running from the wrong location.

You must always check the result of a cd command, and take appropriate
action when it fails.  For example,

#!/bin/bash
cd /home/ken || exit
tar czf ...


If this is the entire script, then that's all you need.  You don't need
the second cd command at all, because the current working directory of
the script doesn't matter after the script exits.

If there's other stuff after this tar command, and you want to "undo"
the cd that you used for tar, there are a few good ways to go about
this.

The first is to encapsulate the cd+tar into a subshell.  The cd happens
in the subshell, so as soon as the subshell terminates, the original
process resumes with its original working directory.

#!/bin/bash
(cd /home/ken &&
 tar czf ...
)
other commands


The second is to take advantage of tar's -C option, which allows tar
to change directory internally.  Then, your script doesn't need to cd
at all.

#!/bin/bash
tar c -C /home/ken -zf ...


Finally, if you *do* choose to store a directory name in a variable and
use that variable later in the script, you must quote it correctly.

cd "$olddir"


This is not optional, and not negotiable.  The quotes are REQUIRED.

https://mywiki.wooledge.org/Quotes

[toc] | [next] | [standalone]

#215336

FromRenato Gallo <renato@aster-lab.com>
Date2019-10-22 11:10 +0200
Message-ID<yTYkV-6ea-3@gated-at.bofh.it>
In reply to#215310

[Multipart message — attachments visible in raw view] — view raw

Always keep a bootable usb of gparted on a chain on your neck it might save you if/when s**t hits the fan 

get it here [ https://gparted.org/download.php | https://gparted.org/download.php ] 

Renato Gallo 



From: "Ken Heard" <ken@heard.name> 
To: "debian-user" <debian-user@lists.debian.org> 
Sent: Tuesday, October 22, 2019 10:16:29 AM 
Subject: Re: Signs of hard drive failure? 

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

As instructed at approximately 19:00 on 2019-10-21 Monday I ran first 
'sudo smartctl -t long /dev/sda' which returned the following: 

ken@SOL:~$ sudo smartctl -t long /dev/sda 
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-9-amd64] (local build) 
Copyright (C) 2002-16, Bruce Allen, Christian Franke, 
www.smartmontools.org 

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === 
Sending command: "Execute SMART Extended self-test routine immediately 
in off-line mode". 
Drive command "Execute SMART Extended self-test routine immediately in 
off-line mode" successful. 
Testing has begun. 
Please wait 212 minutes for test to complete. 
Test will complete after Mon Oct 21 22:38:34 2019 

Use smartctl -X to abort test. 

Without aborting the test, at approximately 03:20 on 2019-10-22 
Tuesday I ran 'sudo smartctl -a /dev/sda which produces the following 
result: 

ken@SOL:~$ sudo smartctl -a /dev/sda 
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-9-amd64] (local build) 
Copyright (C) 2002-16, Bruce Allen, Christian Franke, 
www.smartmontools.org 

=== START OF INFORMATION SECTION === 
Model Family: Seagate Barracuda 7200.14 (AF) 
Device Model: ST2000DM001-1ER164 
Serial Number: Z4Z0WAAC 
LU WWN Device Id: 5 000c50 07969f376 
Firmware Version: CC25 
User Capacity: 2,000,398,934,016 bytes [2.00 TB] 
Sector Sizes: 512 bytes logical, 4096 bytes physical 
Rotation Rate: 7200 rpm 
Form Factor: 3.5 inches 
Device is: In smartctl database [for details use: -P show] 
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b 
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) 
Local Time is: Tue Oct 22 03:41:10 2019 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: ( 80) seconds. 
Offline data collection 
capabilities: (0x7b) SMART execute Offline immediate. 
Auto Offline data collection 
on/off support. 
Suspend Offline collection 
upon new 
command. 
Offline surface scan supported. 
Self-test supported. 
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 supporte 
d. 
Short self-test routine 
recommended polling time: ( 1) minutes. 
Extended self-test routine 
recommended polling time: ( 212) minutes. 
Conveyance self-test routine 
recommended polling time: ( 2) minutes. 
SCT capabilities: (0x1085) SCT Status supported. 

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 117 099 006 Pre-fail 
Always - 165044768 
3 Spin_Up_Time 0x0003 096 096 000 Pre-fail 
Always - 0 
4 Start_Stop_Count 0x0032 100 100 020 Old_age 
Always - 558 
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail 
Always - 0 
7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail 
Always - 29287810 
9 Power_On_Hours 0x0032 096 096 000 Old_age 
Always - 3826 
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail 
Always - 0 
12 Power_Cycle_Count 0x0032 100 100 020 Old_age 
Always - 557 
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age 
Always - 0 
184 End-to-End_Error 0x0032 100 100 099 Old_age 
Always - 0 
187 Reported_Uncorrect 0x0032 100 100 000 Old_age 
Always - 0 
188 Command_Timeout 0x0032 100 100 000 Old_age 
Always - 0 0 0 
189 High_Fly_Writes 0x003a 097 097 000 Old_age 
Always - 3 
190 Airflow_Temperature_Cel 0x0022 072 066 045 Old_age 
Always - 28 (Min/Max 21/30) 
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age 
Always - 0 
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age 
Always - 109 
193 Load_Cycle_Count 0x0032 100 100 000 Old_age 
Always - 839 
194 Temperature_Celsius 0x0022 028 040 000 Old_age 
Always - 28 (0 18 0 0 0) 
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 - 0 
240 Head_Flying_Hours 0x0000 100 253 000 Old_age 
Offline - 3653h+36m+00.581s 
241 Total_LBAs_Written 0x0000 100 253 000 Old_age 
Offline - 19423797637 
242 Total_LBAs_Read 0x0000 100 253 000 Old_age 
Offline - 246124639739 

SMART Error Log Version: 1 
No Errors Logged 

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% 3821 
- 

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. 

My comments: is that what is supposed to happen? I have not done 
/dev/sdb yet. 


"elvis" in an earlier post asked me if I had "tried e2fsck to check 
the filesystem first?" According to 'man e2fsk' I have to run that 
command on an unmounted device. If the devices in question, /dev/sda 
and /dev/sdb, comprise the RAID 1, how can I unmount them and still 
use the computer to run those commands? 

Regards, Ken 


-----BEGIN PGP SIGNATURE----- 

iF0EARECAB0WIQR9YFyM2lJAhDprmoOU2UnM6QmZNwUCXa661QAKCRCU2UnM6QmZ 
NwZmAJ4t7kXxc6Nz6JoQr2nh80tIFmE7vQCfb6uYQCSNV9+G7q+CKn9VTqMI9ec= 
=WZPP 
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#215337

Fromelvis <elvis@dogonfire.com>
Date2019-10-22 11:30 +0200
Message-ID<yTYEi-6lu-13@gated-at.bofh.it>
In reply to#215310
Lots cut

On 22/10/19 6:16 pm, Ken Heard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>       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.
>
> My comments: is that what is supposed to happen?  I have not done
> /dev/sdb yet.
>
>
> "elvis" in an earlier post asked me if I had "tried e2fsck to check
> the filesystem first?"  According to 'man e2fsk' I have to run that
> command on an unmounted device.  If the devices in question, /dev/sda
> and /dev/sdb, comprise the RAID 1, how can I unmount them and still
> use the computer to run those commands?


Hi Ken,

You run e2fsck on the partition. So if your raid is sdb and sda then 
your raid device is /dev/md127 or /dev/kensarray/bigdisk or something 
like that. Then your partition is on top of that.


Hopefully you have your partition mounted on /mnt/allmydata for example 
and you just umount it and run e2fsck on whatever the block device is.


If you have boot and root on raid, I would boot with a recovery USB 
like  sysrescue and then run the tests offline. It should assemble your 
raid automatically to save stuffing around as well.


Also make sure you are using the right filesystem checker, I have just 
assumed you are using ext4







> Regards, Ken
>
>
> -----BEGIN PGP SIGNATURE-----
>
> iF0EARECAB0WIQR9YFyM2lJAhDprmoOU2UnM6QmZNwUCXa661QAKCRCU2UnM6QmZ
> NwZmAJ4t7kXxc6Nz6JoQr2nh80tIFmE7vQCfb6uYQCSNV9+G7q+CKn9VTqMI9ec=
> =WZPP
> -----END PGP SIGNATURE-----
>
-- 
Puritanism: The haunting fear that someone, somewhere may be happy.

[toc] | [prev] | [next] | [standalone]

#215343

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2019-10-22 17:00 +0200
Message-ID<yU3NE-WY-11@gated-at.bofh.it>
In reply to#215337
On Tue 22 Oct 2019 at 19:24:00 (+1000), elvis wrote:
> Lots cut
> On 22/10/19 6:16 pm, Ken Heard wrote:
> >       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.
> > 
> > My comments: is that what is supposed to happen?  I have not done
> > /dev/sdb yet.
> > 
> > "elvis" in an earlier post asked me if I had "tried e2fsck to check
> > the filesystem first?"  According to 'man e2fsk' I have to run that
> > command on an unmounted device.  If the devices in question, /dev/sda
> > and /dev/sdb, comprise the RAID 1, how can I unmount them and still
> > use the computer to run those commands?
> 
> You run e2fsck on the partition. So if your raid is sdb and sda then
> your raid device is /dev/md127 or /dev/kensarray/bigdisk or something
> like that. Then your partition is on top of that.
> 
> Hopefully you have your partition mounted on /mnt/allmydata for
> example and you just umount it and run e2fsck on whatever the block
> device is.
> 
> If you have boot and root on raid, I would boot with a recovery USB
> like  sysrescue and then run the tests offline. It should assemble
> your raid automatically to save stuffing around as well.
> 
> Also make sure you are using the right filesystem checker, I have just
> assumed you are using ext4

Is all this really necessary? I thought one of the benefits of the
extra complication of using initramfs is that the system can check
the root filesystem automatically before it's mounted.

In fact, I've just done it. I typed
# ./check-fs-rebooting-now
which runs   grub-reboot 'fsck>fsck'; reboot
which reboots the machine with   forcefsck   added to the kernel parameters.
After Grub loads the kernel and initrd, the root filesystem gets fsck'd
before any of the normal boot messages appear.

I haven't yet run RAID but am told it's really simple. Is this
going to complicate matters?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#215360

Fromelvis <elvis@dogonfire.com>
Date2019-10-22 23:20 +0200
Message-ID<yU9Jn-4Re-3@gated-at.bofh.it>
In reply to#215343
On 23/10/19 12:50 am, David Wright wrote:
> On Tue 22 Oct 2019 at 19:24:00 (+1000), elvis wrote:
>> Lots cut
>> On 22/10/19 6:16 pm, Ken Heard wrote:
>>>        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.
>>>
>>> My comments: is that what is supposed to happen?  I have not done
>>> /dev/sdb yet.
>>>
>>> "elvis" in an earlier post asked me if I had "tried e2fsck to check
>>> the filesystem first?"  According to 'man e2fsk' I have to run that
>>> command on an unmounted device.  If the devices in question, /dev/sda
>>> and /dev/sdb, comprise the RAID 1, how can I unmount them and still
>>> use the computer to run those commands?
>> You run e2fsck on the partition. So if your raid is sdb and sda then
>> your raid device is /dev/md127 or /dev/kensarray/bigdisk or something
>> like that. Then your partition is on top of that.
>>
>> Hopefully you have your partition mounted on /mnt/allmydata for
>> example and you just umount it and run e2fsck on whatever the block
>> device is.
>>
>> If you have boot and root on raid, I would boot with a recovery USB
>> like  sysrescue and then run the tests offline. It should assemble
>> your raid automatically to save stuffing around as well.
>>
>> Also make sure you are using the right filesystem checker, I have just
>> assumed you are using ext4
> Is all this really necessary? I thought one of the benefits of the
> extra complication of using initramfs is that the system can check
> the root filesystem automatically before it's mounted.
>
> In fact, I've just done it. I typed
> # ./check-fs-rebooting-now
> which runs   grub-reboot 'fsck>fsck'; reboot
> which reboots the machine with   forcefsck   added to the kernel parameters.
> After Grub loads the kernel and initrd, the root filesystem gets fsck'd
> before any of the normal boot messages appear.
>
> I haven't yet run RAID but am told it's really simple. Is this
> going to complicate matters?

That's much easier, the reason I suggested sysrescue is that everytime I 
have had to check the root it has been so hosed it gets mounted ro and 
it is too hard to fix it from the recovery shell.


Raid is really simple, till something goes wrong :-) I reckon most data 
loss is from people taking wrong options to fix things from inexperience 
rather than raid losing the data.



> Cheers,
> David.
>
-- 
We have enough youth, how about a fountain of SMART?

[toc] | [prev] | [next] | [standalone]

#215361

FromChristopher David Howie <me@chrishowie.com>
Date2019-10-23 01:00 +0200
Message-ID<yUbia-5FZ-7@gated-at.bofh.it>
In reply to#215360
On October 22, 2019 9:17:15 PM UTC, elvis <elvis@dogonfire.com> wrote:
>Raid is really simple, till something goes wrong :-) I reckon most data
>
>loss is from people taking wrong options to fix things from
>inexperience 
>rather than raid losing the data.

Also from the wrong assumption that RAID levels with redundancy are a substitute for backups.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[toc] | [prev] | [next] | [standalone]

#215348

FromChristopher David Howie <me@chrishowie.com>
Date2019-10-22 19:40 +0200
Message-ID<yU6it-2zY-5@gated-at.bofh.it>
In reply to#215310
On 10/22/19 1:01 PM, Ken Heard wrote:
> smartctl considers my two hard drives three years old and
> consequently prone to failure

I'm not seeing that anywhere in the smartctl output. All of the
information there suggests that there is nothing wrong with the drives.

Where are you seeing these indications of failure in the smartctl output?

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/

PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5

------------------------------------------------------------------------
                    IMPORTANT INFORMATION/DISCLAIMER

This document should be read only by those persons to whom it is
addressed.  If you have received this message it was obviously addressed
to you and therefore you can read it.

Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.

This overrides any disclaimer or statement of confidentiality that may
be included on your message.

[toc] | [prev] | [next] | [standalone]

#215353

FromBob Weber <bobrweber@gmail.com>
Date2019-10-22 21:20 +0200
Message-ID<yU7Rf-3FJ-9@gated-at.bofh.it>
In reply to#215310

[Multipart message — attachments visible in raw view] — view raw

On 10/22/19 1:01 PM, Ken Heard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> At about 04:35 EDT today 2019-10-22 Tuesday I ran 'sudo smartctl -t
> long /dev/sdb'.  At 12:48 I ran the command in the next line.  The
> result is below after the next paragraph.
>
> Based on the results below relating to /dev/sdb and the results
> relating to /dev/sda quoted in my previous email today, I conclude
> that while smartctl considers my two hard drives three years old and
> consequently prone to failure -- what else really is new, all devices
> are prone to failure -- my current backup problems are not related to
> failure of either or both of these drives.  As I stated in my original
> post, they have been in use for only 1.75 years.  I shall consequently
> continue to examine at my scripts for errors in creating tarballs for
> my backups.
>
> Regards, Ken
> - ---------------------------------------------------
>
> ken@SOL:~$ sudo smartctl -a /dev/sdb
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-9-amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke,
> www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family:     Seagate Barracuda 7200.14 (AF)
> Device Model:     ST2000DM001-1ER164
> Serial Number:    Z4Z0TKY8
> LU WWN Device Id: 5 000c50 0796a3479
> Firmware Version: CC25
> User Capacity:    2,000,398,934,016 bytes [2.00 TB]
> Sector Sizes:     512 bytes logical, 4096 bytes physical
> Rotation Rate:    7200 rpm
> Form Factor:      3.5 inches
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
> SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
> Local Time is:    Tue Oct 22 12:45:42 2019 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:                (   80) seconds.
> Offline data collection
> capabilities:                    (0x7b) SMART execute Offline immediate.
>                                          Auto Offline data collection
> on/off support.
>                                          Suspend Offline collection
> upon new
>                                          command.
>                                          Offline surface scan supported.
>                                          Self-test supported.
>                                          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 supporte
> d.
> Short self-test routine
> recommended polling time:        (   1) minutes.
> Extended self-test routine
> recommended polling time:        ( 219) minutes.
> Conveyance self-test routine
> recommended polling time:        (   2) minutes.
> SCT capabilities:              (0x1085) SCT Status supported.
>
> 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   115   099   006    Pre-fail
> Always       -       90023624
>    3 Spin_Up_Time            0x0003   096   096   000    Pre-fail
> Always       -       0
>    4 Start_Stop_Count        0x0032   100   100   020    Old_age
> Always       -       557
>    5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail
> Always       -       0
>    7 Seek_Error_Rate         0x000f   073   060   030    Pre-fail
> Always       -       24992023
>    9 Power_On_Hours          0x0032   096   096   000    Old_age
> Always       -       3834
>   10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail
> Always       -       0
>   12 Power_Cycle_Count       0x0032   100   100   020    Old_age
> Always       -       556
> 183 Runtime_Bad_Block       0x0032   100   100   000    Old_age
> Always       -       0
> 184 End-to-End_Error        0x0032   100   100   099    Old_age
> Always       -       0
> 187 Reported_Uncorrect      0x0032   100   100   000    Old_age
> Always       -       0
> 188 Command_Timeout         0x0032   100   100   000    Old_age
> Always       -       0 0 0
> 189 High_Fly_Writes         0x003a   096   096   000    Old_age
> Always       -       4
> 190 Airflow_Temperature_Cel 0x0022   070   065   045    Old_age
> Always       -       30 (Min/Max 21/31)
> 191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age
> Always       -       0
> 192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age
> Always       -       104
> 193 Load_Cycle_Count        0x0032   100   100   000    Old_age
> Always       -       832
> 194 Temperature_Celsius     0x0022   030   040   000    Old_age
> Always       -       30 (0 18 0 0 0)
> 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       -       0
> 240 Head_Flying_Hours       0x0000   100   253   000    Old_age
> Offline      -       3733h+04m+36.466s
> 241 Total_LBAs_Written      0x0000   100   253   000    Old_age
> Offline      -       31308850703
> 242 Total_LBAs_Read         0x0000   100   253   000    Old_age
> Offline      -       133591359037
>
> SMART Error Log Version: 1
> No Errors Logged
>
> 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%      3830
>         -
>
> 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.
>
> ken@SOL:~$
>
> -----BEGIN PGP SIGNATURE-----
>
> iF0EARECAB0WIQR9YFyM2lJAhDprmoOU2UnM6QmZNwUCXa816gAKCRCU2UnM6QmZ
> N+GRAJ49DzJwDIA6SlWnmyNBVk1+UUZh8wCdHJhfWS6oChj+SEwtttfuTiiOrwo=
> =e/7+
> -----END PGP SIGNATURE-----
>
 From the long self test everything looks good.  There are only about 3834 hours 
on the drives ... about 6 months worth.  I have drives that have over 5 years 
now.  I run the long self test every other day on my drives to keep up with the 
possibility  of errors.  If you feel that you have had these drives long enough 
you could add another 2TB drive to your raid (the safest thing to do to save 
your data) making it a 3 drive array.

So now you just need to do fsck on the raid drive.  As I explained before the 
sure way to do this is to boot to a linux system cd.  You mentioned knoppix.  I 
use sysrescuecd from http://www.system-rescue-cd.org.
<http://www.system-rescue-cd.org/>

Whatever disk you choose it should be fairly recent so that you know the raid 
will be found and setup correctly.  After booting the cd first do "ls /dev/md*" 
to find the raid drives that have been found.  Then run "fsck -f /dev/mdx" where 
x will be a number up to 3 digits long (I've never seen a longer number ... 
usually something like 127 is the biggest that I have seen).  If that passes 
then your drives should be ok.

There are other tests you could run to see if the 2 drives are alike as far as 
the raid part goes.  The only thing is to correct a difference found ... which 
drive is correct.  The mdadm commands to do this apparently pick one drive as 
correct (who knows which one) and overwrite the other drive for that part that 
part that is different.  Pretty scary to me!

-- 


*...Bob*

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web