cancel
Showing results for 
Search instead for 
Did you mean: 

Unknown Dg and Foreign disk after importing a used LUN - Win2k8

RNebular
Level 3
Hopefully someone has an answer for this. I have SFW 5.1 SP1 installed on a Windows 2008 virtual machine. I import a Raw LUN that was previously formatted in Windows Disk Management of another decommissioned server as a Dynamic disk and Simple Volume. In SFW it shows up as Foreign and a part of an Unknown Dg. I have tried to use vxtool to wipe the disk but get the error: vxtool: nt_write_dev: WriteFile(): The media is write protected. vxtool: Cannot write data I know the LUN device itself should still be write enabled at the array because the masking worked on the previous server. I ran "vxcrub.exe -p" and get the following error: Disk: MPIO\DISK&VEN_DGC&PROD_VRAID&REV_0326\1&7F6AC24&0&60_6_160_75D1E202A5AD3F8 4290DF1120 failed to get uninstalled VxScrub ERROR: Disks()!CallClassInstaller(REMOVE) FAILURE: (0xe0000235) MPIO\DISK&VEN_DGC&PROD_VRAID&REV_0326\1&7F6AC24&0&60_6_160_75D1E202A5AD3F84290DF 1120 Anyone have any ideas what I could do to clear off the previous Microsoft Disk Management header information? I really don't want to have to completely destroy the volume and recreate it.
1 ACCEPTED SOLUTION

Accepted Solutions

RNebular
Level 3
Found my own resolution on this....
Basically I had another single local volume on the server that I had made dynamic within Microsoft Disk Management, so all other LUN devices that had previously been on the server still thought they were part of the basic Dynamic Disk Group that MS creates. I converted the last remaining Microsoft dynamic disk group into SFW, and now all other disks and the foriegn diskgroup can now be manipulated as expected.

Long story short, the Microsoft Dynamic Disk Group and the SFW disk groups didn't play well together. By converting them all to SFW disk groups, all of my "Unknown Dg" objects turned into proper SFW disk groups again.

View solution in original post

1 REPLY 1

RNebular
Level 3
Found my own resolution on this....
Basically I had another single local volume on the server that I had made dynamic within Microsoft Disk Management, so all other LUN devices that had previously been on the server still thought they were part of the basic Dynamic Disk Group that MS creates. I converted the last remaining Microsoft dynamic disk group into SFW, and now all other disks and the foriegn diskgroup can now be manipulated as expected.

Long story short, the Microsoft Dynamic Disk Group and the SFW disk groups didn't play well together. By converting them all to SFW disk groups, all of my "Unknown Dg" objects turned into proper SFW disk groups again.