Boot Sector Difference?

klau1

Member
Oct 2, 2006
29
0
0
Before I migrate the OS partition ( C: ) to an SSD, I want to fix this problem that's been here for a while. (It's what Killdisk is telling me)

Anyone know how to fix the following? (Or will the problem even transfer to the SSD if I'm just copying the OS partition? )

BootSectordiffer.jpg


FYI This are the partitions:
drivepart.jpg


I think this started after I manually migrated from my 3.5" HDD to a 2.5" HDD and re-sized the partitions

Any help appreciated

PS: Before anyone advises not to migrate due to SSD Performance, I am aware that one needs to manually turn on TRIM and turn off the Indexing, Defragging, hibernation and minimize swapfile.
 

Elixer

Lifer
May 7, 2002
10,371
762
126
partition * is the OEM partition, is it not ? Sometimes called recovery partition ?

Anyway, you can't manually turn on TRIM, it is either supported or not.
The SSDs must have a aligned partition, if not, you will get crap performance, and I am unsure how this HD is setup, nor have I ever heard of killdisk, so no idea about the info it gives.
 

taltamir

Lifer
Mar 21, 2004
13,576
6
76
I am aware that one needs to manually turn on TRIM and turn off the Indexing, Defragging, hibernation and minimize swapfile.

actually...
TRIM is always on in win7 and always sent to devices. HDDs ignore it, SSDs use it.

Indexing should not be turned off unless you enjoy waiting forever for searches to complete. Indexing should be placed on the drive with the fastest random writes (during early gen 1 jmicron SSDs that was any HDD, now it is any SSD)

Defragging should be left on, the service only runs when scheduled (not on boot) and only schedules HDDs (not SSDs), that being said, you should remove the schedule for C drive since C drive has changed from HDD to SSD.

Hibernation is really up to you, it can save some space to turn it off but i find it to be a useful feature.

Minizing swap is another way to save space, although many recommend moving it to an HDD that is wrong. it should be on fastest random write device which was HDD in days of gen1 jmicron ssds but today it is any modern SSD.

Anyways, I honestly would not copy the partition over. Just do a clean install on the SSD and then copy your data over and reinstall stuff.
 

klau1

Member
Oct 2, 2006
29
0
0
I googled the terms boot sector copy difference. Apparently from the results, they seem to say that every partition has 2 identical boot records, one in the front and one in the back as backup.

If we are to take the message here at face value, it seems that the two boot records differ.

So logically, the way to fix it would be to make them identical again.
 

klau1

Member
Oct 2, 2006
29
0
0
the * partition is there for boot files. Windows 7 automatically creates it to store boot files so that fools won't accidentally delete it on the C:

Although I appreciate the extra info, This thread isn't actually an inquiry for SSD optimization. It's an inquiry on how to fix the boot sector problem on my HDD.
 

taltamir

Lifer
Mar 21, 2004
13,576
6
76
I googled the terms boot sector copy difference. Apparently from the results, they seem to say that every partition has 2 identical boot records, one in the front and one in the back as backup.

AFAIK that is only in GPT. In MBR there is only the one non backup boot record at the front.

If we are to take the message here at face value, it seems that the two boot records differ.

So logically, the way to fix it would be to make them identical again.
If they differ then one or the other has become corrupt. you can't just make them equal again you need to find the errors...
Actually, did you try running chkdsk?