Search results

I'm having this issue as well. For some reason the active disk is on the NFS share when it should be on the local storage. I need to move this, but don't see how.

Any guidance as to how to expose the dvb_demux.h? It looks like there were some issues around the 3.7 kernel, but given how much more up to date the kernel is in Proxmox, I assumed those methods wouldn't work. root@TVheadend:~/dvbhdhomerun-0.0.15/kernel# apt-get install build-essential...

I guess I'll just wipe everything I've got on there and start over.

The entire system was on four discs in a single zpool (rpool). It was setup similarly to RAID 10 (I forget the order, but two sets of pools, each with two discs, stripped and mirrored).

Any ideas? Bueller? Bueller?

Having gotten nowhere with the existing install, I'm attempting to mount the previous zpool into the Proxmox now on USB stick. After some install issues (3.4 wouldn't install, had to install 3.3 and then upgrade) and then some rootdelay issues (I had to set it to 20 instead of the 10 I saw in...

What about installing ProxMox to a USB stick and importing the ZFS pools on the existing disks? I know in my Nexenta setup, existing pools import rather flawlessly, but of course, I'd have to reconfigure the system unless someone knows a better way?

I'm experiencing similar issues on a Dell Optiplex 790 with four disks in ZFS 10 pools.

Dell OptiPlex 790 with four HDDs in a ZFS 10. I remember having difficulties when I first started in getting PVE to boot, but I must have solved them because I've been running for a while. I shut the system down and now I can't get it to successfully boot. One drive says this...

*bump*I'm looking at a two node setup with ZFS and DRBD. Cheapest way for redundancy. I saw a guide on how to do it, but it was before ProxMox had official ZFS support, so it's probably not accurate anymore.

My problem was that the Virtual Machines page was open in another Chrome tab. That tab had the SSL error screen up and apparently wouldn't load that page elsewhere unless I acknowledged the prompt on the first screen.

I can peruse almost all parts of the web interface. For some reason the virtual machines portion is not responding. I've waited several minutes and nothing. I have maybe 30 VMs. I rebooted the machine. Ideas?

Soon I'll have an iSCSI SAN available. Is iSCSI in ProxMox production ready? Would I be able to setup different locations for different types of servers? Point regular containers to a LUN backed by RAID 5, while high disk activity containers are on a LUN backed by RAID 10 or 1E? I...

Indeed. That's what I did on my ProxMox box to properly accept the OpenVZ migration. Will it stay as it is when moving to a new ProxMox box? Silly Debian. ;-)

When you migrate from OpenVZ to ProxMox, it maintains the files in the original locations. When you migrate from one ProxMox to another, does it maintain that same location, or will it move it to where it is supposed to be? OpenVZ defaults to /vz/ while ProxMox defaults to /var/lib/vz.

I already created the symlink.

Outside of /var/lib/vz, only 900 megs is being used out of 1.5 TB.

Any other ideas?

I can assure you ti is not out of disk space.

Created and I get the following errors when trying to migrate. I made sure to rm-rf the private folders for 110 and 121 first.