Hi,
> On Tue, Apr 21, 2009 at 1:22 PM, Jochen Schulz <m...@well-adjusted.de> >
> wrote:
> Your problem is most probably unrelated to your building a kernel. Take
> a look into /var/log/syslog and/or dmesg output. You will probably find
> messages about hard disk errors. Post them here if you have trouble
> interpreting them.
Strangely this starts off when I try to run make-kpkg. I don´t see any
error messages in the dmesg log, till I run this command. After I run
this, I see the following error messages in the dmesg log. I am not
sure what does that point to...i.e. how it can be fixed.
[ 629.127668] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 629.127668] hdc: dma_intr: error=0x40 { UncorrectableError },
LBAsect=1841587, sector=1841583
[ 629.127668] ide: failed opcode was: unknown
[ 629.127668] end_request: I/O error, dev hdc, sector 1841583
[ 629.127668] EXT3-fs error (device hdc1): ext3_get_inode_loc: unable
to read inode block - inode=58202, block=230190
[ 629.127668] Aborting journal on device hdc1.
[ 629.128573] ext3_abort called.
[ 629.128587] EXT3-fs error (device hdc1): ext3_journal_start_sb:
Detected aborted journal
[ 629.128599] Remounting filesystem read-only
[ 629.129010] Remounting filesystem read-only
[ 629.971851] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 629.971851] hdc: dma_intr: error=0x40 { UncorrectableError },
LBAsect=1841587, sector=1841583
[ 629.971851] ide: failed opcode was: unknown
[ 629.971851] end_request: I/O error, dev hdc, sector 1841583
[ 629.971851] EXT3-fs error (device hdc1): ext3_get_inode_loc: unable
to read inode block - inode=58199, block=230190
[ 630.980013] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 630.980013] hdc: dma_intr: error=0x40 { UncorrectableError },
LBAsect=1841587, sector=1841583
[ 630.980013] ide: failed opcode was: unknown
[ 630.980013] end_request: I/O error, dev hdc, sector 1841583
[ 630.980013] EXT3-fs error (device hdc1): ext3_get_inode_loc: unable
to read inode block - inode=58193, block=230190
[ 632.136021] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 632.136021] hdc: dma_intr: error=0x40 { UncorrectableError },
LBAsect=1841587, sector=1841583
[ 632.136021] ide: failed opcode was: unknown
[ 632.136021] end_request: I/O error, dev hdc, sector 1841583
[ 632.136021] EXT3-fs error (device hdc1): ext3_get_inode_loc: unable
to read inode block - inode=58195, block=230190
[ 633.295745] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 633.295771] hdc: dma_intr: error=0x40 { UncorrectableError },
LBAsect=1841587, sector=1841583
[ 633.295795] ide: failed opcode was: unknown
[ 633.295809] end_request: I/O error, dev hdc, sector 1841583
[ 633.295921] EXT3-fs error (device hdc1): ext3_get_inode_loc: unable
to read inode block - inode=58194, block=230190
[ 634.475282] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost
synchronization, throwing 3 bytes away.
[ 634.515097] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 634.515097] hdc: dma_intr: error=0x40 { UncorrectableError },
LBAsect=1841587, sector=1841583
[ 634.515097] ide: failed opcode was: unknown
[ 634.515097] end_request: I/O error, dev hdc, sector 1841583
[ 634.515097] EXT3-fs error (device hdc1): ext3_get_inode_loc: unable
to read inode block - inode=58206, block=230190
>
> Posting the output of 'smartctl -a /dev/hda' (from smartmontools, insert
> your hard drive device name) might help as well.
>
OK. I will try doing that as well....since the current file system is
readonly, I can´t install anything till I reboot :(. BTW is there a
way to remount the root filesystem as rw after it has encountered this
error and becomes ro ?
Thanks a lot for your help,
Regards,
Divick
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
