Hello, Pondule. Honestly from the surface, it looks and sounds like some simple firmware errors being accumulated, and an update might fix that. I generally see that when there's "destination driver error" and the Component location is "none". BUT, I'd like to take a deeper look and verify that. I sent you an email, and I'll wait for the full support bundle.  Let me know if you have any questions. Looking forward to hearing from you. 
Got  simple dual node Windows Cluster which uses MD3000 dual controller as shared storage. Very stable but I think the self-healing features of the storage may be masking a hardware fault. Can anyone explain the log entries in more detail for me so I know what part to replace? Recovery guru says nothing is wrong but a 1707 critical alert was sent to the monitoring software so it's not all that happy. Can't see how to attach the majoreventlog.txt file so pasting snippets from it...  Description: Controller tray component changed to optimalEvent specific codes: 0/0/0Component type: FanComponent location: Enclosure 0, Slot 0 Description: Controller tray component changed to optimalEvent specific codes: 0/0/0Component type: Power Supply/Cooling Fan moduleComponent location: Enclosure 0, Slot 0 Description: Host card or switch card recovered successfullyEvent specific codes: 0/0/0Component type: Host Board Description: Alternate controller checked in lateEvent specific codes: 0/0/0Component type: RAID Controller ModuleComponent location: RAID Controller Module in slot 0 Description: Destination driver errorEvent specific codes: 0/0/0Component type: Physical DiskComponent location: NoneLogged by: RAID Controller Module in slot 0 Description: Destination driver errorEvent specific codes: 0/0/0Component type: Physical DiskComponent location: NoneLogged by: RAID Controller Module in slot 0 Description: Start-of-day routine completedEvent specific codes: 0/0/0Component type: RAID Controller ModuleComponent location: RAID Controller Module in slot 1Logged by: RAID Controller Module in slot 1 Description: One or more Sundry regions createdEvent specific codes: 0/0/0Component type: RAID Controller Module FirmwareComponent location: NoneLogged by: RAID Controller Module in slot 1 Description: Host card or switch card recovered successfullyEvent specific codes: 0/0/0Component type: Host BoardComponent location: None Description: Start-of-day routine begunEvent specific codes: 0/0/0Component type: RAID Controller ModuleComponent location: RAID Controller Module in slot 1Logged by: RAID Controller Module in slot 1 Description: All connections established through wide portEvent specific codes: 0/0/0Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan) Description: Single connection established through previously failed wide portEvent specific codes: 0/0/0Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan) Description: Controller quiescence haltedEvent specific codes: 0/0/0Component type: RAID Controller ModuleComponent location: RAID Controller Module in slot 0 Description: Cache mirroring on controllers not synchronizedEvent specific codes: 0/0/0Component type: RAID Controller ModuleComponent location: RAID Controller Module in slot 0 Description: Destination driver errorEvent specific codes: 0/0/0Component type: Physical DiskComponent location: NoneLogged by: RAID Controller Module in slot 0 Description: Degraded wide port becomes failedEvent specific codes: 0/0/0Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)  All these events happened between 1:03 and 1:05 AM. It's now 1:21 AM so I'm going to bed hoping someone can post an explanation of how to deal with it while I sleep. I can email the whole majoreventlog.txt in the morning if needed. Thanks. 
MD3000 slightly unwell?