Nothing to boot. No such a file or directory. - On VM start

[herby]

Hey!

Installed a debian to a VM , but its not booting.
Processor: AMD A10-6800K APU
Motherboard: ASRock FM2A88X Extreme6+

root@herby:~#pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.60-2-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-13
pve-kernel-5.15: 7.2-12
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-3
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-4
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

root@herby:~# qm config 100
boot: order=net0
cores: 3
memory: 4656
meta: creation-qemu=7.0.0,ctime=1665665847
name: herby-deb-prd
net0: virtio=36:4B:59:73:74:00,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: guest_os_storage250G:vm-100-disk-0,size=76904M
scsihw: virtio-scsi-pci
smbios1: uuid=8bb33e53-6a5e-40ab-8b83-985e8b154dcd
sockets: 1
unused0: big_data4T:vm-100-disk-0
vmgenid: ce77b595-3eba-44dd-8e56-bce61e02c580

I tried a live cd boot and, I seen the entire filesystem ,that i installed previously. (attached as VM100_live_cd)

The syslog not showing errors during start.

Any ideas?

Thanks,

 

[Moayad]

Hello,

Thank you for the outputs!

Can I ask you what is the unused0 disk is? Maybe you installed the OS on it?

unused0: big_data4T:vm-100-disk-0

In order to re add the disk again, you have to select it from the PVE web UI then click on Edit then add.

 

[herby]

Hello,

Its my data disk. I de-attached this before installation on purpose. I dont wanna risk to lose the data on it by "miss clicking" while partitioning.
Previously it work fine. Today, i screwed a HDD , and i had to change it. Unfotunatly it was the guest-os-storage. So i got a new one and added to the server itself. And now im trying to install the system again.

BR,
Herby

 

[B.Otto]

root@herby:~# qm config 100
boot: order=net0
...
scsi0: guest_os_storage250G:vm-100-disk-0,size=76904M
...
unused0: big_data4T:vm-100-disk-0

Hey,

you have configured that the Bios only tries to boot from the network sevice net0, nothing else. If the disk that you added as scsi0 is the one you want to boot from, then you need to add it to the boot options via

GUI: VM -> Options -> Boot Options

or by editing the config file 100.conf :
boot: order=scsi0;net0

Kind regards,
Benedikt

 

[herby]

Hey,

you have configured that the Bios only tries to boot from the network sevice net0, nothing else. If the disk that you added as scsi0 is the one you want to boot from, then you need to add it to the boot options via

GUI: VM -> Options -> Boot Options

or by editing the config file 100.conf :
boot: order=scsi0;net0

Kind regards,
Benedikt

Hey!

It works!

Thanks!