Search results

  1. E

    Accidentally deleted the partition table of rpool. The system is still running no errors yet. How do I recover?

    I too found a lot online but they all were for restoring after the partition table in the ram was lost. That looks promising but it's 11 years old. I've got only one shot so in the meantime I will wait and test all my backup and prepare for the worst. Considering that the server is connected...
  2. E

    Accidentally deleted the partition table of rpool. The system is still running no errors yet. How do I recover?

    I have the automatic backup set to yes everything is safe. Just a pain in the butt if I have to take the server out, connect a monitor and keyboard and reinstall and restore everything. The partition table should be still loaded into RAM, but I don't know how to retrive it and restore it.
  3. E

    Accidentally deleted the partition table of rpool. The system is still running no errors yet. How do I recover?

    So I made a mistake and using fdisk I deleted the entire partition table and created a MBR. Here's the current output from fdisk. Disk /dev/nvme1n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors Disk model: WDC WDS500G1B0C-00S6U0 Units: sectors of 1 * 512 = 512 bytes...
  4. E

    [SOLVED] Proxmox lxc start issue after apt upgrade

    Had the same issue after I updated my server... installing binutils solved it
  5. E

    "timeout: no zvol device link" when I try to start a VM

    Hi, today I had to reboot the server so I tested it and after running systemctl restart systemd-udevd; udevadm trigger; udevadm settle it worked. But it looks like a temporary fix. Funny how I remember stumbling on that thread a while ago but I missed that line and only tried for i in $(ls -1...
  6. E

    "timeout: no zvol device link" when I try to start a VM

    1) Yes it shows the zvol of vm 205. I typically solve by restoring from backup. 2) ZFS is so much more than redundancy.
  7. E

    "timeout: no zvol device link" when I try to start a VM

    Every time i try to start this VM after rebooting the PVE host i get TASK ERROR: timeout: no zvol device link for 'vm-205-disk-0' found after 300 sec found. Everything is updated. I have another win10 VM and that one starts without any issue. (Disk is on rpool) I suspect it have something to...
  8. E

    VM won't start after every reboot because "timeout: no zvol device link"

    Every time i try to start this VM after rebooting the PVE host i get TASK ERROR: timeout: no zvol device link for 'vm-205-disk-0' found after 300 sec found. Everything is updated. I have another win10 VM and that one starts without any issue. (Disk is on rpool) I suspect it have something to...
  9. E

    Nvidia GT710 makes the server crash every 24-48h

    After some month of testing I can confirm that's the issue. By simply keeping more containers and VM running it stopped crashing
  10. E

    Nvidia GT710 makes the server crash every 24-48h

    I've got a home server with the following hardware: Amd Ryzen 1600 Gigabyte s2h a320m 32 gb ram Nvidia gt 710 some ssd and hdd It took me months to pinpoint the issue but I found out that after I switched from a gt 710 to a rx 570 the server didn’t crash for more than a month. Yesterday I...