ComputerBase Menü
Aktuelles

SMART Daten nicht von jeder Platte

Mueli schrieb:
Die Devicefiles (hda, hdb etc.) passen nur bei IDE Geräten, SCSI und SATA sind meist unter sda, sdb usw. zu finden. Bei SCSI ist SMART etwas anders gestaltet und weicht von SATA an, -d SCSI ist also nicht nötig.

Du solltest also mit /dev/sda beginnen und zunächst mit smartctl -a /dev/sda beginnen, den Status abzufragen, das sollte bei zwei Laufwerken funktionieren.
Zum Vergrößern anklicken....
Geht leider auch nicht.
Code: 
D:\Program Files\smartmontools\bin>smartctl -a /dev/sda
smartctl version 5.38 [i686-mingw32-xp-sp2] Copyright (C) 2002-7 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Hier noch einige Screenshots ...

Platte 1 (smart)
Platte 2
Platte 3
Platte 4 (smart)
raid set info
smart enabled
volume set
sata mode

Die betriebsanleitung sagt, dass wenn SMART nicht vorhanden ist, der Verbund gefailed wird. scheint aber nicht so zu sein.

Gruß,
 
Zuletzt bearbeitet:
Antimon schrieb:
...
Die S.M.A.R.T Sache ist schön recht und gut nur leider protokolliert das Teil Sektorenfehler erst wenn sie von den Schreib/Leseköpfen an der jeweiligen Position festgestellt werden.
...
Zum Vergrößern anklicken....
Hierzu eine prinzipielle Frage bzgl. Sektorfehler (ist unabhängig von RAID). Wenn auf eine Platte geschrieben wird, werden die Daten ja nicht kontrolliert (verify after write). Demnach werden Fehler erst entdeckt, wenn diese daten wieder von der Platte gelesen werden. ist das alles richtig so?

Ich nehme an bei RAID verhält es sich analog. Die Sektorfehler werden erst entdeckt wenn explizit ein Parity check von Administrator gestartet wird. Ist das auch richtig?

Gruß,
 
Hallo.

Ich habe eine Platte, die im ARC-1210 keine SMART Daten ausgegeben hat, direkt an den onboard SATA2 Port (NVIDIA Chip) angeschlossen.

smartmontools hat die SMART Daten angezeigt. Irgend etwas scheint aber faul damit zu sein, dass die ARC-1210 sie nicht anzeigt.

Code: 
smartctl version 5.38 [i686-mingw32-xp-sp2] Copyright (C) 2002-7 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Warning! Drive Identity Structure error: invalid SMART checksum.
=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar RE Serial ATA series
Device Model:     WDC WD5000YS-01MPB0
Serial Number:    WD-WMANUxxxxxxx
Firmware Version: 07.02E07
User Capacity:    500.107.862.016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Apr 18 13:13:13 2008 RDT
SMART support is: Available - device has SMART capability.
                  Enabled status cached by OS, trying SMART RETURN STATUS cmd.
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:  (0x83)	Offline data collection activity
					is in a Reserved state.
					Auto Offline Data Collection: Enabled.
Total time to complete Offline 
data collection: 		 (13560) seconds.
Offline data collection
capabilities: 			 (0x00) 	Offline data collection not supported.
SMART capabilities:            (0x0000)	Automatic saving of SMART data					is not implemented.
Error logging capability:        (0x00)	Error logging supported.
					General Purpose Logging supported.
SCT capabilities: 	       (0x103f)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 2

ATA Error Count: 0
	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 0 occurred at disk power-on lifetime: 65527 hours (2730 days + 7 hours)
  When the command that caused the error occurred, the device was in a vendor specific state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  ff 7f fb ff ff bf ff

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  7f ff ef ff ff ff ff ff  46d+14:28:50.811  SEEK [RET-4]
  ff ff ff b7 ff ff ff ff  49d+17:01:40.727  [VENDOR SPECIFIC]
  7f ff fe ff fb ed fd fd  49d+17:02:47.291  SEEK [RET-4]
  ff fb ff 7f bf df ef ff  49d+16:54:02.879  [VENDOR SPECIFIC]
  ff ff df ff fb ef ff fd  46d+14:28:50.815  [VENDOR SPECIFIC]

