Old computer (asus eeeTop all in one touchscreen) mbr fails to restore after imaging task
Can we get an update on this?
After the image uploaded, I got the same error again.
You mean the upload screwed the source? We should definitely have a close look if that’s the case. This should never ever happen I find!
Is this resizable (I guess) or non-resizable image type?? Please boot your (fixed) client into debug upload and run
fdisk -l /dev/sda. That should give us sufficient information I suppose. Then if you are really keen, do an upload (command
fog) and run the same
fdisk -l /dev/sdacommand when you get back to the shell after uploading. Please post pictures of both.
@Tom-Elliott How would I check this?
Just a guess but this drive is likely based on 512 sectors expecting to be started at 63 but the image is in 2048 which makes the drive not understand how to use the drive (why Windows showed it as inactive)