Skip to main content
8 events
when toggle format what by license comment
Nov 18, 2021 at 0:16 comment added adrianTNT I was able to fix this and added an answer to this topic, I am unsure if this command is OK since it contains i386, seems an uncommon environment ?! grub2-install --directory /usr/lib/grub/i386-pc/ /dev/nvme0n1
Nov 18, 2021 at 0:14 answer added adrianTNT timeline score: 2
Nov 17, 2021 at 23:57 history edited adrianTNT CC BY-SA 4.0
deleted 192 characters in body
Nov 15, 2021 at 2:43 history edited adrianTNT CC BY-SA 4.0
added 187 characters in body
Nov 15, 2021 at 2:42 comment added adrianTNT @VojtechTrefny @telcoM after reading more, I was thinking the UUID in grub and configs would be the problem, can you guys see my updated topic ? It contains the output of many commands like fdisk, blkid, grub.cfg, fstab, etc. Thank you. unix.stackexchange.com/questions/677548/…
Nov 2, 2021 at 7:08 comment added telcoM A NVMe SSD is a PCIe device. When you replace a NVMe SSD with one that is not of identical type, then as far as the BIOS is concerned, it is about as big a change as replacing a hardware RAID card with another one from a different manufacturer. Depending on exactly how the selection of the boot device is stored in the BIOS settings NVRAM, it may include a reference to a particular type of PCIe device, which may not be applicable to a different NVMe drive model. If the BIOS "boot order" list identifies the NVMe by vendor name, you'll probably need to add the new one to the list yourself.
Nov 2, 2021 at 6:20 comment added Vojtech Trefny One possible problem could be sector size, newer NVMe drives usually have 4k sectors and not 512 (and on some drives this can be changed) which could cause this issue when cloning between two different sector size drives. You can check sector size of your drives with blockdev --getpbsz /dev/nvme0n1.
Nov 2, 2021 at 2:54 history asked adrianTNT CC BY-SA 4.0