HDD napake - uveljavitev garancije? @ Slo-Tech

Forum » Strojna oprema »
HDD napake - uveljavitev garancije?

HDD napake - uveljavitev garancije?

bijoloh :: 7. avg 2016, 17:46

Pozdravljeni,

potrebujem mnenje glede HDD-ja.
Imam HDD, ki je še pol leta v garanciji, zadnje čase pa sta se pri pregledu s smartmontools pojavili 2 napaki - prva pred približno mesecem in pol, druga včeraj. Sicer overall-health status napiše PASSED, ampak me zanima vaše mnenje ali bi lahko za to že uveljavil garancijo? Predvsem bi nebi rad, da bo disk kar "čez noč" mrknil in bom ostal brez diska...

Spodaj je izpis preizkusa z napakami:

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.0-327.28.2.el7.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" HDD DT01ACA...
Device Model:     TOSHIBA DT01ACA100
Serial Number:    xxxxxxxxxxx
LU WWN Device Id: xxxxxxxxxxx
Firmware Version: MS2OA750
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
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: 3.0 Gb/s)
Local Time is:    Sun Aug  7 17:01:48 2016 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:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					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: 		( 7022) 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: 	 ( 117) 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   141   141   054    Pre-fail  Offline      -       72
  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       188
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       6
  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   115   115   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       12829
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       6
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       17
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       17
194 Temperature_Celsius     0x0002   206   206   000    Old_age   Always       -       29 (Min/Max 18/37)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
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: 2
	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 2 occurred at disk power-on lifetime: 12815 hours (533 days + 23 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 38 48 1f b9 0c  Error: UNC at LBA = 0x0cb91f48 = 213458760

  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 80 50 00 2e b9 40 08      01:50:58.626  READ FPDMA QUEUED
  60 80 48 80 2d b9 40 08      01:50:58.626  READ FPDMA QUEUED
  60 80 40 00 2d b9 40 08      01:50:58.626  READ FPDMA QUEUED
  60 80 38 80 2c b9 40 08      01:50:58.625  READ FPDMA QUEUED
  60 80 30 00 2c b9 40 08      01:50:58.625  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 11303 hours (470 days + 23 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 38 48 1f b9 0c  Error: UNC at LBA = 0x0cb91f48 = 213458760

  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 b8 80 23 b9 40 08   2d+18:08:51.819  READ FPDMA QUEUED
  60 00 b0 80 1f b9 40 08   2d+18:08:51.816  READ FPDMA QUEUED
  60 00 a8 80 1b b9 40 08   2d+18:08:51.813  READ FPDMA QUEUED
  60 80 a0 00 18 b9 40 08   2d+18:08:51.787  READ FPDMA QUEUED
  60 00 98 00 14 b9 40 08   2d+18:08:51.786  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%     12826         -
# 2  Short offline       Completed without error       00%     12823         -
# 3  Extended offline    Completed without error       00%     11320         -
# 4  Short offline       Completed without error       00%     11317         -

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.

Hvala za vaša mnenja!
LP

Han :: 7. avg 2016, 20:47

Dokler disk prestane teste, uveljavljanje garancije nima smisla, ker ne boš nič dosegel. Preglej ga še s kakšnim drugim programom, npr. Toshibinim in Seagatovim (Seatools).

bijoloh :: 7. avg 2016, 22:33

Sem poskušal poiskati na Toshibini spletni strani kak program za testiranje diskov in pod FAQ piše:

Toshiba does not provide any diagnosis tool for HDD for personal users.

Podpora na višku

Bom poskušal še s Seatools in WD Data Lifeguard Diagnostic programom, če bo prepoznalo disk.

Miha 333 :: 8. avg 2016, 01:35

Poskusi s Hitachijevim DFT, saj gre za rebrandan Hitachi Deskstar 7K1000.D.

bijoloh :: 8. avg 2016, 17:58

Miha 333 je 8. avg 2016 ob 01:35 izjavil:

Poskusi s Hitachijevim DFT, saj gre za rebrandan Hitachi Deskstar 7K1000.D.

Hvala za informacijo, bom jutri poskusil še s tem programom, ko bom znova zagnal sistem.

solatko :: 8. avg 2016, 19:28

Na strani proizvajalca pogledaš do kdaj je garancija in z njihovim orodjem preveriš disk. Če je test negativen, dobiš kodo in navodila za reklamacijo.
To odneseš tja, kjer si kupil ali pa sam pošlješ v zamenjavo.

Delo krepa človeka

bijoloh :: 9. avg 2016, 22:36

solatko je 8. avg 2016 ob 19:28 izjavil:

Na strani proizvajalca pogledaš do kdaj je garancija in z njihovim orodjem preveriš disk. Če je test negativen, dobiš kodo in navodila za reklamacijo.
To odneseš tja, kjer si kupil ali pa sam pošlješ v zamenjavo.

Sliši se preprosto, ampak ko se stvari lotiš se lahko precej zaplete

Grem na Toshiba.si, prijadram do strani za podporo in registracijo naprave. Vnesem serijsko, datum nakupa in državo nakupa in napiše, da serijska št. ni veljavna. Poskusim še enkrat, isto - serijska ni veljavna. Potem poskušam kombinacijo, da vnašam črke kot male tiskane, kot velike tiskane, zmeraj ista napaka - serijska ni veljavna. Ker imam še en disk od Toshibe (isti model) poskusim še s serijsko št. tega drugega diska in spet ista napaka. Potem poskusim še preko domene toshiba.eu in spet ista zadeva 8-O

. A njihova spletna stran sploh resnično deluje?

Potem pišem kar na email slovenske firme, ki je navedena za garancijo (kjer jim razložim situacijo). Pohvalno sem takoj dobil odgovor, da naj jim prinesem disk, da ga bodo oni testirali, da bodo videli za kaj se gre.

Vmes sem zagnal Hirens boot CD in zagnal WD Data LifeGuard Diagnostic, ki je prepoznal v sistemu tako Seagatove, kot Toshibine diske. Na problematičnem Toshibinem disku zaženem najprej quick test, ki prestane preizkus (PASSED), potem pa še extended, ki pa napiše, da je našel bad sektorje, ter mi ponudi možnost popravila. Ker nisem siguren, ali je pametno s programom od WD "popravljati" bad sektorje od Toshibinega diska, sem zaenkrat pustil pri miru. Še poročilo od testiranja:

Test Option:	QUICK TEST
Model Number:	TOSHIBA DT01ACA100
Unit Serial Number:	xxxxxxxx
Firmware Number:	MS2OA750
Capacity:	1000.20 GB
SMART Status:	PASS
Test Result:	PASS
Test Time:	12:37:35, August 09, 2016

Test Option:	EXTENDED TEST
Model Number:	TOSHIBA DT01ACA100
Unit Serial Number:	xxxxxxxx
Firmware Number:	MS2OA750
Capacity:	1000.20 GB
SMART Status:	PASS
Test Result:	FAIL
Test Error Code:	08-
Test Time:	14:25:58, August 09, 2016

Potem znova zaženem sistem (Linux) in še enkrat pregledam disk s smartmoontools, kjer mi javlja, da je sedaj že 11 odkritih napak...

Zdaj sem v dvomu kaj narediti - ali z WD Data LifeGuard Diagnostic "popraviti" bad sektorje ali poslati slovenski firmi v garancijo? Predvsem drugo se mi zdi, da bodo oni naredili enako kot bi lahko jaz - s programsko opremo "popravili" bad sektorje in mi vrnili disk "popravljen" nazaj.

Ima kdo kakšne konkretne izkušnje, kakšna je praksa, če se ti pojavijo bad sektorji na disku v garanciji - ti zamenjajo disk z novim ali ti ga "popravijo"?
LP

Han :: 9. avg 2016, 22:59

Dokler ga lahko, ga popravljajo, potem ga menjajo z novim ali obnovljenim (refurbished). Slabi sektorji se pri 'popravilu' dejansko izločijo iz uporabe. Nadomestijo jih dobri iz rezerve. Ko rezerve zmanjka, dobiš drug disk...

Seatools tudi vidi slabe sektorje?

Kaj pravi CrystalDiskInfo?

Zgodovina sprememb…

spremenil: Han (9. avg 2016 ob 23:00)

solatko :: 10. avg 2016, 13:00

Pojdi na stran Seagate, saj je Toshiba njihova.

Delo krepa človeka

:: 10. avg 2016, 13:27

bijoloh je 9. avg 2016 ob 22:36 izjavil:

Ima kdo kakšne konkretne izkušnje, kakšna je praksa, če se ti pojavijo bad sektorji na disku v garanciji - ti zamenjajo disk z novim ali ti ga "popravijo"?
LP

IMHO ne, ker slabi sektorji so pri klasičnih diskih nekaj povsem vsakdanjega in jih vsebuje skoraj vsak disk. Vsak disk ima zato tudi nekaj rezervnih sektorjev, ki jih uporabi, kadar zazna slabe (jih premapira). Problem slabega sektorja je v tem, da so podatki, ki se iz njega preberejo, napačni. Zato disk sam od sebe ne more premapirati slabih sektorjev, saj ne ve, kaj storiti z napačnimi podatki. To lahko stori samo aplikacija, ki te podatke uporablja. Taki sektorji so v smart označeni s "pending". Druga pesem pa je, kadar v slab sektor nekaj zapišeš. V tem primeru pa disk pozna "zdravo" vsebino, zato lahko vsebino slabega sektorja zavrže (itak je prišel ukaz za njen prepis) in naredi premapiranje. Zdravilo za slabe sektorje je torej njihov prepis. Najenostavneje je shraniti vsebino in prepisati celoten disk, lahko pa izračunaš, kateri blok na particiji moraš prepisati.

solatko :: 10. avg 2016, 14:00

kamikaze5 - Slab sektor na mestu, kjer sistem zapiše neprenosljivo datoteko, je razlog za menjavo diska. Na Sony-evem prenosniku je bil od 1TB pokvarjen samo en sektor, smart je šel normalno skozi, so takoj zamenjali disk, ker se sistem enostavno ni dalo zagnati, pa tudi factorydefault zaradi tega sektorja ni deloval.

Po drugi strani pa imaš diske, ki imajo v smartu 3 ali več rumene trikotnike, pa so še vedno b.p..

Delo krepa človeka

:: 10. avg 2016, 14:08

solatko je 10. avg 2016 ob 14:00 izjavil:

kamikaze5 - Slab sektor na mestu, kjer sistem zapiše neprenosljivo datoteko, je razlog za menjavo diska.

Toliko v detajle ne poznam. Vzdržujem pa računalnike in NAS-e žlahte, skupaj preko 20 diskov. Do sedaj sem slabe sektorje pozdravil s prepisom.

filip007 :: 10. avg 2016, 16:05

Daj slikco od HD Tune pod "Health", da bomo videli za kakšno napako gre.

Prenosnik, konzola, TV, PC upokojen.

bijoloh :: 11. avg 2016, 10:24

Torej, da odgovorim lepo po vrsti.

CrystalDisk nisem pognal, ker na Hirens Boot CD se pritožuje, da rabi neke datoteke od Internet Explorer-ja, ki naj jih prekopiram in potem registriram - se mi ni ljubilo ukvarjat s tem

Začel sem s HD Tune, ki kaže naslednje:

HD Tune - health

HD Tune - quick scan

Nato sem zagnal še en program - Victoria, ki kaže sledeče:

Victoria HD test

Ter še Seatools 2.23 za DOS. Short test je javil kot PASSED:

Seatools short test PASSED

Nato sem šel še Long test, ki pa je pri 29% zmrznil - lučka na ohišju za indikacijo aktivnosti diska je bila ugasnjena, tudi slišati ni bilo, da bi katerikoli od diskov kaj "mlel". V zgornjem delu zaslona od programa Seatools so se pojavili čudni znaki zelene barve... poskušal sem z ukazom Alt-R za prekinitev testa in vse kar je naredilo je bilo to, da je začel sistemski zvočnik neprekinjeno piskati. Edina rešitev je bil gumb za hard reset sistema:

Seatools long test - zmrznil

Potem zaženem znova Hirens Boot CD in sem si rekel, da bom zagnal še enkrat WD Data LifeGuard Diagnostics in poskušal zagnati "popravilo" bad sektorjev v tem programu - začuda oba testa prestane kot PASSED 8-O

WD DLG long test PASSED po zmrznjenju Seatools

Nato zaženem še HD Tune:

HD Tune - health po zmrznjenju Seatools

ter Victoria HD test:

Victoria HD test po zmrznjenju Seatools

In ker mi ni dalo miru kaj se dogaja, še enkrat zaženem Seatools 2.23 za DOS, kjer oba testa - short in long - gresta skozi brez problemov kot PASSED 8-O

Seatools short - drugič PASSED

Seatools long - drugič passed

Nazadnje zaženem sistem normalno (linux), in pogledam še s smartmontools, ki pa še vedno kaže PASSED ampak sedaj 18 napak:

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.0-327.28.2.el7.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" HDD DT01ACA...
Device Model:     TOSHIBA DT01ACA100
Serial Number:    xxxxxxxxxx
LU WWN Device Id: xxxxxxxxxx
Firmware Version: MS2OA750
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
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: 3.0 Gb/s)
Local Time is:    Thu Aug 11 08:09:43 2016 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:  (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: 		( 7022) 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: 	 ( 117) 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   142   142   054    Pre-fail  Offline      -       69
  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       188
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       6
  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   113   113   020    Pre-fail  Offline      -       35
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       12916
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       6
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       19
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       19
194 Temperature_Celsius     0x0002   222   222   000    Old_age   Always       -       27 (Min/Max 18/37)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
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: 18 (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 18 occurred at disk power-on lifetime: 12904 hours (537 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 00 4e 1f b9 0c  Error: UNC at LBA = 0x0cb91f4e = 213458766

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 d0 00 4e 1f b9 e0 00   3d+18:47:58.536  READ VERIFY SECTOR(S) EXT
  42 d0 00 4d 1f b9 e0 00   3d+18:47:54.719  READ VERIFY SECTOR(S) EXT
  42 d0 00 4c 1f b9 e0 00   3d+18:47:50.901  READ VERIFY SECTOR(S) EXT
  42 d0 00 4b 1f b9 e0 00   3d+18:47:47.083  READ VERIFY SECTOR(S) EXT
  42 d0 00 4a 1f b9 e0 00   3d+18:47:43.265  READ VERIFY SECTOR(S) EXT

Error 17 occurred at disk power-on lifetime: 12904 hours (537 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 00 4d 1f b9 0c  Error: UNC at LBA = 0x0cb91f4d = 213458765

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 d0 00 4d 1f b9 e0 00   3d+18:47:54.719  READ VERIFY SECTOR(S) EXT
  42 d0 00 4c 1f b9 e0 00   3d+18:47:50.901  READ VERIFY SECTOR(S) EXT
  42 d0 00 4b 1f b9 e0 00   3d+18:47:47.083  READ VERIFY SECTOR(S) EXT
  42 d0 00 4a 1f b9 e0 00   3d+18:47:43.265  READ VERIFY SECTOR(S) EXT
  42 d0 00 49 1f b9 e0 00   3d+18:47:39.447  READ VERIFY SECTOR(S) EXT

Error 16 occurred at disk power-on lifetime: 12904 hours (537 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 00 4c 1f b9 0c  Error: UNC at LBA = 0x0cb91f4c = 213458764

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 d0 00 4c 1f b9 e0 00   3d+18:47:50.901  READ VERIFY SECTOR(S) EXT
  42 d0 00 4b 1f b9 e0 00   3d+18:47:47.083  READ VERIFY SECTOR(S) EXT
  42 d0 00 4a 1f b9 e0 00   3d+18:47:43.265  READ VERIFY SECTOR(S) EXT
  42 d0 00 49 1f b9 e0 00   3d+18:47:39.447  READ VERIFY SECTOR(S) EXT
  42 d0 00 00 18 b9 e0 00   3d+18:47:35.642  READ VERIFY SECTOR(S) EXT

Error 15 occurred at disk power-on lifetime: 12904 hours (537 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 00 4b 1f b9 0c  Error: UNC at LBA = 0x0cb91f4b = 213458763

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 d0 00 4b 1f b9 e0 00   3d+18:47:47.083  READ VERIFY SECTOR(S) EXT
  42 d0 00 4a 1f b9 e0 00   3d+18:47:43.265  READ VERIFY SECTOR(S) EXT
  42 d0 00 49 1f b9 e0 00   3d+18:47:39.447  READ VERIFY SECTOR(S) EXT
  42 d0 00 00 18 b9 e0 00   3d+18:47:35.642  READ VERIFY SECTOR(S) EXT
  42 d0 00 00 10 b9 e0 00   3d+18:47:35.632  READ VERIFY SECTOR(S) EXT

Error 14 occurred at disk power-on lifetime: 12904 hours (537 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 00 4a 1f b9 0c  Error: UNC at LBA = 0x0cb91f4a = 213458762

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 d0 00 4a 1f b9 e0 00   3d+18:47:43.265  READ VERIFY SECTOR(S) EXT
  42 d0 00 49 1f b9 e0 00   3d+18:47:39.447  READ VERIFY SECTOR(S) EXT
  42 d0 00 00 18 b9 e0 00   3d+18:47:35.642  READ VERIFY SECTOR(S) EXT
  42 d0 00 00 10 b9 e0 00   3d+18:47:35.632  READ VERIFY SECTOR(S) EXT
  42 d0 00 00 08 b9 e0 00   3d+18:47:35.628  READ VERIFY SECTOR(S) EXT

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%     12909         -
# 2  Short offline       Completed without error       00%     12907         -
# 3  Short offline       Completed without error       00%     12907         -
# 4  Short offline       Completed without error       00%     12905         -
# 5  Short offline       Completed without error       00%     12904         -
# 6  Short offline       Completed without error       00%     12874         -
# 7  Extended offline    Completed without error       00%     12826         -
# 8  Short offline       Completed without error       00%     12823         -
# 9  Extended offline    Completed without error       00%     11320         -
#10  Short offline       Completed without error       00%     11317         -

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.

Če na kratko povzamem - vsakič, potem ko sem zagnal WD toolse za testiranje diska, mi smartmontools poveča število napak za 7. Po tem, ko je Seatools zamrznil, mi tako WD DLG kot Seatools oba pokažeta long in short teste kot PASSED!

Razumem zmeraj manj 8-O

Zgodovina sprememb…

spremenil: bijoloh (11. avg 2016 ob 10:27)

bijoloh :: 11. avg 2016, 22:10

Moram popraviti moj povzetek

- vsakič, potem ko sem zagnal WD toolse za testiranje diska, mi smartmontools prikaže povečano število napak - prvič za 9, drugič za 7. Po tem, ko je Seatools zamrznil, mi tako WD DLG kot Seatools oba pokažeta long in short teste kot PASSED!

filip007 :: 12. avg 2016, 14:36

Boš popravil slikce, očitno si pozabil dati na "share".

Prenosnik, konzola, TV, PC upokojen.

bijoloh :: 13. avg 2016, 10:43

Se opravičujem za slikce, jih nisem pozabil dati pod "share", ampak ima dropbox neko omejitev za dnevni ogled in se je očitno prekoračila

Tukaj so na drugi strani naložene slikce:

Začel sem s HD Tune, ki kaže naslednje:

HD Tune health

HD Tune - quick scan

Nato sem zagnal še en program - Victoria, ki kaže sledeče:

Victoria HD test

Ter še Seatools 2.23 za DOS. Short test je javil kot PASSED:

Seatools short test PASSED

Seatools long test - zmrznil

WD DLG long test PASSED po zmrznjenju Seatools

Nato zaženem še HD Tune:

HD Tune - health po zmrznjenju Seatools

ter Victoria HD test:

Victoria HD test po zmrznjenju Seatools

In ker mi ni dalo miru kaj se dogaja, še enkrat zaženem Seatools 2.23 za DOS, kjer oba testa - short in long - gresta skozi brez problemov kot PASSED 8-O:

Seatools short - drugič PASSED

Seatools long - drugič passed

Upam, da so sedaj slikce vidne!
LP

Zgodovina sprememb…

spremenil: bijoloh (13. avg 2016 ob 10:47)

filip007 :: 13. avg 2016, 12:21

Jaz ne vidim nič čudnega, lahko pa probaš še z Linux Mint 18 s programom za formatiranje in tam izbereš Smart in lahko disk dodatno testiraš.

Prenosnik, konzola, TV, PC upokojen.

Spajky :: 14. avg 2016, 18:46

Čisto možno, da z diskom ni nič narobe, je pa s kabli, verjetno tudi z napajalnim delom, ali pa je kak kondenzator na matični slab; možnost je tudi bugast driver za disk ...

"Bluzim na forumu, torej sem !" (še živ ) ...

bijoloh :: 15. avg 2016, 09:58

Spajky je 14. avg 2016 ob 18:46 izjavil:

Čisto možno, da z diskom ni nič narobe, je pa s kabli, verjetno tudi z napajalnim delom, ali pa je kak kondenzator na matični slab; možnost je tudi bugast driver za disk ...

Driver bi jaz kar izključil, ker sta v sistemu dva ista diska in za drugega ne kaže, da bi bilo kaj narobe.
Kabli - ne vem mogoče, čeprav za podatkovni kabel se mi zdi malo verjetno, ker ni bil taknjen odkar so bili diski vgrajeni. Mogoče od napajanja, da se je napajalnik kaj "skuril"?
Kondenzatorji na plošči - bom preveril za vsak slučaj.

Mene pri vsem tem še najbolj moti to, da ko sem prvič zagnam WD DLG je po extensive preverjanju javil, da je našel slabe sektorje (ki jih takrat nisem poskušal "popraviti" s ponujeno opcijo, ker sem želel še prej s Seatools preveriti), potem Seatools po prvikratnem long preverjanju zmrzne pri 29%, ampak do takrat tudi izpiše, da je našel 7 napak (glej slikico). Po tem ko je Seatools zamrznil in sem naredil hard reset pa oba programa kažeta vse OK, edino števec napak pri smartmontools se je povečal...

Vredno ogleda ...

	Tema	Sporočila	Ogledi	Zadnje sporočilo
	Tema	Sporočila	Ogledi	Zadnje sporočilo
»	linux + dm-crypt luks težave z odklepom particije ob bootu gendale2018 Oddelek: Operacijski sistemi	14	906 (665)	gendale2018 23. feb 2019 22:10:58
»	a mi je crknu disk al ne gendale2018 Oddelek: Strojna oprema	13	1468 (909)	filip007 6. sep 2018 21:28:49
»	Po 2 PB zapisanih podatkov tretjina SSD-jev še deluje (strani: 1 2 ) McHusch Oddelek: Novice / Diski	65	27842 (21716)	Laybach 21. dec 2014 12:01:22
»	Disk umira WildChild Oddelek: Strojna oprema	27	1777 (1062)	Ramon dekers 29. mar 2011 19:43:53
»	[Linux - Grub] OS se mi noče naložiti Jst Oddelek: Operacijski sistemi	19	1620 (1335)	kriko1 25. avg 2007 10:36:22

Več podobnih tem

Zadnje novice

Zadnji članki

Išči:

Forum » Strojna oprema »
HDD napake - uveljavitev garancije?

HDD napake - uveljavitev garancije?