Topic
  • 7 replies
  • Latest Post - ‏2013-11-14T22:04:56Z by Tehnoline
Tehnoline
Tehnoline
15 Posts

Pinned topic Bad Block discovered, but on which disk ??

‏2011-10-31T17:07:32Z |
I have X3400 with Adaptec Raid controller.
On ServeRaid Manager have this error log: Bad Block Discovered: controller 1 (636a3280)

How to investigate on which disk are bad sector's ?

Thanks
Updated on 2011-11-02T09:28:42Z at 2011-11-02T09:28:42Z by Stokie
  • Novikov_Alexander
    Novikov_Alexander
    6877 Posts

    Re: Bad Block discovered, but on which disk ??

    ‏2011-10-31T19:22:09Z  
    Dear Denis,

    could you provide DSA log and ServeRAID Support Archive.

    Regards,
    Alexander Novikov
    Russia, Moscow
  • Stokie
    Stokie
    573 Posts

    Re: Bad Block discovered, but on which disk ??

    ‏2011-11-01T12:02:33Z  
    • Tehnoline
    • ‏2011-11-01T09:49:50Z
    In attach ServeRAID support
    Hi,

    In the RAIDevta.log from ServeRAID Manager we can see entries indicating the bad blocks are

    Controller 1, channel 0, SCSI ID 4, LUN 0,

    This drive is part of a RAID1 pair and so you are being protected. I would also note from the model string that it doesn't look like the drives are IBM supplied so if it gives further problems if you are seeking warranty you will need to contact the point of purchase.

    Device #4
    Device is a Hard drive
    State : Online
    Supported : Yes
    Transfer Speed : SATA 1.5 Gb/s
    Reported Channel,Device : 0,4
    Vendor : ST310005
    Model : 28AS
    Firmware : CC38
    Serial number : 9VP32ZC6
    Size : 953869 MB
    Write Cache : Enabled (write-back)
    FRU : None
    PFA : No
    Stokie.
  • Tehnoline
    Tehnoline
    15 Posts

    Re: Bad Block discovered, but on which disk ??

    ‏2011-11-01T12:09:47Z  
    • Stokie
    • ‏2011-11-01T12:02:33Z
    Hi,

    In the RAIDevta.log from ServeRAID Manager we can see entries indicating the bad blocks are

    Controller 1, channel 0, SCSI ID 4, LUN 0,

    This drive is part of a RAID1 pair and so you are being protected. I would also note from the model string that it doesn't look like the drives are IBM supplied so if it gives further problems if you are seeking warranty you will need to contact the point of purchase.

    Device #4
    Device is a Hard drive
    State : Online
    Supported : Yes
    Transfer Speed : SATA 1.5 Gb/s
    Reported Channel,Device : 0,4
    Vendor : ST310005
    Model : 28AS
    Firmware : CC38
    Serial number : 9VP32ZC6
    Size : 953869 MB
    Write Cache : Enabled (write-back)
    FRU : None
    PFA : No
    Stokie.
    Thanks !

    Please tell me how to found this information in log's ? And for future problems.

    Thanks.
  • Stokie
    Stokie
    573 Posts

    Re: Bad Block discovered, but on which disk ??

    ‏2011-11-02T09:28:42Z  
    • Tehnoline
    • ‏2011-11-01T12:09:47Z
    Thanks !

    Please tell me how to found this information in log's ? And for future problems.

    Thanks.
    Well the easiest way to work with a DSA locally is to use -v on the command line when you run it. This generates local html which is more readable than the -text option. Point your browser at the index.html generated in ibm_support and start to review the files.

    (If you have the xml.gz then you can combine the -v switch with -i to import the existing file and generate the html which is what I did to review the report.)

    For this particular case the information is found under the 'ServeRAID Logs' heading which is the Raidevta.log stored by the installed ServeRAID Manager . Scrolling down this log you can see the first bad block event being reported on 10/10/2011 from 00:31 onwards.

    Stokie
  • Tehnoline
    Tehnoline
    15 Posts

    Re: Bad Block discovered, but on which disk ??

    ‏2011-11-11T18:35:31Z  
    Dear Denis,

    could you provide DSA log and ServeRAID Support Archive.

    Regards,
    Alexander Novikov
    Russia, Moscow
    In attach DSA log
    Updated on 2011-11-11T18:35:31Z at 2011-11-11T18:35:31Z by Tehnoline
  • Tehnoline
    Tehnoline
    15 Posts

    Re: Bad Block discovered, but on which disk ??

    ‏2011-11-11T18:35:31Z  
    Dear Denis,

    could you provide DSA log and ServeRAID Support Archive.

    Regards,
    Alexander Novikov
    Russia, Moscow
    In attach ServeRAID support
    Updated on 2011-11-11T18:35:31Z at 2011-11-11T18:35:31Z by Tehnoline
  • Tehnoline
    Tehnoline
    15 Posts

    Re: Bad Block discovered, but on which disk ??

    ‏2013-11-14T22:04:56Z  
    • Stokie
    • ‏2011-11-02T09:28:42Z
    Well the easiest way to work with a DSA locally is to use -v on the command line when you run it. This generates local html which is more readable than the -text option. Point your browser at the index.html generated in ibm_support and start to review the files.

    (If you have the xml.gz then you can combine the -v switch with -i to import the existing file and generate the html which is what I did to review the report.)

    For this particular case the information is found under the 'ServeRAID Logs' heading which is the Raidevta.log stored by the installed ServeRAID Manager . Scrolling down this log you can see the first bad block event being reported on 10/10/2011 from 00:31 onwards.

    Stokie

    Hi !

    I have same problem as above in 2011 year, but in DSA (index.html) I can't see ServeRaid log ??

     

    Attachments