I'm about to look into Ceph storage for my PVE cluster and have some questions I hope you guys can help with :)
I'm having a 3-node PVE3 "cluster" with local disks only. (I use cluster function just to have single web UI)
I'm looking into upgrading to PVE5 and then maybe start looking into...
I have some weird behaviours with PVE 3.3-5.
Occasionally, GUI reports failed/red nodes in our PVE cluster. After some minutes all nodes return to green state again.
This behaviour typically occours while having connection issue with NFS (only used for backup, templates, ISOs).
I don't recommend backing up directly to remote storage. Instead backup to local storage and rsync to remote storage.
Also recommending patching Proxmox Backup to support differential backup:
I actually do have Adaptec controller, and did install the maxView Storage Manager. Didn't have any issues with that though - it just worked :)
I still can log in to maxView - so not sure if that is the reason of the Proxmox upgrade errors. Everything seems to work.. just curious...
Have any of you ever seen this error when upgrading Proxmox?
Setting up pve-firmware (1.1-3) ...
Setting up pve-qemu-kvm (1.7-8) ...
Setting up qemu-server (3.1-16) ...
Setting up libpve-common-perl (3.0-18) ...
Setting up pve-manager (3.2-4) ...
Restarting PVE Daemon: pvedaemonCan't...
CPU BOGOMIPS: 47881.56
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 470.09 MB/sec
AVERAGE SEEK TIME: 5.17 ms
DNS EXT: 144.45 ms
DNS INT: 62.33 ms (lf.local)
We are still seeing backup issues with Proxmox. Issues only occour on Windows VMs.
Backup completes 100%, no errors. But inside Windows VM we receive an Atapi event ID 9 (The device, \Device\Ide\IdePort0, did not respond within the timeout period.).
And Windows either get unrespondable or...
Thanks for your ideas, but as I write, Proxmox installation is indeed working with 3.1 installer. So I can now boot Proxmox, update it to 3.2 and reboot Works fine.
So as I wrote, there must be some changes in the 3.1 vs 3.2 installer.
After some searching in the forum, I tried out installing Proxmox 3.1. Installation went fine, and I can also boot(!!).
After doing aptitude update && aptitude dist-upgrade to Proxmox 3.2, evertyhing still Works perfect!
So there must be some changes/issues in the 3.2 installer?
No, I checked that. Also when starting install with "debug" boot option, I see that the RAID volume is sda - so installer see it as first disk too.
I checked that /sys/Blocks/sda/removable is 1. Don't know if that is a problem... other installs would return 0.
Just tried installing RHEL 6.5 - Works fine.
Will try tomorrow installing Debian Wheezy to see how it reacts.
If you have any ideas what could be the issue - please post! :)
I've googled a bit and seems that there are some issues with GRUB, EFI and Kernel version <3.0 - but since I can install...