On Fri, Jul 16, 2010 at 6:22 PM, Linda Messerschmidt <linda.messerschm...@gmail.com> wrote: >> I have swapped drives, swapped controllers, swapped cables, >> swapped drive carriers and swapped drive bays, and the problem >> always stays in place > > To follow up to this issue, I did eventually track this issue back to a bad > drive. What threw me off is that the LSI SAS controllers apparently > "remember" what SCSI ID they give to a particular device, and that persists > even if you move the drive from one bay to another. So once I eventually > figured that out, I was able to isolate a single drive and confirm it was bad > from another system. > > I'd actually really like to reset the LSI controllers' ideas of what drives > get what ID's, if anybody happens to know how to do that! I can think of > applications where that would be useful, but this isn't one of them.
This presentation should help you understand how OpenSolaris creates the device names based on disk information: http://www.jmcp.homeunix.com/~jmcp/WhatIsAGuid.pdf Personally I prefer to work that way. I can easily match the disk serial to the slot number and light up the location LED. Having a legacy of MegaRAID controllers to manage, I find the fact that each new RAID-0 volume gets a different LUN ID and OpenSolaris allocates the device name randomly (well, it tries to fill the empty slots), pretty annoying when trying to replace a faulty disk. -- Giovanni Tirloni gtirl...@sysdroid.com _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
