Recent content by Dmitrius7

As I understand it, the "Reset to device\Device\RaidPort" problem has been resolved in the latest update of the virtio drivers. As far as I understand, the virtio developers solved this problem by releasing a driver update. They write about it here...

Hello! Yes, hardware verification at the BIOS startup stage is not taken into account. It's always a long time. Yes, I meant the time from the moment of grub to the moment of OS boot (to be more precise, until the moment when the services start running). This means that your system does not...

As far as I understand, the error "Timed out waiting for the udev queue to be empty" occurs if the system freezes for more than 2 minutes or so during boot. As I understand it, the bootloader scans all the disks and searches for file systems on them. If there are a lot of disks and there are...

Hello! I had a similar problem as you. I have written a detailed solution. Please write, did it help you or not? https://forum.proxmox.com/threads/timed-out-for-waiting-the-udev-queue-being-empty.147304/post-736141

I solved this problem! Here are the detailed instructions: Configuring LVM and MDADM to Prevent Proxmox from Scanning VG and MDADM on ZFS Block Devices and Ceph RBDs Disabling Automatic LVM and MDADM Connection for ZD (ZFS ZVOLs) and RBD (Ceph RBDs) Disks ZD-prefixed disks are virtual devices...

Try it.

I was looking for the same thing, but I didn't find it. I have created a script that changes the number of 20,000 records (about 1 year of task history) using cron. My post here https://forum.proxmox.com/threads/task-log-retention.133758/post-736123

I made a script that changes the number of 20,000 entries (around 1 year task history) by cron. How the Script Works This script automatically increases the number of Proxmox VE Task History entries by modifying the $maxsize parameter in the /usr/share/perl5/PVE/RESTEnvironment.pm file. By...

Please write in more detail that what exactly did you do? What means disabling mapping checks?

Hello everyone! The issue persists. I have a hypothesis that if I move the root and bootloader to different disks, the problem might go away. It’s possible that this failure occurs specifically on my NVMe disks for some reason. This is just a hypothesis, and I will check it and update you. My...

I tryed it too, it didn't help.

I installed FreeBSD 14 and imported this pool. It works fine!

I am transferring all the data and will delete the pool. After it I will use mdadm + LVM. There have been no such failures over the years. It's a pity, I really like ZFS.

Important note! If I import the pool as read-only, everything works fine, and the RAM is not consumed. zpool import -o readonly=on -d /dev/disk/by-partlabel/ zp-erp1-hdd Today I reinstalled proxmox with previous version. It didn' help. The problem is still exist. Now: # zfs version...

Proxmox suddenly started freezing due to OOM (Out of Memory). After diagnosis and investigation, I found that ZFS ARC is consuming all the memory. There is a limit set for Max size (high water) at 5.0 GiB, but the system ignores this limit. The server has 64GB of RAM. The swap was 16GB; I added...