Recent content by Fortel

I really appreciate your help, Udo. Even if this proves to be fruitless (which I'm suspecting will be the case.) find /var/lib/vz -name vm-105-disk-1.qcow2 -ls <-- This turns up empty- nothing found. The shell history is an interesting idea. My brief review of that file doesn't show any...

When I first set these up, I followed a tutorial- and everything just worked. But clearly, something wasn't done correctly. Since the VM was running (and had been for a long time,) I thought it must be set up correctly. This is not a production machine, per se, but it did have data on it that...

Hi Udo, The missing disk is not important, but the VM appears to be dead without it. So, in that sense, perhaps the missing disk is important. root@denpm1:~# cat /etc/pve/qemu-server/105.conf bootdisk: ide1 cores: 2 ide1: Backups:105/vm-105-disk-1.qcow2,format=qcow2,cache=writeback,size=54G...

Thanks, Wolfgang. I did find that post earlier today. But the difference is, my vm is not running. Seems my mistake (or one of my mistakes!) was to shut down the VM. That was before I realized the disk was missing. I'm not sure if adding back an empty disk will bring life back to this VM...

Thank you, Wolfgang... The disk is definitely gone. This VM was set up a long time ago, along with another very similar VM. This one ran out of space- I shut it down, and discovered the disk is gone. The other VM is still running, but also has no disk! Any chance of a recovery somehow...

I think I'm hosed. But I have an old (2 months) backup, so not completely hosed. We have a Proxmox 3.3 host in a remote data center, running mostly OpenVZ instances. But we have 2 KVM machines running Windows. I have very little experience with KVM... The drive on one of those filled to...

Love ProxMox, and have several hosts in production, with dozens of containers. We test everything on the bench before putting it into production. So our bench setup is the latest 1.8 version. We use OpenVZ containers exclusively... Here's the issue... We have set the two nics in our...

Okay, finally gave up trying to make hpacucli installed on a VZ guest talk to the controller. The installation (hpacucli_8.28-13.0.10-9_amd64.deb) on the host was easy, and seems to work fine. Next task will be a script to check the array and, if a change exists, to email the information. Peter

Stef1777, So I understand correctly, you installed hpacucli on a Debian vz guest node, as opposed to the hardware host? If so, then maybe the difference is 1.3 (the version I'm using) and your 1.5 installation.

We're not having any luck. We've installed the HP ADU utilities on guest images (both Debian and CentOS) and can launch the software. But the controller isn't detected. Wondering what others are doing to monitor the drive arrays in their HP DL series servers... Peter

We need to be able to monitor the drives, etc, in our servers. HP has the software to do it. We just haven't had any success in running it from a Proxmox OpenVZ guest. A KVM image may produce a better result, but that's not our preference. Thanks for the HP / Debian links. We've been...