<div>Damian,</div>
<div> </div>
<div>Yes the "fsck" issues are to do with the system not shutting down correctly due to either</div>
<div>you switching it off, the PSU crapping out, power cut etc.</div>
<div>It's normal for fsck to complain like that. Windows does it too sometimes.. you must</div>
<div>have seen it do a disk check on boot up before? Same thing.</div>
<div> </div>
<div>It does sound like one of your cards or motherboard has bitten the bullet though. If your</div>
<div>PSU was faulty that could have caused it, or even the other way around!</div>
<div> </div>
<div>Whatever is the case, you're on the right track with a step-by-step rebuild to trace the culprit.</div>
<div> </div>
<div>The nice thing about Linux is that even if you find you need to replace the motherboard,</div>
<div>you won't need to start again building linux from scratch. With Windows if you change the motherboard you are quite likely to have a system that won't even boot (there are tricks to get round this but it's not guaranteed or pretty!).
</div>
<div> </div>
<div>Cheers</div>
<div> </div>
<div>Steve<br><br> </div>
<div><span class="gmail_quote">On 11/07/07, <b class="gmail_sendername">Brian Wood</b> <<a href="mailto:beww@beww.org">beww@beww.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Damian wrote:<br>> Brian Wood wrote:<br>>> Damian wrote:<br>>> <snip><br>>>> What would you suggest I do from here? Doesn't look good to me, but
<br>>>> maybe it's not all lost yet. Not quite sure what's going on, but<br>>>> hopefully I've given enough information to either shed some light or get<br>>>> a couple of suggestions.
<br>>> You should do exactly what it is telling you to do: run fsck manually.<br>>><br>>> But of course you have to get to a working shell and minimal system to<br>>> do that.<br>>><br>>> You could possibly boot from one of the live CDs, or one of the
<br>>> pre-packaged rescue CDs like the "Ultimate Boot CD":<br>>><br>>> <a href="http://www.ultimatebootcd.com/">http://www.ultimatebootcd.com/</a><br>>><br>>> (site seems down right now though)
<br>>><br>>> Unfortunately such preparations for a situation like this require either<br>>> another working machine or having made such a disk ahead of time.<br>>><br>>> Your MoBo's POST test is not happy, as indicated by the beep code. Most
<br>>> MoBos have a list someplace (docs or online support) of precisely what<br>>> each beep code means.<br>>><br>>> I'm guessing you have a failed hard drive, can you get to the BIOS setup<br>
>> screen, and does it show the hard drive(s) correctly?<br>>><br>>> If you can get fsck to run manually from a shell, I'd use the -y option,<br>>> or you will be typing "y" a LOT.<br>
>><br>>> Good Luck.<br>>><br>>> BEWW<br>><br>> Thanks Brian,<br>><br>> I have a couple of working windows machines here so I'm downloading the<br>> UltimateBootCD now.<br>><br>
> Excuse my ignorance, but should I simply run:<br>> fsck -y<br>> when I get to a command prompt?<br><br>Not quite, you have to run fsck -y (filesystem to check)<br><br>In a simple case it would be fsck -y /dev/hda1
<br><br>><br>> From the motherboard beep codes that I can find, the one I'm getting<br>> indicates a problem with the graphics card. That seems to not be the<br>> case though as switching graphics cards produces the same problem, but
<br>> removing other cards seems to fix it.<br>><br>> I've started to have an idea about what's happened ..<br>> Maybe something random failed (sound card?) which caused the computer to<br>> behave oddly, then the hard drive died because a file was copying over
<br>> the net when I shut the computer down.<br><br>As BW said, that would trash a file, not cause a hard drive hardware<br>failure.<br><br>Only on old Star Trek episodes does giving a computer bad instructions<br>cause hardware destruction.
<br><br>><br>> I'll really have lost faith in Linux if that's what has happened. I lost<br>> a hard drive to Linux a few months ago due to a power cut, and having<br>> the trouble now potentially because of shutting down while a file was
<br>> copying. I know neither of those two things are great, but I've had the<br>> same countless times on windows machines and never had such dire<br>> consequences.<br><br>Please do not blame this on Linux, it is not the problem.
<br><br>I'm really beginning to think you have a PS problem, as BW suggested as<br>well. The MoBo is also possible but I'd be astounded if this does not<br>turn out to be a hardware problem.<br><br>BEWW<br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br>