Failed hard drive superblock

[bjbrock57]

Are the beep codes coming at boot? If it's beeping during use, the first thing I would suspect is a hot CPU. An overheated CPU can cause absolutely anything to fail in the system. Check the motherboard for blown capacitors as well - the tops will be pushed up.. This will cause your board to beep.

One other thing to check is the PSU. Open it up and see if any capacitors are blown - the tops will be pushed up. If it's "crowbaring" it will take out a hard drive in a hurry.

Until you determine the cause of the beeps, there is really no need to go any further.

[rgrandin]

Alright, so I unplugged all of my cables and plugged everything back in. And for the 3.5 days after my next boot everything was running just fine and all of my data was still on the suspect hard drive. I thought the problem was solved.

Just now I had the read-only symptoms appear again (Skype signs itself out & "touch" doesn't work because of the read-only filesystem). The computer did reboot successfully...after several attempts required to get past POST. The failed attempts caused the BIOS to think that there was an overclocking problem (this computer isn't overclocked), but I didn't change any BIOS settings when given the opportunity. It was after this overclocking error that the computer finally rebooted.

Before I go through the time and hassle of removing the motherboard and RMAing it to MSI (a 1-2 week process, according to their tech support), what else can I attempt to do to solve the problem?

[DenverD]

rgrandin wrote:
> Alright, so I unplugged all of my cables and plugged everything back in.
> And for the 3.5 days after my next boot everything was running just
> fine and all of my data was still on the suspect hard drive. I thought
> the problem was solved.
>
> Just now I had the read-only symptoms appear again (Skype signs itself
> out & "touch" doesn't work because of the read-only filesystem). The
> computer did reboot successfully...after several attempts required to
> get past POST. The failed attempts caused the BIOS to think that there
> was an overclocking problem (this computer isn't overclocked), but I
> didn't change any BIOS settings when given the opportunity. It was
> after this overclocking error that the computer finally rebooted.
>
> Before I go through the time and hassle of removing the motherboard and
> RMAing it to MSI (a 1-2 week process, according to their tech support),
> what else can I attempt to do to solve the problem?
>
>
well, as i read (when you said it ran days with no problems, and
then...) i was gonna say REPLACE the cable between the drives and
MB...but, when you said "several attempts required to get past POST"
i thought, oh-no sounds like CPU or MB..

my guess is it may be the MB, but if you wanna TRY...go ahead and
remove/replace the CPU...it MIGHT help....but, be SURE you have (and
know how to correctly apply) replacement thermal paste...otherwise
you might fry your processor too..

on the other hand, if the MB's maker's symptom-problem-fix maze made
them think it IS a MB problem, it probably is...i mean, they know
their product a lot better than you or me..

--
see caveat: http://tinyurl.com/6aagco
DenverD (Linux Counter 282315) via NNTP, Thunderbird 2.0.0.14, KDE
3.5.7, SUSE Linux 10.3, 2.6.22.18-0.2-default #1 SMP i686 athlon