search for: lbasect

...= 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=11435968 ide...

...as as to a fix, or to what the problem is? When I do a fsck and it marks the fs as clean I reboot and login the system. 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 b...

...e-positive. Any one can give me suggestions or hints? Thanks a lot. ...... Host: arc242 arc242: Apr 29 13:51:32 arc242 kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc242: Apr 29 13:51:32 arc242 kernel: hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=38613129, sector=38613064 arc242: Apr 29 13:51:36 arc242 kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc242: 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...

...quired 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 transaction: Jou...

...# ================================================= 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:13 server k...

...130ec9>] [<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 { UncorrectableErro...

...wing 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 = 68, blo...

i too am an idiot.. and request help here's the sccop i originally formatted the drive with 3 partitions and installed rh8 /boot / swap everything worked. my plan was to have this drive only be a data drive so i inatlled rh8 on another drive and mounted this one on /share so /share looked like /share /bin /sbin /mp3 /usr /etc /dev and so on so i deleted all the

I can not start my laptop anymore, due to what looks like a physical HD failure. During boot I get: hda: dma_intr: error=0x40 { Uncorrectable Error }, LBAsect=260112, sector 51144 and then JBD: Failed to read block at offset 5864 JBD: recovery failed EXT3-fs: error loading journal then the laptop is frozen. While I understand this drive will need a prompt replacement, I am trying to recover at least the data in the /home directory. Anyone can give...

...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 "fsck&...

...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 == find|l...

...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 badblocks check...

...ted 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 to mount i...

...at 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 since the...

...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 viper kernel:...

.../dev/hda: Model=ST3500320AS, FwRev=SD15, SerialNo= Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=off CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 AdvancedPM=no WriteCache=enabled Drive conforms to: unknown: * signifies the current active mode So from recommendati...

We run several RH7.2/7.3 servers & recently 2 of them, although still working fine, have started to show kjournald as generally using over 50% cpu% on 'top' - virtually continuously. Free cpu% generally less than 25% now! Both machines are also using software RAID5 EIDE ....... otherwise are standard server installs. Any info on what kjournald is & why it should have recently

Hello Folks, We have 2 (identical hardware) busy public 2U rack servers, both have several hundred users & peak email (for example) deliveries at 300/5min during the daytime. Both servers run RAID1 over 2 EIDE disk drives. One server is fine - it never has problems - it is running RH7.3 and CPU loads are normal. The other server has constant disk activity & kjournald at CPU load of

...-i output shows: # hdparm -i /dev/hda /dev/hda: Model=QEMU HARDDISK, FwRev=0.12.1, SerialNo=QM00001 Config={ Fixed } RawCHS=16383/16/63, TrkSize=32256, SectSize=512, ECCbytes=4 BuffType=DualPortCache, BuffSize=256kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=73400320 IORDY=yes, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=no Drive conforms to: ATA/ATAPI-5 published, ANSI NCITS 340-2000: * signifies the cu...

...l=HITACHI_DK23CA-30, FwRev=00H0A0G1, SerialNo=11BPWF Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=36477, SectSize=579, ECCbytes=4 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=58605120 IORDY=yes, tPIO={min:400,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5 AdvancedPM=yes: mode=0x80 (128) Drive Supports : ATA/ATAPI-5 T13 1321D revision 3 : ATA-1 ATA-2...