![partition find and mount for harddrive partition find and mount for harddrive](https://www.partitionwizard.com/images/tu30002/hard-drive-partitions-5.jpg)
Mounting by PARTUUID works without initramfs so that'd be an advantage if you wanted to make an initrd-free system. Only partitions have PARTUUIDs, you don't have them for other block devices If your partition table had an issue, and you end up re-creating the same partitions (with different partuuids), it'll no longer be identified even though the content is still there. If you decide to use the partition for something else (format it), it'll still be identified even though the content is no longer there, and it might get mounted to the wrong place. I also found a nice answer at ArchLinux's forum that worth reading: PARTUUID instead UUID in fstab, Pros / Cons ?.
![partition find and mount for harddrive partition find and mount for harddrive](https://image.slidesharecdn.com/hbcd-121008112923-phpapp02/95/hbcd-14-728.jpg)
Use UUID and no surprises unless you have to use other methods for specific reasons. So I guess it's better to use UUID as it's related to the file system. As you might know fstab stands for File System Table. Also there is no PARTUUID for things like lvm. Even when I'm creating an encrypted swap partition. Īs a personal preference I rather to use use UUID. So Linux just takes whatever serial it can find and sticks them in the /dev/by-uuid/ directory even if they aren't matching the UUID definition.
PARTITION FIND AND MOUNT FOR HARDDRIVE SERIAL NUMBERS
Prior to this, various systems provided various serial numbers of various size to be distinguishable. Why my UUID is so much shorter than other examples that I've seen?Īctual UUIDs are supposed to be 128-bit long and meant to be unique. But remember, if you are using MBR, Unlike a regular PARTUUID of a GPT partition, MBR's pseudo PARTUUID can change if the partition number changes. Now I'm not sure if I should be using that or if I should be using the PARTUUID? More info: How do I use a PARTUUID in fstab?
![partition find and mount for harddrive partition find and mount for harddrive](https://i.stack.imgur.com/AFVcT.png)
It has been already mentioned in the other answer. This gave me an error when I ran findmnt -verify -verbose