История изменений
Исправление manul91, (текущая версия) :
Проверил в debian на виртуалке, все работает.
(убрал quiet из kernel line чтобы смотреть на сообщения. Правда несколько медленней забутился с вытащенном диске, висел где-то 15-20 лишних секунд на каком-то local-block скрипте что не бывает если все нормально).
Процесс теста: инсталляция trixie stable с нуля в виртуалке, / на raid1, UEFI подключено (EFI на оба диска подшаманил чтобы бутился с любого).
Сначала пока с рейдом все нормально, ничего не трогаем.
Выключаем виртуалку.
В выключенном состоянии, убираем одного из дисков рейда.
Запускаем снова, теперь только с одним диском - все работает.
Расходимся, ложная тревога.
Вот результат после запуска:
root@debian-test:~# dmesg | grep md1
[  116.170130] md/raid1:md1: active with 1 out of 2 mirrors
[  116.170406] md1: detected capacity change from 0 to 36046848
[  177.102806] EXT4-fs (md1): orphan cleanup on readonly fs
[  177.104666] EXT4-fs (md1): mounted filesystem 750be247-574a-4afa-9cc8-bace54e390e2 ro with ordered data mode. Quota mode: none.
[  181.933540] EXT4-fs (md1): re-mounted 750be247-574a-4afa-9cc8-bace54e390e2 r/w.
root@debian-test:~# 
root@debian-test:~# cat /proc/mdstat 
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md0 : active (auto-read-only) raid1 sda2[0]
      1950720 blocks super 1.2 [2/1] [U_]
      
md1 : active raid1 sda3[0]
      18023424 blocks super 1.2 [2/1] [U_]
      
unused devices: <none>
root@debian-test:~# cat /etc/mdadm/mdadm.conf 
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md/0  metadata=1.2 UUID=db7490bc:a8145226:33d0a03e:f92d4dc2
ARRAY /dev/md/1  metadata=1.2 UUID=4cf70a58:2d86b830:eff2f233:bcb9c87e
# This configuration was auto-generated on Sun, 02 Nov 2025 13:55:08 -0500 by mkconf
root@debian-test:~# 
root@debian-test:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINTS
sda       8:0    0   20G  0 disk  
├─sda1    8:1    0  953M  0 part  /boot/efi
├─sda2    8:2    0  1.9G  0 part  
│ └─md0   9:0    0  1.9G  0 raid1 [SWAP]
└─sda3    8:3    0 17.2G  0 part  
  └─md1   9:1    0 17.2G  0 raid1 /
