We'd exactly the same error last week but then figured out that the sysadmin rebooted one node with the wrong image.Reverting the right image fixed it. Damn sysadmins.. ;) On Wed, Apr 30, 2014 at 3:51 PM, Chris King <ckaj111@xxxxxxxx> wrote: > Thanks for catching that.. The nodes are VMs and I'm told the VM handles > it as an internal drive, but it physically resides on a SAN. > > > > > On Wednesday, April 30, 2014 3:41:48 PM, Chris Taylor < > christopherdtaylor1994@xxxxxxxxx> wrote: > Before this gets off track, perhaps Chris you could tell us where they > added disks? What I mean by that is, some servers are built with the root > volume as a mirrored set of INTERNAL disks inside the server itself. These > are physical hard drives in the machine. > > Some places build servers with the root volume as a volume presented from > a storage array so what Mark is talking about is more relevant to volumes > presented to servers from an outside storage array, but might not be as > appropriate if you were talking about physical disks inside the server > itself. > > Also there is locally attached storage which is a third option (like an > array of disks that attach to the specific server only) > > Chris > > > On Wed, Apr 30, 2014 at 2:32 PM, Chris King <ckaj111@xxxxxxxx> wrote: > > Thanks. We're trying your suggestion now and will rebuild if it doesn't > work.. Thanks for the clarification.. I kinda figured they hosed me.. > > > >