Festplatte am sterben oder schon Tod?

Entonsammler · 02/22/2017, 17:56

Moin,
bekam heut die Email:

Code:

This is an automatically generated mail message from mdadm
running on *******

A DegradedArray event had been detected on md device /dev/md127.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] 
md124 : active raid1 sdb1[1]
      16760832 blocks super 1.2 [2/1] [_U]
      
md125 : active (auto-read-only) raid1 sdb2[1]
      523712 blocks super 1.2 [2/1] [_U]
      
md126 : active (auto-read-only) raid1 sdb3[1]
      1073610752 blocks super 1.2 [2/1] [_U]
      bitmap: 0/8 pages [0KB], 65536KB chunk

md127 : active (auto-read-only) raid1 sdb4[1]
      1839090112 blocks super 1.2 [2/1] [_U]
      bitmap: 0/14 pages [0KB], 65536KB chunk

unused devices: <none>

daraufhin habe ich mal ein bisschen geschaut:

Code:

~ # mdadm --detail /dev/md124
/dev/md124:
        Version : 1.2
  Creation Time : Fri Aug  5 11:58:54 2016
     Raid Level : raid1
     Array Size : 16760832 (15.98 GiB 17.16 GB)
  Used Dev Size : 16760832 (15.98 GiB 17.16 GB)
   Raid Devices : 2
  Total Devices : 1
    Persistence : Superblock is persistent

    Update Time : Thu Jan 19 14:11:45 2017
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           Name : rescue:0
           UUID : 9e60f246:b2390d0f:20e77a48:d34ee781
         Events : 35

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

wobei 2tes nicht darauf hinweißt

.

Ist die Festplatte nun am Sterben?

Wenn die Festplatte von Provider gewechselt wird sollte die neue Festplatte mit der 2. Synchronisiert werden oder?

Momentan läuft alles (noch)
mal hoffen das es so bleibt

.

Chicken.ShooT · 02/22/2017, 22:37

Am besten liest du mal die Smart-Werte der Festplatte aus (Selbstdiagnose-Werte des Festplatten-Controller). Unter Linux geht das mit dem Paket “smartctl“.

Gesendet von meinem HUAWEI M2-801W mit Tapatalk

Entonsammler · 02/23/2017, 17:06

Hab mal mit Smartctl gemacht:

Code:

~ # smartctl --all /dev/sdb
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" HDD DT01ACA...
Device Model:     TOSHIBA DT01ACA300
Serial Number:    23LHLMAAS
LU WWN Device Id: 5 000039 ff4c7177a
Firmware Version: MX6OABB0
User Capacity:    3,000,592,982,016 bytes [3.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:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Feb 23 16:36:57 2017 CET
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: 		(23800) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					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: 	 ( 397) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   138   138   054    Pre-fail  Offline      -       75
  3 Spin_Up_Time            0x0007   156   156   024    Pre-fail  Always       -       400 (Average 336)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       12
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   124   124   020    Pre-fail  Offline      -       33
  9 Power_On_Hours          0x0012   096   096   000    Old_age   Always       -       32133
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       12
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       225
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       225
194 Temperature_Celsius     0x0002   150   150   000    Old_age   Always       -       40 (Min/Max 25/50)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       4
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 35 (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 35 occurred at disk power-on lifetime: 9256 hours (385 days + 16 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
  -- -- -- -- -- -- --
  40 51 01 cf 1a 0a 0a  Error: UNC at LBA = 0x0a0a1acf = 168434383

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 01 00 cf 1a 0a 40 00   5d+08:00:58.889  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:58.824  READ LOG EXT
  60 02 00 ce 1a 0a 40 00   5d+08:00:55.386  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:55.321  READ LOG EXT
  60 03 00 cd 1a 0a 40 00   5d+08:00:51.984  READ FPDMA QUEUED

Error 34 occurred at disk power-on lifetime: 9256 hours (385 days + 16 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
  -- -- -- -- -- -- --
  40 51 02 ce 1a 0a 0a  Error: UNC at LBA = 0x0a0a1ace = 168434382

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 02 00 ce 1a 0a 40 00   5d+08:00:55.386  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:55.321  READ LOG EXT
  60 03 00 cd 1a 0a 40 00   5d+08:00:51.984  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:51.919  READ LOG EXT
  60 04 00 cc 1a 0a 40 00   5d+08:00:48.265  READ FPDMA QUEUED

Error 33 occurred at disk power-on lifetime: 9256 hours (385 days + 16 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
  -- -- -- -- -- -- --
  40 51 03 cd 1a 0a 0a  Error: UNC at LBA = 0x0a0a1acd = 168434381

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 03 00 cd 1a 0a 40 00   5d+08:00:51.984  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:51.919  READ LOG EXT
  60 04 00 cc 1a 0a 40 00   5d+08:00:48.265  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:48.200  READ LOG EXT
  60 05 00 cb 1a 0a 40 00   5d+08:00:44.655  READ FPDMA QUEUED

Error 32 occurred at disk power-on lifetime: 9256 hours (385 days + 16 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
  -- -- -- -- -- -- --
  40 51 04 cc 1a 0a 0a  Error: UNC at LBA = 0x0a0a1acc = 168434380

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 04 00 cc 1a 0a 40 00   5d+08:00:48.265  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:48.200  READ LOG EXT
  60 05 00 cb 1a 0a 40 00   5d+08:00:44.655  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:44.590  READ LOG EXT
  60 06 00 ca 1a 0a 40 00   5d+08:00:41.194  READ FPDMA QUEUED

Error 31 occurred at disk power-on lifetime: 9256 hours (385 days + 16 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
  -- -- -- -- -- -- --
  40 51 05 cb 1a 0a 0a  Error: UNC at LBA = 0x0a0a1acb = 168434379

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 05 00 cb 1a 0a 40 00   5d+08:00:44.655  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:44.590  READ LOG EXT
  60 06 00 ca 1a 0a 40 00   5d+08:00:41.194  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   5d+08:00:41.129  READ LOG EXT
  60 07 00 c9 1a 0a 40 00   5d+08:00:37.650  READ FPDMA QUEUED

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%     24733         -
# 2  Extended offline    Completed without error       00%     24714         -
# 3  Extended offline    Completed without error       00%     24686         -
# 4  Short offline       Completed without error       00%     24677         -
# 5  Extended offline    Completed without error       00%     24567         -
# 6  Extended offline    Completed without error       00%     24548         -

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.

.:Gam3over · 04/13/2017, 00:13

Lass sie einfach mal vom Provider anschauen und ggf. austauschen lassen