Error -1 occurred at disk power-on lifetime: 65527 hours (2730 days + 7 hours)
  When the command that caused the error occurred, the device was in a vendor specific state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  ff ee ff 7f ff 7f ff

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  fd ff ff fd ff ff ff ff  49d+17:02:47.295  [VENDOR SPECIFIC]
  dd df f7 de df fd ff ff  11d+15:37:12.943  BOOT PRE-BOOT [RET-4]
  fd fe 7f ff ff be bf ff  49d+14:42:58.623  [VENDOR SPECIFIC]
  08 00 00 00 00 00 00 00  49d+14:42:58.687  DEVICE RESET
  10 00 00 00 00 00 20 00      00:01:05.536  RECALIBRATE [OBS-4]

Error -2 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  00 00 00 04 00 00 00  

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 00      00:00:04.096  NOP [Abort queued commands]
  00 00 00 00 00 80 00 00      00:00:00.000  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00   1d+13:16:57.728  NOP [Abort queued commands]
  00 00 04 00 00 80 00 00      00:00:00.000  NOP [Abort queued commands]
  20 00 00 00 00 00 00 00      00:00:00.000  READ SECTOR(S)

Error -3 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  00 00 04 00 00 00 02  

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 08 00 00 00      00:00:00.000  NOP [Abort queued commands]
  00 00 00 00 00 00 20 00      00:00:02.048  NOP [Abort queued commands]
  00 00 00 00 00 00 00 10   6d+05:07:50.912  NOP [Abort queued commands]

Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  00 00 00 00 00 00 00  

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 20 00 80 00      00:00:00.032  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      04:39:37.217  NOP [Abort queued commands]
  00 20 00 00 00 00 00 00      00:00:00.000  NOP [Reserved subcommand]
  00 00 00 00 00 00 00 00  26d+09:48:21.376  NOP [Abort queued commands]
  00 20 00 00 00 00 00 80      00:00:16.640  NOP [Reserved subcommand]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Vendor offline      Self-test routine in progress 150%     65022         -
# 2  Vendor offline      Unknown/reserved test status  150%     65527         -
# 3  Vendor offline      Self-test routine in progress 150%     65535         -
# 4  Vendor offline      Self-test routine in progress 150%     65527         -
# 5  Reserved offline    Self-test routine in progress 150%     65535         -
# 6  Vendor offline      Self-test routine in progress 150%     32767         -
# 7  Vendor offline      Self-test routine in progress 150%     65535         -
# 8  Vendor offline      Self-test routine in progress 150%     65503         -
# 9  Vendor offline      Self-test routine in progress 150%     65399         -
#10  Vendor offline      Self-test routine in progress 70%     61439         -
#11  Vendor offline      Self-test routine in progress 150%     63487         -
#12  Vendor offline      Completed: read failure       150%     65535         4261378047
#13  Vendor offline      Self-test routine in progress 150%     65535         -
#14  Vendor offline      Self-test routine in progress 110%     65535         -
#15  Vendor offline      Self-test routine in progress 150%     64511         -
#16  Vendor offline      Self-test routine in progress 110%     65535         -
#17  Vendor offline      Self-test routine in progress 150%     65527         -
#18  Vendor offline      Self-test routine in progress 150%     65535         -
#19  Vendor offline      Self-test routine in progress 150%     65535         -
#20  Vendor offline      Self-test routine in progress 110%     65534         -
#21  Vendor offline      Self-test routine in progress 150%     63455         -

Device does not support Selective Self Tests/Logging
 
Zuletzt bearbeitet:
Ein S.M.A.R.T.-Log sollte etwa wie folgt aussehen:
Code: 
[FONT="Courier New"]smartctl version 5.38 [i686-mingw32-xp-sp2] Copyright (C) 2002-7 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: ExcelStor Technology J880
Serial Number: PFD810K2BBDP4B
Firmware Version: PF2OA21B
User Capacity: 82.348.277.760 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1
Local Time is: Thu Jan 03 11:31:35 2008 WN
SMART support is: Available - device has SMART capability.
Enabled status cached by OS, trying SMART RETURN STATUS cmd.
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: (1779) 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: ( 30) minutes.

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 -65536
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline -0
3 Spin_Up_Time 0x0007 107 107 024 Pre-fail Always -186 (Average 185)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always -553
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always -5
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always -0
8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline -0
9 Power_On_Hours 0x0012 099 099 000 Old_age Always -10400
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always -0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always -520
192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always -867
193 Load_Cycle_Count 0x0012 100 100 050 Old_age Always -867
194 Temperature_Celsius 0x0002 148 148 000 Old_age Always -37 (Lifetime Min/Max 16/61)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always -5
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always -1
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline -0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always -22

