abclinuxu.cz AbcLinuxu.cz itbiz.cz ITBiz.cz HDmag.cz HDmag.cz abcprace.cz AbcPráce.cz
AbcLinuxu hledá autory!
Inzerujte na AbcPráce.cz od 950 Kč
Rozšířené hledání
Přihlášení | Registrace
×
napište » Zprávičky
inzerujte » Pracovní nabídky

    Nizozemská vláda chce kvůli AI zrušit 15 % míst ve státní správě
    dnes 12:44 | IT novinky

    Nizozemská vláda ve snaze šetřit a zvyšovat efektivitu s využitím umělé inteligence (AI) hodlá zrušit asi 25.000 pracovních míst ve státní správě. Cílem je postupně dosáhnout ročních úspor až 3,5 miliardy eur (85,2 miliardy Kč). Na konci loňského roku ve státní správě pracovalo rekordních 160.000 lidí. „Nemůžeme pokračovat v tom, co jsme dělali dosud,“ uvedl státní tajemník pro efektivní fungování vlády Eric van den Burg. „Proto

    … více »
    Ladislav Hagara | Komentářů: 2
    Fotoaparát CAIM1
    dnes 12:00 | IT novinky

    Příspěvek na blogu PRUSA 3D představuje fotoaparát CAIM1 (Counter Artificial Intelligence Machine 1). Uměle vytvořený obsah je každým dnem těžší rozeznat od skutečných záběrů či fotografií, což podrývá důvěryhodnost žurnalistiky, archivních materiálů i každodenní tvorby obsahu. Fotoaparát CAIM1 byl vyvinut právě k tomu, aby ověřoval původ fotografií a videí přímo během jejich pořizování. Uvnitř fotoaparátu se nachází hardwarová Web3 peněženka se zabezpečovacím čipem Tropic Square TROPIC01.

    Ladislav Hagara | Komentářů: 0
    OpenShot 4.1
    dnes 00:11 | Nová verze

    Jonathan Thomas oznámil vydání nové verze 4.1 video editoru OpenShot (Wikipedie). Zdrojové kódy OpenShotu jsou k dispozici na GitHubu. Ke stažení je i balíček ve formátu AppImage. Stačí jej stáhnout, nastavit právo na spouštění a spustit.

    Ladislav Hagara | Komentářů: 0
    EVPN - jak bránit únosu MAC adresy
    včera 23:33 | Zajímavý článek

    Při běžné migraci virtuálního stroje mezi hypervizory se jeho MAC adresa přesune na jiný leaf switch. EVPN tuto změnu distribuuje pomocí BGP Type-2 route a MAC mobility sequence number. Problém nastává, pokud útočník podvrhne zdrojovou MAC adresu jiného zařízení. Leaf může změnu interpretovat jako legitimní přesun MAC a rozšířit ji přes BGP do celé fabric. Výsledkem může být přesměrování provozu určeného původnímu zařízení. Autor článku rozebírá možnosti detekce pomocí sledování MAC moves, BGP route reflektorů a kontroly na přístupové vrstvě.

    vencour | Komentářů: 0
    Enlightenment 0.28.0 a Enlightenment Foundation Libraries (EFL) 1.29
    včera 15:11 | Nová verze

    Vývojáři desktopového prostředí Enlightenment (Wikipedie) a souvisejících knihoven Enlightenment Foundation Libraries (EFL) vydali nové verze. Enlightenment byl vydán ve verzi 0.28.0 a Enlightenment Foundation Libraries ve verzi 1.29.

    Ladislav Hagara | Komentářů: 3
    Některé odpovědi modelu GLM-5.3 obsahovaly části dat z předchozích požadavků jiných zákazníků
    včera 13:55 | Zajímavý článek

    Cloudflare zjistil, že některé odpovědi modelu GLM-5.3 obsahovaly části dat z předchozích požadavků jiných zákazníků. Příčinou byla kombinace chybné konfigurace a chyby v inference enginu SGLang. Model podporoval kontextové okno 1 048 576 tokenů, ale GPU KV cache pool měl kapacitu pouze 681 280 tokenů. Při překročení kapacity docházelo k nesprávnému zpracování odmítnutého požadavku. Decode část systému následně pracovala se starými

    … více »
    vencour | Komentářů: 1
    Novinky v Knot Resolver 6
    včera 13:00 | Zajímavý článek

    Vývojáři Knot Resolver vysvětlují, jak změnili rozhodování o tom, které DNS záznamy ponechat v cache a které odstranit. Článek obsahuje skutečná měření: devět hodin DNS provozu při 2 000 QPS, srovnání cache o velikosti 25 MB a 40 GB a také porovnání s BIND 9, kromě algoritmů obsahuje konkrétní doporučení pro konfiguraci a diagnostiku.

    vencour | Komentářů: 0
    Hackeři zaútočili na Binance, největší kryptoměnovou burzu světa
    30.10. 13:44 | IT novinky

    Největší kryptoměnová burza světa Binance se stala terčem útoku, při kterém podvodníci odcizili během několika minut kryptoměny v hodnotě přibližně 6,3 miliardy dolarů. Jedná se o největší kryptoměnovou krádež v historii, přibližně čtyřikrát větší než loňský útok na burzu Bybit. Binance se podařilo ve spolupráci s partnery zmrazit aspoň aktiva v hodnotě zhruba 3 miliard dolarů a slíbila, že veškeré ztráty pokryje z vlastních prostředků.

    Ladislav Hagara | Komentářů: 16
    Kritická zranitelnost v Linux kernelu s CVSS 9.8
    30.10. 02:16 | Bezpečnostní upozornění

    Zranitelnost CVE-2026-98432 s CVSS 9.8 odhalila AI od společnosti Anthropic. Jedná se o kritickou chybu v implementaci MPTCP (multipath TCP). Debian vydal patche 16.10. a 22.10., ale např. Ubuntu je zatím bez opravy. Více informací na The Hacker News.

    Max | Komentářů: 20
    Greenie Rally - nová slovenská bezplatná hra
    29.10. 23:22 | Zajímavý software

    Na Slovensku vznikla úplne nová rally hra, ktorá je zadarmo a funguje vo Windowse, Linuxe či na Macu. Greenie Rally má viac ako 50 tratí a vozidiel, šampionáty či turnaje. Má retro feeling a imituje automobilové hry z prelomu tisícročí. Vyskúšate prejsť všetky mapy na Škode 130RS?

    Stanislav Hoferek | Komentářů: 13
    Centrum | Napsat | Starší
    navrhněte » Anketa
    Které desktopové prostředí na Linuxu používáte?
     (9%)
     (7%)
     (4%)
     (20%)
     (30%)
     (9%)
     (5%)
     (2%)
     (14%)
     (20%)
    Celkem 2961 hlasů
     Komentářů: 34, poslední 26.10. 08:24
    Rozcestník
    AbcLinuxu
    AbcLinuxu:/ Poradna / Linuxová poradna / Chybne disky, radic alebo kable?
    Štítky: bez, copyright, data, disk, error, firmware, For, chyba, chyby, Internet, mirror, net, POWER, problém, řadič, řadiče, SATA, Seagate, server, smart, standard, status, Suspend, tag, test, vikend, web

    Dotaz: Chybne disky, radic alebo kable?

    13.5.2013 17:40 GeorgeWH | skóre: 42
    Chybne disky, radic alebo kable?
    Přečteno: 859×
    zdravim. cez vikend sa na 2 rovnakych diskoch (RAID1) objavili vadne sektory. zaujimave na tom je to, ze sa chyba vyskytla v uplne rovnaky cas. vadne sektory som skusal "precitat" pomocou hdparm --read-sector , nehodilo ziadnu chybu. na /dev/sde momentalne bezi longtest, zatial bez chyby. odchadzaju disky, alebo moze byt problem inde? doska uz bola raz reklamovana, nefungovali PS/2 porty. 
    May 11 14:46:31 server kernel: [6556958.684175] ata5.00: exception Emask 0x10 SAct 0x1f SErr 0x810000 action 0xe frozen
