Max

So i just tried booting without VFIO bind thing and i still got the same error. Unraid kernel: nvme 0000:0d:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update So seems like firmware issue to me 😓

I was not using VFIO bind prior to adding NVME to my system, the only thing which is VFIO bound is that NVME only which of course i only bounded after adding it to the system😅. The only other device which i could bind was my GPU but i'm not using VFIO bind with it as i never had any issues relating to gpu utilisation on VM so i'm using my gpu without VFIO bind thing. And as for unsafe interrupts and multifunction on both -- are you sure unsafe interrupts is safe to use cause it's showing that it can cause data corruption on some systems😅. And just tried booting with multifunction on both, first i still got that warning under syslog and now my gpu and its audio are appearing in separate IOMMU groups so i can't use this anyway.

Hey everyone, So recently I upgraded my unraid server from Intel i7 4790K system to AMD Ryzen 9 7900X, basically wanted to move back to PC gaming from PS5 after PS5 Pro launch😅. Long story short -- ideally I wanted one machine for both Unraid Server task as well as for Gaming but as it would be under VM and my prior experience with 4790k wasn't anything to brag about (mainly low CPU performance which on some level i belived because of weak old hardware) I first wanted to slowly test things before upgrading GPU cause GPU wise even with 4790K system i was able to get bare metal level of performance out of my GTX 1070 TI (only in GPU Heavy Benchmarks). So fortunately I am getting basically bare metal level of performance of a 7600X from my 7900X (with 6 Cores and 12 Threads) under VM which is what i hoped to achieve. And that too without any XML tweaks on Unraid v7. So now I'm waiting for my RTX 4070 TI Super. But here's the thing ever since i installed NVME SSD (XPG Gammix S70 Blade) in my server for VM I am getting this error under syslog. Unraid kernel: vfio-pci 0000:0d:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update I have bound it to VFIO and passed it to my VM but I keep getting this error under my Syslog. I have already tried checking firmware on it but it already running on latest version. So is it anything to worry or if anyone knows how can I fix this cause its been already over a week and fortunately I am yet to face any issue because it. So yeah basically wanted to share my success story with those who are under similar dilemma as i once was before finally clicking on buy button and ask around about this error. If anyone can help me fixing it.... or should I just ignore it....😅 unraid-diagnostics-20241129-1134.zip

Hey everyone so yesterday i upgraded my Unraid from i7 4790k to AMD ryzen 9 7900x, so first here's the list of parts i upgraded Motherboard -- Asrock B650E Steel Legend Wifi CPU -- Ryzen 9 7900X RAM -- Adata DDR5 32GBx2 6000 CL30 Everyone thing is working just great but I'm not able to set temperature sensors on this AM5 Platform at first when i tried sensors cmd in the command line i got this response. k10temp-pci-00c3 Adapter: PCI adapter Tctl: +56.4°C Tccd1: +37.4°C Tccd2: +37.5°C amdgpu-pci-0d00 Adapter: PCI adapter vddgfx: 1.44 V vddnb: 1.19 V edge: +44.0°C PPT: 8.12 W then after some research on google i came to realize that some of these AM5 boards have Nuvoton IO Chips and you need to install drivers through community app store. I'm not sure my Asrock B650E Steel Legend Wifi board has this Nuvoton IO Chip but it looks like it does and i was like its not gonna hurt anything either i will get the reading if drivers work or i won't. So after installing the drivers now im getting this response from command line nct6686-isa-0a20 Adapter: ISA adapter +12V: 0.00 V (min = +0.00 V, max = +0.00 V) +5V: 0.00 V (min = +0.00 V, max = +0.00 V) +3.3V: 3.42 V (min = +3.39 V, max = +3.42 V) CPU Soc: 0.00 V (min = +0.00 V, max = +0.00 V) CPU Vcore: 0.00 V (min = +0.00 V, max = +0.00 V) CPU 1P8: 0.00 V (min = +0.00 V, max = +0.00 V) CPU VDDP: 0.00 V (min = +0.00 V, max = +0.00 V) DRAM: 0.00 V (min = +0.00 V, max = +0.00 V) Chipset: 0.00 V (min = +0.00 V, max = +0.00 V) CPU SA: 0.00 V (min = +0.00 V, max = +0.00 V) Voltage #2: 0.00 V (min = +0.00 V, max = +0.00 V) AVCC3: 0.00 V (min = +0.00 V, max = +0.00 V) AVSB: 3.42 V (min = +3.39 V, max = +3.42 V) VBat: 1.81 V (min = +1.81 V, max = +1.81 V) CPU Fan: 1371 RPM (min = 1232 RPM, max = 1857 RPM) Pump Fan: 1396 RPM (min = 1253 RPM, max = 1875 RPM) System Fan #1: 0 RPM (min = 0 RPM, max = 0 RPM) System Fan #2: 0 RPM (min = 0 RPM, max = 0 RPM) System Fan #3: 0 RPM (min = 0 RPM, max = 0 RPM) System Fan #4: 0 RPM (min = 0 RPM, max = 0 RPM) System Fan #5: 0 RPM (min = 0 RPM, max = 0 RPM) System Fan #6: 0 RPM (min = 0 RPM, max = 0 RPM) CPU: +32.0°C (low = +31.5°C, high = +37.0°C) System: +36.0°C (low = +36.0°C, high = +39.5°C) VRM MOS: +37.0°C (low = +36.0°C, high = +47.0°C) PCH: +55.0°C (low = +49.0°C, high = +86.0°C) CPU Socket: +46.0°C (low = +25.0°C, high = +92.0°C) PCIe x1: +64.0°C (low = +64.0°C, high = +64.0°C) M2_1: +63.0°C (low = +62.0°C, high = +63.0°C) k10temp-pci-00c3 Adapter: PCI adapter Tctl: +55.8°C Tccd1: +39.4°C Tccd2: +43.1°C amdgpu-pci-0d00 Adapter: PCI adapter vddgfx: 1.45 V vddnb: 1.19 V edge: +44.0°C PPT: 15.24 W and as you can see now i'm getting much more readings here but most of the Vcore reading are stuck to 0 volts so looks like its still not working as it should. So please help me out here in getting proper temperature readings here. unraid-diagnostics-20241107-1123.zip

