Problem with Dell OptiPlex 790 and 3010

River Valley Computer

Well-Known Member
Reaction score
782
Location
Russellville, AR
This is puzzling three of us.

We cloned a HDD from a Optiplex3010 (i3) to a SSD using Macrum.
Put it in a Optiplex 790 (i5). It comes up saying 'No boot devices......'
We then put the cloned HDD (fully functional) in the 790 - same thing.
We put the SSD into the 3010 - boots right up.
We have went into Settings and changed what we would have thought would fix it - no cigar.

What are we missing. We worked on it until 7 last night.

Help us before we revert to the the tequila bottle.

Thanks in advance.
 
Last edited:
Sounds like your Optiplex 3010 was booting using UEFI and your Optiplex 790 was on legacy. You didn't mention checking this in the BIOS.

When you cloned the disk you should have seen the disk was GPT and had an EFI partition.

From what I can tell the 790 needs to be on bios A05 or higher for UEFI boot with 8gb+ memory.

Check in the BIOS and see if UEFI is available.
1626880364318.png
 
Last edited:
I didn't mention the Bios but yes we have been 'operating' on it. Updated it to A22 - the latest on available. We have tried UEFI, Legacy with no luck. The 3010 was actually a little older than the 890. One thing we did notice is that the Bios on the 890 was missing 'Advanced Boot Options' under General.
 
This has been asked but not answered. Is the source disk formatted as MBR or GPT? Don't think it's the case here but some Dell units no longer support a legacy MBR boot. You must convert it to GPT.
 
have you tried different brand ssd? I had kingston ssd not working in asus laptops before but other brand worked
 
I have run into at least a very similar issue back in the early days of UEFI though I believe ours would boot but So much was wrong with the image that loaded we in the end couldn't solve it and created a unique image for those systems. From reading your post it sounds like what your doing is using a cloned drive like an image for setting up multiple systems. I would try as last person suggested a clean install onto the problem machine and at which point you might see more efficiency to just go forward from there and setup a clone for those machines that way.
 
Back
Top