May 11 14:46:31 server kernel: [6556958.684238] ata5.00: irq_stat 0x00400000, PHY RDY changed
May 11 14:46:31 server kernel: [6556958.684275] ata5: SError: { PHYRdyChg LinkSeq }
May 11 14:46:31 server kernel: [6556958.684293] ata6.00: exception Emask 0x10 SAct 0x1f SErr 0x810000 action 0xe frozen
May 11 14:46:31 server kernel: [6556958.684298] ata6.00: irq_stat 0x00400000, PHY RDY changed
May 11 14:46:31 server kernel: [6556958.684302] ata6: SError: { PHYRdyChg LinkSeq }
May 11 14:46:31 server kernel: [6556958.684306] ata6.00: failed command: WRITE FPDMA QUEUED
May 11 14:46:31 server kernel: [6556958.684313] ata6.00: cmd 61/c0:00:57:c3:21/02:00:05:00:00/40 tag 0 ncq 360448 out
May 11 14:46:31 server kernel: [6556958.684315]          res 40/00:18:17:c6:21/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
May 11 14:46:31 server kernel: [6556958.684318] ata6.00: status: { DRDY }
May 11 14:46:31 server kernel: [6556958.684321] ata6.00: failed command: WRITE FPDMA QUEUED
May 11 14:46:31 server kernel: [6556958.684327] ata6.00: cmd 61/c8:08:cf:bc:21/03:00:05:00:00/40 tag 1 ncq 495616 out
May 11 14:46:31 server kernel: [6556958.684329]          res 40/00:18:17:c6:21/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
May 11 14:46:31 server kernel: [6556958.684332] ata6.00: status: { DRDY }
May 11 14:46:31 server kernel: [6556958.684334] ata6.00: failed command: WRITE FPDMA QUEUED
May 11 14:46:31 server kernel: [6556958.684340] ata6.00: cmd 61/10:10:97:c0:21/02:00:05:00:00/40 tag 2 ncq 270336 out
May 11 14:46:31 server kernel: [6556958.684341]          res 40/00:18:17:c6:21/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
May 11 14:46:31 server kernel: [6556958.684344] ata6.00: status: { DRDY }
May 11 14:46:31 server kernel: [6556958.684347] ata6.00: failed command: WRITE FPDMA QUEUED
May 11 14:46:31 server kernel: [6556958.684353] ata6.00: cmd 61/60:18:17:c6:21/01:00:05:00:00/40 tag 3 ncq 180224 out
May 11 14:46:31 server kernel: [6556958.684354]          res 40/00:18:17:c6:21/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
May 11 14:46:31 server kernel: [6556958.684357] ata6.00: status: { DRDY }
May 11 14:46:31 server kernel: [6556958.684360] ata6.00: failed command: WRITE FPDMA QUEUED
May 11 14:46:31 server kernel: [6556958.684365] ata6.00: cmd 61/b0:20:a7:c2:21/00:00:05:00:00/40 tag 4 ncq 90112 out
May 11 14:46:31 server kernel: [6556958.684367]          res 40/00:18:17:c6:21/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
May 11 14:46:31 server kernel: [6556958.684370] ata6.00: status: { DRDY }
May 11 14:46:31 server kernel: [6556958.684379] ata6: hard resetting link
May 11 14:46:31 server kernel: [6556958.688006] ata5.00: cmd 61/10:18:97:c0:21/02:00:05:00:00/40 tag 3 ncq 270336 out
May 11 14:46:31 server kernel: [6556958.688006] ata5.00: cmd 61/60:08:17:c6:21/01:00:05:00:00/40 tag 1 ncq 180224 out
May 11 14:46:31 server kernel: [6556958.688006] ata5.00: cmd 61/b0:20:a7:c2:21/00:00:05:00:00/40 tag 4 ncq 90112 out
May 11 14:46:31 server kernel: [6556958.688006] ata5.00: cmd 61/c0:00:57:c3:21/02:00:05:00:00/40 tag 0 ncq 360448 out
May 11 14:46:31 server kernel: [6556958.688006] ata5.00: cmd 61/c8:10:cf:bc:21/03:00:05:00:00/40 tag 2 ncq 495616 out
May 11 14:46:31 server kernel: [6556958.688006] ata5.00: failed command: WRITE FPDMA QUEUED
May 11 14:46:31 server kernel: [6556958.688006] ata5.00: status: { DRDY }
May 11 14:46:31 server kernel: [6556958.688006] ata5: hard resetting link
May 11 14:46:31 server kernel: [6556958.688006]          res 40/00:00:57:c3:21/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
May 11 14:46:37 server kernel: [6556964.052283] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 11 14:46:37 server kernel: [6556964.052310] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 11 14:46:37 server kernel: [6556964.232633] ata6.00: configured for UDMA/133
May 11 14:46:37 server kernel: [6556964.232830] ata5.00: configured for UDMA/133

