I/O Waits are quite low as I use SSDs for local storage/lvm-thin but generally disk I/O is high with lots and lots of reads and writes going on (web/email/database within the VMs).Īnd clearly 1000s of proxmox users are also having no problems. I have rebooted both the VM and the entire Node since then with no issues. I can say that I very recently resized a VM's partition by 100GB with no issues. I do not know if anything else might touch the disk in some way during normal KVM/Qemu/Proxmox operations. Outside the VM, during a Proxmox backup operation, when a snapshot is in progress I can imagine there is some sort of interaction with all bits in the disk image. I don't know if the fstrim process could cause damage though, and I have that running weekly within all VMs (with no issues thus far). Surely they are written once and then they only need to be read, unless the partition is resized. It seems to me that NOTHING should write to the MBR or partition table during normal operation of a the VM's OS. ** I do not pretend to know or understand the low level ways filesystems work and what writes/does not write to the MBR/partition table ** but. I've been thinking about it, and I wonder if we should try to determine what could and what could not cause the MBR/partition table to be damaged or lost. There's a hint that it may occur during high disk I/O, or maybe during backup (which is sort of a higher than usual disk I/O, I suppose), but that's about it.įor those who experienced this issue, I'd appreciate it if you could post some information about your setup, such as: PVE version, Local storage or Ceph? LVM-Thin or something else? Generally high disk i/o, high I/O wait, or not? Did you backup very soon before the incident happened? What sort of hardware are you using?Īnd finally, do you keep your Proxmox system up to date or do you have older I'm not sure the issue is the same as we're discussing (disk images that were absolutely fine suddenly losing MBR/partition table and become unbootable with "not a bootable disk") but maybe there's a connection with what you have experienced and I appreciate your post. So far I've not seen any absolute commonality. VirtualBox FATAL No bootable medium found System halted Solucion DefinitivaEn el video se explicara como resolver el error al instalar cualquier sistema o. I'll shortly be making backups of the MBR/partition tables of all my VMs and maybe I'll feel a little better afterwards.īut it seems to me that something must be going on that is causing this to happen to more than one user in recent weeks. Please just take it as being similar to having a broken arm but invisible to the naked eye - it can be fixed but it takes time to heal. If you have no experience of such a mental tunnel vision then you won't understand. Yes, this is silly/stupid, but it is how I am at the moment. Unfortunately this causes me to worry that it might happen to me. Yes, we're only taking about 2 or 3 users posting about a problem out of many, many thousands, but it is clearly not an isolated incident with only one user being unlucky and encountering some random issue. Several people have posted about problems with VMs not booting with "no Bootable Media found" errors recently.
0 Comments
Leave a Reply. |