New
#11
When available post diskpar info results.
This link has information to consider:
https://learn.microsoft.com/en-us/wi...le-boot-device
When available post diskpar info results.
This link has information to consider:
https://learn.microsoft.com/en-us/wi...le-boot-device
UPDATE:
I have just got back to looking at this.
The problem is the SSD [ Disk 1 ] cloning process I think:
>System Reserved
is(Active, Primary Partition)
instead of(System, Active, Primary Partition)
>Win_10
is(Primary Partition)
instead of(Boot, Page File, Crash Dump, Primary Partition)
Probably because they ONLY show up for theBooted Drive
?
> Could there have been a glitch in theCloning
process ?
> Have I wrongly performed theCloning
process [ Log posted above in Post #7 ] ?
> Is there a way around this, or do I need to re-do theCloning Process
?
> Should I swap the HDD for the SSD, would that make a difference ?
Thanks.
Last edited by Paul Black; 31 Aug 2023 at 09:54.
There may be members that know whether the third party software used has or does not have the feature to restore an image.
Then clean install Windows 10 creating the default four partitions.
Follow by restoring only C:.
Hello @zbook,
Yes, that could possibly work.
The thing is though, I should just be able toClone
the HDD to the SSD and thenBoot
the SSD !
I haven't used Macrium Reflect for years, so there is a possibility that I may have made a mistake during the process even though it is pretty straightforward !
UPDATE:
Could it possibly be to do with the SSDdisk id
of the previous owner when he prepared it before posting ?:
Code:<!-- disk is the 1 based index of the disk --> <!-- id is the disk signature and is used in place of the disk index if specified --> <source_disk id="30CF9D4A">1</source_disk> <target_disk id="9877E129">2</target_disk> <!-- Y/N or blank, use the chs values from the source disk. -->
Therefore, do I need to performdiskpart > clean
[ on the SSD ] while attached to the Laptop first and then re-do theCloning
process ?
Last edited by Paul Black; 31 Aug 2023 at 10:35.
Since it is a second-hand used SSD and you are going to live with it, before venturing to do anything else, install Kingston SSD Manager and ascertain the status of its firmware and health. I think SIW2 mentioned it earlier in this thread.
Here is a sample screenshot.
Read this SSD Manager - Monitor Drive Health and Usage - Kingston Technology
@jumanji,
Thank you. I will do that shortly on my Desktop.
EDIT:
It canNOT
be done. It just picked up the installed SSD Desktop OS disk andNOT
the second hand SSD disk.
@zbook,
Here are thediskpar info results
for the SSD. Obviously attached rather thanBooted
:
Code:Microsoft DiskPart version 10.0.18362.1 Copyright (C) Microsoft Corporation. On computer: System-Admin-LT Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 55 GB 0 B Disk 1 Online 223 GB 0 B Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 E DVD-ROM 0 B No Media Volume 1 System Rese NTFS Partition 579 MB Healthy System Volume 2 C Win_10 NTFS Partition 30 GB Healthy Boot Volume 3 I Images_Back NTFS Partition 7168 MB Healthy Volume 4 D Data NTFS Partition 18 GB Healthy Volume 5 F System Rese NTFS Partition 579 MB Healthy Volume 6 G Win_10 NTFS Partition 30 GB Healthy Volume 7 H Images_Back NTFS Partition 50 GB Healthy Volume 8 J Data NTFS Partition 50 GB Healthy Disk 1 is now the selected disk. ASMT 2105 USB Device Disk ID: 9877E129 Type : USB Status : Online Path : 0 Target : 0 LUN ID : 0 Location Path : UNAVAILABLE Current Read-only State : No Read-only : No Boot Disk : No Pagefile Disk : No Hibernation File Disk : No Crashdump Disk : No Clustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 5 F System Rese NTFS Partition 579 MB Healthy Volume 6 G Win_10 NTFS Partition 30 GB Healthy Volume 7 H Images_Back NTFS Partition 50 GB Healthy Volume 8 J Data NTFS Partition 50 GB Healthy Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 579 MB 1024 KB Partition 2 Primary 30 GB 580 MB Partition 3 Primary 50 GB 30 GB Partition 4 Primary 50 GB 80 GB Partition 1 is now the selected partition. Partition 1 Type : 07 Hidden: No Active: Yes Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 5 F System Rese NTFS Partition 579 MB Healthy Partition 2 is now the selected partition. Partition 2 Type : 07 Hidden: No Active: No Offset in Bytes: 608174080 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 6 G Win_10 NTFS Partition 30 GB Healthy Partition 3 is now the selected partition. Partition 3 Type : 07 Hidden: No Active: No Offset in Bytes: 32851886080 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 7 H Images_Back NTFS Partition 50 GB Healthy Partition 4 is now the selected partition. Partition 4 Type : 07 Hidden: No Active: No Offset in Bytes: 86591406080 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 8 J Data NTFS Partition 50 GB Healthy
Last edited by Paul Black; 31 Aug 2023 at 11:30.
How come
vol 1 =...........................................vol 5 ltr F
vol 2 ltr C =................................ vol 6 ltr G
1) vol 3 ltr I..........does not =.......vol 7 ltr H ?
2) vol 4 ltr D........does not =.......vol 8 ltr J ?
3) vol 5 ltr F in the info column does not display system ?
@zbook,
Exactly.
Obviouslydiskparinfo
was run whileBooted
from the HDD with the SSD attached.
This is why I am asking those that use Macrium Reflect if I have performed theCloning
operation incorrectly and whether it would be worth re-doing it even though ALL the data [ Partitions ] is actually on the SSD ?
Google searched: MBR clone inaccessible boot device:
See this link about Macrium boot rescue Legacy/MBR vs UEFI/GPT.
MBR-MBR clone (new pc) "Inaccessible_boot_device"