[Linux-PowerEdge] MD3000 preferred path not working
nick.lunt at patech-solutions.com
Thu Jul 18 05:12:06 CDT 2013
No, not 1000000% sure the array hardware is OK, but MDSM (and Dell) say it
2 x SAS 5/E dual port cards.
Md3000 + 3 MD1000's attached.
Both SAS cards have firmware 00.10.51.00.06.12.05.00
The whole lot has been bounced many times over the past week.
I can't imagine how a disk replacement can lead to all this either, it's a
[image: Nick Lunt | Applications DBA Patech Solutions Limited Tame House,
Wellington Crescent, Fradley Park, Lichfield, WS13 8RZ T:: +44(0)1543 444
707 | M:: +44(0)7554 003 634 E:: Nick.Lunt at Patech-Solutions.com W::
On 18 July 2013 10:59, <G.Bakalarski at icm.edu.pl> wrote:
> Are you 10000000% sure all diskarray hardware is OK ???
> And what SAS cards - server HBA or diskarray controllers ???
> Is it single box diskarray or you have expansion enclosures???
> Single/dual controller ???? (if there are expansions: single/dual pathed
> If dual controller (in case you replaced any) : are controllers' firmwares
> Did you power off/on all componets ?
> I can't imagine how regular disk exchange can make such disaster nowadays
> > we had a disk fail in an MD3000 last week which was replaced under
> > warranty. However, during the replacement of the disk something happened
> > and we ended up getting 2 new SAS cards, MD3000 controllers and a new
> > backplane for the MD3000. This took a week to fix costing us thousands.
> > Now were just about back online, but we are getting these errors from the
> > MD3000:
> > Summary
> > Node ID: WFSC_NON_PROD_SAS
> > Host IP Address: 10.69.0.21
> > Host ID: fintestdb.wales.nhs.uk
> > Event Error Code: 4011
> > Event occurred: Jul 18, 2013 9:51:43 AM
> > Event Message: Virtual Disk not on preferred path due to AVT/RDAC
> > Component type: RAID Controller Module
> > Component location: RAID Controller Module in slot 0
> > Priority:Critical
> > The only way we seem to be able to stop getting these error messages is
> > set the preferred path to path 0 for all luns.
> > Now, we have the exact same setup on another server, but using the
> > preferred paths and we are having none of these issues. Both these
> > have the same OS and MD3000 setup.
> > Could anyone please shed some light on why the server that's just been
> > 'fixed' is generating these errors unless we assign all luns to path 0?
> > Thanks
> > Nick .
> > _______________________________________________
> > Linux-PowerEdge mailing list
> > Linux-PowerEdge at dell.com
> > https://lists.us.dell.com/mailman/listinfo/linux-poweredge
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Linux-PowerEdge