Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 9, 2024 #62 Please run the following command again in the Recovery Environment and post the result. Code: create partition efi size=100
Please run the following command again in the Recovery Environment and post the result. Code: create partition efi size=100
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 10, 2024 #64 That's odd, please use the following commands: create volume simple size=100 Afterwards, if successful, run list part. select partition X (replace X with the number of your newly created partition) SET ID=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
That's odd, please use the following commands: create volume simple size=100 Afterwards, if successful, run list part. select partition X (replace X with the number of your newly created partition) SET ID=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
S Shenziro Well-known member Joined Jun 12, 2024 Posts 92 Jul 10, 2024 #65 Attachments 1720597345726.png 74.5 KB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 10, 2024 #66 Hhhm, I would suggest to restore this server with the created image. Then we can take a look at another option to solve this issue, even on a clone to test some things safely.
Hhhm, I would suggest to restore this server with the created image. Then we can take a look at another option to solve this issue, even on a clone to test some things safely.
S Shenziro Well-known member Joined Jun 12, 2024 Posts 92 Jul 10, 2024 #67 hm, we can use this server without the image, actually is everything running fine, Should the image still be reset? I'm a little worried that we'll have to completely rebuild the server.
hm, we can use this server without the image, actually is everything running fine, Should the image still be reset? I'm a little worried that we'll have to completely rebuild the server.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 10, 2024 #68 Shenziro said: Should the image still be reset? Click to expand... Yes, otherwise you will stay with the modified partition table with the unallocated spaces.
Shenziro said: Should the image still be reset? Click to expand... Yes, otherwise you will stay with the modified partition table with the unallocated spaces.
S Shenziro Well-known member Joined Jun 12, 2024 Posts 92 Jul 11, 2024 #69 Hello, the Image is restore Last edited: Jul 11, 2024
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 11, 2024 #70 Hi, Please provide a new screenshot of diskmgmt.msc.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 11, 2024 #72 Open an elevated command prompt and run the following command for the details of the 200 MB partition. Replace X with the correct number. Code: Diskpart Select disk 0 Select partition X Detail partition Detail volume
Open an elevated command prompt and run the following command for the details of the 200 MB partition. Replace X with the correct number. Code: Diskpart Select disk 0 Select partition X Detail partition Detail volume
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 11, 2024 #74 Please do the same for partition 2. Code: Diskpart Select disk 0 Select partition 2 Detail partition Detail volume
Please do the same for partition 2. Code: Diskpart Select disk 0 Select partition 2 Detail partition Detail volume
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 11, 2024 #76 Are you able to clone this server in another Hyper-V environment so we can test some things safely?
S Shenziro Well-known member Joined Jun 12, 2024 Posts 92 Jul 11, 2024 #77 no but i can snapshots from the server
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 11, 2024 #78 That's a bit tricky because when the fix fails it will result in an unbootable system.
S Shenziro Well-known member Joined Jun 12, 2024 Posts 92 Jul 11, 2024 #79 Hm, i can reboot the server all time, i can restore the snapshot all time, this should be no problem
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 13,410 Location The Netherlands Jul 11, 2024 #80 Okay, normally the System Reserved Partition (200MB) (SRP) is set as System, but in this case the (99MB) is set as system. So I would suggest to rebuild the current SRP partition using the following instructions into the Recovery Environment. These are the steps I have just tested on one of my VM's with Server 2016. Run Diskpart list disk select disk 0 list partition Identify the the SRP partition. select partition X (Recplace X with the number of the SRP partition) Format the SRP partition format fs=NTFS label="System Reserved" Set the SRP Partition as active with the following command Active (Note that it is marked with an * now, when running list partition) Exit DiskPart and press enter Change the focus from X: (the default) on the SRP partition (c:) by running: C: Create a folder called Boot running: Mkdir Boot Copy the content of the boot folder on the system partition (X:) to the new folder: xcopy X:\windows\system32\boot c:\boot /e /h (replace X:with the correct drive letter which contains the Windows folder). Copy the bootmgr from the root of the ISO (X:\) (replace X: with the correct drive letter of the Server 2016 ISO) copy X:\bootmgr Now Run the following commands Bootrec /Fixmbr Bootrec /Fixboot Bootrec /rebuildBCD Press Y when you'll see the message "Add installation too boot list" and press enter. Close the Command Prompt and reboot the server Last edited: Jul 11, 2024
Okay, normally the System Reserved Partition (200MB) (SRP) is set as System, but in this case the (99MB) is set as system. So I would suggest to rebuild the current SRP partition using the following instructions into the Recovery Environment. These are the steps I have just tested on one of my VM's with Server 2016. Run Diskpart list disk select disk 0 list partition Identify the the SRP partition. select partition X (Recplace X with the number of the SRP partition) Format the SRP partition format fs=NTFS label="System Reserved" Set the SRP Partition as active with the following command Active (Note that it is marked with an * now, when running list partition) Exit DiskPart and press enter Change the focus from X: (the default) on the SRP partition (c:) by running: C: Create a folder called Boot running: Mkdir Boot Copy the content of the boot folder on the system partition (X:) to the new folder: xcopy X:\windows\system32\boot c:\boot /e /h (replace X:with the correct drive letter which contains the Windows folder). Copy the bootmgr from the root of the ISO (X:\) (replace X: with the correct drive letter of the Server 2016 ISO) copy X:\bootmgr Now Run the following commands Bootrec /Fixmbr Bootrec /Fixboot Bootrec /rebuildBCD Press Y when you'll see the message "Add installation too boot list" and press enter. Close the Command Prompt and reboot the server