Recent content by Virt

  1. Hacked System

    Extract twice. The first time will give you a generic file.
  2. Hacked System

    Also, be sure to enable logging on the firewall for all rules on that VLAN. You'll be able to track anyone trying to hit your iLO (even if you have it blocked).
  3. Hacked System

    Definitely sounds like someone gained unauthorized access. As a general precaution, you should move your iLOs to a management VLAN that has no access to anything other than a few designated VLANs. I would suggest deleting the user and upgrading iLO. The most recent version for 4 can be found...
  4. Hacked System

    The year break suggests it's not a rootkit but how you were re-infected depends on a lot of factors. What model server and version of iLO are you using? Did you change the default credentials?
  5. Issues installing SCST

    Running into issues after following the instructions here: https://pve.proxmox.com/wiki/Tape_Drives#Installing_from_an_adapted_deb_packages_of_scst_3.1.x_for_Debian_Jessie_8.x_.28Preferred_method_and_recommended.29 I am working with scst 3.2.x rather than 3.1.x (though I should really be...
  6. Cluster storage default configuration

    After further investigation it seems Proxmox just replicated parts of the directory structure to /mnt based on the storage.cfg from the other server. This is confusing behavior to say the least.
  7. Cluster storage default configuration

    Somehow I'm able to access the other host under /mnt I haven't manually mounted anything, the shares showed up after joining the host to the cluster.
  8. Cluster storage default configuration

    When joining a new host, the data stores on the other host(s) become available. I'm trying to figure out how this is setup. I assumed it was NFS but the folders don't show up as mounts, they show up as local folders.
  9. Cluster storage default configuration

    What method is used to share storage once a host is joined to a new cluster? I've been looking for some sort of config file but haven't been able to find any information about it. Does it use the Corosync network?
  10. [SOLVED] Unable to start LXC container after moving storage

    I was able to get it up and running by manually recreating the container using the previous image. The previous transfer had corrupted the image and I was able to move it the second try.
  11. [SOLVED] Unable to start LXC container after moving storage

    Looks like it's binary, cat produces gibberish. Perhaps I need to replace it with a copy from the other image?
  12. [SOLVED] Unable to start LXC container after moving storage

    I have an LXC container (Ubuntu 16.04) that refuses to start after moving it using the GUI. Log from lxc-start: lxc-start 103 20180820144828.681 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 255 lxc-start 103 20180820144828.681 ERROR lxc_start - start.c:lxc_init:815 -...
  13. NVMe Kernel Bug Trigger

    The NVMe device is acting as the cache (bcache) for a two-drive mdraid 10 using ext4. EDIT: Bcache is configured for writeback, I need the write speed that it gives.
  14. NVMe Kernel Bug Trigger

    The issue still exists in the newest version of Proxmox. I just had it lockup again 5 minutes ago.
  15. [SOLVED] QEMU Backing images

    How are the deltas configured in the VM configuration file?

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!