Max

Hey guys i noticed some data corruption errors on my cache drive but logs were not showing which files got corrupted, so i ran a scrub test on my cache drive but scrub didn't find any data corruption. So is there any way to find out which files got corrupted. unraid.local-diagnostics-20230505-2125.zip

Nothing should be accessing it during backup cause it's a file which only useful to PMS and we can see that it wasn't running at that time, weirdly this morning when it ran schedule backup, it ran without any errors. So its quite confusing why sometimes it throws error will sometimes it doesn't.

[02.01.2023 18:08:34] Backup of appData starting. This may take awhile [02.01.2023 18:08:34] Not stopping binhex-krusader: Not started! [ / Exited (0) 4 weeks ago] [02.01.2023 18:08:34] Stopping binhex-qbittorrentvpn... done! (took 2 seconds) [02.01.2023 18:08:36] Not stopping DiskSpeed: Not started! [ / Created] [02.01.2023 18:08:36] Not stopping duckdns: Not started! [ / Created] [02.01.2023 18:08:36] Stopping jackettvpn... done! (took 10 seconds) [02.01.2023 18:08:46] Not stopping jDownloader2: Not started! [ / Created] [02.01.2023 18:08:46] Not stopping MKVToolNix: Not started! [ / Created] [02.01.2023 18:08:46] Not stopping netdata: Not started! [ / Created] [02.01.2023 18:08:46] Stopping PlexMediaServer... done! (took 6 seconds) [02.01.2023 18:08:52] Stopping radarr... done! (took 7 seconds) [02.01.2023 18:08:59] Not stopping Restreamer: Not started! [ / Exited (137) 11 days ago] [02.01.2023 18:08:59] Not stopping RTMPS-Server: Not started! [ / Created] [02.01.2023 18:08:59] Stopping shinobipro... done! (took 10 seconds) [02.01.2023 18:09:09] Stopping sonarr... done! (took 4 seconds) [02.01.2023 18:09:13] Stopping speedtest-tracker... done! (took 4 seconds) [02.01.2023 18:09:17] Stopping tautulli... done! (took 0 seconds) [02.01.2023 18:09:17] Not stopping tdarr: Not started! [ / Exited (255) 7 days ago] [02.01.2023 18:09:17] Not stopping ubooquity: Not started! [ / Exited (0) 25 hours ago] [02.01.2023 18:09:17] Not stopping vm_custom_icons: Not started! [ / Exited (0) 2 months ago] [02.01.2023 18:09:17] Stopping ZeroTier... done! (took 10 seconds) [02.01.2023 18:09:27] Backing up libvirt.img to /mnt/user/Backup/Libvirt/ [02.01.2023 18:09:27] Using Command: /usr/bin/rsync -avXHq --delete --log-file="/var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log" "/mnt/user/system/libvirt/libvirt.img" "/mnt/user/Backup/Libvirt/" > /dev/null 2>&1 2023/01/02 18:09:27 [11274] building file list 2023/01/02 18:09:27 [11274] sent 75 bytes received 19 bytes 188.00 bytes/sec 2023/01/02 18:09:27 [11274] total size is 1,073,741,824 speedup is 11,422,785.36 [02.01.2023 18:09:27] Backing Up appData from /mnt/user/appdata/ to /mnt/user/Backup/Appdata/[email protected] [02.01.2023 18:09:27] Separate archives disabled! Saving into one file. [02.01.2023 18:09:27] Backing Up /usr/bin/tar: ./binhex-qbittorrentvpn/qBittorrent/config/ipc-socket: socket ignored [02.01.2023 18:27:54] Verifying Backup ./PlexMediaServer/Library/Application Support/Plex Media Server/Media/localhost/7/2890f21522a4e9591d4a391f2ff162812f0fb82.bundle/Contents/Indexes/index-sd.bif: Contents differ ./PlexMediaServer/Library/Application Support/Plex Media Server/Media/localhost/c/80b9477376cb3e160f56fc3f2f053d9d6ad6322.bundle/Contents/Indexes/index-sd.bif: Contents differ [02.01.2023 18:35:46] tar verify failed! [02.01.2023 18:35:46] done [02.01.2023 18:35:46] Starting ZeroTier... (try #1) done! [02.01.2023 18:35:48] Starting binhex-qbittorrentvpn... (try #1) done! [02.01.2023 18:35:50] Starting jackettvpn... (try #1) done! [02.01.2023 18:35:52] Starting radarr... (try #1) done! [02.01.2023 18:35:55] Starting shinobipro... (try #1) done! [02.01.2023 18:35:57] Starting PlexMediaServer... (try #1) done! [02.01.2023 18:36:00] Starting sonarr... (try #1) done! [02.01.2023 18:36:02] Starting tautulli... (try #1) done! [02.01.2023 18:36:04] Starting speedtest-tracker... (try #1) done! [02.01.2023 18:36:06] A error occurred somewhere. Not deleting old backup sets of appdata [02.01.2023 18:36:07] Backup / Restore Completed I'm getting content differs error from past couple of days with plexmediaserver.

okay will do but just now when i tried to access that data which first showed that error is now again showing this error. ec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 Dec 2 22:22:41 Unraid kernel: BTRFS error (device md1: state EA): parent transid verify failed on 37945344 wanted 22027 found 20712 i also tried scrubing disk 1 but it just aborts instantly on its own. tried this scrub didn't find any errors. unraid.local-diagnostics-20221202-2231.zip Also today scheduled parity check ran it found more than 42K errors.

Hey guys i need some help with my unraid server, so the thing yesterday i noticed that my MD1 drive was throwing some ATA read errors. and when i tried a recently added data it was throwing these errors. BTRFS error (device md1): parent transid verify failed on 475906048 wanted 21896 found 21309 So after reseating the cable those ATA read errors are gone but this morning when i checked logs, now it showing these BTRFS errors. Dec 1 03:40:25 Unraid kernel: BTRFS error (device md1): parent transid verify failed on 475906048 wanted 21896 found 21309 Dec 1 03:40:25 Unraid kernel: BTRFS error (device md1): parent transid verify failed on 475906048 wanted 21896 found 21309 Dec 1 03:40:25 Unraid kernel: BTRFS: error (device md1: state A) in do_free_extent_accounting:2852: errno=-5 IO failure Dec 1 03:40:25 Unraid kernel: BTRFS: error (device md1: state EA) in btrfs_run_delayed_refs:2157: errno=-5 IO failure Any idea what could be the cause of these errors and what can i do to fix these. unraid.local-diagnostics-20221201-0856.zip

just found the fix for this unraid-api restart put this in terminal, this fixed it for me.

Hey guys, today i noticed that unraid was showing unexpected token error under my username - under myserver section so then i tried incognito mode to check if its some cache related issue again same error then i tried edge browser to it see if its browser related error but there it is showing unraid api Cors error. So thought lets signing out and signing back again but then pop shows timed out error although earlier on unraid.net my server was showing up online and now its offline there but im still getting same error on webgui and it is still showing up as signed in on webgui. Please help me fix this. Update: now its showing online again on unraid.net Update 2: added diagnostics for in case they are needed for this issue. unraid.local-diagnostics-20220807-1157.zip

already replaced the cable. well the thing is im using netgear orbi router which only has one ethernet port but i have tried connecting it to my laptop and there it worked fine so im sure its not my cable or router.

Hey guys i need some help figuring whether its a hardware issue or not --- As i mentioned after a reboot suddenly onboard nic stopped working i have tried cmos reset but that didn't help at all. Plus now its showing some weird ip address after boot -- 169.254.40.83 instead of 10.0.0.X or not set. so if anyone could take look at my diagnostics and let me know why this is happening -- i would really appreciate it unraid-diagnostics-20210509-2316.zip

Looks like it was a bad sata power splitter cause now after connecting that drive directly it's been doing parity check for almost 2.5hours now and so far none of those errors have come up. Although it is already showing more than 20k sync errors. Should run I parity check with correction once and if it finishes without those errors??

okay will try that but now my server is spamming these errors in syslog. Mar 23 14:54:21 Unraid nginx: 2021/03/23 14:54:21 [alert] 7015#7015: worker process 4716 exited on signal 6 Mar 23 14:54:22 Unraid nginx: 2021/03/23 14:54:22 [alert] 7015#7015: worker process 4768 exited on signal 6 Mar 23 14:54:23 Unraid nginx: 2021/03/23 14:54:23 [alert] 7015#7015: worker process 4822 exited on signal 6 Mar 23 14:54:24 Unraid nginx: 2021/03/23 14:54:24 [alert] 7015#7015: worker process 4951 exited on signal 6 Mar 23 14:54:25 Unraid nginx: 2021/03/23 14:54:25 [alert] 7015#7015: worker process 5038 exited on signal 6 Mar 23 14:54:26 Unraid nginx: 2021/03/23 14:54:26 [alert] 7015#7015: worker process 5091 exited on signal 6 Mar 23 14:54:27 Unraid nginx: 2021/03/23 14:54:27 [alert] 7015#7015: worker process 5141 exited on signal 6 Mar 23 14:54:28 Unraid nginx: 2021/03/23 14:54:28 [alert] 7015#7015: worker process 5192 exited on signal 6 Mar 23 14:54:29 Unraid nginx: 2021/03/23 14:54:29 [alert] 7015#7015: worker process 5235 exited on signal 6 Mar 23 14:54:30 Unraid nginx: 2021/03/23 14:54:30 [alert] 7015#7015: worker process 5278 exited on signal 6 Mar 23 14:54:31 Unraid nginx: 2021/03/23 14:54:31 [alert] 7015#7015: worker process 5329 exited on signal 6 Mar 23 14:54:32 Unraid nginx: 2021/03/23 14:54:32 [alert] 7015#7015: worker process 5373 exited on signal 6

.. unraid-diagnostics-20210323-1351.zip

@JorgeB update: so after limiting writes to disk1 and cache everything was going well, no error this time when backup/restore plugin ran but today i accidently shut off my server which resulted in unclean shutdown. so when when i started my array later it ran parity sync check without doing corrections and soon it started reporting many sync errors and it was running at like 4-5 megbabyte/sec and when i checked syslog it was full of these read errors from disk2. Mar 23 12:10:55 Unraid kernel: blk_update_request: I/O error, dev sdd, sector 738691496 op 0x0:(READ) flags 0x0 phys_seg 85 prio class 0 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691432 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691440 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691448 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691456 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691464 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691472 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691480 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691488 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691496 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691504 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691512 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691520 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691528 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691536 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691544 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691552 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691560 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691568 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691576 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691584 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691592 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691600 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691608 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691616 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691624 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691632 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691640 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691648 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691656 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691664 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691672 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691680 Mar 23 12:10:55 Unraid kernel: md: disk2 read error, sector=738691688 im not showing all cause their were literally too of them plus of course those ata3 errors from earlier were also their.

yeah i did had a thought, that maybe RAM plus disk2 is going bonkers but yeah i know, for two seprate parts to go bad plus to both of them to actaully only corrupt data is quite unusual. i thought of that too but unfortunately i don't have one. would making my backup share disk1 or maybe cache only help testing this as for now corruption is only occurring while backing up.

okay so what do u suggest should i claim warranty on disk2 cause so far after replacing ram, only disk 2 is showing data corruption plus those errors. i changed sata port, i have changed sata cable (twice actually) but its still showing errors on only that drive. and i think if it was my board then these would show up randomly on any drive or it would be limited to one of the sata port on board but its not showing up on other drives and its not limited to one port, it is sticking to drive in particular thats disk 2 which would be really weird for board or cpu failure.

@JorgeB hey today when those errors occured i noticed one strange thing which is both today and yesterday when those errors occurred ca backup and restore plugin was creating backup and the only file on entire server (that includes both disk drives and cache drive) was the one it created. and another thing that i noticed is that both the time, first it showed these errors. Mar 22 14:52:25 Unraid kernel: ata3.00: exception Emask 0x50 SAct 0x771e SErr 0x4890800 action 0xe frozen Mar 22 14:52:25 Unraid kernel: ata3.00: irq_stat 0x0c400040, interface fatal error, connection status changed Mar 22 14:52:25 Unraid kernel: ata3: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: READ FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 60/40:08:f8:40:5f/05:00:e0:00:00/40 tag 1 ncq dma 688128 in Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: READ FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 60/40:10:38:46:5f/05:00:e0:00:00/40 tag 2 ncq dma 688128 in Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: READ FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 60/40:18:78:4b:5f/05:00:e0:00:00/40 tag 3 ncq dma 688128 in Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: READ FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 60/40:20:b8:50:5f/05:00:e0:00:00/40 tag 4 ncq dma 688128 in Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: READ FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 60/08:40:f8:55:5f/00:00:e0:00:00/40 tag 8 ncq dma 4096 in Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: READ FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 60/a0:48:00:56:5f/02:00:e0:00:00/40 tag 9 ncq dma 344064 in Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: WRITE FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 61/40:50:38:f2:5e/05:00:e0:00:00/40 tag 10 ncq dma 688128 out Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: WRITE FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 61/40:60:78:f7:5e/05:00:e0:00:00/40 tag 12 ncq dma 688128 out Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: WRITE FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 61/40:68:b8:fc:5e/05:00:e0:00:00/40 tag 13 ncq dma 688128 out Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3.00: failed command: WRITE FPDMA QUEUED Mar 22 14:52:25 Unraid kernel: ata3.00: cmd 61/40:70:f8:01:5f/05:00:e0:00:00/40 tag 14 ncq dma 688128 out Mar 22 14:52:25 Unraid kernel: res 40/00:70:f8:01:5f/00:00:e0:00:00/40 Emask 0x50 (ATA bus error) Mar 22 14:52:25 Unraid kernel: ata3.00: status: { DRDY } Mar 22 14:52:25 Unraid kernel: ata3: hard resetting link Mar 22 14:52:31 Unraid kernel: ata3: link is slow to respond, please be patient (ready=0) Mar 22 14:52:32 Unraid kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 22 14:52:32 Unraid kernel: ata3.00: configured for UDMA/133 Mar 22 14:52:32 Unraid kernel: ata3: EH complete only then it showed corruption errors, so i thought maybe the sata cable that i replaced on disk2 is also faulty, so i bought new sata cable to check just in case but it is still showing those errors is disk2 only could it be my disk2 going bonkers.

Yeah i had 2x8 gigs sticks earlier replaced them with 1x8 gig completely new stick.

@JorgeB would something like lsi 9260-8i help me eliminate motherboard as a suspect.

ohhhh boy😭. would it be possible that somehow i managed to copy some corrupted data and thats why its showing up now, cause when was backing up my data their were some which failed to copy so thought they were corrupt as well but they didn't show up as corrupted under scrub. and is it possible for it to have anything to do with 6.9.1 cause as far as i remember they are were pretty close to each other like less then 24 hours apart.

@JorgeB Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39428833280 csum 0x03d6ab02 expected csum 0xe395e029 mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39428845568 csum 0x11013b58 expected csum 0xaa1a5420 mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39428866048 csum 0xd226d08a expected csum 0x63b2c2c3 mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39428886528 csum 0x33980e71 expected csum 0x4c775c09 mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39428907008 csum 0x1863e21f expected csum 0x3027eacb mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39428968448 csum 0x337f1b41 expected csum 0x2619b33a mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 6, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39429296128 csum 0xc0486401 expected csum 0xa6614d88 mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39429357568 csum 0x7e844d92 expected csum 0xb62cd92e mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39429582848 csum 0x8ae91f99 expected csum 0xf55f5d7c mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 Mar 21 04:18:34 Unraid kernel: BTRFS warning (device md2): csum failed root 5 ino 3611 off 39429869568 csum 0x75e706ad expected csum 0xda1d3603 mirror 1 Mar 21 04:18:34 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 looks like it wasn't my ram cause they are back, so far only disk 2 is showing these errors, so i would like to fix this asap. Any suggestions ??

crap, it can't be fixed. but thanks for all the help, you are life saver man.

is their any way to fix metadata ?? or i will have to do same thing that did with disk1, i.e. backup and restore.

okay, replaced the cable on that disk, now scrub is not showing those errors but i still get these 6 verify error at the very beginning of scrub, these don't say anything about corrupt file, so what should i do to get rid of these. Mar 18 17:59:44 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622215168 on dev /dev/md2, physical 630603776: metadata leaf (level 0) in tree 7 Mar 18 17:59:44 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622215168 on dev /dev/md2, physical 630603776: metadata leaf (level 0) in tree 7 Mar 18 17:59:44 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 48346, gen 68 Mar 18 17:59:44 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622870528 on dev /dev/md2, physical 631259136: metadata leaf (level 0) in tree 7 Mar 18 17:59:44 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622870528 on dev /dev/md2, physical 631259136: metadata leaf (level 0) in tree 7 Mar 18 17:59:44 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 48346, gen 69 Mar 18 17:59:44 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 623017984 on dev /dev/md2, physical 631406592: metadata leaf (level 0) in tree 7 Mar 18 17:59:44 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 623017984 on dev /dev/md2, physical 631406592: metadata leaf (level 0) in tree 7 Mar 18 17:59:44 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 48346, gen 70 Mar 18 17:59:49 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622215168 on dev /dev/md2, physical 1704345600: metadata leaf (level 0) in tree 7 Mar 18 17:59:49 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622215168 on dev /dev/md2, physical 1704345600: metadata leaf (level 0) in tree 7 Mar 18 17:59:49 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 48346, gen 71 Mar 18 17:59:49 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622870528 on dev /dev/md2, physical 1705000960: metadata leaf (level 0) in tree 7 Mar 18 17:59:49 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 622870528 on dev /dev/md2, physical 1705000960: metadata leaf (level 0) in tree 7 Mar 18 17:59:49 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 48346, gen 72 Mar 18 17:59:49 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 623017984 on dev /dev/md2, physical 1705148416: metadata leaf (level 0) in tree 7 Mar 18 17:59:49 Unraid kernel: BTRFS warning (device md2): checksum/header error at logical 623017984 on dev /dev/md2, physical 1705148416: metadata leaf (level 0) in tree 7 Mar 18 17:59:49 Unraid kernel: BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 0, flush 0, corrupt 48346, gen 73

@JorgeBthanks to u i have successfully restored my disk1 and now im running scrub on disk2 to know which files are corrupt on disk2 so that i can replace them but i noticed that my also getting these types of error in between, are they showing cause of corruption and they will go away once i get rid of those corrupt files or their is something that going wrong too. Mar 18 16:03:43 Unraid kernel: ata2.00: failed command: READ FPDMA QUEUED Mar 18 16:03:43 Unraid kernel: ata2.00: cmd 60/20:e8:60:b6:0c/00:00:00:00:00/40 tag 29 ncq dma 16384 in Mar 18 16:03:43 Unraid kernel: res 40/00:20:80:b7:0c/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Mar 18 16:03:43 Unraid kernel: ata2.00: status: { DRDY } Mar 18 16:03:43 Unraid kernel: ata2.00: failed command: READ FPDMA QUEUED Mar 18 16:03:43 Unraid kernel: ata2.00: cmd 60/20:f0:80:b6:0c/00:00:00:00:00/40 tag 30 ncq dma 16384 in Mar 18 16:03:43 Unraid kernel: res 40/00:20:80:b7:0c/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Mar 18 16:03:43 Unraid kernel: ata2.00: status: { DRDY } Mar 18 16:03:43 Unraid kernel: ata2.00: failed command: READ FPDMA QUEUED Mar 18 16:03:43 Unraid kernel: ata2.00: cmd 60/40:f8:a0:b6:0c/00:00:00:00:00/40 tag 31 ncq dma 32768 in Mar 18 16:03:43 Unraid kernel: res 40/00:20:80:b7:0c/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Mar 18 16:03:43 Unraid kernel: ata2.00: status: { DRDY } Mar 18 16:03:43 Unraid kernel: ata2: hard resetting link Mar 18 16:03:49 Unraid kernel: ata2: link is slow to respond, please be patient (ready=0) Mar 18 16:03:50 Unraid kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 18 16:03:50 Unraid kernel: ata2.00: configured for UDMA/133 Mar 18 16:03:50 Unraid kernel: ata2: EH complete

its exfat and yeah data is copying normally but this way it will ages to copy all files. Edit its exfat, i had another ssd under ud plugin with exfat i was getting same error then i tried with xfs and this time no error.