the disk manager will not let me delete the uefi partition, only the windows c partition - i will take a picture
and post momentarily
I didn’t take a picture, but tried it again an no-go.
the only partition the disk manager will let me manipulate is the C windows partition.
The system and uefi partitions have options greyed out.
I even tried wiping them through the Windows 10 setup disc partitioning tool for custom installs, and will not let me remove the uefi partitions.
So all of my machines on this LAN are UEFI.
That means 5 years of bare metal backups was a complete, and utter waste of time.
My god am I lucky this occurred just once.
At that screen before you click run advanced hold on Ctrl alt and shift and let go and see if that gives you a command prompt if so you can do discpart clean
thanks gramps
I am trying another attempt at this, it has an hour to go on the restore.
if it fails again i will try your fix and post.
Failed again. Here is the output from the Log:
10/26/2019 12:25:19 664] RestoreHelper::RestoreData valid clusters processed: 40340116, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:27:02 664] RestoreHelper::RestoreData valid clusters processed: 40864404, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:29:04 664] RestoreHelper::RestoreData valid clusters processed: 41388692, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:30:56 664] RestoreHelper::RestoreData valid clusters processed: 41912980, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:32:51 664] RestoreHelper::RestoreData valid clusters processed: 42437268, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:34:42 664] RestoreHelper::RestoreData valid clusters processed: 42961556, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:36:35 664] RestoreHelper::RestoreData valid clusters processed: 43485844, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:38:39 664] RestoreHelper::RestoreData valid clusters processed: 44010132, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:40:04 664] RestoreHelper::RestoreData valid clusters processed: 44534420, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:41:26 664] RestoreHelper::RestoreData valid clusters processed: 45058708, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:42:57 664] RestoreHelper::RestoreData valid clusters processed: 45582996, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:44:32 664] RestoreHelper::RestoreData valid clusters processed: 46107284, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:46:05 664] RestoreHelper::RestoreData valid clusters processed: 46631572, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:47:32 664] RestoreHelper::RestoreData valid clusters processed: 47155860, missing clusters processed: 4780517, bad clusters processed: 0
[10/26/2019 12:47:53 664] RestoreHelper::FixBootBlock: fixing boot block
[10/26/2019 12:47:53 664] RestoreHelper::ExtendVolume: extending the volume
[10/26/2019 12:47:57 664] RestoreHelper::SetVolumeActive: setting volume active
[10/26/2019 12:47:57 664] Restoring ESP
[10/26/2019 12:47:58 664] existing offset: 0x0, size: 0x4400
[10/26/2019 12:47:58 664] existing offset: 0x4400, size: 0xfbc00
[10/26/2019 12:47:58 664] existing offset: 0x100000, size: 0x21100000
[10/26/2019 12:47:58 664] existing offset: 0x21200000, size: 0x6400000
[10/26/2019 12:47:58 664] existing offset: 0x27600000, size: 0x1000000
[10/26/2019 12:47:58 664] existing offset: 0x28600000, size: 0xe8b8600000
[10/26/2019 12:47:58 664] Found existing volume
[10/26/2019 12:47:58 664] existing offset: 0xe8e0c00000, size: 0x1b1e00
[10/26/2019 12:47:58 664] FormatPartitionEsp called for disk \?\PhysicalDrive0
[10/26/2019 12:47:58 664] Formatting ESP partition at offset 0x40000000
[10/26/2019 12:47:58 664] ESP size 0x16800000
[10/26/2019 12:47:58 664] MSR size 0x8000000
[10/26/2019 12:47:58 664] MSR offset 0x56800000
[10/26/2019 12:47:58 664] ERROR: FormatPartitionEx failed, error 0x80042405
[10/26/2019 12:47:58 664] ERROR: FormatPartitionEsp failed, error 0x80042405
[10/26/2019 12:47:58 664] RestoreHelper::T_Restore: failed to restore ESP, error 0x80042405
[10/26/2019 12:47:58 664] RestoreHelper::T_Restore: restore complete with return value 536870914
[10/26/2019 12:47:58 664] ERROR: CDialog_Restore::Completed failed, HR=0x80070002 (at func: CDialog_Restore::Completed, e:\colorado_qfe_fast\backup\pc\bmr\restorewizard\dialog_restore.cpp (88)
I’m going home now. Another 5 hours completely wasted.
I think you hurt yourself by installing windows. BMR is designed To replace a failed hard drive with a new one. But yes, there are some quirks with uEFI and of course the silly network driver issue.
I have no clue why they never could fix the driver thing.
I removed the drive from the machine, put it in another as a slave, and am using a partitioning utility to wipe the drive clean.
Once done, I’ll put back in the source machine and try another backup and see if that works.
I did recall that earlier in the year I was having issues with backups where they wouldn’t complete, showing a “?” with one of the of the system drives. I posted about here in the forum, and it was chalked up to a change with a Windows 10 update.
I have to wonder if this is what is throwing a wrench into the process?
so latest attempt is a no-go.
I wound up completely wiping the drive clean - no partitions whatsoever.
restored, and it is only copying the restored C windows partition - with NO option to select the other 4 backed up partitions - which of course contain the boot loader.
When I look at the backup on the Sentinel, the backups DO contain all partitions, but the recovery simply won’t let me select them.
let me look at something
in the meantime slave the drive you just restored in another pc and run diskmgr.msc to see if c: really is the only part
I did something similar - I started it up again with the Sentinel recovery USB and looked at the disk on the disk manager, and it is only showing (1) windows partition. Literally 1.
taking me a bit
go ahead and boot the thumb and send me the first screenshot after the password
I have like 6 of these HP machines - they all have the same hardware.
This is a picture of the one that I hooked up the bad slave to.
You’ll notice there are 5 partitions on the system…The Sentinel BM will openly copy the Windows partition on restore…
okay, I just booted a restore
what server>password>what machine>what backup
then it shows what where (and does not show the 2 extra parts)
Hold down ctrl alt shft
a cmd prompt opens
type diskpart >enter
type list dis >enter
type sel dis (correct number)
type cle >enter
type exit
then send a screenshot or we can do whatsapp?
i will post a sequence of images, give me a minute here…
Sorry to report a couple of years ago I wanted to try the W2008 recovery feature and it failed on a HP notebook which underwent the standard backup managed by the DX4000, probably similar error as the one you reported. After some tries I gave up and then I decided not to use anymore the W2008 backup feature but I moved all the backup activities to an external program (Acronis) which I can trust.
thanks for responding.
very distressing to hear.
as it stands now, it seems to be copying the restored Windows partition, but it will not restore the other partitions which contain the necessary boot files.
i have a number of these machines with identical hardware…
wondering if there is a way i could clone the recovered Windows partition to one of the drives with a working disk layout?
