Max

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)

@JorgeB okay something weird is happening again first off replacing psu somehow cleared the bios which resulted it to be back on optimized defaults, meaning no more proper iommu group sepration but i thought i will figure it later. so important stuff now, so last yesterday night when i checked it was going fine i think it was almost 80 percent done without any errors but this morning when logged on webgui it showed a notification saying data rebuild finished with 310912 errors !!! though the disk has returned to normal operations and data is there and accessible and logs also doesn't show any errors or warning. and somehow all this changed my unraid servers name and screwed time, so time is off on the logs. tower-diagnostics-20231204-0829.zip

so far looks like it was bad sata power splitter as i did try again after reseating the cables (i tried reseating cable again cause i realized that last time i mistakenly reseated cables of completely different drive😅) and now while rebuilding data it started throwing errors on disk 2, disk 2 and 3 are the ones that are connected through sata power splitter, so finally decided to pull the plug on sata power splitters and bought myself Gigabyte P750GM which comes with 8 sata connectors. i dont know its just my bad luck or what, my history with SATA cables and power splitters has been quite troublesome. I found myself frequently reseating or replacing these cables every 2-3 months. About 6 or 7 months ago, I invested in an LSI 9207-8i, and since then, I haven't encountered a single issue related to SATA link speed or any other connectivity problems. Here's hoping that this new power supply will have a similar positive impact on my SATA power issues.

yeah actually thats what i meant that it mainly talks about ungraceful shutdown due to too short of a timeout but honestly as this wasn't my first unclean shutdown i have manually tested it many times like deliberately pulled out the cord to see whether it stays on on ups or not or whether it shuts down properly according to set rules. i have tried different plug points on the back of ups, changed the power cords as well, still haven't figured out whats the issue. @JorgeB ahh looks we are back to square one, disk3 is again throwing read errors and its disabled and currently being emulated unraid.local-diagnostics-20231202-1923.zip

just gave it a read but thing is, it mainly talks about ungraceful shutdown after a power failure but there was no power failure.

phewww!!! finally rebuild is finished and fortunately without any errors or weird notifications this time and disk3 is back up and running in normal operation dont know what went wrong the first time. BTW any guesses on what could have caused unclean shutdown in the beginning.

okay i have uninstalled parity check tuning plugin started rebuilding again, so far looks good, started from zero percent this percent time. gonna take much longer this time 😅

here's the latest log unraid.local-diagnostics-20231201-0025.zip

okay once again i just removed the drive from pool and started the array normally although now its says disk3 missing but once again just like earlier disk3 contents are getting emulated and i can access any content that supposed to be there. can i try rebuilding again cause im not too sure about earlier rebuild process i mean how could it do 71-72 percent rebuilding in a couple of minutes ??

i used maintenance mode because unraid docs recommends using it for better speeds. And earlier when it was in normal mode, the emulated disk was mountable and i was able to access any data that was supposed to be there in disk 3.

after rebuilding the data, i stopped the array as it was in maintenance mode and started the array normally and now my disk 3 is saying unmountable: Unsupported or no file system. unraid.local-diagnostics-20231130-1056.zip

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.