Which drive in RAID has a bad sector?

I use the LSI MegaRaid SAS controller to have 4 physical drives in a virtual drive. It seems that (at least) one of the drives has bad sectors, because:

>An error occurred while trying to back up some files.
>Run badblocks to report some bad sectors

I hope that solving this problem is as simple as swapping the problematic disk and rebuilding the raid array. I think LSI MegaRaid WebBIOS allows me to identify the problematic disk, but I cannot find any option to check for bad sectors.

The following is a screenshot of WebBIOS:
enter image description here

Can anyone provide any suggestions on how to identify the problematic disk?

Smartmontools has extended functions that allow it to poll the drive through LSI (and other) RAID arrays to obtain SMART data. Generally, this is not something you can do because the RAID abstraction obscures the direct interface with the drive.

Smartmontools may not be installed on your computer. However, it is most Most of the “main repository” of the release is native, and there is even a Windows version: http://sourceforge.net/projects/smartmontools/files/

It can be used to poll the LSI MegaRAID controller The following drives are as follows:

smartctl -a -d megaraid,N / dev / sdX

where “-a” means display all disk data, -d means device type (megaraid is the type in your case) followed by N to indicate the drive letter in that controller. To access the drive in slot 0, you can say 0 here. If you wish to poll all four drives, please Run this command four times, replacing N with 0 to 3. sdX is the RAID abstraction itself, usually seen in the operating system. Yours may be sda.

You will see the length of each drive Output, and what you are looking for is the reported general SMART failure (you may not find it because your controller did not reject the drive), or report “offline uncorrectable sector” or “pending sector”. In this field Any drive above 0 in is an error. No mercy should be given to these fields, because it requires a lot of failed reads to increment the value by 1.

You can also perform short-term or long-term tests like this (The same rules as above apply):

smartctl -t [long | short] -d megaraid,N / dev / sdX

I use LSI MegaRaid The SAS controller has 4 physical drives in a virtual drive. It seems that (at least) one of the drives has bad sectors because:

>An error occurred while trying to back up some files
>Run badblocks to report some bad sectors

I hope to solve this problem is as easy as swapping the problematic disk and rebuilding the raid array. I think the LSI MegaRaid WebBIOS allows me to identify the problematic disk, but I can’t find it To any option to check for bad sectors.

The following is a screenshot of WebBIOS:
enter image description here

Can anyone provide any suggestions on how to identify the problematic disk?

Smartmontools has an extended function that allows it to poll the drive through LSI (and other) RAID arrays for SMART data. Normally, this is not something you can do , Because the RAID abstraction obscures the direct interface with the drive.

Smartmontools may not be installed on your computer. However, it is native to most “main repositories” of most distributions , There is even a Windows version: http://sourceforge.net/projects/smartmontools/files/

It can be used to poll the drives behind the LSI MegaRAID controller, as shown below:

smartctl -a -d megaraid,N /dev/sdX

where “-a” means display all disk data, -d means device type (megaraid is the type in your case), followed by N represents the drive letter in that controller. To access the drive in slot 0, you can say 0 here. If you wish to poll all four drives, run this command four times, replacing N with 0 to 3. sdX is the RAID abstraction itself, usually seen in the operating system. Yours may be sda.

You will see the long output of each drive, and what you are looking for is the general SMART of the report Failure (you may not find it because your controller did not reject the drive), or report “Offline Uncorrectable Sector” or “Pending Sector”. Any drive exceeding 0 in this field is wrong. No Mercy should be given to these fields, because it requires a lot of failed reads to increment the value by 1.

You can also perform short-term or long-term testing like this (the same rules as above apply):

< p>smartctl -t [long | short] -d megaraid,N / dev / sdX

WordPress database error: [Table 'yf99682.wp_s6mz6tyggq_comments' doesn't exist]
SELECT SQL_CALC_FOUND_ROWS wp_s6mz6tyggq_comments.comment_ID FROM wp_s6mz6tyggq_comments WHERE ( comment_approved = '1' ) AND comment_post_ID = 1419 ORDER BY wp_s6mz6tyggq_comments.comment_date_gmt ASC, wp_s6mz6tyggq_comments.comment_ID ASC

Leave a Comment

Your email address will not be published.