Search results

The Fix was to boot into knoppix, mount the LV and edit fstab. Getting rid of the bad entries solved the problem. My migration path (over time) was 1.8 -> backup -> restore to 2.2 on new hardware - > 2.3 in place upgrade -> 3.0. I am 90% sure that these fstab entries moved with me, I don't...

Here is the end of the boot where it hangs. Note that it looks like I have 2 bad nfs mounts in there, is there any way around this to get the system to the point where I can edit fstab? I'm guessing this is the problem. It will wait here forever, never times out.

I don't know if that is it, I can't remember the boot order but wouldn't sshd be up before rpc comes up? Also, I tried to boot a few of the recovery console's from GRUB and got the same result. Are the recovery consoles set to Run Level 1? I'm pretty concerned here. The system was fine...

Ok, I did a little more checking. 1) Box is pingable 2) ssh is refused (connection refused). 3) I tried the last 2 kernels - same result 4) I tried booting it with the nic unplugged - same result. 5) I went into grub and removed the 'quiet' - booting shows the nic coming up but hangs at the...

Just did an upgrade from 2.2 -> 2.3, that went fine. Then immediately did an upgrade to 3.0. Now on boot the boot process stops with the last message being: Waiting for vmbr0 to get ready (MAXWAIT 2 seconds). It just hangs here forever. This is a Dell R310 Anyone have any ideas?

I ran into an old proxmox server that was still on 1.1. I went to start the upgrade process but it looks like the script is not on the website anymore. Is it available anywhere? wget http://pve.proxmox.com/debian/dists/lenny/pve-upgrade-1.1-to-1.2 --14:41:51--...

Thought I'd pass this along, I spent about a day getting snmp working with proxmox and monitoring DELL hardware level information. Here is how I did it: Install and configure the Zenoss appliance from the appliance repo Get the Dell and AdvHardware zenpacks, install both and then restart...

Hi Tom- The output of pveversion -v before I did the 'aptitude dist-upgrade' is in my first post. Below is the output after: vlinux03:/etc/vz/conf# pveversion -v pve-manager: 1.5-8 (pve-manager/1.5/4674) running kernel: 2.6.18-2-pve proxmox-ve-2.6.18: 1.5-5 pve-kernel-2.6.18-2-pve: 2.6.18-5...

aptitude dist-upgrade fixed it.

Hi all - I had an old machine that was still running 1.1 and I decided tonight to try an upgrade to 1.5.. It looks like the kernel got upgraded but proxmox did not. Anyone have any ideas? vlinux03:~# pveversion -v pve-manager: 1.1-1 (pve-manager/1.1/3664) qemu-server: 1.1-11 pve-kernel...

Just a note to the mods to check the website.

It looks like hardware raid to me, you build the arrays in BIOS. Here is a link to the manual http://www.highpoint-tech.com/PDF/RR26XX/RR2680_UM_EN_10_091008.pdf However I can't find any reference to which chipset it uses. -Mike

Does anyone know if the rocket raid 2680 is supported? Newegg has them on sale for $145!!

That's exactly what I was looking for... thank you!

You are correct. I guess I go back to my original question - is the system smart enough to assign the "test" network to br1? I didn't see a place to configure that.

The network on br1 is simply a /24 with no router. It is a test network. But it sounds like what you are saying is that there is no way to set the mask to other than 255.255.255.255??

I have 2 physical networks, which are not physically connected. I'd like the VM to have a virtual interface on both networks.

Hi - I was wondering if it is possible to create a dual homed VM? I was able to create a second bridge in proxmox - br1. BR0 has eth0 and BR1 has eth1 I also can see how you can add multiple IPs to a VM and this works, by comma separating the IPs. I guess the question is how do I take one...

Actually if you look closer at the log file it looks like the system time is getting set in the middle of the startup. It's actually starting in the right order: init -> rc.sysinit, run level 3 but they messages in the log are coming at different times. Back to the drawing board to figure out...

Here is some more info. I did a simple test. I'm running the standard centos-4-7 template from the proxmox website. After installing I simply did: yum install mysql-server then I did a reboot of the container. here is /var/log/messages: May 8 07:27:26 test2 httpd: httpd shutdown...