SMART Error Log Version: 1
ATA Error Count: 220 (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 220 occurred at disk power-on lifetime: 10397 hours (433 days + 5 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 60 27 1d 2e e1 Error: UNC 96 sectors at LBA = 0x012e1d27 = 19799335

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 68 1f 1d 2e e1 00 00:01:48.200 READ DMA
ca 00 20 77 07 74 e6 00 00:01:48.200 WRITE DMA
ca 00 18 a7 f4 11 e1 00 00:01:48.200 WRITE DMA
c8 00 08 8f 07 74 e6 00 00:01:48.200 READ DMA
c8 00 18 5f 44 4c e9 00 00:01:48.200 READ DMA

Error 219 occurred at disk power-on lifetime: 10392 hours (433 days + 0 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 60 27 1d 2e e1 Error: UNC 96 sectors at LBA = 0x012e1d27 = 19799335

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 68 1f 1d 2e e1 00 03:08:42.100 READ DMA
ca 00 20 17 04 74 e6 00 03:08:42.100 WRITE DMA
ca 00 18 5f 44 4c e9 00 03:08:42.100 WRITE DMA
c8 00 18 a7 f4 11 e1 00 03:08:42.100 READ DMA
c8 00 20 17 04 74 e6 00 03:08:42.100 READ DMA

Error 218 occurred at disk power-on lifetime: 10389 hours (432 days + 21 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 63 27 1d 2e e1 Error: UNC 99 sectors at LBA = 0x012e1d27 = 19799335

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 d0 80 0a 1d 2e e1 00 00:53:10.600 READ DMA
c8 d0 80 8a 1c 2e e1 00 00:53:10.600 READ DMA
c8 d0 80 0a 1c 2e e1 00 00:53:10.600 READ DMA
c8 d0 80 8a 1b 2e e1 00 00:53:10.600 READ DMA
c8 d0 80 0a 1b 2e e1 00 00:53:10.600 READ DMA

Error 217 occurred at disk power-on lifetime: 10389 hours (432 days + 21 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 60 27 1d 2e e1 Error: UNC 96 sectors at LBA = 0x012e1d27 = 19799335

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 d0 68 1f 1d 2e e1 00 00:12:22.200 READ DMA
ca d0 18 a7 f4 11 e1 00 00:12:22.200 WRITE DMA
c8 d0 30 17 81 46 e9 00 00:12:22.200 READ DMA
ca d0 80 27 f4 11 e1 00 00:12:22.200 WRITE DMA
c8 d0 80 97 80 46 e9 00 00:12:22.200 READ DMA

Error 216 occurred at disk power-on lifetime: 10388 hours (432 days + 20 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 60 27 1d 2e e1 Error: UNC 96 sectors at LBA = 0x012e1d27 = 19799335

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 d0 68 1f 1d 2e e1 00 00:04:32.600 READ DMA
ca d0 18 17 81 46 e9 00 00:04:32.600 WRITE DMA
c8 d0 30 a7 f4 11 e1 00 00:04:32.600 READ DMA
ca d0 80 97 80 46 e9 00 00:04:32.600 WRITE DMA
c8 d0 80 27 f4 11 e1 00 00:04:32.600 READ DMA

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


Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
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.[/FONT]
Mir fehlen da Informationen?
 
Mueli schrieb:
Ein S.M.A.R.T.-Log sollte etwa wie folgt aussehen:
Code: 
[FONT="Courier New"]smartctl version 5.38 [i686-mingw32-xp-sp2] Copyright (C) 2002-7 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
...
[/FONT]
Mir fehlen da Informationen?
Zum Vergrößern anklicken....
Was meinst du damit (sorry!)?

Fehlen dir Informationen über meinen SMART Log (wenn ja, was fehlt?) oder über deinen?

Sind in meinem Anhaltspunkte zu erkennen warum der ARC-1210 die SMART `Daten nicht ausgibt?

Gruß,
 
Die eigentlichen Attributes Data wie #5, #196, # 197 usw.
 
Die Attribute wurden nicht ausgegeben, da es ein Problem mit der Firmware bzgl. SMRT gab. Ich habe alle 4 Platten nach und nach auf die neue Firmware gebracht. "07.02E07" war drauf, jetzt ist "09.02E09" drauf. Alle Platten zeigen jetzt die SMART daten an. Merkwürdig dass es anscheinend daran lag ?!?!

Code: 
smartctl version 5.38 [i686-mingw32-xp-sp2] Copyright (C) 2002-7 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Warning! Drive Identity Structure error: invalid SMART checksum.
=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar RE Serial ATA series
Device Model:     WDC WD5000YS-01MPB1
Firmware Version: 09.02E09
User Capacity:    500.107.862.016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Tue Apr 22 11:05:37 2008 RDT
SMART support is: Available - device has SMART capability.
                  Enabled status cached by OS, trying SMART RETURN STATUS cmd.
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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		 (13560) 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 170) minutes.
Conveyance self-test routine
recommended polling time: 	 (   6) minutes.
SCT capabilities: 	       (0x103f)	SCT Status 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     0x000f   100   253   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       3
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   051    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       0
 10 Spin_Retry_Count        0x0013   100   253   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0012   100   253   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2
194 Temperature_Celsius     0x0022   108   108   000    Old_age   Always       -       44
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0009   100   253   051    Pre-fail  Offline      -       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.
 
Unterschiedliche Revisionen der Drives können bei RAID schon Probleme bereiten, im Support von Serversystemen waren wir immer gehalten alle Drives auf einem identischen Firmware-Level zu halten, manchmal recht aufwendig wenn 40 bis weit über 100 Drives in einem RAID steckten.
 
Nein, es waren nie unterschiedliche Versionen online. Zum Zeitpunkt des Postings hatten alle 4 Laufwerke die gleiche FW drauf. Von daher bestand kein Grund dass der ARC-1210 die SMART Daten von 2 HDDs erkannte und von 2 HDDs nicht.

IMHO war im FlashRAM (oder wo die SMART Daten auch immer gespeichert sind) ein nicht vorhergesehener Zustand aufgetreten, der dann dazu führte dass die SMART Daten nicht korrekt ausgegeben wurde. Ein FW Upgrade hat nebenbei nämlich noch die SMART Daten zurückgesetzt (Tacho auf 0 gesetzt).

Wie dem auch sei ... dieses Problem ist mit FW 09.02E09 gelöst.

Danke für die Antworten!

Gruß,
 
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen

B
Wie interpretiert ihr SMART Daten meiner beiden WD RED HDDs?
2
Antworten
21
Aufrufe
1.223
bandchef
B
J
SMART Daten bei neuer Festplatte auffällig?
Antworten
7
Aufrufe
986
Joshy34
J
L
Festplatte für Daten als Zweite Platte
2
Antworten
25
Aufrufe
1.198
TorenAltair
T
G
Sind HDTune und SMART ausreichend um Platte auf defekte zu prüfen?
Antworten
10
Aufrufe
1.104
SilenceIsGolden
SilenceIsGolden
Skudrinka
Warum wird die Platte nicht ausgeworfen? (SMART-Werte)
Antworten
5
Aufrufe
532
xxMuahdibxx
xxMuahdibxx

Passend zum Thema

Zurück
Oben

Willkommen auf ComputerBase!

Mit Werbung weiterlesen

Besuche ComputerBase wie gewohnt mit Werbung und Tracking. Die Zustimmung ist jederzeit widerrufbar.

Details im Privacy Center und in der Liste unserer Partner. Ein Widerruf ist möglich in der Datenschutzerklärung.

… oder ComputerBase Pro bestellen

Nutze ComputerBase ohne Werbebanner, Video-Ads und Werbetracking schon für 4 €/Monat oder 36 €/Jahr.

Mehr zu ComputerBase Pro

Bereits Pro-Nutzer? Hier anmelden.

Tracking: Wir und unsere 187 Partner verarbeiten personenbezogene Daten, indem wir mit auf Ihrem Gerät gespeicherten Informationen (z. B. eindeutige Kennungen in Cookies) ein Nutzungsprofil erstellen, um z. B. Anzeigen zu personalisieren. Verarbeitungszwecke: Genaue Standortdaten und Abfrage von Geräteeigenschaften zur Identifikation, Informationen auf einem Gerät speichern und/oder abrufen, Personalisierte Anzeigen und Inhalte, Anzeigen- und Inhaltsmessungen, Erkenntnisse über Zielgruppen und Produktentwicklungen.

Impressum Kontakt Datenschutz