Boot Failure

  • Thread starter Thread starter rameses
  • Start date Start date
R

rameses

Guest
I've been using Proxmox VE 1.6 since last year with Openfiler and all of a sudden one of the server crashed with error:
Booting from Hard Disk ...
Boot failed: not a bootable disk
FATAL: No bootable device
I tried booting up the same server from another Proxmox VE server but same issue. What could cause the kernel to crash? Is it a Openfiler issue or Proxmox VE? Does Proxmox VE offers any paid support? I'll appreciate any help.
 
I've been using Proxmox VE 1.6 since last year with Openfiler and all of a sudden one of the server crashed with error:
Booting from Hard Disk ...
Boot failed: not a bootable disk
FATAL: No bootable device
I tried booting up the same server from another Proxmox VE server but same issue. What could cause the kernel to crash? Is it a Openfiler issue or Proxmox VE? Does Proxmox VE offers any paid support? I'll appreciate any help.
Hi,
first - the proxmox team offer paid services (tickets). But i don't know if they can do anything with an damaged harddisk-file!
What format has the image? Raw, or qcow2?
If raw, what say "file raw-image" and what "fdisk -l raw-image"?
Whats about backup??

If only the partition is damaged, there are live-cds available which can reconstruct a damage partition-map.

Can you see Partitions if you boot a live-cd like grml?

Udo
 
I've been using Proxmox VE 1.6 since last year with Openfiler and all of a sudden one of the server crashed with error:
Booting from Hard Disk ...
Boot failed: not a bootable disk
FATAL: No bootable device
I tried booting up the same server from another Proxmox VE server but same issue. What could cause the kernel to crash? Is it a Openfiler issue or Proxmox VE? Does Proxmox VE offers any paid support? I'll appreciate any help.
Hi,
i had today a similiar problem. Do you have the parameter "cache=none" in the vm-config (for vm-harddisk)? Normaly this speed up the diskaccess but in my case the client can't boot.
cache=writethrough solve the problem. See also http://forum.proxmox.com/threads/6129-lvm-disk-not-accessible-after-update-to-1.8?p=34736#post34736

Udo