Replace raid5 disk

**guillaume8** · September 8th, 2014

Hello all,

I have a problem with one of my hard drive and I can't figure it out.
As I have no experience with hard drive I list everything I did until now,
if you can find out how I can fix my problem or if I did something wrong it will be awesome !!

The following event may not be totaly acurate, I write as I can recall them.

At the office we have an Ubuntu server (10.04 server) with an SVN, suddently, I couldn't commit anything as the SVN had a problem to write
on the media "/media/md3/SVN..." . After a little research I found that their was a problem with hard drives,
so I decided to reboot the server.

But the server did not want to reboot corectly : "The disk drive /media/md3 is not ready yet or not present".
As the server rebooted one of the hard drive made horrible sounds.
So I assumed that there was an hardware problem with one of our hard drive.

I looked on internet and found that mdX drive are raid disk.
The "/proc/mdstat" give me the folowing results :

Code:

Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md3 : inactive sdb4[1](S) sdc4[2](S)
      XXXXX blocks
       
md0 : active raid1 sdb1[1] sdc1[0]
      9767424 blocks [2/2] [UU]
      
md2 : active raid1 sdb3[1] sdc3[0]
      9767424 blocks [2/2] [UU]
      
md1 : active raid1 sdb2[1] sdc2[0]
      3903680 blocks [2/2] [UU]
      
unused devices: <none>

So, if I understant this file correclty there are 4 partitions. 3 with raid1 which seems fine
and an inactive one.
By opening the server I found only 3 disks so I assume that only one disk (sda) is missing.

I saw that
/dev/md0 is for /
/dev/md1 is for the swap
/dev/md1 is for /home
/dev/md3 is for other stuff (SVN ...)

I check the raid confiration by reading "/etc/mdadm/mdadm.conf"

Code:

...
# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=49735139:366257fa:a5779236:921be48a
   spares=1
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=a2c293ad:48665869:d6cbf604:0332693a
   spares=1
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=babfb377:80fbc55e:b4941712:9acab322
   spares=1
ARRAY /dev/md3 level=raid5 num-devices=3 UUID=417439cd:4ae223bb:160a0374:db61e1ab
...

I know that this file may not correspond to reality because it as to be generated but it seems logical so I continue as it was the good configuration.

So, now that I have the server's raid configuration, I need to figure out which disk broke.
So I plug/unplug disks to test wich one is good.
At this point i forget which cable was connected to the different Sata ports, I hope it is not important ...

Then I plug a new hard drive (same brand aproximatively same characteristics but 1TB instead of 500GB).
With a liveCD and Gparted I partition the new hard drive. I chose the same size for the three first partition (for raid1)
and I let the remaining space for the last partition.
I saw that the 2 other have a 'msdos' partition table and a ~1MB unallocated space at the end of the hard drive.
So I did the same configuration with my new disk. I also chosed the same flags.
The only things different is that the two other disk have no file system on their sdx3 partition and with Gparted I am forced to chose something,
so I selected "ext3".

sda
sda.jpeg

sdb (new disk)
sdb.jpeg

Now that everything is prepared I reboot the server and nothing changed.
So I manually add the 3 first partitions :

Code:

mdadm --manage /dev/mdX --add /dev/sdbY

The partition are added as spare disks ... cool !

Code:

$ : cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md3 : inactive sda4[1](S) sdc4[2](S)
      XXXXX blocks
       
md0 : active raid1 sda1[1] sdc1[0] sdb1[2](S)
      9767424 blocks [2/2] [UU]
      
md2 : active raid1 sda3[1] sdc3[0] sdb3[2](S)
      9767424 blocks [2/2] [UU]
      
md1 : active raid1 sda2[1] sdc2[0] sdb2[2](S)
      3903680 blocks [2/2] [UU]
      
unu

sed devices: <none>

For the raid5 disk I follow instructions here :
http://globalblindspot.blogspot.fr/2...of-raid-5.html
Everything seems fine and the recovery began

Code:

$ : cat /proc/mdstat
...          
md3 : active raid5 sda4[1] sdb4[3] sdc4[2]
      929890176 blocks level 5, 64k chunk, algorithm 2 [3/2] [_UU]
      [>....................]  recovery =  0.8% (3802496/464945088) finish=93.6min speed=82056K/sec
...

But merely at the end the recovery crashed.

I read somewhere that the different raid5 algorithme order data in different ways.
As the initialy missing 'sda' disk re-appers as 'sdb' it may be the cause of my probleme.
Remenber, I played with cables and I may have inverted the two first disks