@JorgeB update... So far after switching to stick 2, its running stable now and no more BTRFS or input output errors, so after 5-6 days of it running stable i added last RAM Stick and its still running stable, no BTRFS or I/O Error except i got segfault errors when i tried to play a episode from a TV series over plex and so far it has only happened with that one single particular file so i just replaced that file. Jul 28 22:41:35 Unraid kernel: PMS GTP[10402]: segfault at 77 ip 00001500349a0e6c sp 000015002b925720 error 4 in Plex Media Server[1500347fd000+d08000] likely on CPU 7 (core 3, socket 0) Jul 28 22:41:57 Unraid kernel: PMS GTP[14390]: segfault at 77 ip 0000148ea43a0e6c sp 0000148e9d38c720 error 4 in Plex Media Server[148ea41fd000+d08000] likely on CPU 4 (core 0, socket 0) Jul 28 22:44:38 Unraid kernel: PMS GTP[15524]: segfault at 77 ip 000015190f7a0e6c sp 0000151908fd4720 error 4 in Plex Media Server[15190f5fd000+d08000] likely on CPU 2 (core 2, socket 0) Jul 28 22:45:00 Unraid kernel: PMS GTP[22766]: segfault at 77 ip 000014b912da0e6c sp 000014b908ce6720 error 4 in Plex Media Server[14b912bfd000+d08000] likely on CPU 5 (core 1, socket 0) So my thinking is so far it looks 1st of the three sticks was causing BTRFS Corruption and somewhere some time that file may have gone corrupt which then now caused these segfault errors when i tried to read them but you are the expert here i'm not..😅

@JorgeB So with just one stick, i deleted the docker image and slowly started reinstalling dockers through community app plugin and it was going fine up until 18th docker. 19th Docker failed with following error Error: failed to register layer: read /var/lib/docker/tmp/GetImageBlob3662119572: input/output error And syslog is showing these same btrfs errors again. Jul 22 19:35:18 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 2846 off 250462208 csum 0x59363698 expected csum 0x508941a2 mirror 1 Jul 22 19:35:18 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Jul 22 19:35:19 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 2846 off 250462208 csum 0x59363698 expected csum 0x508941a2 mirror 1 Jul 22 19:35:19 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Jul 22 19:35:19 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 2846 off 250462208 csum 0x59363698 expected csum 0x508941a2 mirror 1 Jul 22 19:35:19 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 Jul 22 19:35:19 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 2846 off 250462208 csum 0x59363698 expected csum 0x508941a2 mirror 1 Jul 22 19:35:19 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 So i guess its to replace with another stick and start the whole process again😭

. unraid-diagnostics-20240722-1528.zip

@JorgeBhey i booted my system with just 1 stick to see how it goes but now syslog is showing these errors. Jul 22 15:08:02 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 15:08:02 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 16, gen 0 Jul 22 15:08:19 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 15:08:19 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 17, gen 0 Jul 22 15:08:44 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 15:08:44 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 18, gen 0 Jul 22 15:09:15 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 15:09:15 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 19, gen 0 any ideas which drive is device loop2 ? is it cache

