Kerenl Log files

Linux Frank · Post by **Linux Frank** » Wed Feb 11, 2004 8:58 pm

HI all,

I recently decide to look at my kernel log files, and they seemed a little large.

What does anyone think is going on, and should I ever have files looking like this.

Code: Select all


This is how the files list.

-rw-r-----    1 root     root          38K Feb 11 17:22 errors
-rw-r-----    1 root     root          89M Feb 11 17:22 info
-rw-r-----    1 root     root         152M Feb 11 17:22 warnings

What the hell - 152Meg file - Tha aint' right.

Errors

Nov 22 01:08:48 localhost kernel: end_request: I/O error, cmd 0 dev 03:40 (hdb), sector 903784

-- notes --

There is some 900000 lines worth of this, on same date, does not occur again. It gives up on kernel logging then.

(At line 1897 in VI) All this happens after the error messaging mentions something about ISO 9660 M$ Joliet (why am I not suprised that the mention of M$ sends this system in to a spiral? - I think this is proof positive my machine is allergic to that company), so it appears to be reading a CD, but why does it go on so for 900000 lines, close on 12 hours (ends line 958303 in VI) ?

date is Nov. 21 - Nov 22 2003 - Friday night Saturday. wth was I doing then? - Shakspeare Peter Hall Jobbie (Shake was Sun - Went to dinner?)

-- end notes --

Info

Feb 11 11:28:03 localhost kernel: ACPI: Unable to locate RSDP
Feb 11 11:28:03 localhost kernel: ide: late registration of driver.
Feb 11 11:28:03 localhost kernel: Resume Machine:   This is normal swap space

Happens all the time (everytime I start or use a loggin, or shutdown?) - This could be the soundcard issue. This is all that appears in this file. 

Warnings

Nov 21 23:24:42 localhost kernel: hdb: command error: error=0x54
Nov 21 23:24:42 localhost kernel: hdb: command error: status=0x51 { DriveReady SeekComplete Error }

(This error repeats over some 1.9 million lines in VI)

Starts Here

Nov 21 21:42:24 localhost kernel: reiserfs: using ordered data mode
Nov 21 21:42:24 localhost kernel: reiserfs: checking transaction log (device ide1(22,8)) ...
Nov 21 21:42:24 localhost kernel: for (ide1(22,8))
Nov 21 21:42:24 localhost kernel: ide1(22,8):Using r5 hash to sort names
Nov 21 21:42:24 localhost kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Nov 21 21:42:24 localhost kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
Nov 21 22:42:18 localhost kernel: UDF-fs: No VRS found
Nov 21 22:43:16 localhost last message repeated 2 times
Nov 21 23:17:15 localhost kernel: hdb: command error: status=0x51 { DriveReady SeekComplete Error }

(At VI 4963)

Ends here

Nov 22 12:10:04 localhost kernel: hdb: command error: error=0x54
Nov 22 12:10:04 localhost kernel: hdb: command error: status=0x51 { DriveReady SeekComplete Error }
Nov 22 12:10:04 localhost kernel: hdb: command error: error=0x54

(AT VI line 1917768)

I am really just looking for opinons on what this represents. I believe the errors and warning files are the same thing, but I can't figure out what it is.

Void Main · Post by **Void Main** » Wed Feb 11, 2004 9:08 pm

Looks like a failing hdb. hdb is a hard drive right? I get those when my drives are going had. I have one in my firewall doing that now and I can actually hear that one reseting itself constantly. It's been slowly getting worse over the years. :) Actually I usually replace the drive when that starts happening if there is stuff on the drive that I care about.

Linux Frank · Post by **Linux Frank** » Wed Feb 11, 2004 9:46 pm

Doh. Bloody fool, yeah I have a second HDD but it has been pretty crap since I got it (was given it), I thought it failed a while back (actually I think it gave a CRC error when I first used it) - It is essentially useless, an unused install of Slack, or Evil Entity if I recall. I forgot it failed a while back, and thinking closer that might be when I was thinking it failed. Feeling rather foolish now I should have spotted that. It occasionally ramps itself up and wines, and then dies again. One day I'll get a new computer to replace this thing as a desktop and just make it a server full time.

I had to spend most of yesterday backing up a computer network and the job was a mess up from minute one. What does one expect, I had to back up a M$ 95, ME, XP network , and there are at least three sperate laptop backups that are cross linked and repeated. You have no idea - My IQ went from a robust Moron Level to sub-human - takes time to ramp back up again.

Thanks Void.

--Frank