I bought a new 1tb HD adding it to a 750gb drive. I have a duel boot Windows/Linux Mint Debian setup. I did a clonezilla to copy the 750gb drive to the 1tb drive (it used partclone, I believe).

I did an fdisk /dev/sdb (the newer 1tb drive) to examine the drive. It showed this error:

Is this a real problem, or is this an fdisk version issue? If it is a real issue, how do I deal with it? Esp with copying over the Windows recovery partition and windows partitions?

I am also wondering about design issues. I would prefer Windows os on the original and my Windows data (user data, etc) on the new drive and the reverse for my Linux, but how hard is it to switch a Windows data volume to another disk (it is already copied onto that disk). The easier road I think would just be let /dev/sda be for Windows and /dev/sdb be for linux, but performance would be better the other way. Thoughts?

Thanks,
Narnie

This is a real problem. Some newer drives (and it will be more in the future) use physical sector sizes of 4KB instead of the older 512B. In order to get full write performance from the disk partitions have to be aligned to those physical sectors. So make sure that the startsector of any partition can be divided by 8.

1 members found this post helpful.

OK, I wiped the drive and reformated it with SystemRescueCD using gparted mimicking my old HD's partition scheme/sizes. I checked the first sector of each partition and they are all divisible by 8. However, when I do a fdisk, I still get the fdisk warning. Is that OK or should that warning have gone away if my startsector for each partition is divisible by 8 and everything is ok to copy over and put it into production?

Thanks,
Narnie

If you would post the output from "fdisk -lu" for that drive, someone could give a definitive answer.

Here 'tis.

Thank you for any help.

Narnie

That all looks like it should be just fine.

To me, it looks like there's a lot of wasted space in this partitioning scheme. sdb5 starts 2048 sectors past the beginning of sdb4, there's 2048 sectors between the end of sdb5 and the beginning of sdb6, etc. Can anything be done about this?

Right now I'm trying to partition a hard drive with this "issue", and I can't seem to avoid wasting space.

The 5 sets of 2048 wasted sectors works out to 0.00052% of the 1953525168 sectors on the drive. How much effort do you want to put into reclaiming that?

Or to give you some other numbers, 2048 sectors are exactly 1 MB, the the wasted space on this 1TB disk is 5MB.

If I was willing to accept sloppiness without question, I would be an MS Windows user.
I would at least like to know the source of the unclaimed space, and if there's anything that can be done about it.

ulatekh,

What tools do you use to create the partitions ?

I am doing partition with my new 1.5TB WD15EARS as well, and I used parted which can let me to assign the exact START and END sector number, which at the end I could make no waste of space of my partitioned harddisk. Do you want to take a try with parted ?

I was using the fdisk that came with my Fedora Core 17 install/rescue DVD.
I guess I'll have to take another stab at parted...it's been a while since I tried to use that.

The reason is alignment. Modern disk drives with 4KB physical sectors suffer severe degradation in write performance if the filesystem is not aligned to a 4KB boundary, and the erase blocks in SSDs are even larger, perhaps 128KB or 256KB. Current partitioning tools are built to use a 1MB alignment when using sector units (as opposed to legacy cylinder units).

The first partition is always preceded by the single sector MBR, so space must be wasted there to bring that partition back into alignment. Similarly, every logical drive in the extended partition is preceded by a secondary partition table, which again (assuming that the preceding partition uses an integral number of alignment-sized blocks) would misalign them by 1 sector unless some space is wasted to align them properly.

You can use sfdisk with the --force ("Do what I say even if it is stupid") option to place your partitions wherever you like. You could also avoid the use of extended partitions and logical drives by partitioning your disks with GPT, which would only "waste" 68 sectors for the primary and secondary GPTs (34 512-byte sectors each).