Search results

I have a motherboard, CPU and memory on where single bit ECC detection, correction and reporting and multi bit detection and reporting is confirmed to be working. what would be the most straightforward way to recieve an email when ever the OS receives an ECC report?

Could you please elaborate on the tweaking you did? I am getting abysmal results on 2 x Samsung SSD 980 PRO zfs mirrored using default zfs settings during proxmox installation. Used PVE < 6.4 for installation and currently fully upgraded to most recent version. pve-manager/6.4-4/337d6701...

just found myself in a similar situation trying to passthrough a evga rtx 2080 TI to a win2k19 vm. I have done it before on a asus prima x570-p mobo so I know it can work but now on this gigabyte trx-40 mobo I am getting the 43 error in windows. Does anyone have an update on this please?

Thank you @gomu , @developers is there anything down the roadmap to level the functionality of @jeanlau his workflow between nodes?

But in theory having the uppermost part of a zfs pool referted should not be messy? What in practicse shouls i watch out for?

thank you for your more detailed analysis. Why can't one simply snapshot the root/rpool?

I am checking it out sooner or later

@wolfgang , I would very much would like to second @cserem 's request

Could you please try explaining once in a different manner than @jeanlau did the steps you took? I am not getting through his explenation :(

After a lot of effort by mastakilla, someone in close contact with asrock rack, it turns out to be AMD that does not cooperate to get ECC events to be logged by IPMI on non server boards. My stance is that asrock rack should not have marketed my x470d40 board as such in that case

I think it must have been a tmp issue as the shares show up in the gui again

But they are not in storage.cfs The syslog spaming stopped after a reboot though

root@pve-trx40:/etc# cat fstab # <file system> <mount point> <type> <options> <dump> <pass> root@pve-trx40:/etc# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content backup,iso,vztmpl zfspool: local-zfs pool rpool/data content rootdir,images...

every 2 seconds a new row appears in the syslog of pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve) # start copy paste from syslog kernel: CIFS VFS: \\oldnas.lan Send error in SessSetup = -13 # end copy paste from syslog there is no share specified only the server name. The weird...

thx all for the help. finally managed to get the sound passed through. I am happy

Thanks a lot: Almost there now. One error while compiling when using your patch file contents: applying patch '../../patches/kernel/0008-amd-no-flr.patch' patching file drivers/pci/quirks.c patch: **** malformed patch at line 4: DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr);

@qwerty0033 can you please paste me the contents of your 0008 patch file?

I am getting closer, I just got confused, and have the patch file on my system. can you please paste me what you ended up with after the changes you mention? I can double check manufacuter and device id's later. This is what I have now in /usr/src/pve-kernel/patches/kernel/0008-amd-no-flr.patch...

finally I found the inner strength to try and then :( kernel root@pve:/usr/src/pve-kernel/patches# ls kernel root@pve:/usr/src/pve-kernel/patches# cd kernal -bash: cd: kernal: No such file or directory root@pve:/usr/src/pve-kernel/patches# cd kernel root@pve:/usr/src/pve-kernel/patches/kernel#...

wow thank you sooo much for holding my hand. Please allow some time in order for me to try it. I will for sure to get back to this.