Max

okay so after reseating the cables i have started rebuilding data but im not sure wheteher everything is going fine here, cause firstly the moment i clicked sync webgui became unresponsive for almost a minute then when it came back it got paused on its own. Secondly its all ready done 73issh percent. im not sure whether this is how it works or i m doing something wrong here. unraid.local-diagnostics-20231129-2208.zip

Hey guys so for some unknown reason my server detected unclean shutdown this morning although it is connected to apc ups so this should not have happened but it did and i don't know why it did and as usual after an unclean shutdown server started automatic parity check it was all running fine until just now for some reason disk 3 started throwing read and write errors and now my disk 3 is disabled and its contents are currently being emulated. please suggest how should i proceed ? unraid.local-diagnostics-20231129-2100.zip

been using since 6.12. this was mentioned in the changelog of 6.12.

unraid 6.12.3 breaks it again for me, was working on 6.12.2.

Hey guys suddenly this morning i noticed that some of my dockers were running and i tried running them it ended up with these error docker: Error response from daemon: failed to start shim: write /var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/3f6f0373888660b5cc82104b1920b7de44593bd761c184ee1f537df47aa99759/config.json: no space left on device: unknown. docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc did not terminate successfully: exit status 1: unknown. and then when i tried docker exec of some that were running that failed too. So after randomly starting and stoping all dockers i come to conclusion that suddenly its like i have limit of how many dockers i can run at a time cause i noticed if stop some of the dockers that are running and then if i try to docker exec or start a docker which were earlier throwing those errors, they start to work. please help if some knows how can fix this. unraid.local-diagnostics-20230624-1517.zip

for me it showed today only, and for me atleast it's like suddenly i have a limit of running only n number of dockers at a time. As i noticed that reduced the number of dockers that currently, the dockers that earlier the same error here OP mentioned, starts to run back normally. And docker exec too starts running when i reduce number of dockers that are running.

thanks man somehow i missed this part😅, after updating 6.12.1 nextcloud is again throwing the same port 443 is already in use error even though https is disabled and again webgui was unaccessible after update but this ☝️ fixed the zerotier issue. though at first i was a bit confused like what interface, im not using any special network setting or unique interface for zerotier so br0 was already added, then i just added the ip that assigned to my unraid server from zerotier and voilla it worksss!!

hey guys after updating unraid os to 6.12 i noticed that suddenly i cant access unraid webgui anymore via zerotier, although i could still get the ping from zerotier ip and still could access all my docker's webgui. and after 6.12 update nextcloud started to throw 443 port is already in use error even though i have disabled https on my server. So after i little bit googling i came to realize that people have been reporting webgui related issues after updating to 6.12 even though i didnt find any nginx error in my case, i decided to roll back to 6.11.5 and voilla both those issues are gone now. im attaching the log that i took before downgrading, if anyone could shed some light on what was the issue.... unraid.local-diagnostics-20230620-2149.zip

@hugenbdd hey sorry but i can't find the /mover inside my /tmp folder and something even strange that i found is that when i invoke mover myself by clicking move now button it doesn't throw those errors. so it seems like it only throws those errors when it automatically runs at scheduled time.

1.) Yes and it is still throwing those same errors. May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/9/0/b/1/8/a/6/66245/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/9/0/b/1/8/a/6/66245/1024-2268.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/7/c/4/8/0/3/2/66255/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/7/1/3/6/1/8/d/66275/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/2/3/7/f/d/0/9/66265/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/8/f/8/d/9/a/0/66285/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/e/b/4/0/7/9/6/66339/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/e/b/c/a/c/8/1/66088/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/e/7/7/c/7/b/5/66134/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/c/2/5/7/e/c/d/66234/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/c/2/5/7/e/c/d/66234/1024-2276.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/c/7/3/8/3/3/a/66224/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/c/d/9/2/3/9/0/66048/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/d/4/2/7/c/6/2/66193/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/d/8/5/1/9/3/a/66144/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/5/b/d/d/7/b/3/66204/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/5/9/7/3/2/4/1/66154/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/6/0/7/8/0/d/5/66214/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/6/4/c/4/9/b/4/66182/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/0/1/7/6/8/b/3/66172/1024-1024-crop.jpg May 20 04:11:11 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/1/f/1/3/e/d/f/66078/1024-1024-crop.jpg 2.) Don't know where that is. 😅 3.) if you meant unraid version then i'm on 6.11.5.

