I was creating some directories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts 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 = 68, block_bitmap = 2228224 Aug 5 10:48:57 inet05 kernel: Aborting journal on device dm-4. Aug 5 10:48:57 inet05 kernel: ext3_abort called. Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Aug 5 10:48:57 inet05 kernel: Remounting filesystem read-only Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_reserve_inode_write: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in start_transaction: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_mkdir: Journal has aborted
What is going on? How do I fix it?
Regards, Jim
The favour of a direct response is requested as I am a diges subscriber.
Hello,
You probably have a bad disk under there (hda). Copy data of it as fast as you can, maybe you'll get some of it before it bites the dust completely. Of course if you have backups, just sit back and feel good ;-)
The thing that speaks most clearly for a hard error on disk level is: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=43072608, sector=43072608
good luck, Peter
On Friday 05 August 2005 16.54, James B. Byrne wrote:
I was creating some directories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts 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 = 68, block_bitmap = 2228224 Aug 5 10:48:57 inet05 kernel: Aborting journal on device dm-4. Aug 5 10:48:57 inet05 kernel: ext3_abort called. Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Aug 5 10:48:57 inet05 kernel: Remounting filesystem read-only Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_reserve_inode_write: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in start_transaction: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_mkdir: Journal has aborted
What is going on? How do I fix it?
Regards, Jim
The favour of a direct response is requested as I am a diges subscriber.
On 5 Aug 2005 at 18:35, Peter Kjellström wrote:
The thing that speaks most clearly for a hard error on disk level is: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=43072608, sector=43072608
Yes. I am afraid so. I am running e2fsck in non-destructive mode and have about a dozen or so bad blocks reported so far. The Ironic thing is that this is a new high capacity drive installed to host online backups of other servers. It is going back to the dealer once I complete the diagnostics.
Regards, Jim
It look like an hard drive issue not an LVM problem. Look at your DMA setting. Marc Picornell de Louvigny
On 8/5/05, Peter Kjellström cap@nsc.liu.se wrote:
Hello,
You probably have a bad disk under there (hda). Copy data of it as fast as you can, maybe you'll get some of it before it bites the dust completely. Of course if you have backups, just sit back and feel good ;-)
The thing that speaks most clearly for a hard error on disk level is: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=43072608, sector=43072608
good luck, Peter
On Friday 05 August 2005 16.54, James B. Byrne wrote:
I was creating some directories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts 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 = 68, block_bitmap = 2228224 Aug 5 10:48:57 inet05 kernel: Aborting journal on device dm-4. Aug 5 10:48:57 inet05 kernel: ext3_abort called. Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Aug 5 10:48:57 inet05 kernel: Remounting filesystem read-only Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_reserve_inode_write: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in start_transaction: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_mkdir: Journal has aborted
What is going on? How do I fix it?
Regards, Jim
The favour of a direct response is requested as I am a diges subscriber.
--
Peter Kjellström | National Supercomputer Centre | Sweden | http://www.nsc.liu.se
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 8/5/05, Marc Picornell marc.picornell@gmail.com wrote:
It look like an hard drive issue not an LVM problem.
Look at your DMA setting.
Marc Picornell de Louvigny
On 8/5/05, Peter Kjellström cap@nsc.liu.se wrote:
Hello,
You probably have a bad disk under there (hda). Copy data of it as fast as you can, maybe you'll get some of it before it bites the dust completely. Of course if you have backups, just sit back and feel good ;-)
The thing that speaks most clearly for a hard error on disk level is: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=43072608,
sector=43072608
good luck, Peter
On Friday 05 August 2005 16.54, James B. Byrne wrote:
I was creating some directories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts 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 = 68, block_bitmap = 2228224 Aug 5 10:48:57 inet05 kernel: Aborting journal on device dm-4. Aug 5 10:48:57 inet05 kernel: ext3_abort called. Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Aug 5 10:48:57 inet05 kernel: Remounting filesystem read-only Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_reserve_inode_write: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in start_transaction: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_mkdir: Journal has aborted
What is going on? How do I fix it?
Regards, Jim
What is the file system? I think that Knoppix Live CD has a File-system repair option. You can try that.
On 8/6/05, Marc Picornell marc.picornell@gmail.com wrote:
It look like an hard drive issue not an LVM problem.
Look at your DMA setting.
Our hard drive crashed just a two weeks ago and it was also running on Centos 4.1 with LVM (spewing out the same error messages as the OP had encountered). We also have a similar machine to the one whose HD crashed but it's running on FC3 without LVM. No problems on the FC3 setup so far.
I'm getting mixed responses when it comes to using LVM (and its relation to the recent crash). But just in case the DMA settings could be the cause of that failure, what do suggest we do so those things never happen again?
-
duffmckagan -
James B. Byrne -
Marc Picornell -
Matt Arnilo S. Baluyos (Mailing Lists) -
Peter Kjellström