Rick Welykochy wrote:
> Steven Kerr wrote:
>
> > Thanks for those who responded.
> >
> > The fix was a bit of patience and Reading TFM
> >
> > e2fsck -b 16385 -c /dev/hdd1
> >
> > The -c did a bad block check, in frustration I left the system
> > overnight as it appeared just to hang... no disk activity for about 10
> > minutes.
> >
> > This morning it had finished (well dropped back to shell anyway), and
> > now the fs is mountable.
>
> Had a similar disk muckup the other day (found oue that cat had been
> sitting on the keyboard of a server tucked away in the corner ... somehow
> all the errant keystrokes crapped out the machine!) Both corrupted disks
> on the server recovered quite well and the keyboard has been removed :)
>
> This is YALSP (Yet Another Linux Selling Point): When these kinds of disk
> failures occur on Windows, unless you have a Ph.D. in Norton Utilities and
> have forked out $$$, chances are exactly 0% that you will recover your disk,
> since MS fails to provide any tools with its OS to save you from disaster.
>
> --
> Rick Welykochy || Praxis Services Pty Limited
Actually its not too hard in M$ either as long as you have patience. I once
recovered a 340Mb HDD in only a couple of days. Got almost all the files off OK
too ;-)
Stay well and happy
Heracles
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
