Data recovery

[Shawn Tayler]

On Tue, 28 Dec 2004 19:09:30 -0800 "Net Llama!" <netllama at linux-sxs.org>
exclaimed:

> On 12/28/2004 06:54 PM, Shawn Tayler wrote:
> > On Tue, 28 Dec 2004 08:47:50 -0800 "Net Llama!"
> > <netllama at linux-sxs.org> exclaimed:
> > 
> > 
> >>On 12/28/2004 06:12 AM, Shawn Tayler wrote:
> >>
> >>>Hi,
> >>>
> >>>On a side to the previous email.  I recently had some read errors on a
> >>>Quantum Atlas 10K HD, 80G.  It was unfortunately the /usr partition. 
> >I>>copied all the data off and installed a new drive.  restoring the
> >data>> and reinstalling most of the packages seems to have fixed the
> >problem,>> but
> >>>I am feeling that there is something left that is not quite right. 
> >I'd>
> >>Something left where?  What leads you to believe this?
> >>
> >>
> >>>like to spin up the failed unit and see what files are effected.  Is
> >>>there a utility around that would assist in this?
> >>
> >>Assist in what?
> > 
> > 
> > Sorry,
> > 
> > I was hurried and rather short on details.  The drive in question was
> > my workstations /usr.  I started getting sense errors and quickly
> > copied everything off of it to another drive.  I then replaced the bad
> > drive with one of the same type, brand new.  I copied everything back
> > but some apps, namely lpr, X, bash were behaving strangely.  I did a
> > reinstall of all packages that had been updated through
> > swaret(slackware 10 system).  And have cleared the obvious problems.
> > 
> > What I want to do is mount the bad drive on another box and run a
> > read-only test to see what files on the drive are affected.  This would
> > help in figuring out what other application should be rebuilt or
> > reinstalled.
> 
> Ahhh.  I'd guess that running some kind of filesystem check would do the 
> job effectively.  Which filesystem are you using?
> 


EXT3