LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 03-01-2005, 08:29 AM   #16
Darin
Senior Member
 
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024

Rep: Reputation: 45

When I see corrupt filesystem I think of a few things. If the OS has crashed, this can cause some filesystem corruption, the crashes may be a result of disk corruption but it's more likely they are the reason for it. Most multitasking OSs don't like to be taken offline ungracefully (lockup, power loss, etc) and some handle it better than others, although Linux is usually pretty recoverable when it does. The other culprits after crashes causing disk errors are failing disk (obviously), bad RAM or bad mobo/CPU (overclocked?) and usually http://www.memtest.org/ will eliminate RAM or CPU as the cause.
 
Old 03-01-2005, 03:47 PM   #17
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
Quote:
other culprits after crashes causing disk errors are failing disk (obviously), bad RAM or bad mobo/CPU (overclocked?) and usually http://www.memtest.org/ will eliminate RAM or CPU as the cause.
Not overclocked (i'm still a newbie and not ready to tread there)
As I was setting up memtest, she locked up on me again, and again it was a few "Free blocks count wrong," a "Inode Bitmap Differences," and a few "Free Inodes count wrong"
---fewer than in previous lock ups, by the way.

Since I have yet to "personalize" my machine or add any additional apps and whatnot, I'm gonna reformat the HD and do a nice, new, clean install.
I'm gonna go with ext3 file system, and create partitions for /swap, /, /usr, and /home.
(previous install was only swap and /)
First thing after, I'm gonna load up memtest.

Before I do this, is there *anythin* else at all I might want to consider adding in to this plan?

(incidently, I'm typing this out on my wife's XP machine, while she's skeptically saying:

_ ^
* *
_____ "Linux, huh? and what's so great about it again?"


so part of me is hoping its hardware failure)

EDIT*******
if means anything: the two times today this has happened, when it rebooted it saved my session and opened up all the windows i had. It wasn't doing this previously. Indicate anything.

Last edited by redbeansnrice; 03-01-2005 at 03:52 PM.
 
Old 03-01-2005, 04:29 PM   #18
jiml8
Senior Member
 
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 115Reputation: 115
Quote:
so part of me is hoping its hardware failure)
From what you have been describing, it looks to me more and more like a hardware problem. When there is a lockup, if you can, you should try to get to the root screen which can be accessed by ctrl-alt-F1. It might not *really* be locked, but it might be writing error messages there. You also might try to ssh in from that XP box; again, it could be only the X-system that is locked.

Do the numlock and capslock lights come on and off on the keyboard when you select/deselect them, when it is locked up?

The disk problems make me think disk or controller failure, but a memory failure is also a possibility, though probably not a real good one since that won't ordinarily hose your disk.

How cables and jumpers? All done correctly? Are you sure? How are you sure.
 
Old 03-01-2005, 07:44 PM   #19
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
Yeah, unless your system is doing a lot of swapping, a hard drive issue won't USUALLY bring the box down to a full lock up right way. Which is not to say it won't, but it isn't the norm from what I've seen.
 
Old 03-01-2005, 09:49 PM   #20
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
I ran memtest a couple times, but could never get through the whole thing. At some point, once during test 2 and once during test 5, it would stop. The running clock would stop. I would press one of the options key like c or esc, and nothing would happen.
Yesterday afternoon, I picked up a new 512M stick and put it in before the tests, and removed the two old ones.

Quote:
How cables and jumpers? All done correctly? Are you sure? How are you sure.
I dug around and found the manual for my motherboard, and if I'm reading the bit on jumpers correctly, it looks as though the "BIOS Flash Protect" jumper is set to "Disable." I don't know much about BIOS issues, but it would seem inuitive that if there's an option to protect the BIOS, then I should. I've never done anything with this before, so if it is indeed set incorrectly, it would be from the people who built my machine.

Could this be the cause of all the bad juju? (please?)
Should I clear the CMOS, flash the BIOS then set it to protect?

oh, and the mother board is Elite K7SEM, Chipset SiS730S

I sure hope somebody else can get useful info out of this thread as well.
 
Old 03-01-2005, 10:14 PM   #21
jiml8
Senior Member
 
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 115Reputation: 115
Quote:
I ran memtest a couple times, but could never get through the whole thing. At some point, once during test 2 and once during test 5, it would stop. The running clock would stop. I would press one of the options key like c or esc, and nothing would happen.
Yesterday afternoon, I picked up a new 512M stick and put it in before the tests, and removed the two old ones.
Power supply or mobo problem.
Quote:
dug around and found the manual for my motherboard, and if I'm reading the bit on jumpers correctly, it looks as though the "BIOS Flash Protect" jumper is set to "Disable." I don't know much about BIOS issues, but it would seem inuitive that if there's an option to protect the BIOS, then I should. I've never done anything with this before, so if it is indeed set incorrectly, it would be from the people who built my machine.
I meant the jumper on the HD and on the CDROM drive. A conflict there would cause problems with the HD.

