Warning: Function ereg() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 4

Warning: Function split() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 19

Warning: Function ereg() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 4

Warning: Function split() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 19

Warning: Function ereg() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 4

Warning: Function split() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 19

Warning: Function ereg() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 4

Warning: Function split() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 19

Warning: Function ereg() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 4

Warning: Function split() is deprecated in ..../includes/class_postbit.php(345) : eval()'d code on line 19
Do these logs tell my HDD is in trouble?
Results 1 to 5 of 5

Thread: Do these logs tell my HDD is in trouble?

  1. #1
    Junior Member
    Join Date
    Jun 2001
    Location
    Melbourne, Australia
    Posts
    94

    Do these logs tell my HDD is in trouble?

    I a tonne of this stuff in /var/log/messages. Does anyone know what I'm being told here?

    [pre]Sep 15 15:32:54 HAL9000 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Sep 15 15:32:54 HAL9000 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=16581014, sector=194648
    Sep 15 15:32:54 HAL9000 kernel: end_request: I/O error, dev 03:05 (hda), sector 194648
    Sep 15 15:32:54 HAL9000 kernel: vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [68855 70139 0x0 SD]
    Sep 15 15:33:01 HAL9000 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Sep 15 15:33:01 HAL9000 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=16580343, sector=193976
    Sep 15 15:33:01 HAL9000 kernel: end_request: I/O error, dev 03:05 (hda), sector 193976
    Sep 15 15:33:01 HAL9000 kernel: vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [68855 69957 0x0 SD]
    Sep 15 15:33:07 HAL9000 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
    Sep 15 15:33:07 HAL9000 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=16580347, sector=193984
    Sep 15 15:33:07 HAL9000 kernel: end_request: I/O error, dev 03:05 (hda), sector 193984
    Sep 15 15:33:07 HAL9000 kernel: vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [68855 69959 0x0 SD]
    [/pre]

    If it is related, when doing anything through YaST2 (I'm running SuSE 8.0), the final part where config files are re-written, temp files deleted, etc, takes an age. It never used to take that long, hence my suspicion of a link.

    Windows 2000, which only uses a 9G partition at the beginning of the 60G disk, doesn't have any similar entries in it's logs. SuSE uses the rest of the 60G disk.

    Any ideas?

  2. #2

    Re:Do these logs tell my HDD is in trouble?

    hello,
    my 1st guess would be that it is using UDMA100 when it should not be of the kernel module is messed up. I had messages like that when connected to a UDMA100 controller.

  3. #3
    Junior Member
    Join Date
    Jun 2001
    Location
    Melbourne, Australia
    Posts
    94

    Re:Do these logs tell my HDD is in trouble?

    [quote author=pbharris link=board=1;threadid=4965;start=0#49419 date=1032070953]
    hello,
    my 1st guess would be that it is using UDMA100 when it should not be of the kernel module is messed up. I had messages like that when connected to a UDMA100 controller.
    [/quote]

    Cheers. I've now switched UDMA off at the BIOS, see if that stops them. If it does, then I'll have to work out what is next

  4. #4
    Junior Member
    Join Date
    Oct 2001
    Posts
    64

    Re:Do these logs tell my HDD is in trouble?

    I used to get those errors on my old k6-2 500 based system with an FIC-503+ (via chipset) MB. The only way I could get rid of them was to remove UDMA support from the drive. However I recently set the machine up with kernel 2.4.18 & I didn't get them anymore - but I assume SuSE 8 uses a new(ish) kernel. Just out of interest is it a via based MB?

    Regards

    ed

  5. #5

    Re:Do these logs tell my HDD is in trouble?

    Everyone here is right as far as my experience goes.... unless your drive is also making loud burping noises :-) I wound up having to take a machine out of commission because what I thought could be fixed with a recompile actually turned out to be a bum hard drive.

    Backup your data to another disk, then try recompiling and stuff. Good luck.

Similar Threads

  1. Question on SSH and logs
    By gjansky in forum Linux - Software, Applications & Programming
    Replies: 3
    Last Post: 03-26-2004, 06:43 PM
  2. Help With Apache Logs
    By Epsilon in forum Linux - General Topics
    Replies: 1
    Last Post: 05-18-2003, 02:04 PM
  3. Red Hat Logs
    By Rukasboy in forum Linux - Software, Applications & Programming
    Replies: 2
    Last Post: 07-08-2002, 10:10 PM
  4. Apache Logs...
    By groundzero in forum Linux - Hardware, Networking & Security
    Replies: 1
    Last Post: 04-22-2002, 04:47 PM
  5. apache logs
    By agar in forum Linux - Hardware, Networking & Security
    Replies: 10
    Last Post: 01-19-2002, 03:21 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •