Using cluster.exe to create physical disks

I'm trying to write a script that will automate our cluster creation process.
Everything works except sometimes the disk creation command doesn't work.

It creates the physical disk but occasionally gives this error when
assigning the drive letter.

System error 2 has occurred (0x00000002).
The system cannot find the file specified.

These are the commands I am running
cluster resource "Disk R:" /create /group:group1 /type:"Physical Disk"
cluster resource "Disk R:" /priv drive="R:"
cluster resource "Disk R:" /on

check if you can access R:\ before you run your script.
then ensure your cluster group is online on the node where R:\ is

re-try your script,
let us know
HTH,
Edwin.


"bucktaylor100" <> wrote in message
news:7283C557-75F2-4DED-838E-...
> I'm trying to write a script that will automate our cluster creation
process.
> Everything works except sometimes the disk creation command doesn't work.
>
> It creates the physical disk but occasionally gives this error when
> assigning the drive letter.
>
> System error 2 has occurred (0x00000002).
> The system cannot find the file specified.
>
> These are the commands I am running
> cluster resource "Disk R:" /create /group:group1 /type:"Physical Disk"
> cluster resource "Disk R:" /priv drive="R:"
> cluster resource "Disk R:" /on

It's a 2 node cluster and while both can see drive R in my computer only one
server can access it. I guess that's the problem. I guess the question
becomes how do I get the one drive to the other server when the cluster isn't
fully built yet?

"Edwin vMierlo [MVP]" wrote:

> check if you can access R:\ before you run your script.
> then ensure your cluster group is online on the node where R:\ is
>
> re-try your script,
> let us know
> HTH,
> Edwin.
>
>
> "bucktaylor100" <> wrote in message
> news:7283C557-75F2-4DED-838E-...
> > I'm trying to write a script that will automate our cluster creation
> process.
> > Everything works except sometimes the disk creation command doesn't work.
> >
> > It creates the physical disk but occasionally gives this error when
> > assigning the drive letter.
> >
> > System error 2 has occurred (0x00000002).
> > The system cannot find the file specified.
> >
> > These are the commands I am running
> > cluster resource "Disk R:" /create /group:group1 /type:"Physical Disk"
> > cluster resource "Disk R:" /priv drive="R:"
> > cluster resource "Disk R:" /on
>
>
>

That's not it. You shouldn't be trying to mount the disk on the other node
or trying to access it.

The error 2 is occurring because for whatever reason, cluster cannot find an
entry in the registry for the R: disk...I'd check the
HKLM/System\CCSet\MountedDevices keys for starters to see if you've got a
\DosDevices\R: entry on the node where you're running these commands. If
not, something in your procedure for creating this volume is not working
properly.

For your cluster.exe script, you could try using the command syntax "cluster
res "Disk R:" /priv Signature=<value>" instead. If the host sees a disk with
this signature, it should work.

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner


"bucktaylor100" <> wrote in message
news:27A3E657-E367-485A-8C7C-...
> It's a 2 node cluster and while both can see drive R in my computer only
one
> server can access it. I guess that's the problem. I guess the question
> becomes how do I get the one drive to the other server when the cluster
isn't
> fully built yet?
>
> "Edwin vMierlo [MVP]" wrote:
>
> > check if you can access R:\ before you run your script.
> > then ensure your cluster group is online on the node where R:\ is
> >
> > re-try your script,
> > let us know
> > HTH,
> > Edwin.
> >
> >
> > "bucktaylor100" <> wrote in
message
> > news:7283C557-75F2-4DED-838E-...
> > > I'm trying to write a script that will automate our cluster creation
> > process.
> > > Everything works except sometimes the disk creation command doesn't
work.
> > >
> > > It creates the physical disk but occasionally gives this error when
> > > assigning the drive letter.
> > >
> > > System error 2 has occurred (0x00000002).
> > > The system cannot find the file specified.
> > >
> > > These are the commands I am running
> > > cluster resource "Disk R:" /create /group:group1 /type:"Physical Disk"
> > > cluster resource "Disk R:" /priv drive="R:"
> > > cluster resource "Disk R:" /on
> >
> >
> >

I checked the registry key and all the disks exist. If I use the GUI to
create the disks it works just fine every time. I could do it via the disk
signature but I'm attempting to do up to 40 of them via a script. I don't
know of any easy way to get the disk signature and parse it into my script.
It's completelly hit or miss. Sometimes it works flawlessly and other times
it errors out. I'm puzzled on this.

"John Toner [MVP]" wrote:

> That's not it. You shouldn't be trying to mount the disk on the other node
> or trying to access it.
>
> The error 2 is occurring because for whatever reason, cluster cannot find an
> entry in the registry for the R: disk...I'd check the
> HKLM/System\CCSet\MountedDevices keys for starters to see if you've got a
> \DosDevices\R: entry on the node where you're running these commands. If
> not, something in your procedure for creating this volume is not working
> properly.
>
> For your cluster.exe script, you could try using the command syntax "cluster
> res "Disk R:" /priv Signature=<value>" instead. If the host sees a disk with
> this signature, it should work.
>
> Regards,
> John
>
> Visit my blog: http://msmvps.com/blogs/jtoner
>
>
> "bucktaylor100" <> wrote in message
> news:27A3E657-E367-485A-8C7C-...
> > It's a 2 node cluster and while both can see drive R in my computer only
> one
> > server can access it. I guess that's the problem. I guess the question
> > becomes how do I get the one drive to the other server when the cluster
> isn't
> > fully built yet?
> >
> > "Edwin vMierlo [MVP]" wrote:
> >
> > > check if you can access R:\ before you run your script.
> > > then ensure your cluster group is online on the node where R:\ is
> > >
> > > re-try your script,
> > > let us know
> > > HTH,
> > > Edwin.
> > >
> > >
> > > "bucktaylor100" <> wrote in
> message
> > > news:7283C557-75F2-4DED-838E-...
> > > > I'm trying to write a script that will automate our cluster creation
> > > process.
> > > > Everything works except sometimes the disk creation command doesn't
> work.
> > > >
> > > > It creates the physical disk but occasionally gives this error when
> > > > assigning the drive letter.
> > > >
> > > > System error 2 has occurred (0x00000002).
> > > > The system cannot find the file specified.
> > > >
> > > > These are the commands I am running
> > > > cluster resource "Disk R:" /create /group:group1 /type:"Physical Disk"
> > > > cluster resource "Disk R:" /priv drive="R:"
> > > > cluster resource "Disk R:" /on
> > >
> > >
> > >
>
>
>

That could be why Drive= is a "hidden" value for the LUNs in 2003 ;-)

If you re-try the command, does it work the second time?

You can use dumpcfg to get the signature value of the disk or you could try
diskpart

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

"bucktaylor100" <> wrote in message
news:04C487C3-E8A2-4497-A11C-...
> I checked the registry key and all the disks exist. If I use the GUI to
> create the disks it works just fine every time. I could do it via the disk
> signature but I'm attempting to do up to 40 of them via a script. I don't
> know of any easy way to get the disk signature and parse it into my
script.
> It's completelly hit or miss. Sometimes it works flawlessly and other
times
> it errors out. I'm puzzled on this.
>
> "John Toner [MVP]" wrote:
>
> > That's not it. You shouldn't be trying to mount the disk on the other
node
> > or trying to access it.
> >
> > The error 2 is occurring because for whatever reason, cluster cannot
find an
> > entry in the registry for the R: disk...I'd check the
> > HKLM/System\CCSet\MountedDevices keys for starters to see if you've got
a
> > \DosDevices\R: entry on the node where you're running these commands. If
> > not, something in your procedure for creating this volume is not working
> > properly.
> >
> > For your cluster.exe script, you could try using the command syntax
"cluster
> > res "Disk R:" /priv Signature=<value>" instead. If the host sees a disk
with
> > this signature, it should work.
> >
> > Regards,
> > John
> >
> > Visit my blog: http://msmvps.com/blogs/jtoner
> >
> >
> > "bucktaylor100" <> wrote in
message
> > news:27A3E657-E367-485A-8C7C-...
> > > It's a 2 node cluster and while both can see drive R in my computer
only
> > one
> > > server can access it. I guess that's the problem. I guess the question
> > > becomes how do I get the one drive to the other server when the
cluster
> > isn't
> > > fully built yet?
> > >
> > > "Edwin vMierlo [MVP]" wrote:
> > >
> > > > check if you can access R:\ before you run your script.
> > > > then ensure your cluster group is online on the node where R:\ is
> > > >
> > > > re-try your script,
> > > > let us know
> > > > HTH,
> > > > Edwin.
> > > >
> > > >
> > > > "bucktaylor100" <> wrote in
> > message
> > > > news:7283C557-75F2-4DED-838E-...
> > > > > I'm trying to write a script that will automate our cluster
creation
> > > > process.
> > > > > Everything works except sometimes the disk creation command
doesn't
> > work.
> > > > >
> > > > > It creates the physical disk but occasionally gives this error
when
> > > > > assigning the drive letter.
> > > > >
> > > > > System error 2 has occurred (0x00000002).
> > > > > The system cannot find the file specified.
> > > > >
> > > > > These are the commands I am running
> > > > > cluster resource "Disk R:" /create /group:group1 /type:"Physical
Disk"
> > > > > cluster resource "Disk R:" /priv drive="R:"
> > > > > cluster resource "Disk R:" /on
> > > >
> > > >
> > > >
> >
> >
> >