Conference decwet::winnt-clusters

596.0. "Cluster scratch disk and reconfigure" by ROMTSS::MATTACCHIONE () Mon Feb 03 1997 16:11

Hi,

I have many problem to reconfigure the Dec Nt cluster.
I have stop the cluster process then run the deinstallation precedure,
that on both cluster nodes.

Then I have format the Raid 410 disk with the hszutil and reconstruct the
Raidset.

On this disk there was the log disk (physical drive 1).
Actually it is on another raidset (physical drive 0).
Have reinstalled the Dec Nt cluster software on both cluster nodes
and reboot the node in sequence.

Then I have reconfigured it, but the old log disk have many problem:
I can't access to it in any manner.It is falgged on the disk administartor
like unknow, Offline.
I can't manipulate it, and can't format it because a message say me that
a Windows Nt system file is on it!

 I have checked all the registries like written in the release notes and
administrator guide before reinstall the kit, but all the registries
are been deleted from the deinstall procedure.


I suppose that in anywhere in the system  the disk information is maintained
but I  don't know where search it!

Then the last solution is scratch all the Winnt O.S. and restart from it.


Any suggestions are  very,very  appreciated!
 
Gabriele


Follow the report in the cluster log file 


    File: F:\CLUBUILD.351\src\fm\fmcore\fmstartup.c    Line: 367
18:07:42.718 tid=153 Could not read signature for device \\.\PhysicalDrive1.
Either the device is not responding, or the Cluster software
could not negotiate access to the device from the other member.
The device will not be eligible to be brought ON LINE until
this problem is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdb.c    Line: 155
18:07:42.812 tid=153 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive1.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:07:42.906 tid=153 Error opening object FMDisk\_disk_11c6482e
18:07:42.953 tid=153 No such Cfmd class or object.
    File: F:\CLUBUILD.351\src\fm\fmlib\fmdbobj.c    Line: 863
18:07:43.031 tid=153 Failed to create disk _disk_11c6482e
18:07:43.093 tid=153 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive0.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:07:43.187 tid=153 CFMD logging disk is UNDEFINED (no disks available)
18:07:47.921 tid=152 Could not read signature for device \\.\PhysicalDrive1.
Either the device is not responding, or the Cluster software
could not negotiate access to the device from the other member.
The device will not be eligible to be brought ON LINE until
this problem is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdb.c    Line: 155
18:07:48.109 tid=152 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive1.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:07:48.390 tid=152 Error opening object FMDisk\_disk_11c6482e
18:07:48.437 tid=152 No such Cfmd class or object.
    File: F:\CLUBUILD.351\src\fm\fmlib\fmdbobj.c    Line: 863
18:07:48.515 tid=152 Failed to create disk _disk_11c6482e
18:07:48.562 tid=152 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive0.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:10:45.031 tid=153 Could not read signature for device \\.\PhysicalDrive1.
Either the device is not responding, or the Cluster software
could not negotiate access to the device from the other member.
The device will not be eligible to be brought ON LINE until
this problem is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdb.c    Line: 155
18:10:45.125 tid=153 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive1.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:10:45.218 tid=153 Error opening object FMDisk\_disk_11c6482e
18:10:45.265 tid=153 No such Cfmd class or object.
    File: F:\CLUBUILD.351\src\fm\fmlib\fmdbobj.c    Line: 863
18:10:45.343 tid=153 Failed to create disk _disk_11c6482e
18:10:45.390 tid=153 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive0.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:10:45.484 tid=153 The specified network resource or device is no longer
available.
    File: F:\CLUBUILD.351\src\fm\fmdisk\management.c    Line: 476
18:10:47.281 tid=63  Could not read signature for device \\.\PhysicalDrive1.
Either the device is not responding, or the Cluster software
could not negotiate access to the device from the other member.
The device will not be eligible to be brought ON LINE until
this problem is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdb.c    Line: 155
18:10:47.375 tid=63  The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive1.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:10:47.484 tid=63  Error opening object FMDisk\_disk_11c6482e
18:10:47.515 tid=63  No such Cfmd class or object.
    File: F:\CLUBUILD.351\src\fm\fmlib\fmdbobj.c    Line: 863
18:10:47.609 tid=63  Failed to create disk _disk_11c6482e
18:10:47.656 tid=63  The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive0.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:10:47.750 tid=63  The specified network resource or device is no longer
available.
    File: F:\CLUBUILD.351\src\fm\fmdisk\management.c    Line: 476
18:12:15.078 tid=164 Could not read signature for device \\.\PhysicalDrive1.
Either the device is not responding, or the Cluster software
could not negotiate access to the device from the other member.
The device will not be eligible to be brought ON LINE until
this problem is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdb.c    Line: 155
18:12:15.171 tid=164 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive1.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:12:15.265 tid=164 Error opening object FMDisk\_disk_11c6482e
18:12:15.312 tid=164 No such Cfmd class or object.
    File: F:\CLUBUILD.351\src\fm\fmlib\fmdbobj.c    Line: 863
18:12:15.406 tid=164 Failed to create disk _disk_11c6482e
18:12:15.437 tid=164 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive0.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:12:15.531 tid=164 CFMD logging disk is UNDEFINED (no disks available)
18:12:16.843 tid=152 Could not read signature for device \\.\PhysicalDrive1.
Either the device is not responding, or the Cluster software
could not negotiate access to the device from the other member.
The device will not be eligible to be brought ON LINE until
this problem is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdb.c    Line: 155
18:12:16.921 tid=152 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive1.  The disk cannot be brought online until this
condition is corrected.
    File: F:\CLUBUILD.351\src\fm\fmdisk\diskdata.c    Line: 238
18:12:17.015 tid=152 Error opening object FMDisk\_disk_11c6482e
18:12:17.062 tid=152 No such Cfmd class or object.
    File: F:\CLUBUILD.351\src\fm\fmlib\fmdbobj.c    Line: 863
18:12:17.140 tid=152 Failed to create disk _disk_11c6482e
18:12:17.187 tid=152 The Disk DLL was unable to create the initial entry in the configuration
database for disk PhysicalDrive0.  The disk cannot be brought online until this
condition is corrected.

  
>Then I have format the Raid 410 disk with the hszutil and reconstruct the
>Raidset.

>I can't manipulate it, and can't format it because a message say me that
>a Windows Nt system file is on it!

  You may have really confused NT if you re-formatted the raidset
  without first deleting the disk partition via disk administrator.

  Based on the fm log, it seems that NT still thinks there's a disk
  partition which could reflect the previous raidset.

  If this makes any sense, verify that you don't have any bogus
  disk partitions. If so, delete them. Build the storageset
  again. Create new paritions. Reinstall Nt clusters. 

  I hope this helps.



  

Hi,

I have found a possible solution.
Deinstallation procedure don't remove the cluster directory where
some Dec Cluster file remain.
I suppose that any file check if the  _digitalclusterlog file
are on my disk(s) and don't permit me to manipulate its (them) with
Disk Administrator.

Then
I have deleted Cluster directory situated under Program Files->Digital
and reinstalled the Dec Cluster.
All is gone OK!!!!

I things that is a good idea insert this possible situation in the 
release notes.


Regards 
Gabriele