search for: uncorrectableerror

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7576/0/183, sector=1834800 end_request: I/O error, dev 16:02 (hdc), sector 1834800 hdc: dma_in...

...r_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy } ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11242764, high=0, low=11242764, sector=11242760 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11242760 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11435969, high=0, low=11435969, sector=1...

...s stock SMP kernel (required due to third party software). Both have come down with the same symptoms after having run fine for a number of months. The initial errors were these: kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=54666719, high=3, low=4335071, sector=61720 kernel: end_request: I/O error, dev 03:09 (hda), sector 61720 kernel: journal_bmap_Rsmp_41b34d97: journal block not found at offset 7180 on ide0(3,9) kernel: Aborting journal on device ide0(3,9). kernel: ext3_reserve_inode_write: aborting trans...

...cks [root at server /]# ================================================= Errors in messages: ================================================= Jul 20 04:09:13 server kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 20 04:09:13 server kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=526647391, high=31, low=6553695, sector=526647391 Jul 20 04:09:13 server kernel: end_request: I/O error, dev hdc, sector 526647391 Jul 20 04:09:13 server kernel: EXT3-fs error (device hdc1): ext3_get_inode_loc: unable to read inode block - inode=32915539, block=65830916 Jul 20 04:09:...

...c242: Apr 29 13:51:36 arc242 kernel: hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=38613129, sector=38613064 arc242: Apr 29 13:51:43 arc242 kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc242: Apr 29 13:51:43 arc242 kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=38613129, sector=38613064 arc242: Apr 29 13:51:43 arc242 kernel: end_request: I/O error, dev 03:41 (hdb), sector 38613064 arc242: Apr 29 13:51:49 arc242 kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc242: Apr 29 13:51:49 arc242 kernel: hdb: dma_int...

...;d081aa7b>] [<c0130ec9>] [<d081aa5c>] [<d080f777>] [<d081ab0f>] [<c0130fe1>] [<c0106dd3>] Code: 0f 0b 5b 5e 8b 54 24 24 f6 42 10 04 bb e2 ff ff ff b8 01 00 hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854, sector=163854 end_request: I/O error, dev 03:02 (hda), sector 163854 EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=20100, block=81927 hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x40 { Uncorr...

...ttempts give the following error: #mkdir: cannot create directory `xxxxx': Input/output error The contents of /var/log/messages shows this: Aug 5 10:48:57 inet05 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Aug 5 10:48:57 inet05 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=43072608, sector=43072608 Aug 5 10:48:57 inet05 kernel: ide: failed opcode was: unknown Aug 5 10:48:57 inet05 kernel: end_request: I/O error, dev hda, sector 43072608 Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4): read_block_bitmap: Cannot read block bitmap - block_group...

...don my ignorance about LINUX OS. I have installed LINUX 7.2 on IBM netfinity 4000R server. OS works fine for few days and start giving me this error message all of a sudden: "kernel: hda: dma_intr: status=0x51 { Driveready SeekComplete Error }" "kernel: hda: dma_intr: status=0x40 { UncorrectableError }, LBAsect=4944861, sector=4736016" "kernel: end_request: I/O error. dev 03:02 (hda), sector 4736016" SYSTEM details: Red hat 7.2(2.4.7-10) BIOS DATE: 5/17/00 Drive: /dev/hda(Geom: 2482/255/63) (mode: IBM-DLTA-307020) When I rebooted, system was not able to mount / I tried running...

...a while: How to obtain failed file (inode) from LBA section reported by Linux kernel? The following lines are a simple example: ... FCbox1: Nov 1 04:08:59 FCbox1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } FCbox1: Nov 1 04:08:59 FCbox1 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=165843413, high=9, low=14848469, sector=129761360 ... I'd like to know the tools|commands(&subcommands) used to do the translation below, any help are greatly appreciated. LBA section == ?? => logical sector in partition == ?? => block == ?? => inode in ext3 fileSystem...

All, Trying to figure out how to deal with, I assume, a dying disk that's unfortunately on / (ext3). Getting errors similar to: Dec 31 20:44:30 mybox kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 31 20:44:30 mybox kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=163423, high=0, low=163423, sector=163360 Dec 31 20:44:30 mybox kernel: end_request: I/O error, dev 03:41 (hdb), sector 163360 When I rebooted, the system threw me into a shell, to get me to "fix" things. So, I did an e2fsck -c -v /dev/hdb1 to attempt to fix things. The badb...