😭 thats what I pretty much did last time around bought a new 8 gig stick used it for week and it ran stable so afterwards replaced my older 2x8 gig sticks that i was using. So i guess a year later i'm back to square one then😭 But thanks, as always you have been much help i just hope it last before i can upgrade. ( I had been thinking of upgrading my CPU ever since ryzen 5000 series came out and ryzen 9000 is almost out 😅.)

i have tested my ram using Live mem tester plugin multiple times and it always comes out without any errors and actually last time when i had these kind of errors, you suggested that ram is generally the first thing to test in these kind of scenarios so i had replaced all my ram sticks since these Kingston hyperx sticks come with lifetime warranty so...😅 Shortly after which i got myself apc ups for my server and LSI 9207-8i and also replaced my SMPS and after which it had been running quite stably so far, so i had thought maybe it was ram even though last time too memtest didn't find any errors but now they are back again. Surely i can't be that unlucky when it comes to RAM😅 And this morning again while running appdata backup it again failed on Tar verification of plex appdata and i noticed that again syslog is showing similar errors Jul 22 03:01:26 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 03:01:26 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 12, gen 0 Jul 22 03:12:59 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 03:12:59 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 13, gen 0 Jul 22 03:43:30 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 03:43:30 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 14, gen 0 Jul 22 04:14:00 Unraid kernel: BTRFS warning (device loop2): csum failed root 26983 ino 3290 off 5459968 csum 0x851cd069 expected csum 0xa5ae22ba mirror 1 Jul 22 04:14:00 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 15, gen 0 Jul 22 11:19:27 Unraid nginx: 2024/07/22 11:19:27 [error] 19942#19942: *1010208 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 10.0.0.23, server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/1.1", host: "10.0.0.3", referrer: "http://10.0.0.3/Shares/Browse?dir=%2Fmnt%2Fuser%2FBackup%2FAppdata%2Fab_20240722_021002-failed" Could this also happen due same hardware issue here.

deleted that file and scrub ran without any error this time UUID: 8206daa0-8850-4ac1-8149-65d3d6d92f27 Scrub started: Sun Jul 21 16:52:22 2024 Status: finished Duration: 0:11:20 Total to scrub: 216.22GiB Rate: 325.61MiB/s Error summary: no errors found But why is this corruption happening again and again, i forgot to mention this earlier but originally back a week ago when earlier i noticed these errors i was actually installing some docker container using community application which ended up failing due input output error thats how i noticed these errors. Any thoughts on why its this errors could occuring ?

UUID: 8206daa0-8850-4ac1-8149-65d3d6d92f27 Scrub started: Sun Jul 21 15:41:00 2024 Status: finished Duration: 0:11:29 Total to scrub: 239.14GiB Rate: 355.41MiB/s Error summary: csum=1 Corrected: 0 Uncorrectable: 1 Unverified: 0 ☝️ Scrub results Jul 21 15:41:00 Unraid kernel: BTRFS info (device sdd1): scrub: started on devid 1 Jul 21 15:49:17 Unraid kernel: BTRFS warning (device sdd1): checksum error at logical 4283911495680 on dev /dev/sdd1, physical 248789721088, root 5, inode 46457306, offset 11439251456, length 4096, links 1 (path: Media/All Movies/Movies/X2 (2003)/X2 (2003) Bluray-2160p.mkv) Jul 21 15:49:17 Unraid kernel: BTRFS error (device sdd1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 33, gen 0 Jul 21 15:49:17 Unraid kernel: BTRFS error (device sdd1): unable to fixup (regular) error at logical 4283911495680 on dev /dev/sdd1 Jul 21 15:52:29 Unraid kernel: BTRFS info (device sdd1): scrub: finished on devid 1 with status: 0 Same file that tdarr was using earlier.

Hey guys i noticed some corruption errors, BTRFS csum Errors and input output errors on server's syslog today, all were on cache drive and i think both time i was running tdarr. Please give suggestion on how can fix these errors, could input output errors cause corruption or vice versa. And almost a week ago similar input output and errors on cache drive occured so when i ran scrub on it its was showing 2-3 plex meta data files as corrupt so i just deleted those files as at that time my APC ups was also having some battery related issues so my server did face one or two unclean shutdowns, so i didnt think on it much but they are back again. Could it be my cache drive going bad ? unraid-diagnostics-20240721-1326.zip

hey everyone i just noticed that my parity drive has come up with a SMART error and its UDMA CRC error and so far its only one error, should i be worried and replace it asap ?? The drive in question here 8TB Seagate Ironwolf and its only 9 months old. unraid-diagnostics-20231204-2155.zip

thanks unraid's main page shows zero errors. Should I go ahead with the parity check that failed on Dec 2nd. ( that was scheduled parity check)