New
#51
here it is. Since I was using the HD I kept adding the drive letter. Right now I haven't added it yet
here it is. Since I was using the HD I kept adding the drive letter. Right now I haven't added it yet
You must have used a 3rd party tool to do that
diskpart
list vol
sel vol #
ATTRIBUTES VOLUME CLEAR HIDDEN
select the vol from disk 1
Also find the bootmanager by
cmd
bcdedit
and set (C:) as active
What does your Partition Tool tell you?
DISKPART
sel disk 1
sel par 1
det par
hidden or not?
I am in a hurry
Last edited by Pentagon; 2 Weeks Ago at 15:12.
No 3rd party tool it was all fine until I used Macrium to restore the image from my current HD. THen the hidden problem started and nothing we’ve done has solved it from losing the letter after reboot. The drive is already wiped from files, so I can run your disk1.txt routine and then follow Megahertz Macrium.routine.
Read my 1st post again to see what I did wrong with Macrium.
Here’s what the CMD did:
Microsoft Windows [Version 10.0.19045.3693]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>diskpart
Microsoft DiskPart version 10.0.19041.3636
Copyright (C) Microsoft Corporation.
On computer: Q9450
DISKPART> list vol
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 D DVD-ROM 0 B No Media
Volume 1 C Win10 NTFS Partition 73 GB Healthy System
Volume 2 L SEA 400 Q9 NTFS Partition 298 GB Healthy
Volume 3 NTFS Partition 542 MB Healthy Hidden
Volume 4 1T boot NTFS Partition 73 GB Healthy Hidden
Volume 5 1T WD DATA NTFS Partition 857 GB Healthy Hidden
DISKPART> sel vol 5
Volume 5 is the selected volume.
DISKPART> ATTRIBUTES VOLUME CLEAR HIDDEN
DiskPart has encountered an error: Incorrect function.
See the System Event Log for more information.
=-=-=-=-=-=-=-=-
Here’s what the boot manager said:
Microsoft Windows [Version 10.0.19045.3693]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {f35986f3-1d55-11ee-a940-ecadf0dc9648}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {c43b6341-1d3d-11ee-850f-844d5f5c3149}
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {f35986f3-1d55-11ee-a940-ecadf0dc9648}
nx OptIn
bootmenupolicy Standard
C:\WINDOWS\system32>
-=-=-=-=--=-=-=-=
Right now the boot drive of the 1T is blank and it says it’s active also. My C drive is already set as active and is working fine.
Here’s what your 2nd Diskpart commands said. As you can see everything on Disk 1 is hidden as usual. On thurs I can try the disk1.txt routine and restore the Macrium image
C:\WINDOWS\system32>diskpart
Microsoft DiskPart version 10.0.19041.3636
Copyright (C) Microsoft Corporation.
On computer: Q9450
DISKPART> sel disk 1
Disk 1 is now the selected disk.
DISKPART> sel par 1
Partition 1 is now the selected partition.
DISKPART> det par
Partition 1
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 4 1T boot NTFS Partition 73 GB Healthy Hidden
DISKPART>
That was a misunderstanding: I mean the partition changes in post # 51.
I also checked your mentioning about the partition size of „System“ Partition. You are right, it was 350 MB some years ago for Business Computers.
As long as your Windows-Partition is set „ACTIVE“ you can play with the size setings in the script I provided.
You see the result immediately in Diskmanagement. Do it to learn s.th. new. And check the drive letter behavior also.
Then go into the BIOS and check, if the mainboard (ASROCK ?) supports UEFI
Edit:
All the trouble we have here is probably a Extended/Logical partition problem we didn't consider.
And if you create a new Backup from (C:) only (!) and run the Recovery straight afterwords to you new target partition, Macrium will not change the Partition Layout as long as you don’t have more than 4 partitions totaly on disk 1. You do not even have to reboot.
Last edited by Pentagon; 1 Week Ago at 06:13.
No UEFI on my 15 year old Q9450 computer. I do have it on my ProStudio main computer.
Your Disk1.txt worked perfectly. I ran Crystaldiskinfo and got a caution from it. I then did a diskpart clean and used Disk management to do a long format on it. I had it as a USB drive in my main computer and it took about 6 hours. Dispart showed it had no hidden volumes, so that was fixed. I ran Crystaldiskinfo and got a caution from it. So I'm leaving it as a data HD and will continue to monitor it, before I buy a new HD. This is my internet computer and I backup every night, so if it goes bad I can adjust just fine.
The 1T drive just showed up as letter E, without me even having to assign it
Last edited by GerryPeters; 1 Week Ago at 19:31.
Good decision to leave it as Data-Disk. But that is a good reason to run it as a much safer GPT disk.
Run
diskpart
sel disk 1
clean
convert GPT
create partition primary
format quick fs=ntfs label="Data"
assign letter=E
exit
- - - Updated - - -
In order to fix the Recovery Environment
cmd (admin)
reagentc /disable
diskpart
sel disk 0
sel par 2
delete partition override
sel par 1
extend
shrink minimum=1025
create partition primary
format quick fs=ntfs label="Recovery"
set id=27
exit
reagentc /enable
Last edited by Pentagon; 1 Week Ago at 01:07.
Why is GPT better than MBR for this data disk?
I almost never have used the Recovery Environment unless it was used without me knowing. I remember at times I needed to put in my Win 10 CD. I thought the Recovery Environment is something that let's you use that instead of having to put the CD in. At times I’ve used this computer with no Recovery Environment partition
- - - Updated - - -
I converted it to GPT
Good! Since I run all my disks as GPT and some Servers with ZFS-Pools I didn't loose 1 KB!
The problem we had wouldn't have happend on a GPT. MBR allows just 4 primary partitions
Some diskpart commands work different on MBR-Disks etc.
Since Win XP (64) GPT is supported by WINDOWS
UEFI and GPT is a different thing!
We are all here to get Help and to learn s.th. we didn't know. You and ME
Did you try/run Crystaldiskinfo after the conversion?
PS: And the next time you want to copy a txt-File to (C:)
Run "Notepad" from the Start-Menue as ADMINISTRATOR (RightClick). Then select File>Open ==> navigate to the Download-Folder, select the txt-file and then under "Save as.." select the (C:) and OK.
cmd (admin) and the xcopy command works as well.
Last edited by Pentagon; 1 Week Ago at 14:49.
I ran Crystaldiskinfo and here's the screenshot. The reallocated sectors show 1E. Not sure what that means, since I don't convert Hex to Dec. I will for sure keep a good eye on this HD and replace it it I need to