>>777923>The reason it's not bootable is you didn't copy the master boot record and the partition table....I had a feeling that I should've copied the whole drive (ddrescue /dev/sda instead of doing ddrescue /dev/sda2). I didn't want to dd the other partition (Recovery) because I thought it would be irrelevant or not needed.
As far as I know, partition table and MBR can still be regenerated using third-party tools, right?
>I meant treating it as a file: ...I didn't go the image route because I wasn't so confident for it, so I went with the disk method. Turns out it is a bit messier, but I'll try my best to figure it out.
>Why? Do you really need that space...I thought it is needed for MBR or something similar? I read that the beginning sectors of a drive are used for something specific.
>- the copied drive is the only backup on a non-fucked storage device. It's not for writing to at all, because if you fuck it up you don't have a backupI got the entirety of the laptop's C: drive now (pic related), so I feel rather secure with the data and anything I do next is "free game". I am not sure what are the 2 files that failed to get copied (log file doesn't mention it:)
Results
P MS Data 32768 466192383 466159616
NTFS, blocksize=4096, 238 GB / 222 GiB
P MS Data 510611456 976771071 466159616
NTFS found using backup sector, blocksize=4096, 238 GB / 222 GiB
$MFT has invalid magic.
ntfs_mft_load(): Failed.
Failed to load $MFT: Input/output error.
Failed to startup volume: Input/output error.
$MFT has invalid magic.
ntfs_mft_load(): Failed.
Failed to load $MFT: Input/output error.
>Personally, I'd get a replacement 250GB drive and image the entire laptop drive to it.I suppose I will give this a shot then.
But just to be sure, can I copy the extract in U: drive (pic related) or the backup from X: drive and proceed from there? Or should I actually re-probe the laptop drive again? Hesitant to do the latter option.
