Error Device Ide0 3
ext3_readdir Date: Tue, 20
Fortigate Error 174
Nov 2001 20:02:39 +0100 Hi, yesterday I upgraded forticlient error my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and
Fortinet Support
had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device http://kb.fortinet.com/kb/documentLink.do?externalID=FD31857 ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have any of raid, acl or anything else, just a plain ide https://www.redhat.com/archives/ext3-users/2001-November/msg00379.html drive. So what should I do now ? Go to runlevel 1, umount /usr and run fsck ? Remounting rw doesn't work : root enterprise:/ #mount -o remount,rw /usr mount: block device /dev/hda9 is write-protected, mounting read-only and then in syslog: Nov 20 19:47:04 enterprise kernel: ext3_abort called. Nov 20 19:47:04 enterprise kernel: EXT3-fs abort (device ide0(3,9)): ext3_remount: Abort forced by user As I already said, the first time ever I had any problems since the very first versions. Thanks for your great work ! Cheers, Dirk Follow-Ups: Re: EXT3-fs error (device ide0(3,9)): ext3_readdir From: Andreas Dilger [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
is this drive dying? Date: Wed, 20 Nov 2002 06:20:48 -0500 (EST) On Mon, 18 Nov http://www.redhat.com/archives/psyche-list/2002-November/msg02059.html 2002, Peter Blomgren wrote: >Date: Mon, 18 Nov 2002 19:38:50 -0800 >From: Peter Blomgren >To: psyche-list redhat com >Content-Type: text/plain; charset=us-ascii >List-Id: Discussion of Red Hat Linux 8.0 (Psyche) >Subject: EXT3 errors -- is this drive dying? > >I'm seeing EXT3 errors: > >kernel: hda: dma_intr: status=0x51 { unable to DriveReady SeekComplete Error } >kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=81156390, sector=21233872 >kernel: end_request: I/O error, dev 03:06 (hda), sector 21233872 >kernel: EXT3-fs error (device ide0(3,6)): ext3_get_inode_loc: unable to read inode block - inode=1325185, block=2654234 >kernel: EXT3-fs error (device ide0(3,6)) in ext3_reserve_inode_write: IO failure >kernel: EXT3-fs error (device ide0(3,6)) in ext3_new_inode: IO failure unable to read >kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } >kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=81156390, sector=21233872 >kernel: end_request: I/O error, dev 03:06 (hda), sector 21233872 >kernel: EXT3-fs error (device ide0(3,6)): ext3_get_inode_loc: unable to read inode block - inode=1325186, block=2654234 >kernel: EXT3-fs error (device ide0(3,6)) in ext3_reserve_inode_write: IO failure >kernel: EXT3-fs error (device ide0(3,6)) in ext3_new_inode: IO failure > >Is this drive dying, or can it be saved? (Kernel 2.4.18-14) Your disk is toast. Pray that your backups are safe. :o/ The ext3 errors are due to disk corruption caused by the disk dying, and are not due to filesystem related problems. Replace your disk ASAP. -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer XFree86 maintainer Red Hat Inc. Follow-Ups: Re: [8.0] EXT3 errors -- is this drive dying? From: Peter Blomgren References: EXT3 errors -- is this drive dying? From: Peter Blomgren [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]