Linux
驅動器不會從其 Grub 啟動，但會在複製後從另一個驅動器的 Grub 啟動，為什麼？
那是一個月前的事了，所以如果你問我細節，我可能還記得，但最好根據現在可以提供的資訊採取行動。由於時間不夠，我沒有在這裡尋求幫助。
我已將 SATA SSD 驅動器複製到更大的 NVMe 驅動器。
- 原來的 SATA 驅動器可以正常啟動。
- 新的 NVMe 驅動器將僅通過 SATA Grub 載入程序啟動，我必須在其中選擇 NVMe 啟動驅動器。
一些有用的命令輸出如下：
# fdisk -l Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 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 Disklabel type: gpt Disk identifier: 1207A335-32CA-4B6C-A508-29A0E85597C4 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 194559 192512 94M EFI System /dev/nvme0n1p2 194560 488396799 488202240 232,8G Linux filesystem Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 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 Disklabel type: gpt Disk identifier: 1207A335-32CA-4B6C-A508-29A0E85597C4 Device Start End Sectors Size Type /dev/sda1 2048 194559 192512 94M EFI System /dev/sda2 194560 488396799 488202240 232,8G Linux filesystem
bootinfoscript我在 SourceForge 上找到了一個可能有用的腳本，它包含太多資訊，但這就是重點，對吧（？）# ./bootinfoscript Boot Info Script 0.61 [1 April 2012] ============================= Boot Info Summary: =============================== => No boot loader is installed in the MBR of /dev/sda. sda1: __________________________________________________________________________ File system: vfat Boot sector type: FAT32 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/BOOT/fbx64.efi /efi/ubuntu/fwupx64.efi /efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi sda2: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Linux Mint 19 Tara Boot files: /boot/grub/grub.cfg /etc/fstab ============================ Drive/Partition Info: ============================= Drive: sda _____________________________________________________________________ Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 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 Disklabel type: gpt Partition Boot Start Sector End Sector # of Sectors Id System /dev/sda1 1 488,397,167 488,397,167 ee GPT GUID Partition Table detected. Partition Start Sector End Sector # of Sectors System /dev/sda1 2,048 194,559 192,512 EFI System partition /dev/sda2 194,560 488,396,799 488,202,240 Data partition (Linux) "blkid" output: ________________________________________________________________ Device UUID TYPE LABEL /dev/nvme0n1 /dev/nvme0n1p1 4966-E925 vfat /dev/nvme0n1p2 f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ext4 /dev/sda1 7C00-9D19 vfat /dev/sda2 b235cea3-ea5b-4571-a252-b75b9cb3f5f0 ext4 ================================ Mount points: ================================= Device Mount_Point Type Options /dev/fuse /run/user/1000/doc fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) /dev/nvme0n1p1 /boot/efi vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/nvme0n1p2 / ext4 (rw,relatime,errors=remount-ro,data=ordered) =========================== sda2/boot/grub/grub.cfg: =========================== -------------------------------------------------------------------------------- # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function recordfail { set recordfail=1 if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 b235cea3-ea5b-4571-a252-b75b9cb3f5f0 else search --no-floppy --fs-uuid --set=root b235cea3-ea5b-4571-a252-b75b9cb3f5f0 fi font="/usr/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=800x600 load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_US insmod gettext fi terminal_output gfxterm if [ "${recordfail}" = 1 ] ; then set timeout=30 else if [ x$feature_timeout_style = xy ] ; then set timeout_style=hidden set timeout=10 # Fallback hidden-timeout code in case the timeout_style feature is # unavailable. elif sleep --interruptible 10 ; then set timeout=0 fi fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### set menu_color_normal=white/black set menu_color_highlight=black/light-gray ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload="${1}" if [ "${1}" = "keep" ]; then set vt_handoff=vt.handoff=1 else set vt_handoff= fi } if [ "${recordfail}" != 1 ]; then if [ -e ${prefix}/gfxblacklist.txt ]; then if hwmatch ${prefix}/gfxblacklist.txt 3; then if [ ${match} = 0 ]; then set linux_gfx_mode=keep else set linux_gfx_mode=text fi else set linux_gfx_mode=text fi else set linux_gfx_mode=keep fi else set linux_gfx_mode=text fi export linux_gfx_mode menuentry 'Linux Mint 19 Cinnamon' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-b235cea3-ea5b-4571-a252-b75b9cb3f5f0' { recordfail load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 b235cea3-ea5b-4571-a252-b75b9cb3f5f0 else search --no-floppy --fs-uuid --set=root b235cea3-ea5b-4571-a252-b75b9cb3f5f0 fi linux /boot/vmlinuz-4.15.0-39-generic root=UUID=b235cea3-ea5b-4571-a252-b75b9cb3f5f0 ro quiet splash fsck.mode=force fsck.repair=yes $vt_handoff initrd /boot/initrd.img-4.15.0-39-generic } submenu 'Advanced options for Linux Mint 19 Cinnamon' $menuentry_id_option 'gnulinux-advanced-b235cea3-ea5b-4571-a252-b75b9cb3f5f0' { menuentry 'Linux Mint 19 Cinnamon, with Linux 4.15.0-39-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-39-generic-advanced-b235cea3-ea5b-4571-a252-b75b9cb3f5f0' { recordfail load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 b235cea3-ea5b-4571-a252-b75b9cb3f5f0 else search --no-floppy --fs-uuid --set=root b235cea3-ea5b-4571-a252-b75b9cb3f5f0 fi echo 'Loading Linux 4.15.0-39-generic ...' linux /boot/vmlinuz-4.15.0-39-generic root=UUID=b235cea3-ea5b-4571-a252-b75b9cb3f5f0 ro quiet splash fsck.mode=force fsck.repair=yes $vt_handoff echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.15.0-39-generic } menuentry 'Linux Mint 19 Cinnamon, with Linux 4.15.0-39-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-39-generic-recovery-b235cea3-ea5b-4571-a252-b75b9cb3f5f0' { recordfail load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 b235cea3-ea5b-4571-a252-b75b9cb3f5f0 else search --no-floppy --fs-uuid --set=root b235cea3-ea5b-4571-a252-b75b9cb3f5f0 fi echo 'Loading Linux 4.15.0-39-generic ...' linux /boot/vmlinuz-4.15.0-39-generic root=UUID=b235cea3-ea5b-4571-a252-b75b9cb3f5f0 ro recovery nomodeset echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-4.15.0-39-generic } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_memtest86+ ### ### END /etc/grub.d/20_memtest86+ ### ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Linux Mint 19 Tara (19) (on /dev/nvme0n1p2)' --class linuxmint --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-f1fc7345-be7a-4c6b-9559-fc6e2d445bfa' { insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa else search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa fi linux /boot/vmlinuz-4.15.0-39-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro quiet splash fsck.mode=force fsck.repair=yes $vt_handoff initrd /boot/initrd.img-4.15.0-39-generic } submenu 'Advanced options for Linux Mint 19 Tara (19) (on /dev/nvme0n1p2)' $menuentry_id_option 'osprober-gnulinux-advanced-f1fc7345-be7a-4c6b-9559-fc6e2d445bfa' { menuentry 'Linux Mint 19 Cinnamon (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-39-generic--f1fc7345-be7a-4c6b-9559-fc6e2d445bfa' { insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa else search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa fi linux /boot/vmlinuz-4.15.0-39-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro quiet splash fsck.mode=force fsck.repair=yes $vt_handoff initrd /boot/initrd.img-4.15.0-39-generic } menuentry 'Linux Mint 19 Cinnamon, with Linux 4.15.0-39-generic (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-39-generic--f1fc7345-be7a-4c6b-9559-fc6e2d445bfa' { insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa else search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa fi linux /boot/vmlinuz-4.15.0-39-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro quiet splash fsck.mode=force fsck.repair=yes $vt_handoff initrd /boot/initrd.img-4.15.0-39-generic } menuentry 'Linux Mint 19 Cinnamon, with Linux 4.15.0-39-generic (recovery mode) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-39-generic-root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro recovery nomodeset-f1fc7345-be7a-4c6b-9559-fc6e2d445bfa' { insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa else search --no-floppy --fs-uuid --set=root f1fc7345-be7a-4c6b-9559-fc6e2d445bfa fi linux /boot/vmlinuz-4.15.0-39-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro recovery nomodeset initrd /boot/initrd.img-4.15.0-39-generic } } set timeout_style=menu if [ "${timeout}" = 0 ]; then set timeout=10 fi ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/30_uefi-firmware ### menuentry 'System setup' $menuentry_id_option 'uefi-firmware' { fwsetup } ### END /etc/grub.d/30_uefi-firmware ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### -------------------------------------------------------------------------------- =============================== sda2/etc/fstab: ================================ -------------------------------------------------------------------------------- # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda2 during installation UUID=b235cea3-ea5b-4571-a252-b75b9cb3f5f0 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/sda1 during installation UUID=7C00-9D19 /boot/efi vfat umask=0077 0 1 # the swap file was created during installation #/swapfile none swap sw 0 0 # RAM disk none /ramdisk tmpfs size=2G,mode=0777 0 0 # auto-mount of windows drive #/dev/disk/by-uuid/9CDAC383DAC357E2 /mnt/9CDAC383DAC357E2 auto nosuid,nodev,nofail,x-gvfs-show,ro 0 0 -------------------------------------------------------------------------------- =================== sda2: Location of files loaded by Grub: ==================== GiB - GB File Fragment(s) =============================== StdErr Messages: =============================== cat: /tmp/BootInfo-Pd0sZIg3/Tmp_Log: No such file or directory我不知道如何處理它，我嘗試了太多東西，甚至無法記住它們。
我希望以上資訊會有所幫助，否則我會卡住。
NVMe 驅動器的目前行為 - 如果我嘗試直接從它啟動，它會自動重新啟動。
我現在只是這樣做：
我確實還記得一個細節：我使用 GParted 更改了新驅動器上的分區 UUID 並進行了
fstab相應的編輯。我相信問題是由具有相同磁碟 UUID 的兩個驅動器引起的，對嗎？
如果是這樣，我現在應該如何進行？
我試過的：
# tune2fs /dev/nvme0n1 -U random tune2fs 1.44.1 (24-Mar-2018) tune2fs: Bad magic number in super-block while trying to open /dev/nvme0n1 Found a gpt partition table in /dev/nvme0n1那麼，我想更改整個磁碟 UUID 是以不同的方式完成的？
磁碟 UUID
我相信這是罪魁禍首，需要改變。
就像在 SATA 驅動器上啟動系統並執行一樣簡單：
# gdisk /dev/nvme0n1
x專家菜單
g用於新磁碟 GUID
R用於隨機化
w將更改寫入磁碟
y確認磁碟 UUID 已更改…當然不需要更改它們。
# fdisk -l | grep -i identifier Disk identifier: 989573D5-37E7-437A-B680-9410F7234A94 Disk identifier: 1207A335-32CA-4B6C-A508-29A0E85597C4分區 UUID
同樣，要更改我使用的那些：
# gdisk /dev/nvme0n1
x專家菜單
c用於新分區 UUID
1對於第一個分區；對第二個分區重複這些步驟
R用於隨機化
w將更改寫入磁碟
y確認GRUB 更新
這就像執行一樣簡單：
# update-grub初始化再生
# update-initramfs -u -k allUEFI BIOS 設置
必須刪除和更新引導選項。
NVMe 驅動器現在可以正常啟動。
筆記
- 我不
chroot用於複製。我使用普通cat或更方便pv的磁碟複製目的。我現在讀了一些關於它的東西。我從來不需要它，從來沒有。我已經複製了一百個驅動器。- 每當我想做一個精確的副本時，我都會在我的 SATA 伺服器上進行，但是這個新的 M.2 PCIe 不能完全插入它。所以我稍微闡述了一下。這超出了本問答的範圍。
- 我聽說有適配器，但我不喜歡那些，所以我使用我的伺服器作為本地網路的中間人。
- 我不喜歡並發症。複製系統，無論是 Linux 還是 Windows，對我來說都相當容易。但在這種情況下（SATA 到 M.2）有點痛苦。
- 那是因為在一個驅動器上是 Linux，而在第二個驅動器上是 Windows。而且我想保持一切就位，不重新安裝，不
rsync，或任何可能用來複製的東西。我確實複製了完全相同的副本。- 你所需要的只是你的大腦
gdisk，我通常用它來修復 PMBR 之類的東西，這些都是我的方法無法避免的，但解決起來非常快。- 這個案子不一樣，不過，我確實準備了很多。喜歡做（1：1）備份等。這是我的個人電腦，我只想切換系統驅動器：M.2 + Windows & SATA + Linux。我想反其道而行之。
- 一旦我需要確保新的 Linux 驅動器執行良好，就出現了這個問題，因為它是我的主要作業系統……