Search results

Good on ya. Fingers crossed.

I Agree. I've seen so many issues just because of wrong type memory. Simply swapping memory between two hosts solved problem for me. Or in some cases buying brand new memory sticks of different brand/suplier. Please post dump here. Might be there is something interesting.

No. But I guess you should try to reinstall grub. I noticed you have /boot on raid. Please do the following next time you onsite: ~# vim /etc/fstab comment out UIID /boot ~# echo 'GRUB_DISABLE_LINUX_UUID=true' >> /etc/default/grub ~# echo 'GRUB_PRELOAD_MODULES="raid dmraid"' >>...

UEFI? - switch to EFI legacy mode and disable "secure boot" in MB BIOS wrong disk? fake raid?

Should be. It just standard LVM thing. UUID is better because in that case you never mix up your disks. nope. Yep. Just do filter LVM each other on both 1st and 2nd drives. This workaround is not for mirroring. It just one way to have dual boot. PS: Hmm... I just realise what if you need to...

My 2c for DRDB. http://pve.proxmox.com/wiki/DRBD DRBD might be beneficial if you run two cluster nodes and wish to have replicated shared storage. I used DRBD for a number of projects and that what I can summarise from my experience. pros: +can squeeze maximum performance vs other clustered...

Agreed. To dangerous for production. You might have other ideas how to localise the problem. eg. USB HDD connected temporary to work it out. Sometimes figures looks bigger the default bwlimit however it cached and balanced when goes to the network. I agreed with symmcom that more likely...

Hard to diagnose when problem is not persistent. Can you guess what's common for these vms? Are they all Windows? Windows can do filesystem optimisations which might make it more difficult to use gzip (good compression). Try lzo. What if you try to backup some vm's on local storage? Backup...

Don't be afraid of raid. It works great. With RAID1 you will get data security + better read read performance. If you need just simple spare disk with working system on it I can suggest to physically remove main disk and install Proxmox on to second disk. Then you have to make sure each...

Hello Martin, You can redirect all mail for root by editing /etc/aliases. ~# echo "root: monitor-it@mydomain.com" >> /etc/aliases && newaliases Or just emailaddress for backup reports via WebUI Datacenter -> Backup -> Edit -> Send mail to Filesystem file you can found backup job with all...

Hello Mares, Terrible incident. The recovery might be s challenge. I can only give you a brief idea. Nothing for action. Data recovery is not straight forward but if you lucky enough you can get your data back. You need to split work on two jobs: investigate from where intrusion come from and...

What is the model number? Dedicated switch/switches for storage area network might be better. What if your 6248 die? I am not sure if VLAN somehow related to LACP. You might need to make sure that switch configuration is right before proceed any further. CLI will show you how switch...

Re: .Re: Mount a simple local folder to a VM Sorry my not careful reading I just rush to help. For KVM/QEMU there is another way to mount local folder using 9p. Example in guest: guest# mount -t 9p -o trans=virtio,version=9p2000.L,rw share /mnt It might be still not implemented. Please...

You can also use bind mounts for CT (openvz)

Think about: 1. NFS (just standard simple network filesystem) 2. GlusterFS (You will get NFS, SMB and fault tolerant shared and replicated storage in one). Works over local eg. ext4 filesystem and install is as simple as running one command. 3. ??

I am guessing NFS was not quite happy during the backup process. It might be because of many factors: hardware, networking, cabling, etc. Simple exclude one by one but one thing at the time. Try to exercise mounted nfs with various tests like: (just vary size and number of files) ~# dd...

No worries. Nice to know that finally you win. :-) Community can not fix all your problems but can make you guess right. Cheers.

Not even think. Restoration is rare and mostly manual anyway.

Thanks for all of that. Let me resume: 1) You've got public ip 192.99.10.135 and it's gateway 192.99.10.25 2) It works from the proxmox (hypervisor level) -- confirms that ip, gw, and networking config is correct 3) It doesn't work if you assign 192.99.10.135 to vm. can't get out to the...

What is in your /etc/pve/kvm-networking.sh? What can you see inside vm 103? ~#tcpdump -n -i eth0