VM doesn't work - No bootable device

[Golden Automação]

Virtual machine doesn't start the operation system. It shows an error message: "No botable device".



This machine was working normally before the pve server reboot.

I've tried:
- Check de boot configuration

vm "102.conf":
agent: 1
balloon: 1024
boot: order=sata0
cores: 2
cpu: qemu64
ide2: none,media=cdrom
memory: 2048
name: cloud-server
net0: virtio=56:60:AA:EC:E2A,bridge=vmbr0
numa: 0
ostype: l26
sata0: local-lvm:vm-102-disk-0,size=128G
scsihw: virtio-scsi-pci
smbios1: uuid=b031a9b3-327d-4722-a272-c617d0f622ca
sockets: 2
tablet: 0
vga: virtio
vmgenid: 1f08b1b9-30b2-4acc-92f8-464e0eba62b4

 

[JeremyKou]

I saw the same error in pve-manager/7.1-8/5b267f33 (running kernel: 5.13.19-2-pve) , two VMs working fine before restart VM node, my VMs are backend with iSCSI storage. I have changed scsi controller and hard disk type with no change, also I have tried fix boot error with CentOS iso without finding file system at all, mount this VM disk to a running Linux run fsck failed.

[root@bogon ~]# fsck -f /dev/sda


fsck，来自 util-linux 2.23.2


e2fsck 1.42.9 (28-Dec-2013)


ext2fs_open2: Bad magic number in super-block


fsck.ext2: 超级块无效, trying backup blocks...


fsck.ext2: Bad magic number in super-block 当尝试打开 /dev/sda 时





The 超级块 could not be read or does not describe a correct ext2


文件系统. If the 设备 is valid and it really contains an ext2


文件系统 (and not swap or ufs or something else), then the 超级块


is corrupt, and you might try running e2fsck with an alternate 超级块:


e2fsck -b 8193 <设备>





[root@bogon ~]# e2fsck -b 8192 /dev/sda


e2fsck 1.42.9 (28-Dec-2013)


e2fsck: Bad magic number in super-block 当尝试打开 /dev/sda 时





The 超级块 could not be read or does not describe a correct ext2


文件系统. If the 设备 is valid and it really contains an ext2


文件系统 (and not swap or ufs or something else), then the 超级块


is corrupt, and you might try running e2fsck with an alternate 超级块:






e2fsck -b 8193 <设备>

 

[systemd-dont-suck]

I resolved going to VM>Options>boot order and making sure my SCSI drive I installed OS on was selected, my boot order had defaulted to nic since I had erroneously set my controller type to Default, and then back to VirtIOSCSI.