[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Is this ext3 or bad drive sectors problem?



Thanks for the reply. In single user mode, I ran e2fsck -y /dev/hda7 and it
conveyed me message
Pass 1: Checking inodes, block, and sizes
Error reading block 5684 (Attempt to read block from filesystem
resulted in short read) while doing inode scan.  Ignore error<y>?

Pass 2: Checking directory structure
Pass 3: xxxx
Pass 4: xxxx
/: 17466/130560 files (0.3% non-contigous) 87516/522081 blocks

I did poweroff and system rebooted fine. To make sure system is all fine, I
rebooted again and started getting problem of:
Checking root filesystem
/ contains a file system with errors, check forced.
Error reading block 5684 (Attempt to read block from filesystem
resulted in short read) while doing inode scan.

/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
     (i.e., without -a or -p options)


*** An error occured during the file system check.
*** Droping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup):

I will appreciate for your response...

BTW: I have purchased new Maxtor drive too but wanted to give a shot with my
old drive before I install new drive.
Does anybody know what will be the best way to install this new drive? Can I
make use of my so called corrupted drive seems like?
Thanks,
Lav

----- Original Message -----
From: "Stephen C. Tweedie" <sct redhat com>
To: "Lav Aneja" <lavaneja hotmail com>
Cc: <ext3-users redhat com>
Sent: Thursday, March 28, 2002 6:29 AM
Subject: Re: Is this ext3 or bad drive sectors problem?


> Hi,
>
> On Wed, Mar 27, 2002 at 11:41:51PM -0600, Lav Aneja wrote:
> > I am resending this message again as after getting various suggestions,
I reinstalled RED Hat 7.2 LINUX after formatting with option "fix bad
sector" as well as installing boot into 1st available sector instead of MBR
and everything worked fine for 4-5 days and then again while installing
qpopper, I got the error message as
> >
> > iat1 Kernel: Assertion failure in journal_bmap_R2ac88d7a() at
journal.c:602: "ret!=0"
> >
> > System halted after above message. I rebooted my system but no success
as system conveyed message
> > "I9990301 Disk Failure or disk reset failed"
>
> Your disk is dying.  Replace it.
>
> > FYI: My system has crashed 5-6 times and I always ended up in
re-installing Linux. Please Please Please suggest how to fix this issue...Is
there any patch I have to apply...
>
> No patch can cure such a hardware fault.
>
> --Stephen
>





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]