May 11 15:11:36 server kernel: [6558463.110687] ata6.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
May 11 15:11:36 server kernel: [6558463.110730] ata6.00: irq_stat 0x40000008
May 11 15:11:36 server kernel: [6558463.110765] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:11:36 server kernel: [6558463.110805] ata6.00: cmd 60/00:10:ff:b7:21/01:00:05:00:00/40 tag 2 ncq 131072 in
May 11 15:11:36 server kernel: [6558463.110806]          res 41/40:00:7d:b8:21/00:01:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:11:36 server kernel: [6558463.110921] ata6.00: status: { DRDY ERR }
May 11 15:11:36 server kernel: [6558463.110954] ata6.00: error: { UNC }
May 11 15:11:36 server kernel: [6558463.133811] ata6.00: configured for UDMA/133
May 11 15:11:40 server kernel: [6558466.869250] ata6.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
May 11 15:11:40 server kernel: [6558466.869293] ata6.00: irq_stat 0x40000008
May 11 15:11:40 server kernel: [6558466.869328] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:11:40 server kernel: [6558466.869368] ata6.00: cmd 60/00:08:ff:b7:21/01:00:05:00:00/40 tag 1 ncq 131072 in
May 11 15:11:40 server kernel: [6558466.869369]          res 41/40:00:7d:b8:21/00:01:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:11:40 server kernel: [6558466.869485] ata6.00: status: { DRDY ERR }
May 11 15:11:40 server kernel: [6558466.869517] ata6.00: error: { UNC }
May 11 15:11:40 server kernel: [6558466.979340] ata6.00: configured for UDMA/133
May 11 15:11:43 server kernel: [6558470.768038] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:11:43 server kernel: [6558470.768081] ata6.00: irq_stat 0x40000008
May 11 15:11:43 server kernel: [6558470.768115] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:11:43 server kernel: [6558470.768154] ata6.00: cmd 60/00:00:ff:b7:21/01:00:05:00:00/40 tag 0 ncq 131072 in
May 11 15:11:43 server kernel: [6558470.768155]          res 41/40:00:7d:b8:21/00:01:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:11:43 server kernel: [6558470.768268] ata6.00: status: { DRDY ERR }
May 11 15:11:43 server kernel: [6558470.768300] ata6.00: error: { UNC }
May 11 15:11:44 server kernel: [6558470.835835] ata6.00: configured for UDMA/133
May 11 15:11:47 server kernel: [6558473.838943] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:11:47 server kernel: [6558473.838985] ata6.00: irq_stat 0x40000008
May 11 15:11:47 server kernel: [6558473.839019] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:11:47 server kernel: [6558473.839058] ata6.00: cmd 60/00:00:ff:b7:21/01:00:05:00:00/40 tag 0 ncq 131072 in
May 11 15:11:47 server kernel: [6558473.839059]          res 41/40:00:7d:b8:21/00:01:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:11:47 server kernel: [6558473.839172] ata6.00: status: { DRDY ERR }
May 11 15:11:47 server kernel: [6558473.839204] ata6.00: error: { UNC }
May 11 15:11:47 server kernel: [6558473.862020] ata6.00: configured for UDMA/133
May 11 15:11:50 server kernel: [6558476.829157] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:11:50 server kernel: [6558476.829200] ata6.00: irq_stat 0x40000008
May 11 15:11:50 server kernel: [6558476.829234] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:11:50 server kernel: [6558476.829273] ata6.00: cmd 60/00:00:ff:b7:21/01:00:05:00:00/40 tag 0 ncq 131072 in
May 11 15:11:50 server kernel: [6558476.829274]          res 41/40:00:7d:b8:21/00:01:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:11:50 server kernel: [6558476.829387] ata6.00: status: { DRDY ERR }
May 11 15:11:50 server kernel: [6558476.829419] ata6.00: error: { UNC }
May 11 15:11:50 server kernel: [6558476.852291] ata6.00: configured for UDMA/133
May 11 15:11:53 server kernel: [6558480.594038] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:11:53 server kernel: [6558480.594080] ata6.00: irq_stat 0x40000008
May 11 15:11:53 server kernel: [6558480.594114] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:11:53 server kernel: [6558480.594153] ata6.00: cmd 60/00:00:ff:b7:21/01:00:05:00:00/40 tag 0 ncq 131072 in
May 11 15:11:53 server kernel: [6558480.594155]          res 41/40:00:7d:b8:21/00:01:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:11:53 server kernel: [6558480.594268] ata6.00: status: { DRDY ERR }
May 11 15:11:53 server kernel: [6558480.594300] ata6.00: error: { UNC }
May 11 15:11:53 server kernel: [6558480.617179] ata6.00: configured for UDMA/133
May 11 15:11:53 server kernel: [6558480.617242] sd 5:0:0:0: [sdf] Unhandled sense code
May 11 15:11:53 server kernel: [6558480.617245] sd 5:0:0:0: [sdf] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 15:11:53 server kernel: [6558480.617250] sd 5:0:0:0: [sdf] Sense Key : Medium Error [current] [descriptor]
May 11 15:11:53 server kernel: [6558480.617258] Descriptor sense data with sense descriptors (in hex):
May 11 15:11:53 server kernel: [6558480.617262]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
May 11 15:11:53 server kernel: [6558480.617281]         05 21 b8 7d
May 11 15:11:53 server kernel: [6558480.617289] sd 5:0:0:0: [sdf] Add. Sense: Unrecovered read error - auto reallocate failed
May 11 15:11:53 server kernel: [6558480.617296] sd 5:0:0:0: [sdf] CDB: Read(10): 28 00 05 21 b7 ff 00 01 00 00
May 11 15:11:53 server kernel: [6558480.617314] end_request: I/O error, dev sdf, sector 86095997
May 11 15:11:53 server kernel: [6558480.617352] raid1: sdf1: rescheduling sector 86095896
May 11 15:11:53 server kernel: [6558480.617394] raid1: sdf1: rescheduling sector 86095984
May 11 15:11:57 server kernel: [6558484.583784] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:11:57 server kernel: [6558484.583827] ata6.00: irq_stat 0x40000008
May 11 15:11:57 server kernel: [6558484.583861] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:11:57 server kernel: [6558484.583899] ata6.00: cmd 60/08:00:77:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:11:57 server kernel: [6558484.583901]          res 41/40:08:7d:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:11:57 server kernel: [6558484.584014] ata6.00: status: { DRDY ERR }
May 11 15:11:57 server kernel: [6558484.584046] ata6.00: error: { UNC }
May 11 15:11:57 server kernel: [6558484.606881] ata6.00: configured for UDMA/133
May 11 15:12:00 server kernel: [6558487.565694] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:00 server kernel: [6558487.565737] ata6.00: irq_stat 0x40000008
May 11 15:12:00 server kernel: [6558487.565771] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:12:00 server kernel: [6558487.565810] ata6.00: cmd 60/08:00:77:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:00 server kernel: [6558487.565811]          res 41/40:08:7d:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:00 server kernel: [6558487.565924] ata6.00: status: { DRDY ERR }
May 11 15:12:00 server kernel: [6558487.565956] ata6.00: error: { UNC }
May 11 15:12:00 server kernel: [6558487.588830] ata6.00: configured for UDMA/133
May 11 15:12:03 server kernel: [6558490.564283] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:03 server kernel: [6558490.564326] ata6.00: irq_stat 0x40000008
May 11 15:12:03 server kernel: [6558490.564360] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:12:03 server kernel: [6558490.564399] ata6.00: cmd 60/08:00:77:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:03 server kernel: [6558490.564401]          res 41/40:08:7d:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:03 server kernel: [6558490.564514] ata6.00: status: { DRDY ERR }
May 11 15:12:03 server kernel: [6558490.564546] ata6.00: error: { UNC }
May 11 15:12:03 server kernel: [6558490.587407] ata6.00: configured for UDMA/133
May 11 15:12:07 server kernel: [6558494.404134] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:07 server kernel: [6558494.404177] ata6.00: irq_stat 0x40000008
May 11 15:12:07 server kernel: [6558494.404211] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:12:07 server kernel: [6558494.404249] ata6.00: cmd 60/08:00:77:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:07 server kernel: [6558494.404251]          res 41/40:08:7d:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:07 server kernel: [6558494.404364] ata6.00: status: { DRDY ERR }
May 11 15:12:07 server kernel: [6558494.404396] ata6.00: error: { UNC }
May 11 15:12:07 server kernel: [6558494.427221] ata6.00: configured for UDMA/133
May 11 15:12:11 server kernel: [6558498.152336] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:11 server kernel: [6558498.152378] ata6.00: irq_stat 0x40000008
May 11 15:12:11 server kernel: [6558498.152412] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:12:11 server kernel: [6558498.152451] ata6.00: cmd 60/08:00:77:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:11 server kernel: [6558498.152453]          res 41/40:08:7d:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:11 server kernel: [6558498.152565] ata6.00: status: { DRDY ERR }
May 11 15:12:11 server kernel: [6558498.152598] ata6.00: error: { UNC }
May 11 15:12:11 server kernel: [6558498.175469] ata6.00: configured for UDMA/133
May 11 15:12:14 server kernel: [6558501.159235] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:14 server kernel: [6558501.159278] ata6.00: irq_stat 0x40000008
May 11 15:12:14 server kernel: [6558501.159311] ata6.00: failed command: READ FPDMA QUEUED
May 11 15:12:14 server kernel: [6558501.159350] ata6.00: cmd 60/08:00:77:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:14 server kernel: [6558501.159352]          res 41/40:08:7d:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:14 server kernel: [6558501.159464] ata6.00: status: { DRDY ERR }
May 11 15:12:14 server kernel: [6558501.159497] ata6.00: error: { UNC }
May 11 15:12:14 server kernel: [6558501.182364] ata6.00: configured for UDMA/133
May 11 15:12:14 server kernel: [6558501.182378] sd 5:0:0:0: [sdf] Unhandled sense code
May 11 15:12:14 server kernel: [6558501.182381] sd 5:0:0:0: [sdf] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 15:12:14 server kernel: [6558501.182386] sd 5:0:0:0: [sdf] Sense Key : Medium Error [current] [descriptor]
May 11 15:12:14 server kernel: [6558501.182394] Descriptor sense data with sense descriptors (in hex):
May 11 15:12:14 server kernel: [6558501.182398]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
May 11 15:12:14 server kernel: [6558501.182417]         05 21 b8 7d
May 11 15:12:14 server kernel: [6558501.182425] sd 5:0:0:0: [sdf] Add. Sense: Unrecovered read error - auto reallocate failed
May 11 15:12:14 server kernel: [6558501.182432] sd 5:0:0:0: [sdf] CDB: Read(10): 28 00 05 21 b8 77 00 00 08 00
May 11 15:12:14 server kernel: [6558501.182450] end_request: I/O error, dev sdf, sector 86095997
May 11 15:12:14 server kernel: [6558501.218079] raid1:md5: read error corrected (8 sectors at 86095928 on sdf1)
May 11 15:12:14 server kernel: [6558501.225122] raid1: sde1: redirecting sector 86095896 to another mirror
May 11 15:12:14 server kernel: [6558501.230327] raid1: sde1: redirecting sector 86095984 to another mirror
May 11 15:12:18 server kernel: [6558505.030334] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:18 server kernel: [6558505.030374] ata5.00: irq_stat 0x40000008
May 11 15:12:18 server kernel: [6558505.030407] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:18 server kernel: [6558505.030446] ata5.00: cmd 60/50:00:af:b8:21/00:00:05:00:00/40 tag 0 ncq 40960 in
May 11 15:12:18 server kernel: [6558505.030448]          res 41/40:50:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:18 server kernel: [6558505.030560] ata5.00: status: { DRDY ERR }
May 11 15:12:18 server kernel: [6558505.030593] ata5.00: error: { UNC }
May 11 15:12:18 server kernel: [6558505.053260] ata5.00: configured for UDMA/133
May 11 15:12:22 server kernel: [6558509.411546] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:22 server kernel: [6558509.411588] ata5.00: irq_stat 0x40000008
May 11 15:12:22 server kernel: [6558509.411623] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:22 server kernel: [6558509.411662] ata5.00: cmd 60/50:00:af:b8:21/00:00:05:00:00/40 tag 0 ncq 40960 in
May 11 15:12:22 server kernel: [6558509.411663]          res 41/40:50:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:22 server kernel: [6558509.411777] ata5.00: status: { DRDY ERR }
May 11 15:12:22 server kernel: [6558509.411809] ata5.00: error: { UNC }
May 11 15:12:22 server kernel: [6558509.434487] ata5.00: configured for UDMA/133
May 11 15:12:25 server kernel: [6558512.376822] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:25 server kernel: [6558512.376863] ata5.00: irq_stat 0x40000008
May 11 15:12:25 server kernel: [6558512.376897] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:25 server kernel: [6558512.376936] ata5.00: cmd 60/50:00:af:b8:21/00:00:05:00:00/40 tag 0 ncq 40960 in
May 11 15:12:25 server kernel: [6558512.376937]          res 41/40:50:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:25 server kernel: [6558512.380803] ata5.00: error: { UNC }
May 11 15:12:25 server kernel: [6558512.380803] ata5.00: status: { DRDY ERR }
May 11 15:12:25 server kernel: [6558512.399748] ata5.00: configured for UDMA/133
May 11 15:12:28 server kernel: [6558515.375376] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:28 server kernel: [6558515.375419] ata5.00: irq_stat 0x40000008
May 11 15:12:28 server kernel: [6558515.375453] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:28 server kernel: [6558515.375493] ata5.00: cmd 60/50:00:af:b8:21/00:00:05:00:00/40 tag 0 ncq 40960 in
May 11 15:12:28 server kernel: [6558515.375495]          res 41/40:50:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:28 server kernel: [6558515.375609] ata5.00: status: { DRDY ERR }
May 11 15:12:28 server kernel: [6558515.375642] ata5.00: error: { UNC }
May 11 15:12:28 server kernel: [6558515.398347] ata5.00: configured for UDMA/133
May 11 15:12:31 server kernel: [6558518.382289] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:31 server kernel: [6558518.382331] ata5.00: irq_stat 0x40000008
May 11 15:12:31 server kernel: [6558518.382366] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:31 server kernel: [6558518.382404] ata5.00: cmd 60/50:00:af:b8:21/00:00:05:00:00/40 tag 0 ncq 40960 in
May 11 15:12:31 server kernel: [6558518.382406]          res 41/40:50:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:31 server kernel: [6558518.382519] ata5.00: status: { DRDY ERR }
May 11 15:12:31 server kernel: [6558518.382551] ata5.00: error: { UNC }
May 11 15:12:31 server kernel: [6558518.405207] ata5.00: configured for UDMA/133
May 11 15:12:34 server kernel: [6558521.405841] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:34 server kernel: [6558521.405881] ata5.00: irq_stat 0x40000008
May 11 15:12:34 server kernel: [6558521.405915] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:34 server kernel: [6558521.405953] ata5.00: cmd 60/50:00:af:b8:21/00:00:05:00:00/40 tag 0 ncq 40960 in
May 11 15:12:34 server kernel: [6558521.405955]          res 41/40:50:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:34 server kernel: [6558521.406068] ata5.00: status: { DRDY ERR }
May 11 15:12:34 server kernel: [6558521.406100] ata5.00: error: { UNC }
May 11 15:12:34 server kernel: [6558521.428797] ata5.00: configured for UDMA/133
May 11 15:12:34 server kernel: [6558521.428812] sd 4:0:0:0: [sde] Unhandled sense code
May 11 15:12:34 server kernel: [6558521.428815] sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 15:12:34 server kernel: [6558521.428820] sd 4:0:0:0: [sde] Sense Key : Medium Error [current] [descriptor]
May 11 15:12:34 server kernel: [6558521.428828] Descriptor sense data with sense descriptors (in hex):
May 11 15:12:34 server kernel: [6558521.428832]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
May 11 15:12:34 server kernel: [6558521.428852]         05 21 b8 f0
May 11 15:12:34 server kernel: [6558521.428859] sd 4:0:0:0: [sde] Add. Sense: Unrecovered read error - auto reallocate failed
May 11 15:12:34 server kernel: [6558521.428866] sd 4:0:0:0: [sde] CDB: Read(10): 28 00 05 21 b8 af 00 00 50 00
May 11 15:12:34 server kernel: [6558521.428884] end_request: I/O error, dev sde, sector 86096112
May 11 15:12:34 server kernel: [6558521.428923] raid1: sde1: rescheduling sector 86095984
May 11 15:12:37 server kernel: [6558524.479410] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:37 server kernel: [6558524.479452] ata5.00: irq_stat 0x40000008
May 11 15:12:37 server kernel: [6558524.479486] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:37 server kernel: [6558524.479526] ata5.00: cmd 60/08:00:ef:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:37 server kernel: [6558524.479527]          res 41/40:08:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:37 server kernel: [6558524.479640] ata5.00: status: { DRDY ERR }
May 11 15:12:37 server kernel: [6558524.479672] ata5.00: error: { UNC }
May 11 15:12:37 server kernel: [6558524.501987] ata5.00: configured for UDMA/133
May 11 15:12:40 server kernel: [6558527.461286] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:40 server kernel: [6558527.461328] ata5.00: irq_stat 0x40000008
May 11 15:12:40 server kernel: [6558527.461362] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:40 server kernel: [6558527.461401] ata5.00: cmd 60/08:00:ef:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:40 server kernel: [6558527.461402]          res 41/40:08:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:40 server kernel: [6558527.461515] ata5.00: status: { DRDY ERR }
May 11 15:12:40 server kernel: [6558527.461547] ata5.00: error: { UNC }
May 11 15:12:40 server kernel: [6558527.483927] ata5.00: configured for UDMA/133
May 11 15:12:43 server kernel: [6558530.501479] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:43 server kernel: [6558530.501521] ata5.00: irq_stat 0x40000008
May 11 15:12:43 server kernel: [6558530.501555] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:43 server kernel: [6558530.501594] ata5.00: cmd 60/08:00:ef:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:43 server kernel: [6558530.501595]          res 41/40:08:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:43 server kernel: [6558530.501708] ata5.00: status: { DRDY ERR }
May 11 15:12:43 server kernel: [6558530.501740] ata5.00: error: { UNC }
May 11 15:12:43 server kernel: [6558530.524114] ata5.00: configured for UDMA/133
May 11 15:12:46 server kernel: [6558533.491741] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:46 server kernel: [6558533.491784] ata5.00: irq_stat 0x40000008
May 11 15:12:46 server kernel: [6558533.491818] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:46 server kernel: [6558533.491856] ata5.00: cmd 60/08:00:ef:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:46 server kernel: [6558533.491858]          res 41/40:08:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:46 server kernel: [6558533.491971] ata5.00: status: { DRDY ERR }
May 11 15:12:46 server kernel: [6558533.492004] ata5.00: error: { UNC }
May 11 15:12:46 server kernel: [6558533.514355] ata5.00: configured for UDMA/133
May 11 15:12:49 server kernel: [6558536.515272] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:49 server kernel: [6558536.515315] ata5.00: irq_stat 0x40000008
May 11 15:12:49 server kernel: [6558536.515349] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:49 server kernel: [6558536.515387] ata5.00: cmd 60/08:00:ef:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:49 server kernel: [6558536.515389]          res 41/40:08:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:49 server kernel: [6558536.515502] ata5.00: status: { DRDY ERR }
May 11 15:12:49 server kernel: [6558536.515534] ata5.00: error: { UNC }
May 11 15:12:49 server kernel: [6558536.537957] ata5.00: configured for UDMA/133
May 11 15:12:52 server kernel: [6558539.522192] ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
May 11 15:12:52 server kernel: [6558539.522235] ata5.00: irq_stat 0x40000008
May 11 15:12:52 server kernel: [6558539.522269] ata5.00: failed command: READ FPDMA QUEUED
May 11 15:12:52 server kernel: [6558539.522308] ata5.00: cmd 60/08:00:ef:b8:21/00:00:05:00:00/40 tag 0 ncq 4096 in
May 11 15:12:52 server kernel: [6558539.522309]          res 41/40:08:f0:b8:21/00:00:05:00:00/00 Emask 0x409 (media error) <F>
May 11 15:12:52 server kernel: [6558539.522422] ata5.00: status: { DRDY ERR }
May 11 15:12:52 server kernel: [6558539.522454] ata5.00: error: { UNC }
May 11 15:12:52 server kernel: [6558539.544836] ata5.00: configured for UDMA/133
May 11 15:12:52 server kernel: [6558539.544852] sd 4:0:0:0: [sde] Unhandled sense code
May 11 15:12:52 server kernel: [6558539.544855] sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 11 15:12:52 server kernel: [6558539.544860] sd 4:0:0:0: [sde] Sense Key : Medium Error [current] [descriptor]
May 11 15:12:52 server kernel: [6558539.544867] Descriptor sense data with sense descriptors (in hex):
May 11 15:12:52 server kernel: [6558539.544871]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
May 11 15:12:52 server kernel: [6558539.544891]         05 21 b8 f0
May 11 15:12:52 server kernel: [6558539.544899] sd 4:0:0:0: [sde] Add. Sense: Unrecovered read error - auto reallocate failed
May 11 15:12:52 server kernel: [6558539.544906] sd 4:0:0:0: [sde] CDB: Read(10): 28 00 05 21 b8 ef 00 00 08 00
May 11 15:12:52 server kernel: [6558539.544924] end_request: I/O error, dev sde, sector 86096112
May 11 15:12:52 server kernel: [6558539.545969] raid1:md5: read error corrected (8 sectors at 86096048 on sde1)
May 11 15:12:52 server kernel: [6558539.569732] raid1: sdf1: redirecting sector 86095984 to another mirror
May 11 15:22:49 server smartd[2606]: Device: /dev/sde [SAT], ATA error count increased from 0 to 12
May 11 15:22:49 server smartd[2606]: Device: /dev/sdf [SAT], ATA error count increased from 0 to 12

    # smartctl -a /dev/sde
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda ES.2
Device Model:     ST3750330NS
Serial Number:    XXX
Firmware Version: SN05
User Capacity:    750,156,374,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon May 13 17:19:06 2013 CEST