...an't even get started on this one. I have been looking at lde but don't think I know enough of what I'm doing to make that work. During the booting of the machine it throws the following errors: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=90895772, high=5, low=7009692, sector=0 end_request: I/O error, dev 03:03 (hda), sector 0 ... repeats 10 time kjournald starting. Commit interval 5 seconds I have commented the particular partition (/dev/hda3) out of the fstab file so it isn't even trying to mount it. When trying...

...orrupt fs? Will fsck tonight when a new power supply is going into the machine. Kernel: 2.4.17 Drive: Maxtor D740X-6L 80GB connected via HPT366 Feb 25 21:26:33 viper kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 25 21:26:33 viper kernel: hde: dma_intr: error=0x40 { UncorrectableError }, LBAsect=96469063, sector=96469000 Feb 25 21:26:33 viper kernel: end_request: I/O error, dev 21:01 (hde), sector 96469000 Feb 25 21:26:33 viper kernel: EXT3-fs error (device ide2(33,1)): read_inode_bitmap: Cannot read inode bitmap - block_group = 368, inode_bitmap = 12058625 Feb 25 21:26:33 vi...

...the reported disk failure. Let me explained the above with the following several example. scenario #1, a PATA hard disk failed.. Host: host1 ..... Jun 21 16:55:09 host1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jun 21 16:55:09 host1 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=234304234, high=13, low=16200426, sector=196487120 Jun 21 16:55:09 host1 kernel: end_request: I/O error, dev 03:0b (hda), sector 196487120 ..... The case #1, showed that /dev/hda failed in a simple way, but some stuff are not obvious: Q1: which failed partition? "dev 03:0b&quot...

...drives fail. I know that the disks fail because there are error messages like the following logged in /var/log/messages. ..... arc144: Apr 24 12:52:53 arc144 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc144: Apr 24 12:52:53 arc144 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=90186647, sector=52432952 arc144: Apr 24 12:52:53 arc144 kernel: end_request: I/O error, dev 03:0b (hda), sector 52432952 ..... My question is: How to figure out the file|directory occupying the failed sector|LBAsect? If I can figure it out then I can skipped the files|directories...

...e the syslog facility in an interesting way. The following example is a good one that can put misleading information in the logs. ------------------------------- #include <syslog.h> void main(void){ const char *mesg1 = "hda: read_intr: status=0x59 { SeekComplete DataRequest Error } { UncorrectableError }, CHS=157/2/9, sector=2826\0"; const char *mesg2 ="end_request: I/O error, dev 03:00, sector 2826\0"; const char *mesg3 = "EXT2-fs: group descriptors corrupted !\0"; openlog("kernel", LOG_CONS, LOG_KERN); syslog(LOG_ERR, mesg1); syslog(LOG_ERR, mesg2); sys...

Hi, yesterday my linux machine gave me some smartd errors so i checked the disk in another machine and it had defective sectors, I installed a new hard disk on the original machine. Today this is being reported in logwatch. I have a Maxtor (200gig) as hda, a cdrom as hdc and another hard disk that is used for storage as hdd. All plain IDE (not sata) --------------------- Kernel Begin

...the reported disk failure. Let me explained the above with the following several example. scenario #1, a PATA hard disk failed.. Host: host1 ..... Jun 21 16:55:09 host1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jun 21 16:55:09 host1 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=234304234, high=13, low=16200426, sector=196487120 Jun 21 16:55:09 host1 kernel: end_request: I/O error, dev 03:0b (hda), sector 196487120 ..... The case #1, showed that /dev/hda failed in a simple way, but some stuff are not obvious: Q1: which failed partition? "dev 03:0b&quot...

...em. But I still cannot load xwindows. below is some output from dmesg: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=81423, sector=81360 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=10223775, sector=10223712 end_request: I/O error, dev 03:41 (hdb), sector 10223712 EXT3-fs error (device ide0(3,65)): ext3_get_inode_loc: unable to read inode block - inode=636706, block=1277964 EXT3-fs error (device ide0(3,65)) in ext3_reserve_inode_write: IO failure EXT3-fs error (devi...