You are not logged in.
Hi guys,
when i run fdisk -l i get the following message:
Partition table entries are not in disk order.
Some solved it by running fdisk with the f (fix partitions order) option.
They say that if you don't have references with /dev/nvmeXX but UUID references of the partitions there shouldn't be any problems.
fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p9
UUID=b177476c-53c0-4a8f-bac2-3955040ce0b3 / ext4 rw,relatime 0 1
# /dev/nvme0n1p7
UUID=B26C-A1E5 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/nvme0n1p10
UUID=a25a996b-c90a-4597-9fb6-cdaa2ebf6de3 /home ext4 rw,relatime 0 2
# /dev/nvme0n1p8
UUID=3915a4f1-d3de-4ada-964a-09fef8733b5f none swap defaults 0 0
partial grub.cfg
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-b177476c-53c0-4a8f-bac2-3955040ce0b3' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root B26C-A1E5
else
search --no-floppy --fs-uuid --set=root B26C-A1E5
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=b177476c-53c0-4a8f-bac2-3955040ce0b3 rw intel_iommu=on video=1920x1080 resume=UUID=3915a4f1-d3de-4ada-964a-09fef8733b5f verbose
echo 'Loading initial ramdisk ...'
initrd /intel-ucode.img /initramfs-linux.img
}
As you can see there are references only to UUIDs.
If they change the name of the various / dev / nvmeXX there should be no problems with booting (grub) and mounting (fstab).
Can you confirm?
nb: that message annoys me
Last edited by archdom (2020-03-06 09:24:00)
Offline
even though it's just a comment and won't affect functionality, I'd still remove those device names from comment (or update them accordingly). bad documentation can be confusing, and confusion can lead to errors...
also run a grep just in case, as there might be other files (like crypttab, mdadm.conf, smartd.conf, ...) that might also reference to devices by name instead of UUID
in general UUID has exactly this purpose... identify things by content, regardless of device name. only causes problems when you duplicate content (like dd cloning). two devices with same uuid, it can't pick the correct one.
Last edited by frostschutz (2020-03-05 22:51:18)
Offline
it worked!
I had to regenerate grub.cfg beacuse arch boot was missing via arch-chroot command.
Before run arch-chroot command, i have regenerate fstab file so now i have also correct name of partitions.
Mark as solved
Offline
I want to remind all users that it is a modification that requires manual intervention.
see you next time
Offline