Hi, Thanks for the controller log. I see that drive 1 failed due to timeouts back in November and was replaced by the hot spare. Drive 1 was then copyback by drive 3 which was the hot spare and inserted back into the virtual drive. There weren't any errors being reported on drive 1. The timeouts could be caused by another drive. Drive 0 has had several block errors (sense code 3:11:0 Medium Error - unrecovered read error)  and continues to do so. it will probably go predictive fail in the future after enough errors occur. You can wait for the drive to go predictive fail and replace at that point or proactively replace. Seeing that the medium error is being recovered. "Corrected medium error during recovery on PD 00".
i have Raid-5 config with 3 HD(3TB) and 1 Hotspare. I already run Consistency check but still after running, bad blocks persist. Is it safe now to run "Clear Virtual disk Bad Blocks"??? Right now the Read Patrol is still running. I am planning to replace the disk with Bad Blocks but i cannot pinpoint the disk with bad blocks as status of all disk are OK and online. In the logs this is what i saw,"Unexpected sense. SCSI sense data: Sense key: 1 Sense code: 0 Sense qualifier: 0:" on Physical disk 0:1:0 and Physical disk 0:1:2. Does this mean Physical disk 0:1:0 and Physical disk 0:1:2 are the disk wit bad blocks?? or How to pinpoint the disk with Bad blocks?? I cannot perform the backup as the backup exec fails even after running consistency check. Help please....
The Virtual Disk has bad blocks on Poweredge r720