l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Jun 24 09:00

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] In Denial About These Hard Drive Problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] In Denial About These Hard Drive Problems

Quoting msimons@moria.simons-clan.com (msimons@moria.simons-clan.com):

>   I should provide more of an explanation... I am not saying all IBM
> drives are junk.  I do still recommend people with Deskstar 75GXP, 60GXP, 
> and 120GXP models find replacements and use them instead.

Just to clarify, I absolutely agreed with that recommendation.  I was
just saying that there have been lots of _other_ IBM Deskstar and
Ultrastar models, not members of those series, that have been just fine.

> As easy as Redhat and 2000 may be to load and configure...
>   If you consider either the time or the hassle trade-off,
>     of reinstalling and reconfiguring 
>       both operating systems and associated application suites, 
>     and later reloading the data files 
>      (those which were remembered at backup time)...
>   then I am certain that the method used was far superior.
> ;)

I can't speak to Win2k, having little relevant experience.  However
"reconfiguring" for the Linux side could be nothing more that migrating
and unpacking a tarball of /etc.

> Two points:
> - The filesystems were unstable: 
>   they were marked as unclean and e2fsck could not run over the partitions
>   due to bad blocks.  Mounting them could have been possible with -fr, but
>   ext3 tries to replay the journal even in readonly mode... and I didn't
>   want to risk more corruption.  I didn't try to fight it (*).
> - "cp" places more stress on the drive, and handles errors badly.

Yeah, good points.  I usually aim to get things off at the _first_ signs 
of drive trouble -- which from evidence cited would have been a lot earlier.

Doing a "dd" of the partition and piping it over ssh to another box
might have been useful.

>   When I arrived at the machine it was booting into Linux and a prior 
> unsuccessful shutdown had flagged the unclean bit on the root filesystem.
> The e2fsck failed due to bad blocks... and it dumped us into the 'root 
> password: please, repair the filesystem prompt".  The root filesystem had 
> been mounted in read-only mode...

Really bad juju.  I think I'd have called in an exorcist.

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.