Adaptec Controller showed all 4 drives with status failed and the array was on failed too. It is surprisingly often that it’s not disk who is at fault, but SCSI bus. Is there any way to find out why the Raid and all drives failed? Post as a guest Name. Ben Short 1 6
|Date Added:||23 May 2005|
|File Size:||67.18 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
ADAPTEC 2010S LOW PROFILE PCI RAID CONTROLLER
I did get timeouts from the tapedrive when i tried to eject winddows tape and short after this i had the crash. I used raidutil to force it back to optimal state after reboot didn’t help at all.
Super Micro Computer, Inc. | Support | FAQs
Ben Short 1 6 aadaptec It is surprisingly often that it’s not disk who is at fault, but SCSI bus. When the vendor was called in to explain, it was found that the firmware revision had a fault where it would cause striping errors on the RAID5 array.
Adaptec Controller showed all 4 drives with status failed and the array was on failed too. Post as a guest Name.
Will the Adaptec Storage Manager check this for me? Home Questions Tags Users Unanswered.
Sign up or log in Sign up using Google. Updating the firmware resolved the issue. Might also pay to investigate the firmware revision of your raid controller, and if it is out of date see if there any any major bugfixes in a new version. Sign up using Email and Password.
Could it be that some broken tape in a tapedrive on the same controller caused all iwndows troubles?