Search results

Just a word of advice, the swap and the rrd will kill the SD Card on that RPI in the near future.... If you absolutely must run pmox/ceph on only 2 hosts, then consider having a VM or two as a witness/3rd node. The ceph conf looks ok! Good luck

This might also be the reason why I could install fine from an external USB to an external SSD caddie (which might use the modules above) but couldn't boot from the said external SSD caddie if the proxmox install usb was removed... Thanks for your efforts

Try the same on Linux VM and Windows and see if it is the same, then its the Plex app that is at fault.

Try adding more pg's now that you have larger drives. This is what I had to do when ceph pools was eventually filling up...

Try adding iommu=pt pcie_acs_override=downstream to /etc/default/grub -> GRUB_CMDLINE_LINUX_DEFAULT

The more nodes you have, the faster ceph is. You will however also need SSDs/NVMe's for journals and/or writeback cache to get some speed. 10G switches are a must if you have NVMe's, if you don't have that its not really worth it as it only speeds recovery (rebuilding) and not normal transfer...

Use the Proxmox PCI Passthrough guide to dump the ROM of the card, that's what I did to get my Nvidias working

Nice writeup, hope it gets more attention

Sounds like either the target HDD is full or your Proxmox OS HDD?

Try Legacy mode in BIOS instead

Hi, Try Debian and see if it works since proxmox is based on that. Also, I'd love to hear a report on the new HC2 once you are setup and running since I was planning to use them as a ceph node as well!

Crystaldisk inside Windows VM. I would still deactivate service after service or do a reinstall. However, dual core is dual core, so there is that, along with a spinning rust..well :)

You are right, 1mb/sec aint much. I'd try to install a second disk as VirtIO disk / scsi disk, install the drivers, then migrate the OS disk to VirtIO (+IO Thread) or scsi disk.

Out of ideas. start disabling service by service and see if there is one that is specially problematic because I think "Hosta servizio" is actually svchost..

Its "/usr/share/perl5/PVE/QemuServer.pm" if ($winversion >= 7) { push @$cpuFlags , 'hv_relaxed'; } to if ($winversion >= 7) { push @$cpuFlags , 'hv_relaxed'; push @$cpuFlags , 'hv_synic'; push @$cpuFlags , 'hv_stimer'; } and maybe if ($winversion >= 6) { push @$globalFlags...

For the idle part, there is a known bug that might still be in pve 5.3, try https://forum.proxmox.com/threads/high-cpu-load-for-windows-10-guests-when-idle.44531/ For "restore a single folder or file from a backup.vma.lzo" I frankly don't know..

Hi, try installing the proxmox guest agent https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-qemu-ga/

Try "rescue mode" booting your OS on the disk from your Promox USB media. If it works, I had the same, which was unresolved so I had to move the disk from usb external to internal SATA and fix the BIOS boot order.

So I am now guessing a dd of the boot partition on the Install USB and use gparted to copy that to the external USB caddie in order to get grub to boot on my computer?

Update: I managed to boot on the SSD by booting from rescue mode on the Proxmox 5.2 Boot ISO/USB Stick. Any ideas how to boot directly into the drive without having the Boot ISO Rescue mode ?