==> WARNING: There are known problems with these drives,
see the following Seagate web pages:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207963

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:      ( 242)	Self-test routine in progress...
					20% of test remaining.
Total time to complete Offline 
data collection: 		 ( 634) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 178) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) 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: 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   070   063   044    Pre-fail  Always       -       97476645
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       41
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       44276420
  9 Power_On_Hours          0x0032   083   083   000    Old_age   Always       -       15361
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   037   020    Old_age   Always       -       41
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   088   088   000    Old_age   Always       -       12
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   085   085   000    Old_age   Always       -       15
190 Airflow_Temperature_Cel 0x0022   068   064   045    Old_age   Always       -       32 (Lifetime Min/Max 31/35)
194 Temperature_Celsius     0x0022   032   040   000    Old_age   Always       -       32 (0 18 0 0)
195 Hardware_ECC_Recovered  0x001a   036   026   000    Old_age   Always       -       97476645
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

SMART Error Log Version: 1
ATA Error Count: 12 (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 12 occurred at disk power-on lifetime: 15311 hours (637 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 00 f0 b8 21 05

  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 ef b8 21 45 00      00:26:15.032  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:26:15.031  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:26:15.030  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:26:15.030  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:26:15.029  READ NATIVE MAX ADDRESS EXT

Error 11 occurred at disk power-on lifetime: 15311 hours (637 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 00 f0 b8 21 05

  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 ef b8 21 45 00      00:26:12.008  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:26:12.008  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:26:12.006  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:26:12.006  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:26:12.006  READ NATIVE MAX ADDRESS EXT

Error 10 occurred at disk power-on lifetime: 15311 hours (637 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 00 f0 b8 21 05

  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 ef b8 21 45 00      00:26:09.018  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:26:09.018  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:26:09.016  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:26:09.016  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:26:09.015  READ NATIVE MAX ADDRESS EXT

Error 9 occurred at disk power-on lifetime: 15311 hours (637 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 00 f0 b8 21 05

  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 ef b8 21 45 00      00:26:05.978  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:26:05.978  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:26:05.976  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:26:05.976  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:26:05.975  READ NATIVE MAX ADDRESS EXT

Error 8 occurred at disk power-on lifetime: 15311 hours (637 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 00 f0 b8 21 05

  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 ef b8 21 45 00      00:26:02.996  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:26:02.996  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:26:02.994  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:26:02.994  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:26:02.993  READ NATIVE MAX ADDRESS EXT

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 20%     15361         -
# 2  Extended offline    Completed without error       00%     15329         -
# 3  Extended offline    Completed without error       00%     15161         -
# 4  Extended offline    Completed without error       00%     14993         -
# 5  Extended offline    Completed without error       00%     14824         -
# 6  Extended offline    Completed without error       00%     14656         -
# 7  Extended offline    Completed without error       00%     14488         -
# 8  Extended offline    Completed without error       00%     14321         -
# 9  Extended offline    Completed without error       00%     14154         -
#10  Extended offline    Completed without error       00%     13986         -
#11  Extended offline    Completed without error       00%     13818         -
#12  Extended offline    Completed without error       00%     13650         -
#13  Extended offline    Completed without error       00%     13493         -
#14  Extended offline    Completed without error       00%     13346         -
#15  Extended offline    Completed without error       00%     13178         -
#16  Extended offline    Completed without error       00%     13010         -
#17  Extended offline    Completed without error       00%     12842         -
#18  Extended offline    Completed without error       00%     12674         -
#19  Extended offline    Completed without error       00%     12506         -
#20  Extended offline    Completed without error       00%     12338         -
#21  Extended offline    Completed without error       00%     12170         -

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.

    # smartctl -a /dev/sdf
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda ES.2
Device Model:     ST3750330NS
Serial Number:    XXX
Firmware Version: SN05
User Capacity:    750,156,374,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon May 13 17:35:05 2013 CEST

==> WARNING: There are known problems with these drives,
see the following Seagate web pages:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207963

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: 		 ( 642) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 173) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) 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: 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   068   060   044    Pre-fail  Always       -       212763482
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       90
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   075   060   030    Pre-fail  Always       -       17302664910
  9 Power_On_Hours          0x0032   060   060   000    Old_age   Always       -       35569
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   037   020    Old_age   Always       -       90
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   088   088   000    Old_age   Always       -       12
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   071   060   045    Old_age   Always       -       29 (Lifetime Min/Max 29/32)
194 Temperature_Celsius     0x0022   029   040   000    Old_age   Always       -       29 (0 19 0 0)
195 Hardware_ECC_Recovered  0x001a   040   027   000    Old_age   Always       -       212763482
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

SMART Error Log Version: 1
ATA Error Count: 12 (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 12 occurred at disk power-on lifetime: 35519 hours (1479 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 00 7d b8 21 05

  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 77 b8 21 45 00      00:25:36.652  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:25:36.652  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:25:36.650  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:25:36.650  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:25:36.649  READ NATIVE MAX ADDRESS EXT

Error 11 occurred at disk power-on lifetime: 35519 hours (1479 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 00 7d b8 21 05

  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 77 b8 21 45 00      00:25:32.904  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:25:32.904  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:25:32.902  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:25:32.902  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:25:32.901  READ NATIVE MAX ADDRESS EXT

Error 10 occurred at disk power-on lifetime: 35519 hours (1479 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 00 7d b8 21 05

  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 77 b8 21 45 00      00:25:29.064  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:25:29.064  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:25:29.062  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:25:29.062  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:25:29.061  READ NATIVE MAX ADDRESS EXT

Error 9 occurred at disk power-on lifetime: 35519 hours (1479 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 00 7d b8 21 05

  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 77 b8 21 45 00      00:25:26.066  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:25:26.065  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:25:26.064  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:25:26.063  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:25:26.063  READ NATIVE MAX ADDRESS EXT

Error 8 occurred at disk power-on lifetime: 35519 hours (1479 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 00 7d b8 21 05

  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 77 b8 21 45 00      00:25:23.084  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:25:23.084  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:25:23.082  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:25:23.081  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:25:23.081  READ NATIVE MAX ADDRESS EXT

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%     35537         -
# 2  Extended offline    Completed without error       00%     35369         -
# 3  Extended offline    Completed without error       00%     35201         -
# 4  Extended offline    Completed without error       00%     35032         -
# 5  Extended offline    Completed without error       00%     34864         -
# 6  Extended offline    Completed without error       00%     34696         -
# 7  Extended offline    Completed without error       00%     34529         -
# 8  Extended offline    Completed without error       00%     34362         -
# 9  Extended offline    Completed without error       00%     34194         -
#10  Extended offline    Completed without error       00%     34026         -
#11  Extended offline    Completed without error       00%     33858         -
#12  Extended offline    Completed without error       00%     33701         -
#13  Extended offline    Completed without error       00%     33554         -
#14  Extended offline    Completed without error       00%     33386         -
#15  Extended offline    Completed without error       00%     33218         -
#16  Extended offline    Completed without error       00%     33050         -
#17  Extended offline    Completed without error       00%     32882         -
#18  Extended offline    Completed without error       00%     32714         -
#19  Extended offline    Completed without error       00%     32546         -
#20  Extended offline    Completed without error       00%     32378         -
#21  Extended offline    Completed without error       00%     32210         -

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.
    Nástroje: Začni sledovat (0) ?Zašle upozornění na váš email při vložení nového komentáře.

    Odpovědi

    13.5.2013 18:10 ewew | skóre: 40 | blog: ewewov_blog
    Rozbalit Rozbalit vše Re: Chybne disky, radic alebo kable?

    ==> WARNING: There are known problems with these drives, see the following Seagate web pages: http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931 http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207963

    V smartctl je vypis o problemovosti daného disku. V prvom rade by si mal odzálohovať obsah diskov bez ohľadu na chybu.

    Root v linuxe : "Root povedal, linux vykona."
    13.5.2013 22:40 GeorgeWH | skóre: 42
    Rozbalit Rozbalit vše Re: Chybne disky, radic alebo kable?
    skusal si tie linky aj otvorit? asi nie... ocakavam skor rady od ludi, co s tym maju prakticku skusenost.
    13.5.2013 23:20 ewew | skóre: 40 | blog: ewewov_blog
    Rozbalit Rozbalit vše Re: Chybne disky, radic alebo kable?

    Neskôr som zistil,že linky nefungujú. Vieš o tom, že chyba na jednom disku sa prejavi na druhom. RAID 1 je zrkadlenie. Existuje možnosť, že disky sú poškodené a pri ďalšom reštarte nemusia nabehnúť. Myslím, že je lepšie mať nejakú zálohu v prípade problému. Nevylučujem problém s doskou, radičom a káblami. Kľudne to môže byť náhodna chyba. Sú pre teba tie data cenné ?

    Root v linuxe : "Root povedal, linux vykona."

    Založit nové vlákno • Nahoru

    Tiskni Sdílej: Linkuj Jaggni to Vybrali.sme.sk Google Del.icio.us Facebook

    Píšeme jinde
    ISSN 1214-1267   www.czech-server.cz
    Redakce | Inzerce | Podmínky použití | Osobní údaje
    © 1999-2015 Nitemedia s. r. o. Všechna práva vyhrazena.