dodo |
J'ai démarré sur un OMV en dur, c'est plus stable que sur proxmox, mes disques me remontent des erreurs sont bien monté.
J'arrive bien à lire les données smart.
Code :
- 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 0x002f 200 200 051 Pre-fail Always - 0
- 3 Spin_Up_Time 0x0027 175 168 021 Pre-fail Always - 4250
- 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 249
- 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
- 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
- 9 Power_On_Hours 0x0032 029 029 000 Old_age Always - 52035
- 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
- 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
- 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 249
- 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 188
- 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5400
- 194 Temperature_Celsius 0x0022 117 106 000 Old_age Always - 30
- 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
- 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
- 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
- 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
- 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
- SMART Error Log Version: 1
- ATA Error Count: 26 (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 26 occurred at disk power-on lifetime: 51998 hours (2166 days + 14 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
- -- -- -- -- -- -- --
- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT
- Commands leading to the command that caused the error were:
- CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
- -- -- -- -- -- -- -- -- ---------------- --------------------
- ef 03 45 00 00 00 a0 08 03:04:09.019 SET FEATURES [Set transfer mode]
- ec 00 00 00 00 00 a0 08 03:04:09.016 IDENTIFY DEVICE
- ec 00 00 00 00 00 a0 08 03:04:03.139 IDENTIFY DEVICE
- ef 03 45 00 00 00 a0 08 03:04:03.136 SET FEATURES [Set transfer mode]
- ec 00 00 00 00 00 a0 08 03:04:03.134 IDENTIFY DEVICE
- Error 25 occurred at disk power-on lifetime: 51998 hours (2166 days + 14 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
- -- -- -- -- -- -- --
- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT
- Commands leading to the command that caused the error were:
- CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
- -- -- -- -- -- -- -- -- ---------------- --------------------
- ef 03 45 00 00 00 a0 08 03:04:03.136 SET FEATURES [Set transfer mode]
- ec 00 00 00 00 00 a0 08 03:04:03.134 IDENTIFY DEVICE
- ec 00 00 00 00 00 a0 08 03:03:57.120 IDENTIFY DEVICE
- ef 03 45 00 00 00 a0 08 03:03:57.118 SET FEATURES [Set transfer mode]
- ec 00 00 00 00 00 a0 08 03:03:57.116 IDENTIFY DEVICE
- Error 24 occurred at disk power-on lifetime: 51998 hours (2166 days + 14 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
- -- -- -- -- -- -- --
- 04 61 45 00 00 00 a0 Device Fault; Error: ABRT
- Commands leading to the command that caused the error were:
- CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
- -- -- -- -- -- -- -- -- ---------------- --------------------
- ef 03 45 00 00 00 a0 08 03:03:57.118 SET FEATURES [Set transfer mode]
- ec 00 00 00 00 00 a0 08 03:03:57.116 IDENTIFY DEVICE
- ec 00 00 00 00 00 a0 08 03:03:56.317 IDENTIFY DEVICE
- ef 03 46 00 00 00 a0 08 03:03:56.315 SET FEATURES [Set transfer mode]
- Error 23 occurred at disk power-on lifetime: 51998 hours (2166 days + 14 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
- -- -- -- -- -- -- --
- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT
- Commands leading to the command that caused the error were:
- CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
- -- -- -- -- -- -- -- -- ---------------- --------------------
- ef 03 46 00 00 00 a0 08 03:03:56.315 SET FEATURES [Set transfer mode]
- ec 00 00 00 00 00 a0 08 03:03:56.313 IDENTIFY DEVICE
- ec 00 00 00 00 00 a0 08 03:03:56.297 IDENTIFY DEVICE
- ef 03 46 00 00 00 a0 08 03:03:56.295 SET FEATURES [Set transfer mode]
- Error 22 occurred at disk power-on lifetime: 51998 hours (2166 days + 14 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
- -- -- -- -- -- -- --
- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT
- Commands leading to the command that caused the error were:
- CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
- -- -- -- -- -- -- -- -- ---------------- --------------------
- ef 03 46 00 00 00 a0 08 03:03:56.295 SET FEATURES [Set transfer mode]
- ec 00 00 00 00 00 a0 08 03:03:56.293 IDENTIFY DEVICE
- ec 00 00 00 00 00 a0 08 03:03:56.277 IDENTIFY DEVICE
- ef 03 46 00 00 00 a0 08 03:03:56.275 SET FEATURES [Set transfer mode]
- SMART Self-test log structure revision number 1
- Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
- # 1 Short offline Completed without error 00% 51966 -
- # 2 Short offline Completed without error 00% 95 -
- # 3 Short offline Completed without error 00% 83 -
- # 4 Short offline Completed without error 00% 80 -
- # 5 Short offline Completed without error 00% 60 -
- # 6 Short offline Completed without error 00% 41 -
- # 7 Short offline Completed without error 00% 31 -
- # 8 Short offline Completed without error 00% 28 -
- # 9 Short offline Completed without error 00% 15 -
- #10 Short offline Completed without error 00% 7 -
- #11 Short offline Completed without error 00% 7 -
- #12 Short offline Completed without error 00% 6 -
- #13 Short offline Completed without error 00% 6 -
- 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.
|
A chaque fois que j'essaye d'isoler le disque en cause, j'ai l'impression que j'ai des erreurs sur d'autres disques.
j'ai deux disques WD RED 2TO et un vieux disque.
Faboss a écrit :
Ai-je dit le contraire ?
Le gros intérêt d'un RAID c'est que c'est instantané et qu'une fois mis en service on ne s'en préoccupe pas.
Là du coup, il a potentiellement paumé des données entre sa dernière sauvegarde et la panne
|
En démarrant sur OMV en direct, j'ai profité hier pour faire une sauvegarde complète via rsync à voir si elle fiable.
Au pire, je referais une synchro sur ma dernière sauvegarde de la semaine dernière, les modifs représente quelques Mo.
Habituellement, j'ai une synchro journalière, mais là pour des raisons techniques, je l'avais supprimé.
enikka a écrit :
je comprends jamais ce débat éternel
raid c’est pas pour de la sauvegarde, mais ca sert à quoi de la continuité de service sur un nas perso?
raid 0, c’est le mode miroir, le 2ème disque est identique, ca ne suffit pas pour de la sauvegarde (vu qu’il est dans le même pc, même localisation) mais typiquement en cas de panne d’un des 2, ca fonctionne non?
|
C'est bien ça le soucis, même en ayant des sauvegardes je me rend compte que mon disque de sauvegarde est sur mon NAS, en cas de coupure électrique les données comme la sauvegarde peuvent se retrouver corrompus.
C'est pour ça que j'ai mis en place une sauvegarde sur disque externe une fois par semaine. Message édité par dodo le 01-11-2023 à 11:40:34
|