{"id":293,"date":"2008-03-31T18:57:09","date_gmt":"2008-03-31T15:57:09","guid":{"rendered":"http:\/\/www.void.gr\/kargig\/blog\/?p=293"},"modified":"2008-03-31T18:57:29","modified_gmt":"2008-03-31T15:57:29","slug":"another-wd-failure-not-an-april-fools-joke","status":"publish","type":"post","link":"https:\/\/www.void.gr\/kargig\/blog\/2008\/03\/31\/another-wd-failure-not-an-april-fools-joke\/","title":{"rendered":"Another WD failure – not an april fool’s joke"},"content":{"rendered":"

In one of my previous posts (titled: It\u2019s official: Western Digital hates me and I hate them too)<\/a> I described how 3 Western Digital<\/a> drives I owned crashed in 2 months. <\/p>\n

Last week I left the city I live to go to Athens, Greece where fosscomm<\/a> was taking place. When I returned I checked the logs of my machines and in one of them I found this:<\/p>\n


\nhdi: lost interrupt
\nhdi: status error: status=0x51 { DriveReady SeekComplete Error }
\nhdi: status error: error=0x04 { DriveStatusError }
\nide: failed opcode was: unknown
\nhdi: no DRQ after issuing MULTWRITE_EXT
\nhdi: status error: status=0x51 { DriveReady SeekComplete Error }
\nhdi: status error: error=0x04 { DriveStatusError }
\nide: failed opcode was: unknown
\nhdi: no DRQ after issuing MULTWRITE_EXT
\nhdi: status error: status=0x51 { DriveReady SeekComplete Error }
\nhdi: status error: error=0x04 { DriveStatusError }
\nide: failed opcode was: unknown
\nhdi: no DRQ after issuing MULTWRITE_EXT
\nhdi: status error: status=0x51 { DriveReady SeekComplete Error }
\nhdi: status error: error=0x04 { DriveStatusError }
\nide: failed opcode was: unknown
\npdc202xx_new: Primary channel reset.
\nhdi: no DRQ after issuing MULTWRITE_EXT
\nide4: reset: success
\nhdi: dma_timer_expiry: dma status == 0x21
\nhdi: DMA timeout error
\nhdi: dma timeout error: status=0x80 { Busy }
\nide: failed opcode was: unknown
\nhdi: DMA disabled
\npdc202xx_new: Primary channel reset.
\nide4: reset: success
\nhdi: lost interrupt
\nmd: super_written gets error=-5, uptodate=0
\nraid5: Disk failure on hdi1, disabling device. Operation continuing on 5 devices
\n<\/code><\/p>\n

This the fourth crashed WD drive in 2 months! It’s not an april fool’s joke.. it’s still 31st of March..<\/p>\n


\nModel Family: Western Digital Caviar SE family
\nDevice Model: WDC WD2000JB-55GVA0
\nSerial Number: WD-WCALL1025118
\n<\/code><\/p>\n

Of course it’s out of warranty. Again.<\/p>\n

As Fuzz said, this whole thing must be a logic timebomb planted inside WD disks years ago to force us move to SSD drives<\/a>.<\/p>\n

I’m getting pretty tired of it though…<\/p>\n","protected":false},"excerpt":{"rendered":"

In one of my previous posts (titled: It\u2019s official: Western Digital hates me and I hate them too) I described how 3 Western Digital drives I owned crashed in 2 months. Last week I left the city I live to go to Athens, Greece where fosscomm was taking place. When I returned I checked the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"footnotes":""},"categories":[1,3],"tags":[],"class_list":["post-293","post","type-post","status-publish","format-standard","hentry","category-general","category-linux"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t