This post is more than 5 years old
40 Posts
0
75232
February 10th, 2014 10:00
MD3000i 4011 error
Hello, a customer just had this error on their MD3000i:
" Node ID: CorSAN1
Host IP Address: horse.wlv.com/172.16.1.39 Host ID: horse.wlv.com Event Error Code: 4011 Event occurred: Feb 9, 2014 3:26:17 AM Event Message: Virtual Disk not on preferred path due to AVT/RDAC failover Component type: RAID Controller Module Component location: RAID Controller Module in slot 0 "
Everything seems to be fine in MDSM and normal. And this exact error occurred 2 months ago, but they never called it in. Does this indicate a RAID controller going bad? Something to worry about?
And advice would be appreciated!
Thanks!
DELL-Sam L
Moderator
•
7.7K Posts
0
February 10th, 2014 11:00
Hello stonewall40,
The alert on the system is due to a virtual disk not being on the preferred path. When virtual disks are created, they are assigned to one of the two controllers as a preferred communication path. If that path is not available – due to a network issue, controller reset, etc. – the array will communicate via the alternate controller. In some cases the communication does not shift back to the primary path when it becomes available again. To correct this you just need to manually redistribute the virtual disks back to their preferred paths.
To redistribute virtual disks:
1. Open Modular Disk Storage Manager (MDSM)
2. Click on the Support tab
3. Select Manage Raid Controller Modules
4. Click on Redistribute Virtual Disks
• You will get an alert telling you that this will disrupt communications if you do not have the multipath drivers installed. You can ignore this message and proceed. If you still have access to the virtual disk that is not on preferred path, you have multipath drivers installed
Please let us know if you have any other questions.
DELL-Sam L
Moderator
•
7.7K Posts
0
February 18th, 2014 08:00
Hello stonewall40,
The virtual disk can run on the secondary controller. There is no extra risk other than if a controller fails & if that happens it will revert back to the primary controller.
Please let us know if you have any other questions.
Dev Mgr
4 Operator
•
9.3K Posts
0
February 18th, 2014 08:00
There is no real direct risk by keeping the disk on the other controller, but it may cause you not to notice a 'real' change in status of the array.
Dev Mgr
4 Operator
•
9.3K Posts
0
February 12th, 2014 05:00
Also; something as simple as a server reboot could cause this error to pop up. When the server boots up, if one connection happens to come up a little faster than the other, the virtual disk may be 'pulled' to that controller and trigger this message.
stonewall40
40 Posts
0
February 18th, 2014 07:00
Thanks very much for the helpful replies!
Quick question: is there any risk in keeping the Array on the alternate controller or should it be moved back to the primary ASAP?
If the alternate fails, will it revert back to primary on it's own?
stonewall40
40 Posts
0
February 18th, 2014 08:00
Thanks again! Very helpful. Much appreciated!