Search results

Indeed it did cross my mind, but that would require hooking up 2 ethernet cables, so I'll go with a smart socket. Thank you for the input :)

It appears that Atheros Killer driver has a bug and WOL was disabled for it a while back. Some insights: https://bugzilla.kernel.org/show_bug.cgi?id=61651 There's a patch, originally prepared for Ubuntu: https://github.com/AndiWeiss/alx-wol However, correct me if I'm wrong, but even if I...

Yep, the systemd drop-in unit (followed by systemctl daemon-reload) did the trick: # cat /etc/systemd/system/getty@.service.d/autologin.conf [Service] ExecStart= ExecStart=-/sbin/agetty --noclear --autologin root %I $TERM The original unit has ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear...

I repurposed my old gaming rig into a PVE host, it's equipped with Fatal1ty Z170 Gaming K4 motherboard that comes with Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10). Back, when this host had Windows 7 installed, I was able to configure the Wake-on-lan in NIC's settings to...

Hello! I'm looking for a way to enable root auto-login or bypass the password prompt, but only for local TTY (physical monitor and keyboard). It's important that full PAM authentication remains for web GUI and remote access. Anybody knows the elegant way to achieve this?

Hello! I'm looking for neat way, to allow given user/token to perform only one particular action: to shutdown a node and shutdown/start a VM. The only way I came up with, it using SSH and adding a command-specific SSH key to the /root/.ssh/authorized_keys, something like command="shutdown"...

@limone - the umount does the trick, but I'm worried about running this in crontab. Sometimes while this issue is happening, the `ls /mn/pve` appears to take forever. Did you ever have any issues with this?

I noticed, that LVM-think works way worse, than Directory storage + qcow2 files for VM disks. What FS for the Directory should I use for such approach? xfs, or ext4? it will only contain the qcow2 files...

Thanks, that helped a bit: With IO Thread disabled: Throughput: read, MiB/s: 26.73 written, MiB/s: 17.82 With IO Thread enabled: Throughput: read, MiB/s: 34.65 written, MiB/s: 23.10 Is this the best I can aim...

I cannot seem to change the SCSI Controller value from GUI and for Bus/Device I can only see: You're right. I wiped the disk, set up a Directory storage using ext4 and repeated the test: Throughput: read, MiB/s: 111.64 written, MiB/s: 74.43 Thus...

I should add that those drives are connected to the server via HPE Smart Array P420i controller, it has this little battery. I wonder how safe would it be to use "writeback" Cache mode

I'm not sure, I use GUI with following settings: ("fast" is the lvm-thin storage) The first one is ADATA SU630, the second one (the one that is bottlenecking) is Seagate IronWolf 125. I would expect it to have better performance than ADATA.

On my proxmox machine I got two SSD drives natively connected to it. First disk is for proxmox OS, the other I want to use in VMs. Basically, I want to use half of this second SSD drive in one VM, and other half in another, preferably with auto-adjusting sizes (in case one VM needs more than a...

On another Proxmox installation I have this issue: Again - rebooting VM solves the issue. How can I fix this?

I have one VM that has a RAID volume passed-through to it and that VM creates CIFS shares to be used on another VM. Both VMs have similar CPU issues. My PVE is up to date.

Hello! Every couple of weeks various VMs tend to become problematic and their consoles show the following errors: Rebooting the VM fixes the issue. How do I diagnose what's going wrong? In that state of the VM, I'm unable to SSH into it. The Proxmox is installed on HP Proliant DL380e...

Thank you very much for your help :)

Of course :) Wait - what? So you say that this VM was never able to be snapshotted and I only noticed this now? I cannot be certain, but I think I would've noticed this before. So the VM backup-snapshot does not utilize the copy-on-write feature of LVM? So this basically boils down to the...

More info from PVE: [00:06:57][root@zoltan]:~# qm guest cmd 100 fsfreeze-status thawed On the VM itself: [00:10:21][root@yarpen]:~# uname -a Linux yarpen 5.10.0-0.bpo.9-amd64 #1 SMP Debian 5.10.70-1~bpo10+1 (2021-10-10) x86_64 GNU/Linux

I have a VM (id=100) that runs OpenMediaVault - NAS server with CIFS shares. For the past 117 days everything was working properly, the backups were done every night with no errors. I initiated manual backup of this VM - and it failed. Here's the event log: INFO: starting new backup job...