Well, the PC hasn't been slow, but I have had a lot of hangups where I'd have to do a
physical reboot with the evil button. I just don't really understand why I'd be
having problems, because the disk isn't that old. <sigh> I guess I will head over to
Memory Express on Thursday (payday) to pick up a new drive.
Frustrating, because all my job search stuff is on there :O(
Any idea how I would go about "ghosting" the drive? I've heard of this, but never
seen it done before.
Thanks,
Brad Camroux
----- Original Message -----
From: Jason M Moran <[EMAIL PROTECTED]>
Date: Tuesday, October 12, 2004 10:17 am
Subject: RE: [clug-talk] Please Help (Urgent!)
> To me, It does sound like the drive is pooched. Sorry. Has the PC been
> running kinda slow lately? If you have another PC or at least
> another HD it
> may be possible to Ghost the drive to get some or all of the data
> off of it.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf
> Of Brad Camroux
> Sent: Tuesday, October 12, 2004 9:55 AM
> To: [EMAIL PROTECTED]
> Subject: [clug-talk] Please Help (Urgent!)
> Importance: High
>
> Hi all,
>
> I have a rather severe and urgent problem. I'm not certain, but I
> think one
> of my hard drives has crashed (possibly physically, in which case
> I'm pretty
> certain that I have no hope). I am unable to boot to my normal
> screen - the
> best I can do is the root maintenance shell after e2fsck fails.
>
> In this shell, I have managed to discern that it is /dev/hdb that
> is having
> trouble. Curiously, I am able to get logical output from
> /dev/hdb3 and
> /dev/hdb5, while /dev/hdb1 and /dev/hdb2 result in severe errors.
> I tried
> running fsck manually with no success:
>
> <snip>
> Couldn't find ext2 superblock, trying backup blocks
> hdb: read_intr: status=0x59
> hdb: read_intr: error=0x40 {UncorrectableError}, LBAsect=262147,
> sector=262147
> end_request: I/O error, dev 03:40 (hdb), sector 262147
> hdb: read_intr: error=0x40 ... LBAsect=1048591, sector=1048591
> end_request: I/O error, dev 03:40 (hdb), sector 1048591
> fsck.ext2: Bad magin number in super-block while trying to open
> /dev/hdb
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem ..., then the superblock is corrupt, and you might try
> runninge2fsck with an alternate superblock:
> e2fsck -b 8193 <device>
> </snip>
>
> I tried this with no luck, getting the same error messages as
> above with
> different sectors. Then I tried to reboot, which was
> unsuccessful, giving
> me the maintenance root shell. Tried pressing <CTRL>+D for "normal"
> startup, but that didn't work.
>
> I cannot even boot from CD into something like PHLAK to perform/learn
> forensics!
>
> Is there anything I can do, or do I just throw the HD out and buy
> a new one?
> (Really can't afford this option, but if it's all I can do, then
> hey....)
> Please help... I'm desperate :O(
>
> Thanks in advance,
>
> Brad Camroux
>
>
> _______________________________________________
> clug-talk mailing list
> [EMAIL PROTECTED]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>
>
> _______________________________________________
> clug-talk mailing list
> [EMAIL PROTECTED]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
