Search results

give the error: cannot import 'rpool': no such pool available

How i can get to a menu to update zfs sleep args? "ZFS_INITRD_PRE_MOUNTROOT_SLEEP"

for some reason i thought it worked. and tried to do another reboot, now after running zpool import i receive no pools available

grub files does not exist, i updated zfs pre sleep, but how i "commit" force config update for the change? because update-initramfs does not exist

how i can scann the boot drives?

*yes from iso zpool import: lbsk: ls -la /dev: starts with blkid: the end of dmseg:

This morning we had some power outage issue on our server room, all nodes recovered except one. This node is part of (one of three) ceph cluster , (pools are set to replication 3) so the data is safe and the cluster is stable, (excluding ceph warning) Any idea how i can fix it?

the proxmox host had the same ram usage as before: the max ram available to the vm was marked as used, even when the vm used around 1% of the ram

i installed virtio and enable the flag, but the system still uses all ram and it is not shared i see "BalloonService " running on windows

I assume that this is impossible, but ill ask this anyway. i need to put one lxc (ubuntu) and one vm on each host (for large computational tasks) somtiems we need windows and sometimes we need linux the problem that the VM need to have all the ram prealocation and not freed when not in use...

nfs (qnap based) over 40GB network. tmp dir is default (what come pre configured with proxmox)

how i can pull only the relevant file ? libpve-common-perl >= 6.2-3 i did not see instructions

proxmox 6.2-12 any idea? INFO: starting new backup job: vzdump 140 --storage vqfiler1-lxc --remove 0 --node pve-srv1 --compress zstd --mode snapshot INFO: Starting Backup of VM 140 (lxc) INFO: Backup started at 2020-10-02 15:37:29 INFO: status = running INFO: CT Name: grid-master INFO...

i have lxc containers hostes on ceph storage (with speed over 5GBs ) when making backup using zstd the speed is between 20-90MBs the storage i am writing to store the backup have read/write speed around 1GB proxmox 6.2.12

my mistake, repository was on strech insted of buster . updating .. upgrade fixes the issue, thanks

most nodes are 6.2-11 (oldest is 6.1-2) (upgraded but did not rebooted yet)

on some hosts the ZSTD backup compression is not working? any idea why ? this is the error? Parameter verification failed. (400) compress: value 'zstd' does not have a value in the enumeration '0, 1, gzip, lzo' solution: upgrade proxmox to latest version on all nodes.

i think i found something that cause it, hope you can recreate it: i just run manual back on lxc container (Ubuntu 18.04 ) with multiple nfs mount points, but one of the nfs mounts is unavailing (down) once the backup failed with the following error: INFO: excluding bind mount point mp7...

Nope, i guess i missed it, I thought this relatively basic and that that is already implemented.. * we did not change the ID or the name Ill probably wait for a beta of PBS to end..

We usually got for enterprise refurbished hardware (dell\supermicro 1-5 years) and used (but relatively new sas ssds 1-2 years old)) I guess our top budget for this is 1500$ (including storage) We dont need high (around 5-10TB redundant , with some scale options in the future) The question if...