There's nothing to fix, and this is perfectly normal.
ext4 creates a lot of overhead before any files are created. It does not mean it is "worse" than ext3. If you fill that partition with files, you will notice that ext3's (and NTFS's) overhead will grow proportionally with the files, as with ext4 it will basically remain constant forever.
By "pre-allocating" the overhead, it can manage it much better than a growing one. So ext4 is just doing now what ext3 would do later.
Besides, 27G may look a lot, but it's still a mere 1.5% overhead. Compare that to the old days of FAT, where slack space could eat anything from 5% to 30% of your partition space, and you'll notice how greatly things have evolved since then.
Also, I strongly recommend against using -m 0. Reserved space is there for a reason: it lowers the fragmentation chances and saves some space for fsck. It is reserved only from users, but root (and thus all your software installs) can fully use it. If you think 5% is excessive, leave at least 1% .
Remember: there's no fragmentation nightmares in ext. But this beauty comes at a price. It needs free space as room for proper management. Give it to him and things will run much smoother. Besides, who ever uses their HDD beyond 90% before buying a larger one? So what's the problem about a 5% reserved space? It may save you the next time you accidentally create a dozen-GB file that fills up the whole partition and end up crashing the OS due to lack of space for other processes.
For a more detailed, further technical reading, read here
Solution: the problem was in /etc/initramfs-tools/conf.d/resume where was still some wierd old UUID. After replacing with the new one and invoking sudo update-initramfs -u it works now!
Maybe if I just did these steps, it would work:
- comment-out the line with
/dev/mapper/cryptswap1 in /etc/fstab and
enable the line with UUID under the # swap was on /dev/sda5 during installation line (= enabling swap with no encryption)
- comment-out the only line in
/etc/crypttab
- edit
/etc/initramfs-tools/conf.d/resume in order to contain the swap's UUID from /etc/fstab
sudo update-initramfs -u- reboot and check
Best Answer
The
/dev/mapper/ubuntu--vg-rootin place of a traditional/dev/sdxNblock device just indicates that you chose to install the system using LVM2 logical volume management. See What is LVM and what is it used for?