Hello everybody!
TL
R: my vm gives me a error: unable to read tail (got 0 bytes)
Full story:
So i just installed a new network card using the realtek r8125 chipset, i added the physical card to my proxmox bridge, and it all worked, at gigabit speeds, while this is a 2.5 gigabit card.
So i checked using lspci what driver it was using (google told me to do so) and it was on a 8169 driver.
Realtek said their driver for this card was for an older kernel, so i found this one:
https://github.com/awesometic/realtek-r8125-dkms
I downloaded the deb package from their releases.
Installed it with the dpkg command they mentioned.
It gave a dependancy error, so i used apt install --fix-broken, wich installed a bunch of packages.
I rebooted and it all worked!
So i used lspci to check, but it was still on the old drivers.
I added a blacklist for the r8169 using the command to create a blacklist-r8169.conf file with blacklist r8125 in it.
I think this is where i messed something up.
After reboot, i could not connect any more. I forgot that if the driver is not working, blackisting the working driver might not be the best plan.
So with no screen connected, i had to pull out my driver and i powered it off.
I connected my screen, rebooted and i got an error:
failed to start dkms.service
Also my keyboard was not working and i could not log in.
Another forced reboot, started up in recovery mode and now the keyboard was working. I removed the driver with a dkms remove followed by the driver i tried to add. I removed the blacklist file as well. As my keyboard was now working in recovery, typed in the systemctl reboot, but it was not working. I had to force a shutdown.
Now, proxmox worked over network again, so the page loaded again. Everything seems to work, except my vm.
The vm uses a zfs pool with 3 drives in raid6.
When i try to start the vm, i now get the error:
Error: unable to read tail (got 0 bytes)
That is about it. I hope that i did solve my screwup with the network driver, did i forget to fix something there? How can i check?
As for my vm problem, can anybody help me out? Need any logs from a command to see where and how bad i messed up?
I am thinking the forced reboots were not enjoyed by the zfs pool, am i correct? Is this fixable?
TL

Full story:
So i just installed a new network card using the realtek r8125 chipset, i added the physical card to my proxmox bridge, and it all worked, at gigabit speeds, while this is a 2.5 gigabit card.
So i checked using lspci what driver it was using (google told me to do so) and it was on a 8169 driver.
Realtek said their driver for this card was for an older kernel, so i found this one:
https://github.com/awesometic/realtek-r8125-dkms
I downloaded the deb package from their releases.
Installed it with the dpkg command they mentioned.
It gave a dependancy error, so i used apt install --fix-broken, wich installed a bunch of packages.
I rebooted and it all worked!
So i used lspci to check, but it was still on the old drivers.
I added a blacklist for the r8169 using the command to create a blacklist-r8169.conf file with blacklist r8125 in it.
I think this is where i messed something up.
After reboot, i could not connect any more. I forgot that if the driver is not working, blackisting the working driver might not be the best plan.
So with no screen connected, i had to pull out my driver and i powered it off.
I connected my screen, rebooted and i got an error:
failed to start dkms.service
Also my keyboard was not working and i could not log in.
Another forced reboot, started up in recovery mode and now the keyboard was working. I removed the driver with a dkms remove followed by the driver i tried to add. I removed the blacklist file as well. As my keyboard was now working in recovery, typed in the systemctl reboot, but it was not working. I had to force a shutdown.
Now, proxmox worked over network again, so the page loaded again. Everything seems to work, except my vm.
The vm uses a zfs pool with 3 drives in raid6.
When i try to start the vm, i now get the error:
Error: unable to read tail (got 0 bytes)
That is about it. I hope that i did solve my screwup with the network driver, did i forget to fix something there? How can i check?
As for my vm problem, can anybody help me out? Need any logs from a command to see where and how bad i messed up?
I am thinking the forced reboots were not enjoyed by the zfs pool, am i correct? Is this fixable?