Fórum Root.cz
Hlavní témata => Hardware => Téma založeno: e3k 11. 09. 2024, 21:35:28
-
magnety samozrejme vyberem!
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.47-gentoo-dist] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST2000DM001-1ER164
Serial Number: Z4Z3M0N3
LU WWN Device Id: 5 000c50 08700cbd7
Firmware Version: CC26
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
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Sep 11 21:15:07 2024 CEST
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 248) Self-test routine in progress...
80% of test remaining.
Total time to complete Offline
data collection: ( 80) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No 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: ( 216) 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 - 154796888
3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1156
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 56
7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 16130225
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1886
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1146
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 066 066 000 Old_age Always - 34
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0
189 High_Fly_Writes 0x003a 088 088 000 Old_age Always - 12
190 Airflow_Temperature_Cel 0x0022 063 054 045 Old_age Always - 37 (Min/Max 22/40)
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 - 169
193 Load_Cycle_Count 0x0032 093 093 000 Old_age Always - 14532
194 Temperature_Celsius 0x0022 037 046 000 Old_age Always - 37 (0 17 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 - 1478h+09m+27.378s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 30097244763
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 70948224161
SMART Error Log Version: 1
ATA Error Count: 34 (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 34 occurred at disk power-on lifetime: 1860 hours (77 days + 12 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 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 08 ff ff ff 4f 00 11:11:04.424 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 11:11:04.410 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 11:11:04.384 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 11:11:04.383 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 11:11:04.371 SET FEATURES [Set transfer mode]
Error 33 occurred at disk power-on lifetime: 1860 hours (77 days + 12 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 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 08 ff ff ff 4f 00 11:11:00.658 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 11:11:00.648 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 11:11:00.622 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 11:11:00.621 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 11:11:00.609 SET FEATURES [Set transfer mode]
Error 32 occurred at disk power-on lifetime: 1860 hours (77 days + 12 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 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 08 ff ff ff 4f 00 11:10:56.879 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 11:10:56.868 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 11:10:56.841 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 11:10:56.841 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 11:10:56.828 SET FEATURES [Set transfer mode]
Error 31 occurred at disk power-on lifetime: 1860 hours (77 days + 12 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 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 08 ff ff ff 4f 00 11:10:53.115 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 11:10:53.105 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 11:10:53.079 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 11:10:53.078 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 11:10:53.066 SET FEATURES [Set transfer mode]
Error 30 occurred at disk power-on lifetime: 1860 hours (77 days + 12 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 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 08 ff ff ff 4f 00 11:10:49.228 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 11:10:49.192 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 11:10:48.391 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 11:10:48.377 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 11:10:48.376 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 Self-test routine in progress 80% 1886 -
# 2 Short offline Completed without error 00% 1652 -
# 3 Short offline Completed without error 00% 1404 -
# 4 Extended offline Completed without error 00% 3 -
# 5 Short offline Completed without error 00% 0 -
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.
The above only provides legacy SMART information - try 'smartctl -x' for more
-
Nevím co chceš vědět, ale za mě to klidně vyhoď... Je mi to jedno...
-
Za mně ne, např. pro sekundární zálohu může ještě posloužit.
Doporučuji sledovat atribut Reallocated_Sector_Ct, zda nebude časem neúměrně narůstat. Také doporučuji vyměnit datový SATA kabel za nový, nekvalitní kabel bývá příčinou vysokého počtu chyb při čtení.
-
Seagate má v parametru Raw_Read_Error_Rate vždycky nějaké šílené číslo.
Ale je nenulový počet realokovaných sektorů, to je potřeba sledovat.
No a navíc jste netrpělivý, ještě nedoběhl extended self test.
A nakonec záleží, jak si ceníte dat na disku uložených - já bych se raději už podíval po jiném.
-
Technická, resp jazyková: vyhodit ho samozřejmě můžeš, to je tvoje věc.
Správná otázka zní "je bezpečné ho nadále používat pro data, na kterých nějak záleží?".
Aneb UTG "Jak se správně ptát" / "How to ask the right questions".
-
Aneb UTG "Jak se správně ptát" / "How to ask the right questions".
Co je zač zkratka UTG? nenašel jsem ji ani na stránce wikipedia ani acronymněcofinder
Patří snad UTG do řady:?
1. RtFM
2. UtG
3. AtAI
-
Vidím Reallocated_Sector_Ct = 56. To je mrzuté - minimálně se zamyslete, zda máte zálohy dat, na kterých Vám záleží.
Zatím tam vidím Offline Uncorrectable = 0, což je asi relativně dobrá zpráva.
Pikantní jsou nalogované chyby UNC na LBA adrese 0x0FFFFFFF . Dle ATA standardu adresa (2^28)-1 není platná pro LBA28 :-)
https://forum.root.cz/index.php?topic=24196.msg343871#msg343871
https://www.abclinuxu.cz/poradna/hardware/show/376246#20
Co máte za verzi kernelu? Je to docela přízračné "shledání po letech"... Dumám, jestli to není něco starého / ozvěna dávných dob, ale ten disk není úplně starý model a má naběháno necelých 2000 hodin... že by se ten bug vrátil do kernelu, potřetí nebo po kolikáté? V aktuálním zdrojáku Libata (aha.h) to vypadá v pořádku. (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/ata.h#n1034) Viz lba_28_ok(). Na tomto místě je to opravené dávno (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=45c4d015a92f72ec47acd0c7557abdc0c8a6499d) (cca 2.6.32).
-
UTG = Use The Google
nebo jestli chceš, dosaď si tam F na UTFG.
-
Ale je nenulový počet realokovaných sektorů, to je potřeba sledovat.
No a navíc jste netrpělivý, ještě nedoběhl extended self test.
1. pustil som na to badblocks a naslo mi ich 24 -> tie uz su inkludovane v tom SMART vypise.
2. self test povedal ze vsetko oka
-
Vidím Reallocated_Sector_Ct = 56. To je mrzuté - minimálně se zamyslete, zda máte zálohy dat, na kterých Vám záleží.
Pikantní jsou nalogované chyby UNC na LBA adrese 0x0FFFFFFF .
ano disk je uz zmigrovany. a prepisany badblock -w
ad UNC: tu chybu som tam dostal az po zbehnuti badblocku. vidim to prvy krat a je to jeden z dovodov preco som sem vobec pisal. kernel = 6.6.47-gentoo-dist
-
ad UNC: tu chybu som tam dostal az po zbehnuti badblocku. vidim to prvy krat a je to jeden z dovodov preco som sem vobec pisal. kernel = 6.6.47-gentoo-dist
UNC obecně znamená uncorrectable error (na médiu, = vadný sektor), ale LBA adresa 2^28-1 je speciální případ, kdy se o vadný sektor nejspíš nejedná :-) protože jde o nedorozumění mezi hostitelem (libata) a diskem.
Koukám do badblocks.c v balíku e2fsprogs... podle všeho jede skrz blokovou vrstvu, jenom si podle potřeby zapne O_DIRECT - ale ATA příkazy formátuje libata (nebo co je vespod za disk).
Nebyl ten disk připojený skrz nějaký bridge (USB/SATA), který teoreticky možná mapoval UMass nebo SCSI verzi LBA na (S)ATA LBA? Zas jestli Vám skrz to chodí nastojato ATA S.M.A.R.T. tak bych tam nějaký "překlad protokolu" nehledal.
Co máte za diskový řadič?
-
$ lspci|grep -i sata
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller