I have a few servers with Intel S3420GPLC server board using Intel Embedded server RAID Technology II.
All servers have Windows Server 2008 R2 64bit. Running Hyper-V role
BIOS Version A.09.07211059I
I have all running fine but I am unable to get Patrol Read to work. When I try to save settings for Patrol read I get "Command failed by Operating System" error.
RAID Web Console 2 - 9.00.0000
This problem just got more serious as one of my RAID1 virtual drives seems to have bad sectors and Intel Raid is unable to cope with it. Of course virtual machines are in this volume :-) A few lines form raid log:
D = 143
SEQUENCE NUMBER = 37
TIME = 05-05-2012 22:06:43
LOCALIZED MESSAGE = Controller ID: 0 Unexpected sense: PD = 0:2 - No addtional sense information, CDB = 0x28 0x00 0x00 0xbe 0xbb 0x4a 0x00 0x00 0x01 0x00 , Sense = 0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x80 0x00 0x02
ID = 142
SEQUENCE NUMBER = 36
TIME = 05-05-2012 22:06:42
LOCALIZED MESSAGE = Controller ID: 0 Unrecoverable medium error during recovery: PD 0:2 Location 0xbebb49
Now I need to do something to fix situation. What would you suggest?
- Start Initialization on affected VD
- Start Consistency check on affected VD
- run CHKDSK /R on parent VD
- run CHKDSK /R "inside" virtual machines
For a start you definitely don't want to be initializing any of your VDs as it will wipe all your data!
If you are not having any luck with the RAID tools then perhaps shut the system down and scan the drives on another system using seatools or similar utility. If you find a faulty drive, then boot your system back up without the faulty drive so it can mark the VD as degraded and then replace it with a new drive.
It's also worth making sure you have the latest BIOS/BMC/FRU as well as RAID drivers installed.
A few months later and I'm sure your drives were repaired by now but just for some peace of mind you can check this thread: /message/96509# 96509 http://communities.intel.com/message/96509# 96509
I'm sure that as a one time solution you could have run a consistency check from the ESRT2 bios console.
Also, I am having a somewhat similar problem here: /thread/31015 http://communities.intel.com/thread/31015 so if you can share your solution it would be great.