But given the failed mem test in conjunction with the HD problems, I would be looking - in order - at the motherboard then the power supply. Looks to me like you might have one or more bad voltage regulators or filters on the mobo. Could also be a problem on the +5 power supply line, but I would rate a mobo problem as a higher liklihood.

If you have a voltmeter, put it on the PS +5 line and watch it. If you have an oscilloscope, use that instead. If you don't see any anomalies, such as low voltage - below about 4.6 volts - or lots of spikes (you'll only see this with a scope), then you need to consider replacing the motherboard.
 
Old 03-01-2005, 11:21 PM   #22
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
poo.
That's the last thing I wanted to hear.
No chance its the BIOS jumper or a faulty video card then?
 
Old 03-02-2005, 03:29 AM   #23
jiml8
Senior Member
 
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 115Reputation: 115
video card problem is possible. Stick another video card in and see.
 
Old 03-02-2005, 03:35 AM   #24
Darin
Senior Member
 
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024

Rep: Reputation: 45
A BIOS jumper is not likely to cause problems, unless you've been running it for a few days with it jumpered for "CMOS Clear" and a video card may cause graphical lockups, but is not likely to get memtest to hardlock. Doing a jumpered CMOS clear isn't likely to hurt though, as long as you put the jumper back per your motherboard manual's instructions.

The "BIOS flash protect" sounds like it's unrelated to any crashes. It's sort of like the write protect tab on floppy disks, but for your BIOS. Flashing the BIOS is normally not a bad idea, and setting the BIOS protect jumper won't hurt either (old viruses used to try to write themselves into BIOS flashROM.)

Given that memtest is hardlocking though, I would say hold off on doing a BIOS flash in case the flash process locks up, which is like a bad CD burn except blank CDs are worth pennies and a dead motherboard doesn't do very well as a drink coaster

If you have another power supply laying around, I'd try swapping that and seeing if memtest stops hardlocking. That is a relativly easy thing to do IF you have a spare PS on hand.
 
Old 03-02-2005, 09:12 AM   #25
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
This is really new, odd territory for me.
For example, right now I'm back on the problematic box to write this, and have been for an hour or so. Meanwhile the memtest consistently locks inside of 5 minutes.

Also, the last two times I rebooted into Slack, besides it remembering what windows I had open (which is nothing I've asked this to do) it also changed the appearence back to the default.
odd, i thought.

Also, I was considering late last night, that when I previously had FC2, it would lock up once in a while, but never as I was using it. Only after it had been sitting for a while (overnight). I read a thread somewhere about it having to do with acpi on with that particular distro.

These frequent lock ups have only been happening since trying to get Slack up and running (not that I'm blaming Slack for this)

As it happens, I do have an old power supply I can try and drop in. It is OLD though. It was fine the last time I used it two years ago.

I'll give it a shot. Wish me luck.

Thanks again.
 
Old 03-02-2005, 09:43 AM   #26
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
It could be heat related then. Memtest generates a LOT of heat (high CPU+memory load). Having the box on for a while (i.e., under Fedora) would also let it get warm. I suggest you install the lm_sensors package to see about CPU/mobo temps.
 
Old 03-02-2005, 09:47 AM   #27
jiml8
Senior Member
 
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 115Reputation: 115
Swapping the power supply, if you have one, is a good plan. Pay attention to the power rating of the supply and don't overload it.

This may require you to leave some things off with the old supply in place, and that adds a bit of complexity to the testing because you need to be sure that none of the things you leave off were causing the problem you are having.

Beyond that, since your problem seems to occur when the system has been running for awhile, have you considered the possibility of a thermal problem? Have you cleaned all the dust bunnies off of the mobo and the heatsinks?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Fat32 Harddrive errors, causing system instability redness Linux - Hardware 2 02-01-2005 03:49 AM
Harddrive size errors in bios teval Linux - Hardware 1 08-28-2004 03:49 AM
wacky syntax, i see it in c and java djgerbavore Programming 2 08-04-2004 02:01 PM
reiserfs harddrive errors brittbs Linux - Hardware 2 11-18-2003 02:36 PM
computer gone wacky corbintechboy Slackware 10 10-16-2003 01:22 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 09:49 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration