Re: Move fails - some drives do not come online?
- From: "Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 11 Aug 2007 19:59:19 -0400
Yep, here are some problems:
00000dfc.00000d28::2007/08/11-23:21:18.078 ERR Physical Disk <Disk M:>: Online: Unable to open ClusDisk signature key 219631be. Error: 2.
00000dfc.000003ac::2007/08/11-23:21:20.656 ERR Physical Disk <Disk G:>: Online: Unable to open ClusDisk signature key 7f6a0381. Error: 2.
00000dfc.00000c8c::2007/08/11-23:21:20.656 ERR Physical Disk <Disk H:>: Online: Unable to open ClusDisk signature key 7f6a039e. Error: 2
00000dfc.00000e90::2007/08/11-23:21:23.578 ERR Physical Disk <Disk I:>: Online: Unable to open ClusDisk signature key be0dc20f. Error: 2.
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.
<doug.masters@xxxxxxxxx> wrote in message news:1186875589.107769.87260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for helping out, Chuck.
Unfortunately the error is all too reproducable. Cluster.log from
the failing node has been zipped & uploaded to http://www.dougmasters.com/cluster/
Sorry about the other log, however a more readable version of it was
posted as cluster.log.doc in Word format.
The 1069 error says:
"Cluster resouce 'Disk M:' in Resouce Group 'MSDTC' failed. (That
same error occurs for each disk that did not come online.)
I do see an error about the disk signature, but don't know what it
means to me really...
On Aug 11, 7:55 am, "Chuck [MSFT]" <cti...@xxxxxxxxxxxxxxxxxxxx>
wrote:
I looked over your cluster log, which was difficult to read as posted,
recommend next time saving the log, zip it and then post. If you can repro
the problem, capture the log from the node on which the disks fail to come
online, zip it up, report the log and then tell us which failures are being
mentioned in the Event ID 1069 messages in the system log, that may help.
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.
<doug.mast...@xxxxxxxxx> wrote in message
news:1186834580.798859.95390@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Another tidbit that may or may not be important. Server1 was a hand
> load, Server2 is a Ghost of Server1. Server1 was loaded to
> workgroup mode and just the basic common settings & custom settings
> were done. The drives on the DAS had not been configured yet.
> Made Ghost image with the -fdsp switches. Restored to Server2,
> booted, changed IPs', ran NewSID to apply new SID & change name.
> I honestly cannot remember if we used Ghost images in the previous
> builds.
> On Aug 10, 6:58 pm, doug.mast...@xxxxxxxxx wrote:
>> Trying to save myself a call to MS on Monday here!
>> First off: Documentation used to create the cluster & copies of the
>> cluster.log files are located athttp://www.dougmasters.com/cluster/
>> The only error logged in the Event Log is ClusSvc 1069
>> I have confidence with the document since it's been used many times to
>> create clusters at my work, document was created building cluster on
>> the exact same hardware that I am now having troubles with. After I
>> wrote the document all of my co-workers flattened the servers and
>> rebuilt with it so they would know how to do, never had problems.
>> Until this week...
>> Details:
>> Two Dell PE 6450 Servers, PERC cards in each. One PERC foir internal
>> drives, One PERC connected to external Dell SCSI Array
>> Windows Server 2003 Ent with SP1 at first. Installing SP2 didn't
>> help my life any. No other patches or software installed, these guys
>> are fresh & clean.
>> Problem:
>> All of the resources work just fine on Server1, but when I try to move
>> the Resource Groups to Server2, most of the disks "fail" and won't
>> come on-line. The Cluster Group with the Quorum disk comes up just
>> fine, as does one of the resource disks, but the MSDTC drive and three
>> of the other resource drives do not.
>> I am at a total loss, my co-worker has spent days re-doing this over
>> and over to the same result. I took over on it today and I'm having
>> the same problem. On Tuesday, this was a working active-active
>> SQL2000 cluster and is a ground up rebuild to get an active-active
>> SQL2005 cluster going.
>> Thanks for any help!- Hide quoted text -
- Show quoted text -
.
- Follow-Ups:
- Re: Move fails - some drives do not come online?
- From: doug . masters
- Re: Move fails - some drives do not come online?
- References:
- Move fails - some drives do not come online?
- From: doug . masters
- Re: Move fails - some drives do not come online?
- From: doug . masters
- Re: Move fails - some drives do not come online?
- From: Chuck [MSFT]
- Re: Move fails - some drives do not come online?
- From: doug . masters
- Move fails - some drives do not come online?
- Prev by Date: Re: Move fails - some drives do not come online?
- Next by Date: Re: Move fails - some drives do not come online?
- Previous by thread: Re: Move fails - some drives do not come online?
- Next by thread: Re: Move fails - some drives do not come online?
- Index(es):
Relevant Pages
|