Recent content by homozavrus

i Have the same error on this network-card. but in my case, the interfaces and Ceph monitors fall.

I had the same problem after upgrade from 5.4 to 6.0. Complete reinstall helped me )) what if i have more than one pool? using the same cache file?

i've reinstalled proxmox. For a week all goes without problem. I use write-back for VM.

I understand that, so I deleted multipath. What should i do now? disable one by one services, that mount zfs on boot?

i've removed multipath completely. No effect. Something at the start creates a path and then the pool can't export into it. prx-06:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 5.5T 0 disk sdb 8:16 0 5.5T 0 disk sdc 8:32 0 5.5T 0 disk sdd...

Now I'm not sure that multipath working correctly. I have a suspicion that the pool is imported before the multupath starts. Is there some way to figure it out? or should blacklist disk in multipath and restart host?

1. prx-06:~$ sudo -i root@hst-cl-prx-06:~# zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 7.82G 891G 96K /rpool rpool/ROOT 6.53G 891G 96K...

Alwin, i need help. Something strange is going on with mount zfs pools in 6.0. I think it race with mount zfs pool on startup, but cannot understand where. Upgraded 5.4 to 6.0 - What i make: 1. create pool zpool create -f -o ashift=12 -O compression=lz4 -O checksum=edonr...

All works after reboot. One correction, right variant - mkdir 0 My working config from storage.cfg dir: storagepool-backup path /storagepool/backup/ is_mountpoint yes mkdir 0 content backup maxfiles 10 shared 0

I have rebooted the host. i have no other options (( All works for now. I think that issue coming again. prx-06:~# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve) pve-manager: 6.0-4 (running version: 6.0-4/2a719255) pve-kernel-5.0: 6.0-5 pve-kernel-helper: 6.0-5...

Hi all, i have a updated to 6.0 proxmox from 5.4 (without any issues). Community edition. All containers and VM are on zfs pool (10 disks in zfs raid10). I have tried to reset one stucked VM. I have stopped and when i try to start that, i have strange error - prx-06:~# qm start 6008 timeout...

i have the same issue after upgrade. Thanks for information. i'll check that tonight with next reboot.

Hi, i am trying to find where exactly this option - disable cache for VM images :) What does that mean?

Hi all:) I have the same issue on Hetzner AX160-NVMe server with sata-ssd mirror zfs root. Installed Proxmox 5.2, than upgraded to 5.3 and after reboot get - no such device, unknown filesystem.

there is no script in repo :)