End_request I/o Error Dev Sda Sector Dd
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might i o error dev sda sector linux have Meta Discuss the workings and policies of this site About
End_request I/o Error Dev Sector
Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with
Blk_update_request I/o Error Dev Sector
us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only
Blk_update_request I/o Error Dev Fd0 Sector 0
takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top I/O error, dev sda, sector xxxxxxxxxx up vote 1 down vote favorite 2 Heading My machine has crashed couple of times this week. Ran smartmontools test and got this blk_update_request i/o error dev sr0 result: === START OF INFORMATION SECTION === Model Family: Fujitsu MJA BH Device Model: FUJITSU MJA2250BH G2 Serial Number: K94PT972B7RS LU WWN Device Id: 5 00000e 043bcbddd Firmware Version: 8919 User Capacity: 250,059,350,016 bytes [250 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3f Local Time is: Mon Feb 10 09:24:22 2014 IST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 118) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 783) seconds. Offline data collection capabilities: (0x51) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. No Offline surface scan supported.
1 #1 2013-05-18 23:14:08 gay Member Registered: 2012-12-16 Posts: 73 Harddisk problem: ata1.00: end_request: I/O error, dev sda, sector ... I got errors like the following:ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata1.00: irq_stat 0x40000008 ata1.00: end_request i/o error dev sda sector 0 failed command: READ FPDMA QUEUED ata1.00: cmd 60/08:00:68:33:32/00:00:31:00:00/40 tag 0 ncq 4096 in res blk_update_request i/o error dev sr0 sector 41/40:00:68:33:32/00:00:31:00:00/40 Emask 0x409 (media error)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://unix.stackexchange.com/questions/99553/does-a-bad-sector-indicate-a-failing-disk Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are o error voted up and rise to the top Does a bad sector indicate a failing disk? up vote 7 down vote favorite 5 My Ubuntu 13.10 system has been performing very poorly over the last day or so. Looking at the kernel logs, it appears that the <1yr old 3TB SATA disk is having issues with a particular sector: Nov 4 20:54:04 mediaserver kernel: [10893.039180] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 o error dev action 0x0 Nov 4 20:54:04 mediaserver kernel: [10893.039187] ata4.01: BMDMA stat 0x65 Nov 4 20:54:04 mediaserver kernel: [10893.039193] ata4.01: failed command: READ DMA EXT Nov 4 20:54:04 mediaserver kernel: [10893.039202] ata4.01: cmd 25/00:08:f8:3f:83/00:00:af:00:00/f0 tag 0 dma 4096 in Nov 4 20:54:04 mediaserver kernel: [10893.039202] res 51/40:00:f8:3f:83/40:00:af:00:00/10 Emask 0x9 (media error) Nov 4 20:54:04 mediaserver kernel: [10893.039207] ata4.01: status: { DRDY ERR } Nov 4 20:54:04 mediaserver kernel: [10893.039211] ata4.01: error: { UNC } Nov 4 20:54:04 mediaserver kernel: [10893.148527] ata4.00: configured for UDMA/133 Nov 4 20:54:04 mediaserver kernel: [10893.180322] ata4.01: configured for UDMA/133 Nov 4 20:54:04 mediaserver kernel: [10893.180345] sd 3:0:1:0: [sdc] Unhandled sense code Nov 4 20:54:04 mediaserver kernel: [10893.180349] sd 3:0:1:0: [sdc] Nov 4 20:54:04 mediaserver kernel: [10893.180353] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 4 20:54:04 mediaserver kernel: [10893.180356] sd 3:0:1:0: [sdc] Nov 4 20:54:04 mediaserver kernel: [10893.180359] Sense Key : Medium Error [current] [descriptor] Nov 4 20:54:04 mediaserver kernel: [10893.180371] Descriptor sense data with sense descriptors (in hex): Nov 4 20:54:04 mediaserver kernel: [10893.180373] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 4 20:54:04 mediaserver kernel: [10893.180384] af 83 3f f8 Nov 4 20:54:04 mediaserver kernel: [10893.180389] sd 3:0:1:0: [sdc] Nov 4 20:54:04 mediaserver kernel: [10893.180393] Add. Sense: Unrecovered read error - auto reallocate faile