sr0      11:0    1 1024M  0 rom   
root@debian-test:~# efibootmgr -v | grep debian
Boot0001* debian2       HD(1,GPT,6f9e73da-2140-4648-a163-3e62860d9835,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
Boot0004* debian        HD(1,GPT,c6367fff-b688-4570-9370-8b6f8723c267,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
root@debian-test:~# ls -al /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 100 Nov  2 14:49 .
drwxr-xr-x 8 root root 160 Nov  2 14:47 ..
lrwxrwxrwx 1 root root   9 Nov  2 14:49 3caf28fc-ebb0-4486-9769-5ec78ee31304 -> ../../md0
lrwxrwxrwx 1 root root  10 Nov  2 14:47 5BA0-ED87 -> ../../sda1
lrwxrwxrwx 1 root root   9 Nov  2 14:49 750be247-574a-4afa-9cc8-bace54e390e2 -> ../../md1
root@debian-test:~# cat /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).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/md1 during installation
UUID=750be247-574a-4afa-9cc8-bace54e390e2 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=5BA0-ED87  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/md0 during installation
UUID=3caf28fc-ebb0-4486-9769-5ec78ee31304 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
root@debian-test:~# 
root@debian-test:~# cat /boot/grub/grub.cfg | grep linux | grep boot
        linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
root@debian-test:~# hostnamectl 
 Static hostname: debian-test
       Icon name: computer-vm
         Chassis: vm 🖴
      Machine ID: debd53a7af31403fbd3d2d4e249d672d
         Boot ID: f2992371a4bf4c3bb61a84877b341b47
    Product UUID: 5accc1b2-947e-6440-a405-00387bf6301d
    AF_VSOCK CID: 1
  Virtualization: oracle
Operating System: Debian GNU/Linux 13 (trixie)                   
          Kernel: Linux 6.12.48+deb13-amd64
    Architecture: x86-64
 Hardware Vendor: innotek GmbH
  Hardware Model: VirtualBox
 Hardware Serial: VirtualBox-b2c1cc5a-7e94-4064-a405-00387bf6301d
Firmware Version: VirtualBox
   Firmware Date: Fri 2006-12-01
    Firmware Age: 18y 11month 2d      
Исправление manul91, :
Проверил в debian на виртуалке, все работает.
(убрал quiet из kernel line чтобы смотреть на сообщения. Правда несколько медленней забутился с вытащенном диске, висел где-то 15-20 лишних секунд на каком-то local-block скрипте что не бывает если все нормально).
Процесс теста: инсталляция trixie stable с нуля в виртуалке, / на raid1, UEFI подключено (EFI на оба диска подшаманил чтобы бутился с любого).
Выключаем виртуалку. В выключенном состоянии, убираем одного из дисков. Запускаем снова, теперь только с одним диском - все работает.
Расходимся, ложная тревога.
Вот результат после запуска:
root@debian-test:~# dmesg | grep md1
[  116.170130] md/raid1:md1: active with 1 out of 2 mirrors
[  116.170406] md1: detected capacity change from 0 to 36046848
[  177.102806] EXT4-fs (md1): orphan cleanup on readonly fs
[  177.104666] EXT4-fs (md1): mounted filesystem 750be247-574a-4afa-9cc8-bace54e390e2 ro with ordered data mode. Quota mode: none.
[  181.933540] EXT4-fs (md1): re-mounted 750be247-574a-4afa-9cc8-bace54e390e2 r/w.
root@debian-test:~# 
root@debian-test:~# cat /proc/mdstat 
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md0 : active (auto-read-only) raid1 sda2[0]
      1950720 blocks super 1.2 [2/1] [U_]
      
md1 : active raid1 sda3[0]
      18023424 blocks super 1.2 [2/1] [U_]
      
unused devices: <none>
root@debian-test:~# cat /etc/mdadm/mdadm.conf 
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md/0  metadata=1.2 UUID=db7490bc:a8145226:33d0a03e:f92d4dc2
ARRAY /dev/md/1  metadata=1.2 UUID=4cf70a58:2d86b830:eff2f233:bcb9c87e
# This configuration was auto-generated on Sun, 02 Nov 2025 13:55:08 -0500 by mkconf
root@debian-test:~# 
root@debian-test:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINTS
sda       8:0    0   20G  0 disk  
├─sda1    8:1    0  953M  0 part  /boot/efi
├─sda2    8:2    0  1.9G  0 part  
│ └─md0   9:0    0  1.9G  0 raid1 [SWAP]
└─sda3    8:3    0 17.2G  0 part  
  └─md1   9:1    0 17.2G  0 raid1 /
sr0      11:0    1 1024M  0 rom   
root@debian-test:~# efibootmgr -v | grep debian
Boot0001* debian2       HD(1,GPT,6f9e73da-2140-4648-a163-3e62860d9835,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
Boot0004* debian        HD(1,GPT,c6367fff-b688-4570-9370-8b6f8723c267,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
root@debian-test:~# ls -al /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 100 Nov  2 14:49 .
drwxr-xr-x 8 root root 160 Nov  2 14:47 ..
lrwxrwxrwx 1 root root   9 Nov  2 14:49 3caf28fc-ebb0-4486-9769-5ec78ee31304 -> ../../md0
lrwxrwxrwx 1 root root  10 Nov  2 14:47 5BA0-ED87 -> ../../sda1
lrwxrwxrwx 1 root root   9 Nov  2 14:49 750be247-574a-4afa-9cc8-bace54e390e2 -> ../../md1
root@debian-test:~# cat /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).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/md1 during installation
UUID=750be247-574a-4afa-9cc8-bace54e390e2 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=5BA0-ED87  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/md0 during installation
UUID=3caf28fc-ebb0-4486-9769-5ec78ee31304 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
root@debian-test:~# 
root@debian-test:~# cat /boot/grub/grub.cfg | grep linux | grep boot
        linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
root@debian-test:~# hostnamectl 
 Static hostname: debian-test
       Icon name: computer-vm
         Chassis: vm 🖴
      Machine ID: debd53a7af31403fbd3d2d4e249d672d
         Boot ID: f2992371a4bf4c3bb61a84877b341b47
    Product UUID: 5accc1b2-947e-6440-a405-00387bf6301d
    AF_VSOCK CID: 1
  Virtualization: oracle
Operating System: Debian GNU/Linux 13 (trixie)                   
          Kernel: Linux 6.12.48+deb13-amd64
    Architecture: x86-64
 Hardware Vendor: innotek GmbH
  Hardware Model: VirtualBox
 Hardware Serial: VirtualBox-b2c1cc5a-7e94-4064-a405-00387bf6301d
Firmware Version: VirtualBox
   Firmware Date: Fri 2006-12-01
    Firmware Age: 18y 11month 2d      
Исправление manul91, :
Проверил на виртуалке, все работает.
(убрал quiet из kernel line чтобы смотреть на сообщения. Правда несколько медленней забутился с вытащенном диске, висел где-то 15-20 лишних секунд на каком-то local-block скрипте что не бывает если все нормально).
Процесс теста: инсталляция trixie stable с нуля в виртуалке, / на raid1, UEFI подключено (EFI на оба диска подшаманил чтобы бутился с любого).
Выключаем виртуалку. В выключенном состоянии, убираем одного из дисков. Запускаем снова, теперь только с одним диском - все работает.
Вот результат после запуска:
root@debian-test:~# dmesg | grep md1
[  116.170130] md/raid1:md1: active with 1 out of 2 mirrors
[  116.170406] md1: detected capacity change from 0 to 36046848
[  177.102806] EXT4-fs (md1): orphan cleanup on readonly fs
[  177.104666] EXT4-fs (md1): mounted filesystem 750be247-574a-4afa-9cc8-bace54e390e2 ro with ordered data mode. Quota mode: none.
[  181.933540] EXT4-fs (md1): re-mounted 750be247-574a-4afa-9cc8-bace54e390e2 r/w.
root@debian-test:~# 
root@debian-test:~# cat /proc/mdstat 
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md0 : active (auto-read-only) raid1 sda2[0]
      1950720 blocks super 1.2 [2/1] [U_]
      
md1 : active raid1 sda3[0]
      18023424 blocks super 1.2 [2/1] [U_]
      
unused devices: <none>
root@debian-test:~# cat /etc/mdadm/mdadm.conf 
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md/0  metadata=1.2 UUID=db7490bc:a8145226:33d0a03e:f92d4dc2
ARRAY /dev/md/1  metadata=1.2 UUID=4cf70a58:2d86b830:eff2f233:bcb9c87e
# This configuration was auto-generated on Sun, 02 Nov 2025 13:55:08 -0500 by mkconf
root@debian-test:~# 
root@debian-test:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINTS
sda       8:0    0   20G  0 disk  
├─sda1    8:1    0  953M  0 part  /boot/efi
├─sda2    8:2    0  1.9G  0 part  
│ └─md0   9:0    0  1.9G  0 raid1 [SWAP]
└─sda3    8:3    0 17.2G  0 part  
  └─md1   9:1    0 17.2G  0 raid1 /
sr0      11:0    1 1024M  0 rom   
root@debian-test:~# efibootmgr -v | grep debian
Boot0001* debian2       HD(1,GPT,6f9e73da-2140-4648-a163-3e62860d9835,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
Boot0004* debian        HD(1,GPT,c6367fff-b688-4570-9370-8b6f8723c267,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
root@debian-test:~# ls -al /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 100 Nov  2 14:49 .
drwxr-xr-x 8 root root 160 Nov  2 14:47 ..
lrwxrwxrwx 1 root root   9 Nov  2 14:49 3caf28fc-ebb0-4486-9769-5ec78ee31304 -> ../../md0
lrwxrwxrwx 1 root root  10 Nov  2 14:47 5BA0-ED87 -> ../../sda1
lrwxrwxrwx 1 root root   9 Nov  2 14:49 750be247-574a-4afa-9cc8-bace54e390e2 -> ../../md1
root@debian-test:~# cat /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).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/md1 during installation
UUID=750be247-574a-4afa-9cc8-bace54e390e2 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=5BA0-ED87  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/md0 during installation
UUID=3caf28fc-ebb0-4486-9769-5ec78ee31304 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
root@debian-test:~# 
root@debian-test:~# cat /boot/grub/grub.cfg | grep linux | grep boot
        linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
root@debian-test:~# hostnamectl 
 Static hostname: debian-test
       Icon name: computer-vm
         Chassis: vm 🖴
      Machine ID: debd53a7af31403fbd3d2d4e249d672d
         Boot ID: f2992371a4bf4c3bb61a84877b341b47
    Product UUID: 5accc1b2-947e-6440-a405-00387bf6301d
    AF_VSOCK CID: 1
  Virtualization: oracle
Operating System: Debian GNU/Linux 13 (trixie)                   
          Kernel: Linux 6.12.48+deb13-amd64
    Architecture: x86-64
 Hardware Vendor: innotek GmbH
  Hardware Model: VirtualBox
 Hardware Serial: VirtualBox-b2c1cc5a-7e94-4064-a405-00387bf6301d
Firmware Version: VirtualBox
   Firmware Date: Fri 2006-12-01
    Firmware Age: 18y 11month 2d      
Исходная версия manul91, :
Проверил на виртуалке, все работает.
(убрал quiet из kernel line чтобы смотреть на сообщения. Правда несколько медленней забутился с вытащенном диске, висел где-то 15-20 лишних секунд на каком-то local-block скрипте что не бывает если все нормально).
Процесс теста: инсталляция trixie stable с нуля в виртуалке, / на raid1, UEFI подключено (EFI на оба диска подшаманил чтобы бутился с любого).
Выключаем виртуалку. В выключенном состоянии, убираем одного из дисков. Запускаем снова, теперь только с одним диском - все работает.
Вот результат после запуска:
root@debian-test:~# dmesg | grep md1
[  116.170130] md/raid1:md1: active with 1 out of 2 mirrors
[  116.170406] md1: detected capacity change from 0 to 36046848
[  177.102806] EXT4-fs (md1): orphan cleanup on readonly fs
[  177.104666] EXT4-fs (md1): mounted filesystem 750be247-574a-4afa-9cc8-bace54e390e2 ro with ordered data mode. Quota mode: none.
[  181.933540] EXT4-fs (md1): re-mounted 750be247-574a-4afa-9cc8-bace54e390e2 r/w.
root@debian-test:~# 
root@debian-test:~# cat /proc/mdstat 
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md0 : active (auto-read-only) raid1 sda2[0]
      1950720 blocks super 1.2 [2/1] [U_]
      
md1 : active raid1 sda3[0]
      18023424 blocks super 1.2 [2/1] [U_]
      
unused devices: <none>
root@debian-test:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINTS
sda       8:0    0   20G  0 disk  
├─sda1    8:1    0  953M  0 part  /boot/efi
├─sda2    8:2    0  1.9G  0 part  
│ └─md0   9:0    0  1.9G  0 raid1 [SWAP]
└─sda3    8:3    0 17.2G  0 part  
  └─md1   9:1    0 17.2G  0 raid1 /
sr0      11:0    1 1024M  0 rom   
root@debian-test:~# efibootmgr -v | grep debian
Boot0001* debian2       HD(1,GPT,6f9e73da-2140-4648-a163-3e62860d9835,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
Boot0004* debian        HD(1,GPT,c6367fff-b688-4570-9370-8b6f8723c267,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi)
root@debian-test:~# ls -al /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 100 Nov  2 14:49 .
drwxr-xr-x 8 root root 160 Nov  2 14:47 ..
lrwxrwxrwx 1 root root   9 Nov  2 14:49 3caf28fc-ebb0-4486-9769-5ec78ee31304 -> ../../md0
lrwxrwxrwx 1 root root  10 Nov  2 14:47 5BA0-ED87 -> ../../sda1
lrwxrwxrwx 1 root root   9 Nov  2 14:49 750be247-574a-4afa-9cc8-bace54e390e2 -> ../../md1
root@debian-test:~# cat /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).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/md1 during installation
UUID=750be247-574a-4afa-9cc8-bace54e390e2 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=5BA0-ED87  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/md0 during installation
UUID=3caf28fc-ebb0-4486-9769-5ec78ee31304 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
root@debian-test:~# 
root@debian-test:~# cat /boot/grub/grub.cfg | grep linux | grep boot
        linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.48+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro  
                linux   /boot/vmlinuz-6.12.43+deb13-amd64 root=UUID=750be247-574a-4afa-9cc8-bace54e390e2 ro single dis_ucode_ldr 
root@debian-test:~# hostnamectl 
 Static hostname: debian-test
       Icon name: computer-vm
         Chassis: vm 🖴
      Machine ID: debd53a7af31403fbd3d2d4e249d672d
         Boot ID: f2992371a4bf4c3bb61a84877b341b47
    Product UUID: 5accc1b2-947e-6440-a405-00387bf6301d
    AF_VSOCK CID: 1
  Virtualization: oracle
Operating System: Debian GNU/Linux 13 (trixie)                   
          Kernel: Linux 6.12.48+deb13-amd64
    Architecture: x86-64
 Hardware Vendor: innotek GmbH
  Hardware Model: VirtualBox
 Hardware Serial: VirtualBox-b2c1cc5a-7e94-4064-a405-00387bf6301d
Firmware Version: VirtualBox
   Firmware Date: Fri 2006-12-01
    Firmware Age: 18y 11month 2d