On Wed, Jun 07, 2000 at 03:19:25PM -0400, Jerry Human wrote:
> I sure hope you can help me with this one. Last week I installed a
> WD Caviar 102AA 10 gig hard drive and made four partitions: hdc1
> four gig, hdc2 100 meg, hdc3 three gig, and hdc4 three gig. I
> installed RH 6.2 on hdc1 and used hdc2 for the swap file. The drives
> hda and hdb are used for DOS and Win95.
>
> After a two days on boot up I get a prompt to enter root password
> for maintenance to run fsck manually. When I do, I get a series of
> errors for inodes 2 through 283692:
>
> Inode xxxxx has imagic flag set. Clear <y>?
> Inode xxxxx is in use, but has dtime set. Fix <y>?
> Inode xxxxx has illegal block(s). Clear <y>?
> Inode xxxxx ref count is x, should be x. Fix <y>?
> i_fsize for inode xxxxx (...) is xxx, should be xxx. Clear <y>?
> Inode xxxxx (...) has a bad mode (xxxxx). Clear <y>?
> i_frag for inode xxxxx (...) is xxx, should be xxx. Clear <y>?
> i_faddr for inode xxxxx (...) is xxx, should be xxx. Clear <y>?
>
> After ~ 40 minutes of holding the 'Y' key down, fsck reports the fs
> is currupted and is automatically restarting and I spend another ~40
> minutes holding the 'Y' key down. Upon completion, shut down and
> reboot. RH does start and prompts for login. After login, RH seems
> to work slugishly and some things don't work anymore. Checking the
> /lost + found dir reveals ~16 screens of numbers in various colors,
> dark blue, yellow, brown, etc. I assume these were put here by fsck.
>
> The first time this happened I just blew of RH and formatted the
> partition and installed again from CD. Now it's happened again.
>
> Can anyone tell me what is happening and perhaps why and possibly a
> path/ method to fixing it permanetly?
Don't want to be the bearer of bad news, but I recently had some
similar errors on a newish WD caviar, and now RH is running on a
Maxtor instead. Maybe mine weren't so bad. I could run several days,
maybe a week or two, before errors. I did several partial re-installs.
Blamed it on SMP for a while. IOW, I would suspect the drive. Things
you might try: try a different cable. Make sure cable is seated
properly. Use a memory testing program like memtest86 to check RAM.
Also, cpu and mboard stress testers like burnCPU and burnBX (not exact
names, I forget). If using hdparm to tweak, turn it all off. I did all
this, and got it down to the drive. Zero errors on the Maxtor now (up
21 days). I also have another WD which is not doing this. The WD in
question, replaced a WD that died abruptly well before its time. I am
a little soured on WD at this point. I hope this is not it for you.
--
Hal B
[EMAIL PROTECTED]
--
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
