Transfer Windows to larger hard drive success using Linux! 321

That's a good question, but I don't think so because when I copied the parbreastion table, I used the raw drive names versus the parbreastion names.

dev-sda dev-hdb when doing the boot record, dev-sda1 dev-hdb1 when doing the actual parbreastion.

I think the detection of new hardware thing is just because the new drive was a completely different make and model from the old drive, and windows in device manager, does see the drive makes and models and such, and I buttume would detect new hardware even if the disk contents were perfectly mirrored.

On the other hand, you may be right--not so much for the detecting new hardware that I saw windows do, but because of the chkdsk it had to do. I'm not sure.

I used 1k because that was the block size reported when I did a du -s . when mounting the original drive's ntfs parbreastion, and I wanted to make the block size small enough rather than too large. I don't have a perfect understanding of the topic, but I had read some things indicating that if th block size is chosen too large, you run a risk of missing something if there's a bad block or something on the target drive.

Thanks. It was a fun thing to actually try and see friggin work!

-- Todd H.