3

I did some partitioning of my file disk (E:\) which I didn't like, so I removed the partitions I made and resized the original partition back to the full disk space. I kept a small bit of unallocated space which I couldn't add to the partition, I don't know why.

Now I'd like to add that bit of unallocated space to the actual partition using EaseUS Partition Manager (the program I used to remove the earlier partitions about a year back), but it doesn't want to add the remaining 7.8MB to the partition.

How do I fix this?

EaseUS Partition Manager // Resize/Move partition

I cannot seem to remove the number 7,8 nor drag the allocated partition (E:) to the beginning of the file. I already tried making the unallocated space bigger by shrinking the partition, but once I added it back to the partition, the 7,8MB remained unallocated.

Jochem Kuijpers
  • 412

2 Answers2

3

Don't worry about it.

The unallocated space appears before the partition. This means that adding that space to the partition will require moving the start of the partition, which in turn means that it will have to move a lot of the partition's data structures. This type of operation is time-consuming and risky -- a power failure, system crash, cat stepping on the keyboard, etc., can all interrupt the process and cause catastrophic data loss. The amount of unallocated space in question is 0.00082% of your total disk space; or put another way, it's about 5.4 3.5-inch floppy disks' worth of capacity. In other words, it's trivial. I understand that this sort of thing seems non-optimal and can bring out even normal peoples' obsessive-compulsive sides, but it's best to not take the risk. Granted, the risk is small, but the hassle on those rare occasions when a problem occurs is huge, so it's not worth taking that small risk. (Even if you've got good backups, do you really want to spend the time restoring your backup?)

Rod Smith
  • 22,290
2

The space is there for compatibilty and alignment.

Hard drives have a very convulted history and the operating systems dealing with them even more so. Chances are, that, if you were to use that space (and make no mistake, with the right operating system / filesystem combination, you can use every byte) - if the space is at the beginning of a physical drive, it is entirely possible that another operating system or BIOS might overwrite or corrupt data in that area and so render your partition corrupt.

Dagelf
  • 1,060