I've just installed Ubuntu on a new SSD along with a HDD for data.
Strangely, when I divided partitions at install, 1MB of non-removable free space was reserved at the beginning of each disk. I ignored them however, because I thought they wouldn't be a problem.
But after install, when I sudo fdisk -l
, I get the following warnings:
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 250069679 125034839+ ee GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
I have little knowledge on GPT/GUIDs, but I'm guessing that the warnings were caused because of the 1MBs at the installation stage.
So here are my questions:
- Can the warning be a potential problem, issue or difficulty in the future?
- Is there a smart & safe way to fix the warning?
The warning is not a problem.
It's only warning you that the
fdisk
tool doesn't work on disks using GPT for partitions. It only works on disks using the older MBR (DOS style) partitions .However, as the warning says,
parted
(an alternative to fdisk) does work for disks using GPT partition types.The warning is not related to the 1MB free space. That free space (which will in reality be slightly less than 1MB) is only there to ensure that the partitions line up on 1MB boundaries on the drive, which is generally a good idea for performance on newer drives like SSDs.