Search results

Lets begin to fix it from the ZFS point. Is your nvme_cluster ZFS pool dedicated to VM data? Then lets set his mountpoint to /nvme_cluste or /media/nvme_cluste as I do. #zfs set mountpoint=/nvme_cluste nvme_cluste

First of all - Why you want to use ZFS? All other stuff can do it too: H/R, mdadm, LVM, filesystems, etc. But none of them do data integrity check. Except others filesystems like btrfs. If you don't need data integrity validation before it reach program then use regular tools and by happy...

I see nvme_cluster mount point is / Doesn`t it overlaps with rpool ? Or your OS is in nvme_cluster ? I think this is how it should be. I see you are doing small mistakes in every step.

Mounting in Live CD you can use -R : zpool import pool -R /another/mount/point So you could do what you need without mixing with Live CD / mountpoint Or -N : Import the pool without mounting any file systems. p.s. it is OK for /rpool/PVE and /rpool/DATA to be empty

Don't know how to help you but I use Jellyfin with disabled transcoding and I watch using Jellifin player on computer or on phone.

If zpool list show empty did you tried zpool import ?

BTW nvme_cluster/vm-123-disk-0 you can access from host in /dev/zvol/nvme_cluster/vm-123-disk-0 or /dev/zvol/nvme_cluster/pve/vm-123-disk-0 ( depend on storage config) From there you can mount/format virtual disk/block volume. Just do it then VM using this storage is off.

Hello blastmun As I can see it is filesystem in ZFS, not a block volume This config search for the file, not catalog. try to remove .raw And make sure you can access files /nvme_cluster/subvol-122-disk-0 from host

This is standalone. If kernel 6.2.16-18-pve will work good I`ll update ZFS.

No need to wait for the night. Rebooted again. I`m running kernel 6.2.16-18-pve now with ZFS 2.1.13-pve1 - is it possible to update this kernel with ZFS 2.1.14 ?

My story of LUKS and ZFS For one server I needed to encrypt as much as possible with auto password insert at boot. I did it in using Proxmox 5.0 at that time and from that moment system still running up to this day. Partitions: for system raid disks I splitted into unencrypted boot partitions...

Hello fiona, This night it happened again. BIOS and CPU microcode are up to date. External log monitoring didn't give a clue. System worked very well for a long time before. On 2024-01-07 I did update, perhaps I need to go back to proxmox-kernel-6.2.16-18-pve

Same problem ( post ), but I use my own script for backup sync and I`m not sure does it really happens because of backups

The server has rebooted unattended for the last 3 nights. The first night I thought maybe it had something to do with sending backups to another server. In this process, the backup server is started using IPMI and the backup server is shut down after completion. But in the morning the backup...

All ZFS pools in the same host share the same ZFS memory. I don't know are you effected read (ARC) or write (dirty cache) cache. I can suggest to lower dirty cache or change zfs_txg_timeout. How will it help for you or will it help at all I don't know.

ZFS 2.2.0 have a lot of bugs. I prefer to wait for 'more' stable release. 2.2.1 is out https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1

As spectre-meltdown-checker is saying: > SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:OK CVE-2018-3639:OK CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK CVE-2018-12126:OK CVE-2018-12130:OK CVE-2018-12127:OK CVE-2019-11091:OK CVE-2019-11135:OK CVE-2018-12207:OK...

It is good for homelab

Hello, I`m preparing server with new installation of Proxmox 8. I have HP Ethernet 10Gb 2-port 557SFP+ Adapter and this device initiates this kernel message at startup: Kernel: 6.2.16-10-pve [ 25.252287] ------------[ cut here ]------------ [ 25.252837] Voluntary context switch within RCU...

This is old thread but I run into this problem today too. Choosing recovery mode from grub I saw controller problem. Switching from default (LSI 53C895A) to VirtIO SCSI solve the problem. It was the last VM running with LSI 53C895A controller mode and upgrading kernel somehow matched with the...