辨識作業系統分區所在的磁碟（對於腳本）？

我正在嘗試為某個程序自動辨識作業系統駐留在哪個磁碟（不是分區）上，該程序將格式化許多附加磁碟（因此它不會意外格式化作業系統磁碟）。

我目前正在使用dmidecode -s system-uuid，但我認為這給出了分區 UUID。

我可以向使用者索要它，但這會很麻煩。

有什麼方法可以辨識可以在腳本格式中使用的磁碟（如 /dev/sdX）和 UUID？

如果它產生準確的結果，如： run CODE_HERE，並得到 result /dev/sdX，那就更好了:)

System:
 Host: MidnightStarSign Kernel: 5.12.9-1-MANJARO x86_64 bits: 64 compiler: gcc 
 v: 11.1.0 Desktop: KDE Plasma 5.21.5 Distro: Manjaro Linux base: Arch Linux 
Machine:
 Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x 
 serial: <superuser required> UEFI: American Megatrends v: 3001 
 date: 12/04/2020 
CPU:
 Info: 16-Core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3 
 rev: 0 cache: L2: 8 MiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
 bogomips: 217667 
 Speed: 3728 MHz min/max: 2200/3400 MHz boost: enabled Core speeds (MHz): 
 1: 3728 2: 3664 3: 4122 4: 3754 5: 3678 6: 3659 7: 3682 8: 3661 9: 3670 
 10: 3683 11: 3664 12: 3658 13: 3660 14: 4580 15: 3660 16: 4585 17: 3668 
 18: 4585 19: 3662 20: 3671 21: 3662 22: 3670 23: 3660 24: 3662 25: 3661 
 26: 3661 27: 3732 28: 3662 29: 4573 30: 3721 31: 4575 32: 3681 
Graphics:
 Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: ASUSTeK driver: nvidia 
 v: 465.31 bus-ID: 0b:00.0 
 Device-2: Microdia USB 2.0 Camera type: USB driver: snd-usb-audio,uvcvideo 
 bus-ID: 7-1:2 
 Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia resolution: 
 1: 1920x1080~60Hz 2: 1920x1080 3: 1920x1080 
 OpenGL: renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2 v: 4.6.0 NVIDIA 465.31 
 direct render: Yes 
Audio:
 Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel 
 bus-ID: 0b:00.1 
 Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
 v: kernel bus-ID: 0e:00.4 
 Device-3: JMTek LLC. Plugable USB Audio Device type: USB 
 driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-1:2 
 Device-4: Schiit Audio Schiit Modi 3+ type: USB driver: snd-usb-audio 
 bus-ID: 3-2:3 
 Device-5: ASUSTek ASUS AI Noise-Cancelling Mic Adapter type: USB 
 driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-5:3 
 Device-6: Microdia USB 2.0 Camera type: USB driver: snd-usb-audio,uvcvideo 
 bus-ID: 7-1:2 
 Sound Server-1: ALSA v: k5.12.9-1-MANJARO running: yes 
 Sound Server-2: JACK v: 0.125.0 running: no 
 Sound Server-3: PulseAudio v: 14.2 running: yes 
 Sound Server-4: PipeWire v: 0.3.30 running: yes 
Network:
 Device-1: Realtek RTL8125 2.5GbE driver: r8169 v: kernel port: d000 
 bus-ID: 05:00.0 
 IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: 3c:7c:3f:a6:c3:22 
 Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel 
 port: c000 bus-ID: 07:00.0 
 IF: enp7s0 state: down mac: 24:4b:fe:5b:08:2a 
Bluetooth:
 Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB 
 driver: btusb v: 0.8 bus-ID: 3-5.3:6 
 Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends 
Drives:
 Local Storage: total: 3.89 TiB used: 1.83 TiB (47.1%) 
 ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T3X0C-00SJG0 
 size: 931.51 GiB 
 ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS100T2B0C-00PXH0 
 size: 931.51 GiB 
 ID-3: /dev/sda vendor: Seagate model: ST2000LM015-2E8174 size: 1.82 TiB 
 ID-4: /dev/sdb type: USB vendor: Generic model: USB3.0 CRW -SD 
 size: 119.08 GiB 
 ID-5: /dev/sdd type: USB vendor: Samsung model: Flash Drive FIT 
 size: 119.51 GiB 
 ID-6: /dev/sde type: USB vendor: Toshiba model: TransMemory size: 14.92 GiB 
 ID-7: /dev/sdf type: USB vendor: SanDisk model: Gaming Xbox 360 size: 7.48 GiB 
Partition:
 ID-1: / size: 767 GiB used: 726.35 GiB (94.7%) fs: btrfs dev: /dev/dm-0 
 mapped: luks-466d5812-64c7-4a28-bcc4-a1a5adfa9450 
 ID-2: /boot/efi size: 511 MiB used: 26.1 MiB (5.1%) fs: vfat 
 dev: /dev/nvme0n1p1 
 ID-3: /home size: 767 GiB used: 726.35 GiB (94.7%) fs: btrfs dev: /dev/dm-0 
 mapped: luks-466d5812-64c7-4a28-bcc4-a1a5adfa9450 
Swap:
 ID-1: swap-1 type: partition size: 64 GiB used: 128.2 MiB (0.2%) 
 dev: /dev/dm-1 mapped: luks-81b2dc57-06f5-4471-b484-77c3a516f307 
Sensors:
 System Temperatures: cpu: 79.6 C mobo: 0 C gpu: nvidia temp: 41 C 
 Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:
 Processes: 964 Uptime: 1d 4h 28m Memory: 62.78 GiB used: 39.02 GiB (62.2%) 
 Init: systemd Compilers: gcc: 11.1.0 clang: 12.0.0 Packages: 2014 Shell: Bash 
 v: 5.1.8 inxi: 3.3.04 

我認為不可能輕易解決一般情況。但對於非常基本的情況來說，這並不太難。獲取根分區就像執行一樣簡單df -h /。現在一個分區是/dev/sdXdigit（最終/dev/hdXdigit）或者/dev/xxxxxpdigitxxxxx 類似於nvme0n1or的地方mmcblk0。因此，在簡單的情況下，獲取系統磁碟相對簡單：

1. 獲取 / 分區名稱
2. • 如果零件名稱以 結尾digitpdigits，則刪除pdigits

• 否則只需刪除尾隨數字

你可以這樣做：

df -h / | awk '
 NR == 2 && $1 ~ /[0-9]p[0-9]+$/ {
   disk=$1
   sub( /p[0-9]+$/, "", disk )
   print disk
 }
 NR == 2 && $1 ~ /[sh]d.[0-9]+$/ {
   disk=$1
   sub( /[0-9]+$/, "", disk )
   print disk
 }
'

但一般情況確實很複雜。/ 可以在 lvm 卷上，建構在加密設備之上設備冗餘，你最終得到一個物理設備的 2 個設備名稱）或 zfs RAID 或我不知道……

因此，假設您的系統以 EFI 模式啟動，您可能對 /boot/efi 所在的啟動盤感興趣。在這種情況下，只需替換df -h /為即可df -h /boot/efi。為什麼使用/boot/efi？因為 EFI 韌體只能引導簡單的分區，不能引導 zfs raid、luks、linux raid 或其他 Linux 可以使用的怪異東西。注意，還是有檢測系統盤的問題；完全有可能在 zfs raid、lvm、linux raid 等上/dev/sda和/上或上的某個地方安裝 /boot/efi…/dev/sdb

引用自：https://unix.stackexchange.com/questions/657296