Repair volume command for dynamic mirrored volumes. Reactivate volume command. Bring a dynamic volume back to a healthy state Prev Resolving common problem situations Next. Bring a dynamic volume back to a healthy state. What sort of equipment are you running.
What make server is it? Most known brand Servers offer diagnositics to troubleshoot any problems you might have, check on the manufacturers website for any tools you can use to establish the cause, it might just save you a lot of work I had a similar issue at our sister company. The UPS would run for awhile and then kick out completely no notification or anything and the server would reboot, it eventually corrupted everything so badly that I had no choice but to do a complete re-installation.
This is a great reason to have everything locked up in a cabnet and NO ONE else is allowed access to it! Had this happen on an XP workstation recently. In our case other machines on the network couldn't see it, network scans weren't hitting it except Spiceworks for some reason. Nothing in the logs to explain why it happened, but the machine was fine after we rebooted it and no problems since.
To continue this discussion, please ask a new question. Spiceworks Help Desk. The help desk software for IT. Thank Christ for that. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
I have the same question Report abuse. Details required :. Cancel Submit. TaurArian MVP. How satisfied are you with this reply? And any network shares associated with the dynamic disk would be lost unshared.
The dynamic disk would need to be activated manually in Disk Manager. Then I would have to reshare the folders I wanted shared, and set the share permissions. Dynamic disks have certain advantages on paper that make them see like a good choice, but Microsoft pulled another undocumented fubar here with the iSCSI devices.
They have reportedly fixed it in newer MS operating systems, but of course have no pressing motivation to go back and patch it in the Windows Server OS. This failure to reactivate has something to do with the timing and order of operations during the boot processes. Disk Management loads either too soon or too late for the dynamic disk to be activated automatically at startup.
I discovered a scripted solution to reactivate the affect dynamic disk at startup without user intervention using a bat file and setting startup options in Windows Server Group Policy. Note: It should be obvious to many Administrators, but just in case You will need to ignore the dashes Htike Win puts in front of the commands. He uses them like bullet characters, but they should not be included in the batch file and text file you will create.
Also, the quotes characters shown on his web page are smart quotes, which are not recognized by Windows commands. You need to retype those as simple quotes in the batch script. Just retype the "quote" characters on the keyboard and you will be fine. That runs after the diskpart command completes and then provides a simple text log of the reboot times. It is a redundancy that I build into some of my batch scripts when I want to be able to double check if they are running regularly.
Next, if you have network shares that you set up with that iSCSI drive, you will want another script using net share commands to reshare the resource and set permissions.
0コメント