Question

  • Creator
    Topic
  • #2244737

    Mysql error

    Locked

    by tatauwal ·

    Recently I had to install ntop on one my ML350 Proliant servers for monitoring Bandwidth usage on my network. It was working successfully cause I was observing the outcome via my web browser. But after some few days I started havingproblems. I could not view the statistics. When I view the services that were started at run time I realised that mysql was failing. When I tried starting it manually I ended up with the error below
    end_request: I/O error, dev sda, sector 3191137.
    Please can anybody help me out? I am running centos 5.

    Tata

All Answers

  • Author
    Replies
    • #2560084

      Clarifications

      by tatauwal ·

      In reply to Mysql error

      Clarifications

    • #2560068

      May Be Hard Disk

      by sajchurchey ·

      In reply to Mysql error

      You may have some bad sectors or a failing hard disk.

      Run “badblocks -o /some/output/file /dev/sda” to check for bad sectors. You can feed the output file to the “fsck” command and it will make the file system skip the bad blocks.

      You may need to run “fsck” on all of the partitions on /dev/sda (the primary scsi/sata hard drive).

      If you run “fdisk -l” it should list the partitions available similar to the output below:

      Device Boot Start End Blocks Id System
      /dev/sda1 * 1 31 248976 83 Linux
      /dev/sda2 32 4498 35881177+ 83 Linux

      In the above case you would have to run fsck on each of the partitions like so:

      fsck /dev/sda1
      fsck /dev/sda2

      etc.

      fsck will report any major errors, and with the output of the badblocks command, it will make sure that nothing is written to those. However, if you have one bad sector, chances are you have more. There’s also a good chance your disk is failing, and you may want to back it up ASAP.

      Learn more about fsck and badblocks using the manpages b/c I’m not familiar with centos.

Viewing 1 reply thread