teda vlastne SEAGATE Barracuda 7200.11 500GB ST3500320AS
mal som jeden z tychto, teda kym nechcipol... a na reklamacnom sa tvarili ze nejsom prvy ktory ide s presne tymto hdd (akurat som tam vtedy stretol chalana, co tam bol s presne tym istym hdd, tymi istymi popismi poruchy)
no a zaujimalo by ma kolko ludom sa to stalo celkovo, rad by som si vytvoril nejaku percentaz poruchovosti
otvorim tuto starsiu temu.. chcem sa spytat co to bol vlastne za problem pri tomto disku, stacilo upgradovat fw?
Snake uz svoj podpis ma davno zmazany a bojim sa, ze presne tento disk zacina mat priznaky svojho koncu pomaly, ale isto (btw ma uz tri roky)..
Desktop: Intel Core i5 11400F - CoolerMaster Hyper 212+ GIGABYTE B560M AORUS PRO AX Asus ROG Strix RX6650XT 8GB ADATA XPG 512GB + 2TB WD Green 16GB ADATA XPG GAMMIX D30 3200MHz CL16 SilentiumPC Supremo M2 Gold 550W V2 SilentiumPC Regnum RG4TF Frosty White TG LENOVO G32QC-10 Logitech Z-4e Logitech MX Keys + Razer Deathadder V2 Mini + SteelPad QCK mini
LAN NB: Asus XDAB AMD Athlon X2 Dual-Core QL-65 2,1GHz ATI Radeon HD 4570 512MB 32gb SSD 4GB DDR2 Razer Krait + SteelPad QCK mini
Mobile: Iphone 12 mini 128gb + Iphone 8 64gb + iPad 2021 64gb + Apple Watch 7 45mm
TV: LG OLED48A1
za to že už daná téma neexistuje sa poďakuj adminovi cruxovi
Problém bol nasledový (nechce sa mi to prekladať, v pôvodnej téme to bolo pekne popísané, holt už neni medzi nami):
This condition was introduced by a firmware issue that sets the drive event log to an invalid location causing the drive to become inaccessible.
The firmware issue is that the end boundary of the event log circular buffer (320) was set incorrectly. During Event Log initialization, the boundary condition that defines the end of the Event Log is off by one. During power up, if the Event Log counter is at entry 320, or a multiple of (320 + x*256), and if a particular data pattern (dependent on the type of tester used during the drive manufacturing test process) had been present in the reserved-area system tracks when the drive's reserved-area file system was created during manufacturing, firmware will increment the Event Log pointer past the end of the event log data structure. This error is detected and results in an "Assert Failure", which causes the drive to hang as a failsafe measure. When the drive enters failsafe further update s to the counter become impossible and the condition will remain through subsequent power cycles. The problem only arises if a power cycle initialization occurs when the Event Log is at 320 or some multiple of 256 thereafter. Once a drive is in this state, there is no path to resolve/recover existing failed drives without Seagate technical intervention. For a drive to be susceptible to this issue, it must have both the firmware that contains the issue and have been tested through the specific manufacturing process.
ok, tak uz je tam SD1A.. spravilo to rychlo, bez straty dat.. preco som to uz neurobil skor (zvyknem na vsetkom cca raz za rok , aj castejsie updatovat fw)..
on takto "hapruje"(aj ked v beznej praci sa to este nicim neprejavilo, pozorujem to "iba" v SMARTE) uz cca rok a pol, sa divim, ze funguje uz stvrty rok
Desktop: Intel Core i5 11400F - CoolerMaster Hyper 212+ GIGABYTE B560M AORUS PRO AX Asus ROG Strix RX6650XT 8GB ADATA XPG 512GB + 2TB WD Green 16GB ADATA XPG GAMMIX D30 3200MHz CL16 SilentiumPC Supremo M2 Gold 550W V2 SilentiumPC Regnum RG4TF Frosty White TG LENOVO G32QC-10 Logitech Z-4e Logitech MX Keys + Razer Deathadder V2 Mini + SteelPad QCK mini
LAN NB: Asus XDAB AMD Athlon X2 Dual-Core QL-65 2,1GHz ATI Radeon HD 4570 512MB 32gb SSD 4GB DDR2 Razer Krait + SteelPad QCK mini
Mobile: Iphone 12 mini 128gb + Iphone 8 64gb + iPad 2021 64gb + Apple Watch 7 45mm
TV: LG OLED48A1
co je vlastne ten Spin Retry Count, citam ze to je nieco ako pocet opakovanych pokusov o roztocenie platni, cize nieco ako ked sa pokusa opakovane po neuspesnom roztoceni roztacat ich znova a tym naznacuje ze tolko krat to uz musel zopakovat (tych 6 znaci, ze uz 6krat nenabehol hdd na prvy krat a musel to opakovat/viac krat/?).. odchadza na nom elektronika napr.?
pokial som spravne pochopil, tak to moze to chybne roztocenie opakovat este 91 krat v pohode a az potom by som sa mal zacat vaznejsie obavat o hdd?
a ked to tak prepocitavam, ma dokonca len ~ 3hodiny denne (sa mi to nezda, vsak som pri pc skoro cele dni, sice to robi asi ten intrak, takto zraza priemer dolu:D)..
Desktop: Intel Core i5 11400F - CoolerMaster Hyper 212+ GIGABYTE B560M AORUS PRO AX Asus ROG Strix RX6650XT 8GB ADATA XPG 512GB + 2TB WD Green 16GB ADATA XPG GAMMIX D30 3200MHz CL16 SilentiumPC Supremo M2 Gold 550W V2 SilentiumPC Regnum RG4TF Frosty White TG LENOVO G32QC-10 Logitech Z-4e Logitech MX Keys + Razer Deathadder V2 Mini + SteelPad QCK mini
LAN NB: Asus XDAB AMD Athlon X2 Dual-Core QL-65 2,1GHz ATI Radeon HD 4570 512MB 32gb SSD 4GB DDR2 Razer Krait + SteelPad QCK mini
Mobile: Iphone 12 mini 128gb + Iphone 8 64gb + iPad 2021 64gb + Apple Watch 7 45mm
TV: LG OLED48A1
je to už staršia téma, ale napíšem sem,, aj bratranec má tento hdd, a z ničoho nič mu prestalo ísť PC, naskočí len BIOS, skúšal som ako ste tu písali aktualizovať FW cez moj pc, namontovali sme jeho hdd do mojho, ale jak sme to tam pridali, tak nenašlo moje pc jeho seagate a ani moj hdd ako disk ho nes.rie len údaje na nom, fotky a tak, dá sa to zachrániť?
a ešte druhá vec, skontroloval som moje disky cez hdd tune pro, a píše mi na vačšom disku kde mám fotky hudbu film atd, (disk na dáta) ten spin,, vid na fotke
(znamená to že mám nejaký problém s hdd? je na čase kúpiť nový a presunúť naň veci? alebo mám tiež aktualizovať svoje disky a ten warning tam zmizne?
win mám na 160gb WD a dáta na 1TB samsung