hey guys was there some issues with the previous version of mover cause today i noticed that mover has been throwing errors like these from 17th may. May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/Shivam/files/AutoSync/Oneplus 8T/CAM/2023/05/IMG_20230516_190018.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/Shivam/files/AutoSync/Oneplus 8T/CAM/2023/05/IMG_20230516_190035.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/Shivam/files/AutoSync/Oneplus 8T/CAM/2023/05/IMG_20230516_190028.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/Shivam/files/AutoSync/Oneplus 8T/CAM/2023/05/IMG_20230516_190222.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/Shivam/files/AutoSync/Oneplus 8T/CAM/2023/05/IMG_20230516_190224.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/9/0/b/1/8/a/6/66245/1849-4096-max.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/9/0/b/1/8/a/6/66245/256-256-crop.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/7/c/4/8/0/3/2/66255/4000-1800-max.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/7/c/4/8/0/3/2/66255/256-256-crop.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/7/1/3/6/1/8/d/66275/4096-1849-max.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/7/1/3/6/1/8/d/66275/256-256-crop.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/2/3/7/f/d/0/9/66265/4000-1800-max.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/2/3/7/f/d/0/9/66265/256-256-crop.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/8/f/8/d/9/a/0/66285/4096-1849-max.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Data/appdata_oci6r1eodkwt/preview/8/f/8/d/9/a/0/66285/256-256-crop.jpg May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Media/All Movies/Movies/The Super Mario Bros. Movie (2023)/The Super Mario Bros. Movie (2023) WEBDL-2160p.mkv May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/cctv/uItw4yLwPX/an1AnomvOg/2023-05-16T05-55-47.mp4 May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/cctv/uItw4yLwPX/an1AnomvOg/2023-05-16T06-18-35.mp4 May 17 04:05:07 Unraid move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/cctv/uItw4yLwPX/an1AnomvOg/2023-05-16T06-23-14.mp4 And i checked for these files and they are there in the disk now, so it looks like even though mover successfully moved these files it is throwing these errors.

hey i ran scrub on disk1 and here too it didnt find any errors.

@JorgeB could those corruption errors caused due to ATA Link errors cause the thing is from like past month or so i was getting ATA link errors on disk 1 but i had been quite busy with work so i never got around fixing that until last sunday but then by then it had already started showing disk read errors and corruption errors so after some reseating/interchange came to conclusion that it was bad sata power splitter. And after i replaced it those read and corruption warnings were gone so i thought maybe because of bad sata power splitter it wasn't able to read properly maybe thats why it was showing corruption errors too. I just now realized that its still showing corruption, its just that now its under normal text instead of warning or text.

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

yup you are right, this is with vm is running. root@Unraid:~# nvidia-smi -L GPU 0: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad) no gtx 1070ti. root@Unraid:~# nvidia-smi -L GPU 0: GeForce GTX 1070 Ti (UUID: GPU-b3281921-cd4e-952e-a85c-853c365a663b) GPU 1: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad) and this here when vm is shut nvidia-smi can see both my gou again. i see, so this why gpu stats goes blank when i select gpu 1 and start my vm cause now there is no gpu 1 .😅

yeah i had felling that it was getting a little confusing. okay i try my best to explain it. you see here i have to nvidia GPU's, 0 is gtx 1070 ti which im using for my vm and 1 is gtx 750 for plex hardware transcoding. (i only want to see the stats for gpu 1 i.e. gtx 750) https://imgur.com/a/mGddMgH Now if i select gpu 1 i.e. gtx 750 from the dropdown list of unit ID for dashboard option it will keep posting stats until vm starts, the moment i start the vm all info on dashboard page will go blank and it will only resume posting when i shutdown my vm. Now if i click on this default button (while vm is still running) on gpu stats's page it will shows stats for gpu 1 i.e. gtx 750 but now when i shutdown my vm it will switch back to gpu 0 i.e. gtx 1070 ti cause under unit id for option it has switched back to gpu 0 cause we selected default option earlier, so cause 0 should be default it is now set gpu 0 i.e.e gtx 1070 ti. https://imgur.com/a/YzY4YmW so as long as its set to gpu 0 it will keep posting stats, now ofcourse it wil switch between gpu's whenever vm starts or stops but now atleast its always posting gpu stats. So basically its like this if its set it to gpu 0 it will always show gpu stats, it won't go blank but if i set it to gpu 1 it wont shows stats when the vm's are running.

looks like i spoke too soon it looks like everytime i run my vm it stop posting gpu stats and it only working once i click on default. but then when vm is shutdown it switch to gpu 0 which was being used by vm cause i clicked on default. so it looks like it will keep posting if i dont maually select gpu 1, here it will keep posting and switch to gpu 1 whenever i run my vm and then switch back to gpu 0 when vm is no longer running but i mainly wanna see stats for gpu 1 as this the gpu that is being used by plex and gpu 0 is for my vm's but this way i wont be able to see stats for gpu1 when vms are not running i will only be able to see stats for it when vm are running and if i do maually select gpu 1 in gpu stats plugin settings then it will stop posting as soons vm start to run and then start posting once again when vm is shutdown. a really weird glitch i guess if am not the only one with this issue.

i was experiencing empty stats issue and this fixed it for me. even though it was detecting both my gpu's but as soon as i started my vm it used to stop posting stats for my second gpu which is being used by plex. luckily this fixed it for me.

are the new versions of opencore (0.5.7 onwards) compatible with nvidia web drivers, i think i have read somewhere that nvdadrv wasn't needed anymore or it doesn't work or its deprecated or something like that.