So I change the two first disks. Unfortunately, with this configuration
the server cannot boot and stop at "Verifying DMI Pool Data ....".

I thought that the computer cannot boot because the partition with boot
information (/dev/md0) is empty on the new disk as it is only a spare disque
in a raid1 configuration.
So I plug back the disks as they were before and I set faulty the first
partition of the third disk (/dev/sdc1), so everything from the third disk was
copied on the new one.

I inverte again the two first disk and ... the boot is stuck again at
"Verifying DMI Pool Data ....".

I do not know waht I can do next, If you have any idea how I can make the
server boot again properly it will be great.

**nerdtron** · September 8th, 2014

Might have better chance of answering if an admin moves this to Server Platforms.

**guillaume8** · September 9th, 2014

So I posted in the wrong place ...

If nobody moves my thread can I close it and open it again in the good subforum ?

**nerdtron** · September 9th, 2014

As the initialy missing 'sda' disk re-appers as 'sdb' it may be the cause of my probleme.
Remenber, I played with cables and I may have inverted the two first disks

Bad...really bad...

I inverte again the two first disk and ... the boot is stuck again at
"Verifying DMI Pool Data ....".

Seems like problems arise the more you fiddle with it. You can't even boot on the OS, you can't do anything.

Do you have any backups of the files from the server?

**coffeecat** · September 9th, 2014

Originally Posted by guillaume8

So I posted in the wrong place ...

If nobody moves my thread can I close it and open it again in the good subforum ?

I've moved it to Server Platforms.

If you ever want a thread moving, it's quite OK to send a request to the staff area by clicking on the "report post" button in your own post. It'll be acted on quicker than hoping a member of forum staff happens to notice the need. Don't worry about using the report button - we use it for more than just problematic posts here. It's an effective and quick way of sending a message/request to forum staff.

**guillaume8** · September 10th, 2014

Originally Posted by nerdtron

Seems like problems arise the more you fiddle with it. You can't even boot on the OS, you can't do anything.

Do you have any backups of the files from the server?

No, We only have old saves.

Do you know how disk are named ? Are they named according to the port they are pluged in ?
For exemple, the disk pluged in the port0 will be sda, the one in the port1 sdb ...
If yes, I should be abble to find how the diks were pluged before the incident.

Because the new disk seems to be at fault is there a way to make the computer boot on an other disk even if it's not the first one (sdb) ?

PS: Thanks coffeecat for the explanation

**nerdtron** · September 11th, 2014

Do you know how disk are named ? Are they named according to the port they are pluged in ?
For exemple, the disk pluged in the port0 will be sda, the one in the port1 sdb ...

I think this is correct. but...

If yes, I should be abble to find how the diks were pluged before the incident

You said you changed the disk port order before you build the raid? Also, Verifying DMI Pool means no data is detected on this, even the boot loader can be found. So I guess when you build up the raid using the wrong configuration you messed with the order of parity algorithm of raid 5.

I'm sorry but I can't offer any more solution in this situation.

**guillaume8** · September 12th, 2014

Thanks for your replies !

Is the "boot loader" something for each raid disk or is it for the OS ?
If it is for the OS it should be place on the raid disk marked as "boot" with gparted, isn't it ?

By rebuilding the raid5 disk with a wrong order it may have mix the data in the wrong order like you said.

I do not know how the rebuilding of a raid5 works but it should only modified the new disk.
If I set it faulty then plug it back in the good order the two others should be intact, isn't it ?

**rubylaser** · September 12th, 2014

Putting a filesystem on each partition and then causing a sync by adding the disk was not a good idea. It would have been better to remove the disk (if it was in fact failing) with mdadm and then replace the failed disk with the new one. What you did very likely overwrote any data on that partition. Instead of trying to get the OS to boot, I would start by trying to recover your data. I would boot a live Ubuntu cd, run apt-get install mdadm. And then try to use mdadm to examine the metadata info on each disk like this.

Code:

sudo -i
apt-get update && apt-get install mdadm smartmontools -y

Code:

mdadm --examine /dev/sd[ab]1
mdadm --examine /dev/sd[ab]2
mdadm --examine /dev/sd[ab]3
mdadm --examine /dev/sd[ab]4

Also, I would check the SMART data on each disk.

Code:

smartctl -a /dev/sda
smartctl -a /dev/sdb

