Summary of steps that I am attempting:
- Detach OS volume from Windows_Server_A
- Attach volume to Windows_Server_B
- Modify a harmless file
- Detach from B and reattach at /dev/sda1 for Windows_Server_A
- Boot Successfully
This is not working. The attach / disk management online/offline / detach process is causing the volume to NOT boot when it returns to Server_A
** Detailed Steps**
- Detach OS volume from EC2 windows 2012 instance. Let this be Volume_X
- Attach Volume_X to a temporary EC2 windows instance
- In Disk Management of temporary EC2 server, turn new volume online
- Note that there are two partitions. One small one (350MB) without a drive letter and one large one (100GB). The large one gets a drive letter assigned: G
- Navigate to a particular file on G drive
- Modify the file
- Close all windows
- Turn drive offline in Disk Management
- Shut down temporary EC2 server
- Detach Volume_X from temporary server
- Re-Attach Volume_X to its original server at mount point /dev/sda1
- Attempt to boot original server
The instance never gets past "initialized" and going to Instance Settings - Get Screenshot yields the following:
To isolate the problem, I tried without modifying a file:
- With a fresh, working copy of Volume_X. Detach from Original server. Attach to alternate server.
- All I did was turn the drive "online" and then 2 seconds later turned it "offline" without modifying any data on the drive.
- Reattaching to the original server yields the same exact problem
Thus, it appears that I am corrupting Volume_X by simply attaching it and turning it "online" (disk management) on a separate server.
What is the proper way to move a windows OS volume to another server, for file modification, to then be returned to its original instance and successfully booted from?
- Stop original server
- Detach volume
- Attach volume to alternate server
- ????? then modify a file then ?????
- Detach volume from alternate server
- Attach volume to original server
- original server should boot fine
Thanks for your time