Visit Open-E website
Results 1 to 4 of 4

Thread: Strange error - bad block

  1. #1

    Default Strange error - bad block

    Hi,

    I have raid controller with configured 2 logical devices with raid 5 protection. On web gui in open-e i recently have 4 srange errors:

    2009/02/03 22:35:20 [418] Bad block discovered: controller 1 (642f000).
    2009/02/03 22:16:57 [418] Bad block discovered: controller 1 (15ec800).

    2009/01/27 00:47:50 [418] Bad block discovered: controller 1 (bd7a100).
    2009/01/27 00:47:40 [418] Bad block discovered: controller 1 (bd7a000).


    I verify health of physical disck's and logical disck's - all are ok.

  2. #2

    Default

    When a bad block is discovered in a particular disk the bad block is then remapped within the remapping pool and is stored across multiple disks. I would contact the RAID manufacture and ask to assist you on a deeper investigation. Please back up your data!
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  3. #3

    Default

    when i veryfy physical and logical disk's all are have state - optimal

  4. #4

    Default

    I would start with the basics and run the memtest and then the file system repair utility - if you are using NAS.

    Memtest is done by rebooting the system and after POST hit the ESC or TAB key there you will see the basic menu - run the memtest for at least 45 min. If now errors then reboot and go to the Console screen and enter CTRL + ALT + X then run the File repair option.

    Only do this if you are absolutely sure your RAID set is good!
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

Posting Permissions

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