Please run these and report back.

**guillaume8** · September 15th, 2014

Hi,

Here the results :

Code:

root@ubuntu:~# mdadm --examine /dev/sd[ab]1
/dev/sda1:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 49735139:366257fa:a5779236:921be48a
  Creation Time : Wed Oct 22 15:04:45 2008
     Raid Level : raid1
  Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
     Array Size : 9767424 (9.31 GiB 10.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0


    Update Time : Mon Sep 15 09:01:57 2014
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : fe4c5064 - correct
         Events : 423262




      Number   Major   Minor   RaidDevice State
this     1       8        1        1      active sync   /dev/sda1


   0     0       8       17        0      active sync   /dev/sdb1
   1     1       8        1        1      active sync   /dev/sda1
/dev/sdb1:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 49735139:366257fa:a5779236:921be48a
  Creation Time : Wed Oct 22 15:04:45 2008
     Raid Level : raid1
  Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
     Array Size : 9767424 (9.31 GiB 10.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0


    Update Time : Mon Sep 15 09:01:57 2014
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : fe45db14 - correct
         Events : 423263




      Number   Major   Minor   RaidDevice State
this     0       8       17        0      active sync   /dev/sdb1


   0     0       8       17        0      active sync   /dev/sdb1
   1     1       8        1        1      active sync   /dev/sda1

root@ubuntu:~# mdadm --examine /dev/sd[ab]2
/dev/sda2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : a2c293ad:48665869:d6cbf604:0332693a
  Creation Time : Wed Oct 22 15:05:33 2008
     Raid Level : raid1
  Used Dev Size : 3903680 (3.72 GiB 4.00 GB)
     Array Size : 3903680 (3.72 GiB 4.00 GB)
   Raid Devices : 2
  Total Devices : 3
Preferred Minor : 126


    Update Time : Thu Sep  4 15:44:31 2014
          State : clean
 Active Devices : 2
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 1
       Checksum : b9604c6 - correct
         Events : 1824




      Number   Major   Minor   RaidDevice State
this     1       8        2        1      active sync   /dev/sda2


   0     0       8       34        0      active sync
   1     1       8        2        1      active sync   /dev/sda2
   2     2       8       18        2      spare   /dev/sdb2
/dev/sdb2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : a2c293ad:48665869:d6cbf604:0332693a
  Creation Time : Wed Oct 22 15:05:33 2008
     Raid Level : raid1
  Used Dev Size : 3903680 (3.72 GiB 4.00 GB)
     Array Size : 3903680 (3.72 GiB 4.00 GB)
   Raid Devices : 2
  Total Devices : 3
Preferred Minor : 126


    Update Time : Thu Sep  4 15:43:01 2014
          State : clean
 Active Devices : 2
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 1
       Checksum : b960478 - correct
         Events : 1824




      Number   Major   Minor   RaidDevice State
this     2       8       18        2      spare   /dev/sdb2


   0     0       8       34        0      active sync
   1     1       8        2        1      active sync   /dev/sda2
   2     2       8       18        2      spare   /dev/sdb2

root@ubuntu:~# mdadm --examine /dev/sd[ab]3
/dev/sda3:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : babfb377:80fbc55e:b4941712:9acab322
  Creation Time : Wed Oct 22 15:05:44 2008
     Raid Level : raid1
  Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
     Array Size : 9767424 (9.31 GiB 10.00 GB)
   Raid Devices : 2
  Total Devices : 3
Preferred Minor : 2


    Update Time : Thu Sep  4 16:00:03 2014
          State : clean
 Active Devices : 2
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 1
       Checksum : d1e5c3ae - correct
         Events : 109694




      Number   Major   Minor   RaidDevice State
this     1       8        3        1      active sync   /dev/sda3


   0     0       8       35        0      active sync
   1     1       8        3        1      active sync   /dev/sda3
   2     2       8       19        2      spare   /dev/sdb3
/dev/sdb3:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : babfb377:80fbc55e:b4941712:9acab322
  Creation Time : Wed Oct 22 15:05:44 2008
     Raid Level : raid1
  Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
     Array Size : 9767424 (9.31 GiB 10.00 GB)
   Raid Devices : 2
  Total Devices : 3
Preferred Minor : 2


    Update Time : Thu Sep  4 16:00:03 2014
          State : clean
 Active Devices : 2
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 1
       Checksum : d1e5c3ba - correct
         Events : 109694




      Number   Major   Minor   RaidDevice State
this     2       8       19        2      spare   /dev/sdb3


   0     0       8       35        0      active sync
   1     1       8        3        1      active sync   /dev/sda3
   2     2       8       19        2      spare   /dev/sdb3

root@ubuntu:~# mdadm --examine /dev/sd[ab]4
/dev/sda4:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 417439cd:4ae223bb:160a0374:db61e1ab
  Creation Time : Wed Oct 22 15:05:53 2008
     Raid Level : raid5
  Used Dev Size : 464945088 (443.41 GiB 476.10 GB)
     Array Size : 929890176 (886.81 GiB 952.21 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 3


    Update Time : Thu Sep  4 17:15:22 2014
          State : clean
 Active Devices : 1
Working Devices : 2
 Failed Devices : 1
  Spare Devices : 1
       Checksum : dfc30c50 - correct
         Events : 724278


         Layout : left-symmetric
     Chunk Size : 64K


      Number   Major   Minor   RaidDevice State
this     1       8        4        1      active sync   /dev/sda4


   0     0       0        0        0      removed
   1     1       8        4        1      active sync   /dev/sda4
   2     2       0        0        2      faulty removed
   3     3       8       20        3      spare   /dev/sdb4
/dev/sdb4:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 417439cd:4ae223bb:160a0374:db61e1ab
  Creation Time : Wed Oct 22 15:05:53 2008
     Raid Level : raid5
  Used Dev Size : 464945088 (443.41 GiB 476.10 GB)
     Array Size : 929890176 (886.81 GiB 952.21 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 3


    Update Time : Thu Sep  4 17:15:22 2014
          State : clean
 Active Devices : 1
Working Devices : 2
 Failed Devices : 1
  Spare Devices : 1
       Checksum : dfc30c5e - correct
         Events : 724278


         Layout : left-symmetric
     Chunk Size : 64K


      Number   Major   Minor   RaidDevice State
this     3       8       20        3      spare   /dev/sdb4


   0     0       0        0        0      removed
   1     1       8        4        1      active sync   /dev/sda4
   2     2       0        0        2      faulty removed
   3     3       8       20        3      spare   /dev/sdb4

Code:

root@ubuntu:~# smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.5.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net


=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST3500320AS
Serial Number:    5QM2ZL78
LU WWN Device Id: 5 000c50 011563ae4
Firmware Version: SD1A
User Capacity:    500,106,780,160 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon Sep 15 09:46:59 2014 UTC
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:         (  634) 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 supported.
Short self-test routine 
recommended polling time:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 117) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x103b)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table 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   118   099   006    Pre-fail  Always       -       190665705
  3 Spin_Up_Time            0x0003   095   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       21
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   082   060   030    Pre-fail  Always       -       4468748299
  9 Power_On_Hours          0x0032   042   042   000    Old_age   Always       -       51414
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       73
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   094   000    Old_age   Always       -       36
189 High_Fly_Writes         0x003a   085   085   000    Old_age   Always       -       15
190 Airflow_Temperature_Cel 0x0022   064   053   045    Old_age   Always       -       36 (Min/Max 24/36)
194 Temperature_Celsius     0x0022   036   047   000    Old_age   Always       -       36 (0 17 0 0)
195 Hardware_ECC_Recovered  0x001a   035   021   000    Old_age   Always       -       190665705
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


SMART Error Log Version: 1
No Errors Logged


SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]




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.


root@ubuntu:~# smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.5.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net


=== START OF INFORMATION SECTION ===
Device Model:     ST1000DM003-1ER162
Serial Number:    Z4Y0GLDM
LU WWN Device Id: 5 000c50 0675d2291
Firmware Version: CC43
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   9
ATA Standard is:  Not recognized. Minor revision code: 0x001f
Local Time is:    Mon Sep 15 09:47:04 2014 UTC
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 supported.
Short self-test routine 
recommended polling time:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 110) 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   114   100   006    Pre-fail  Always       -       69712880
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       16
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       743060
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       172
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       16
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
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   062   045    Old_age   Always       -       34 (Min/Max 24/34)
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       -       4
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       47
194 Temperature_Celsius     0x0022   034   040   000    Old_age   Always       -       34 (0 20 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      -       187891934298282
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       2284470464
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       34502039


SMART Error Log Version: 1
No Errors Logged


SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]




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.

Thread: Replace raid5 disk

Thread Tools

Display

Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Re: Replace raid5 disk

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions