LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
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 02-27-2005, 10:43 PM   #1
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Rep: Reputation: 15
Wacky errors on harddrive


OK, I think this is a hard drive issue, so I'll post it here.
Last night I installed Slack 10.1 No other OS.
I let it run all night, and everything was fine in the morning. Mid day it freezes on me. Rebooting it ran through fsck, found some errors and fixed them. Boots up fine. Little while latter same thing happens. Since I had no personal data, being a new install, I start from scratch.
Newly installed again, a while after using it, it freezes.
I started running fsck manually, getting a bunch of errors such as:

Unattended inode 524183
inode 524183 ref count is 2, should be 1

Then on rebooting I get
"/dev/hda2 has gone 49710 with out being checked, check forced"

This freezing happened a few times today. Some of the other messages I got were:

Inode ######, i_blocks is 64 should be 56
" ######, " "128 " " 120
(about a dozen messages like these with diff inode/i_blocks)

Block Bitmap differences.....(numbers that mean nothing to me)

Deleted inode ####### has zero dtime fixed

free blocks count wrong for group ### xxxxx; counted: yyyyyy


So, does this sound like a hardware issue (as in my hd is toast) or could this (please) be simply a matter of need to set up the partitions differently or compiling the kernel or......something?

oh yeah, only 2 partions, 1024M of swap, the rest for /

History on this drive is that it had WinXP up untill about 6 months ago. I put Fedora on it and all was mostly fine. There was a rare freeze, but I blame it on acpi and a couple of apps that were running when it happened.

Thanks,
Michael
(oh, and if there's a more appropriate board for this....sorry, lemme know and I'll move it)

Last edited by redbeansnrice; 02-27-2005 at 10:46 PM.
 
Old 02-27-2005, 10:51 PM   #2
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
As far as I can tell... no guarantees though... it looks like it's just filesystem corruption. In other words, it's PROBABLY not failing hardware.

Look in your "dmesg" for other errors. If you see hardware specific errors, then you might have a problem with hardware.
 
Old 02-27-2005, 11:00 PM   #3
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
OK, I looked about and found my demsg, but I really don't understand if what I'm looking at is "hardware specific error" or not, and I had another freeze as i was looking over the dmesg log.
Should I post it, or can anyone tell me what a common "hardware specific error" might look like?

if its not a hardware issue, is this a good example of needing to compile the kernel myself?


thanks

Last edited by redbeansnrice; 02-28-2005 at 12:11 AM.
 
Old 02-28-2005, 09:39 AM   #4
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
This should have nothing to do with needing to recompile a kernel. To get the hda-related information from dmesg, please do:
Code:
dmesg | grep hda
Hardware errors generally look like:
Code:
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
seeing "DriveReady SeekComplete Error" scares the heck out of any sysadmin.
 
Old 02-28-2005, 11:37 AM   #5
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
here's the output from dmesg | grep hda:
Code:
root@michael:~# dmesg | grep hda
    ide0: BM-DMA at 0x4000-0x4007, BIOS settings: hda: DMA, hdb: pio
hda: QUANTUM FIREBALLlct20 20, ATA DISK drive
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 39876480 sectors (20417 MB) w/418KiB Cache, CHS=39560/16/63, UDMA(33)
 hda: hda1 hda2
Thankfully, there's nothing in /var/log/dmesg that's saying anything about "DriveReady SeekComplete Error"

So I suppose this is less of a hardware issue than I thought.
Should I take this issue to another board, then?

It froze up again last night before I went to bed and when i rebooted again this morning it when through the same thing with fixing errors.

Thanks to everyone - I'm still new and its getting a bit frustrating.
I have plenty of patience stored up to make Linux work. Anyone's patience with me is greatly appreciated.

-Michael
 
Old 02-28-2005, 01:17 PM   #6
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
Well, I'll try to be there as much as I can for you.

If dmesg isn't showing any of those errors, then it's highly unlikely there is failing hardware involved. Most likely, your filesystem has been corrupted. This is relatively rare, but can occur when you reboot without shutting down properly (or the computer locks up). I have to wonder if the lockups may be independent of the hard drive issues; perhaps they actually CAUSED it. What filesystem are you using on this partition?
 
Old 02-28-2005, 07:36 PM   #7
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
Being a new install, clean install with no other OS (and being new still to Linux myself) I set the files system to ext2 because...well...I dunno. Just seemed the thing to do.

I compiled the 2.6.10 kernel just a little earlier for 2 reasons:
1 - I thought that maybe this could help my lock up/freezing issues some how (maybe?)
and
2 - Just to do it. Maybe learn something.

Think the compile of the new kernel might help? I guess I'll find out.

Should I have used a different file system?

Thanks again.
 
Old 02-28-2005, 08:24 PM   #8
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
It might. I suppose there's a small chance there's a bug in your IDE chipset that could've caused the corruption. A new kernel MIGHT help.
 
Old 02-28-2005, 09:36 PM   #9
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
So the ext2 file system is ok?
 
Old 02-28-2005, 09:46 PM   #10
jiml8
Senior Member
 
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 115Reputation: 115
I am going to disagree somewhat with Matir. The problem you are having *could* be a HD failure in progress, even if no seek errors are appearing in the logs (or on the default root screen, which can be accessed by a ctrl-alt-F1 with ctrl-alt-F7 to get back to the display manager).

Recurring file system corruption, particularly in a clean install, often is a harbinger of drive failure.

You need to take a look at your bad blocks list to see if it is growing. If it is growing, then you need to change the HD. This kind of problem should result in I/O errors being reported, often on the root display.

Seek errors can point to the drive, the controller, or the cables.
 
Old 02-28-2005, 10:32 PM   #11
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
Perhaps I was a little too strong on indicating that it was unlikely to be a hardware failure. I don't think it is on a single instance. Also, I would use ext3 over ext2 given the journaling features of ext3 and that the performance of the two is quite comparable. (Or reiserfs, but that's a whole different story).

Look into the smartmontools suite of programs. They handle SMART hard drives. SMART is Self-Monitoring Analysis and Reporting Technology... in other words, hard drive diagnostics. Have it run a 'long offline' test and see if it completes successfully.
 
Old 02-28-2005, 10:58 PM   #12
redbeansnrice
Member
 
Registered: Aug 2004
Location: Eastern Shore
Distribution: Slack 10.1
Posts: 36

Original Poster
Rep: Reputation: 15
well, thanks again...y'all have given me a lotta good information.
Quote:
I would use ext3 over ext2 given the journaling features of ext3 and that the performance of the two is quite comparable
I don't suppose there is a way to switch to ext3 now, is there?

Nothign looks bad on the root display except a few:

"QPixmap: Cannot not create a QPixmap when no GUI is being used"

and a referrence to a souund problem, which I'm aware of.
I'll look into smartmontools.


pax,
Michael
 
Old 03-01-2005, 05:18 AM   #13
jiml8
Senior Member
 
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 115Reputation: 115
Quote:
Perhaps I was a little too strong on indicating that it was unlikely to be a hardware failure. I don't think it is on a single instance.
Perhaps I misread, but it was not my understanding that this was a single occurrence. If it was, then I agree that a hardware fault is unlikely.
 
Old 03-01-2005, 08:24 AM   #14
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
Quote:
Originally posted by jiml8
Perhaps I misread, but it was not my understanding that this was a single occurrence. If it was, then I agree that a hardware fault is unlikely.
Actually, I was the one who misread/forgot that he had reinstalled. I thought it was all one install.
 
Old 03-01-2005, 08:26 AM   #15
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 125Reputation: 125
Quote:
Originally posted by redbeansnrice
I don't suppose there is a way to switch to ext3 now, is there?
Actually, there is. You can add a journal to an ext2 system by doing 'tune2fs -j /dev/hdaX', though you need to make sure your kernel has support for ext3 when you do this.
 
  


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 03:45 PM.

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