Having big problems imaging windows 10 to a larger disk

I guess you are trying the old BIOS boot method.

Boot into BIBM and create a new Boot Item...

Boot Edit, Add. Fill out the fields as you have already learnt. With one exception. Put a tick in Swap (not the One Time Option). You need this for OS not on the BIBM drive.

You probably also need a BCD Edit. Maybe.

 

If you need a Boot Edit, no problem. But it can be avoided if you tick Update Boot Partition in the Options when you restore/copy the Win10 partition.

 

n

Ah ok .. I just expected it to boot as it did from the partition on the nvme but of course I had to do that then.

BCD edit looks ok but what is confusing me here is that under work with partitions it shows this (bearing in mind in windows I made one single large partition and formatted it .

Code:

EMBR partitions
-------  partition 238515 Free space
SRP-2 partition 500 MiB
Win10-2 partition 237923 MiB
------- partition 1 MiB

Clicking on that top one all buttons grey out. So question is what I see exactly how the partitions are ordered. So if I want to get that top partition to the end I presume I'd need to use slide.

 

Does it boot from BIBM?

 

ok so now that edit got me back to INACESSIBLE BOOT DEVICE. Going back to BCD edit to see if I missed something

 

Not the 850

 

Strange Part Work, but it's fine.

If you wanted to fix it you would slide SRP-2 to the start
Slide Win10-2 up to SRP-2 and then resize Win10-2 to fill the drive.

I'd do this in IFL Part Work but I don't think that works in trial IFL. I've forgotten. You could do it in BIBM but your BIBM is slow. Part Work in IFL is the same as BIBM Part Work but it is fast.

 

We don't like that. Did you Copy partitions in IFL or use image/restore?

 

Try booting without the tick in Swap.

 

I don't like partitions with the same name. In Partwork make the partitions on the 850 SSD
SRP-2A
Win10-2A
Then check BCD Edit. But that BSOD is tricky. Concerning.

 

If removing the tick from Swap doesn't work, put it back and click Settings. Put a tick in Fix Swap.

 

I didn't see anything in the IFL boot other than IFL itself. I think I ticked some options such as align and that might have done it since there I backed up SRP-2/Win10-2 which is in the middle.
I'm just doing another restore with only change guid / sig bit.

All the tests image restore. The image was done by IFD and the restore by IFL.

I'll let you know how this one goes but I have a nasty feeling this is going the same way.

 

Ok

 

We know that image is good as it restores to the M.2
But it doesn't work when restored to the 850.
Is that correct?

Me too.

 

Yes - it was looking so hopeful up until now....

 

Try my swap recommendations and if no success try a different SATA data cable and a different SATA port on the motherboard.

 

Ugh this is going from bad to worse.

After the second restore I tried swap off and swap on but not getting inaccessible boot device despite the table being intact and renaming SRP2a / Win10-2a
I'm getting that dreaded

Code:

EMBR partitions
-------  partition 238515 Free space
SRP-2 partition 500 MiB
Win10-2 partition 237923 MiB
------- partition 1 MiB

Stuff again


I've removed the nvme and booting from the usb bootit to see if there's something I can do with only the 850 in place.

One thought - is there a nifty util somewhere that will compare the boot partitions for differences. Even if there's a text dump of the config that can be put into a text editor and scanned for differences?


Edit: hmmm bootit on the usb doesn't have boot edit

 

I'll contact the TeraByte developer and back back to you.

On my Google searches it seems a common issue when copying to/from SSD/NVMe in MBR mode. I'm using UEFI mode with my M.2 so I can't test it.

 

Was the BSOD a 0x0000007B error? Called a 7B error.

 

No I don't think the inaccessible boot device actually prints a number

Except that I did the test which was from the 850 to the 860 and it still failed .. Unless you mean ssd <> ssd AND / or ssd <> nvme

Just thinking : again I can get the disk to boot as I've described in the first post and by that logic then there should be something that can fix this without going that drastic.

 

In BIBM, click Run on the desktop. Do you have fixboot.tbs in the list? I doubt you will have it as I think it's only in the paid version.

 

Was that with Win7 or Win10?

 

Win 7 is always successful.
It was Win 10. In my initial post I thought I had done it successfully but later on as we were going through various things I did it again just to be certain and it failed.

Can't do that at the moment as win 10 not available but looking in the zip file it ain't there.

Just finished doing the "slide dance" and about to create a bootit partition so I can install it on the 850. Can't remember the exact steps though so have to go back in the thread and look ..

 

Have you uninstalled BIBM from the M.2? You can only have one BIBM.

It's a good idea.

 

No but currently the m.2 out of the sytem.

I didn't really do anything other than install BIBM but now intoead of the EMBR error I am back to INACCESSIBLE BOOT DEVICE


... this is fun .. a hundred things to do in lockdown!