comet424

ah ok fingers crossed.. so far i on test 9 no errors ill run it twice in my desktop pc... and then i going to pull the video card out and shove it in my server and run it twice in there... the 32gig i pulled out of unraid i posted a diagnostic in my other post that was with the 32gig ram in it and i found multiple errors on test 6 and 8... so i switched to the 16 gig ram and it was doing the sync error correct and running at 5 m/s so thats why it says its going to take a week.. i dunno why its taking a week is it not enough ram that i need 32gig or more and 16 gig slows things down? ill get get back when i finish doing 2 tests in the desktop and then 2 tests in the unraid oh and things were ok last night i was using syncthing to copy files from the server to the backup server.. notsure if that was the reason and that i should have left parity thing just run on its own

gonna shut down unraid and move the ram back in the desktop and run the memtest and ill get back to ya.. should be a few hours to do 1 run maybe less

@JorgeB should i stop the parity then as i dont wanna damange more and loose my important files

i did run mem test on the ram that was in there.. the 32 gig and it failed.. so is it saying the the 16 gig ram i took out of my desktop has also corrupted? parity is 4 days 15 hours its been running and another 3 4 days estimated.... are my files gone? is parity holding up... i also got 444 sync errors.. it my other post i as asking help for why parity slowed down i mentioned i had like 300 sync errors before i rebooted cuz it seemed to stall lik 50 percent.. whats a bitflip like 0 is now a 1... does that mean the files are gone and then id need to run mem test onthe desktop pc.. since unraid is headless

so parity been running 4 days 3 more days to go.. i asked already here but no one replied if you can speed up parity... but something happened... and error logs shwo something but i dont know what it means now my disk 1 has all the disk space still used but i lost all the file folders.. whats going on.. is this all the result from bad memory i posted in my last question that no one replied guess no one knew how to answer it... so i been stuck.. so just allowing parity check to go and been transfering files to my backup server will the folders and files come back once unraid is rebooted and or after the parity and sync errors are fixed and is is best to have 2 parity drives to prevent these errors from happening tardis-diagnostics-20230518-0900.zip

i found out that had memory problems constantly crashing unraid.. and making it look like cpu nvme or maclan errors.. so it would crash during parity checks etc... well i swapped out my memory from my desktop pc.... and running the parity check.. and it usually takes 23-25 hours to parity check.. but at somespotys it jumps to 107 days to partity check.. its typically running at 6 days it says.. i did reboot it to see if it was some error... but it ran fast to close the 50% but in 2 days i made it to 55.4% its estimating 7 more days to run... right now 327 sync errors i had more before i rebooted... is the errors what causes it? oh not sure if it matters. i went from 32gig ram down to 16 gig for the time being.. is the several days due to 16 gig rams? and is there a way to get unraid to notify when there is system log errors.. notifications doesnt offer anything when memory is failing or errors that show up in system log... is there a plugin that notifiys you on this.. as its impossible to check system logs every 5 min to check if there is an error

hi i had nvme issues and i transfered what i could to the array and run my appdata and so off the array.. but i getting nothing but May 12 12:46:18 Tardis kernel: CPU: 7 PID: 22939 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:18 Tardis kernel: Call Trace: May 12 12:46:18 Tardis kernel: CPU: 7 PID: 22942 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:18 Tardis kernel: Call Trace: May 12 12:46:18 Tardis kernel: CPU: 14 PID: 22954 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:18 Tardis kernel: Call Trace: May 12 12:46:29 Tardis kernel: CPU: 1 PID: 26433 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:29 Tardis kernel: Call Trace: May 12 12:46:29 Tardis kernel: CPU: 14 PID: 26438 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:29 Tardis kernel: Call Trace: May 12 12:46:29 Tardis kernel: CPU: 10 PID: 26441 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:29 Tardis kernel: Call Trace: May 12 12:46:29 Tardis kernel: CPU: 15 PID: 26455 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:29 Tardis kernel: Call Trace: May 12 12:46:40 Tardis kernel: CPU: 6 PID: 28683 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:40 Tardis kernel: Call Trace: May 12 12:46:40 Tardis kernel: CPU: 9 PID: 28686 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:40 Tardis kernel: Call Trace: May 12 12:46:40 Tardis kernel: CPU: 13 PID: 28691 Comm: find Tainted: G D O 5.19.17-Unraid #2 May 12 12:46:40 Tardis kernel: Call Trace: May 12 12:46:40 Tardis kernel: CPU: 4 PID: 28806 Comm: find Tainted: G D O 5.19.17-Unraid #2 what does all that mean?? and i also lost all my shares in unraid.. and its not really responding... im also running latest version of unraid 6.11.5 i did reboot and it brought my shares back so i finding parity crashes and says it will take 17 days and keeps adding up... can you tell me if my cpu is failing since it says cpu?? May 12 21:03:52 Tardis kernel: CPU: 3 PID: 17111 Comm: unraidd0 Tainted: G O 5.19.17-Unraid #2 May 12 21:03:52 Tardis kernel: Call Trace: May 12 21:03:52 Tardis kernel: WARNING: CPU: 3 PID: 17111 at kernel/exit.c:741 do_exit+0x39/0x8e5 May 12 21:03:52 Tardis kernel: CPU: 3 PID: 17111 Comm: unraidd0 Tainted: G D O 5.19.17-Unraid #2 May 12 21:03:52 Tardis kernel: Call Trace: May 12 21:07:28 Tardis nginx: 2023/05/12 21:07:28 [error] 11530#11530: *6425 limiting requests, excess: 20.297 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis" May 12 21:07:28 Tardis nginx: 2023/05/12 21:07:28 [error] 11530#11530: *6427 limiting requests, excess: 20.282 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis" May 12 21:07:29 Tardis nginx: 2023/05/12 21:07:29 [error] 11530#11530: *6443 limiting requests, excess: 20.647 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis" May 12 21:07:29 Tardis nginx: 2023/05/12 21:07:29 [error] 11530#11530: *6445 limiting requests, excess: 20.625 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis" May 12 21:07:29 Tardis nginx: 2023/05/12 21:07:29 [error] 11530#11530: *6448 limiting requests, excess: 20.610 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis" May 12 21:07:29 Tardis nginx: 2023/05/12 21:07:29 [error] 11530#11530: *6452 limiting requests, excess: 20.588 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis" May 12 21:07:29 Tardis nginx: 2023/05/12 21:07:29 [error] 11530#11530: *6454 limiting requests, excess: 20.573 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis" May 12 21:08:28 Tardis kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 270 off 27823837184 csum 0x7a0a148c expected csum 0x82f62317 mirror 1 May 12 21:08:28 Tardis kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 27, gen 0 May 12 21:08:28 Tardis kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 270 off 7319093248 csum 0x97150a85 expected csum 0xb98992ba mirror 1 May 12 21:08:28 Tardis kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 28, gen 0 May 12 21:09:00 Tardis kernel: WARNING: CPU: 3 PID: 17112 at arch/x86/kernel/fpu/core.c:427 kernel_fpu_begin_mask+0x30/0xc6 May 12 21:09:00 Tardis kernel: CPU: 3 PID: 17112 Comm: unraidd1 Tainted: G D W O 5.19.17-Unraid #2 May 12 21:09:00 Tardis kernel: Call Trace: May 12 21:09:00 Tardis kernel: WARNING: CPU: 3 PID: 17112 at arch/x86/kernel/fpu/core.c:428 kernel_fpu_begin_mask+0x3d/0xc6 May 12 21:09:00 Tardis kernel: CPU: 3 PID: 17112 Comm: unraidd1 Tainted: G D W O 5.19.17-Unraid #2 May 12 21:09:00 Tardis kernel: Call Trace: May 12 21:09:14 Tardis kernel: traps: unraid-api[12252] trap int3 ip:ebf052 sp:7ffc9ad460a0 error:0 in unraid-api[91c000+167b000] ip tardis-diagnostics-20230512-2113.zip tardis-diagnostics-20230512-1250.zip

i tried googling for help if others had same issue but nothing.. currently at 60% of parity with the video card out... i dunno if there is a conflict? i have a hba card network card expander card in the computer and when i plug the 3060 in the first slot where the video card goes thats where unraid goes haywire... anyone ever come across thiss???

i also had docker error that it didnt load it and gave error stuff i didnt copy i pull out the video card.. and boot back up and its running parity and its running fine again... what is wrong? is this common issue with geforce 3060? or is it unraid incompatible with this card? i dunno?

so i re booted.. and its staying on.. but it says parity checking still.. but its actually not running.. i took a look at the logs and this is what i got May 10 21:51:25 Tardis unassigned.devices: Warning: Unassigned Devices are not set to be shared with NFS. May 10 21:51:42 Tardis kernel: CPU: 0 PID: 12343 Comm: unraidd0 Tainted: P O 5.19.17-Unraid #2 May 10 21:51:42 Tardis kernel: Call Trace: May 10 21:51:42 Tardis kernel: WARNING: CPU: 0 PID: 12343 at arch/x86/kernel/fpu/core.c:427 kernel_fpu_begin_mask+0x30/0xc6 May 10 21:51:42 Tardis kernel: CPU: 0 PID: 12343 Comm: unraidd0 Tainted: P D O 5.19.17-Unraid #2 May 10 21:51:42 Tardis kernel: Call Trace: May 10 21:51:42 Tardis kernel: WARNING: CPU: 0 PID: 12343 at arch/x86/kernel/fpu/core.c:428 kernel_fpu_begin_mask+0x3d/0xc6 May 10 21:51:42 Tardis kernel: CPU: 0 PID: 12343 Comm: unraidd0 Tainted: P D W O 5.19.17-Unraid #2 May 10 21:51:42 Tardis kernel: Call Trace: May 10 21:51:42 Tardis kernel: WARNING: CPU: 0 PID: 12343 at kernel/exit.c:741 do_exit+0x39/0x8e5 May 10 21:51:42 Tardis kernel: CPU: 0 PID: 12343 Comm: unraidd0 Tainted: P D W O 5.19.17-Unraid #2 May 10 21:51:42 Tardis kernel: Call Trace: May 10 21:51:44 Tardis kernel: CPU: 7 PID: 25866 Comm: shfs Tainted: P D W O 5.19.17-Unraid #2 May 10 21:51:44 Tardis kernel: Call Trace:

im running lastest version of unraid 6.11.5 i added a 3060 video card to my unraid in hopes it helps with shinobi to record videos since just the cpu is messing up but i find that the unraid gui page stops working after a couple min when unraid array goes online... home assistant and my vms are running i can ping unraid box.. but i get ```500 Internal Server Error``` for my page.. is there a reason its doing this.. any fixes? i did install a while ago the nvidia drivers... i can ssh in my unraid box but i cant get the gui to work.. and i know since i rebooted it a few times thinking it totally froze its running parity check .... what happened? and anyway to get system info logs to see what crashed from the video card... the card works cuz i see see my motherboard bios etc and it worked in my desktop pc update i guess after around 20 min of running like this home assistant stopped working,.. and my windows vms but i can still ssh and do 'ls' and stuff so that part still running and samba shares still work too update... after an hour or 2 i cant remember... ssh logged out.. i got this message and i no longer can ssh into the server ```root@Tardis:/# client_loop: send disconnect: Connection reset``` so i not sure how i can keep the video card in and run unraid

got a 500 Error Server internal error... and the log for the app is ``` text error warn system array login WARNING:werkzeug: * Running on all addresses. WARNING: This is a development server. Do not use it in a production deployment. INFO:werkzeug: * Running on http://172.17.0.7:5000/ (Press CTRL+C to quit) ERROR:app:Exception on / [GET] Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 2070, in wsgi_app response = self.full_dispatch_request() File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1515, in full_dispatch_request rv = self.handle_user_exception(e) File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1513, in full_dispatch_request rv = self.dispatch_request() File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1499, in dispatch_request return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args) File "/app/app.py", line 17, in index monitoredPlaylist = pytubDef.returnMonitoredPlaylist() File "/app/pytubDef/__init__.py", line 429, in returnMonitoredPlaylist logstr = logstr + monitoredPlaylistArray[len(monitoredPlaylistArray) - 1].title File "/usr/local/lib/python3.9/site-packages/pytube/contrib/playlist.py", line 351, in title return self.sidebar_info[0]['playlistSidebarPrimaryInfoRenderer'][ File "/usr/local/lib/python3.9/site-packages/pytube/contrib/playlist.py", line 93, in sidebar_info self._sidebar_info = self.initial_data['sidebar'][ KeyError: 'sidebar' INFO:werkzeug:192.168.0.227 - - [01/Apr/2023 14:46:15] "GET / HTTP/1.1" 500 - * Serving Flask app 'app' (lazy loading) * Environment: production WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. * Debug mode: off ```

@ljm42 i did check today when i tried to follow the instructions and run the script to shrink array article.. everything i have is reference the first 2 drives then let loose on the rest lol so i think im safe there?

@ljm42 ah i didnt see that when i did the new config there was just none all slots and all i chose all as i usually jsut replace a bad drive never downsized lol... learning moment lol excuse to buy another 12 or 14tb to shove in the disk 4 slot lol

@ljm42well i have 27tb free well not 25tb free.. and i wanted to take out the 2TB drive as my others are all 12 and 14tb drives but i may have to add another 12 or 14tb i removed disk4 the 2tb drive well now it goes disk 1 2 3 5 6 7 lol guess i did something wrong i preserved it all as i feared if i do none i loose all my data i usually add a drive or replaced a drive never reduced a drive lol

ok i re paritying least i got the drive removed.. just the save parity never worked..... go figure.. but least its pariting and array back online

@Hoopster ok ill try reading that.. i did these steps but it didnt work at all Shrink array - Unraid | Docs https://wiki.unraid.net/Shrink_array

hi i googled today and did the script for unraid thats supposed to remove a drive from the array but it didnt work.. i moved all the files off.. created the folder clear-me and ran script kept saying there files when there wasnt it stated format the disk while in the array.. but it doesnt tell ya how to format it while online.. then there was the alternative.. you unmount the drive and then run the dd command... but it failed too ```root@Tardis:/# dd bs=1M if=/dev/zero of=/dev/md4 status=progress 2000323346432 bytes (2.0 TB, 1.8 TiB) copied, 14767 s, 135 MB/s dd: error writing '/dev/md4': No space left on device 1907730+0 records in 1907729+0 records out 2000398901248 bytes (2.0 TB, 1.8 TiB) copied, 14767.8 s, 135 MB/s``` i wanna removed my 2TB drive as i wanna use it for cctv.. but i have enough diskspace so i wanna shrink the array by the 2tb... what do i need to do that will work i was hoping unraid. had it built in.. so you stop array.. you choose the drive to remove from the array.. to no device and then restart the array and it rebuilds it without it but it didnt so not sure how i down size

ah ok.. and ya its showing now.. i dunno if something broke in unraid int last couple weeks.. as it was working but when i did a reboot i wasnt able to mount anymore... but ya when i search it shows up the shares.. and i can mount it now.. dunno what happened ... weird

ah ok it jiust can create the share successfully just cant mount it afterwards.. what about hidden shares

i guess its working again... after couple reboots and re creating the user name i had before.. will allow me mount the it.. dunno why it didnt before? so what i did was i erased the user name on my main server .. and re created it... as i guess user name root isnt allowed to be used.. but i did use a user name prior.. but i deleted it rebooted everything re created it and now its all mounting again... on the other unraid servers i didnt delete the remote share links i hit mount and they mount again.. as i was testing on the backupserver... so not sure what when wrong.. but too late to find out diagnostics i guess as i rebooted and re created teh user name

the only other thing i can think of it is recently did the "docker update" addon.. dunno if it has anything to do with it.. other then that everything auto updates each night too.. so i dunno what to check? update.. so i apparently can't mount any smb share so i create a remote share i do a search it finds my servers.. so i can do hostname or ip address i type in root for user and password i click next on the domain i click search for shares.. but it never finds any.. so i manually type it in.. then click submit then i get success... then i try to mount the share and it wont if i create a user name and use it to create a link to a rootshare i can see the share names and when i click submit.. it says sucessful.. but i still cant mount it ill try deleting all remote shares on backupserver and main server.. reboot everything and then re try the user name i used.. since i could see the shares but it wouldnt mount.. maybe a another clean reboot will help

@dlandon yes correct ip so if i do the ip or host name i enter the user name and password and then the share "root" i click submit.. it then says successfully created.. and then when i go to mount it it throws me the error.. it was working a week or 2 ago and if i do a Windows mapped network drive to the same directory that works fine so like z: = \\192.168.0.3\root that has no problem mounting z: the problem is unraid to unraid i was thinking it might be one of the last ud updates in the last couple weeks that maybe stopping it to mount.. i only found out when i rebooted the unraid servers.. that it wasnt auto mounting anymore

@itimpi it used to work i only noticed last couple days.. as i could no longer access it from any of the servers... as i use my other unraid servers as backup and tdarr nodes and it wasnt able to do it anymore main server is set for smb security public auto case sensitive and yes to force a nobody as i used to use rootshare as my rootshare.. in the one section but with the one of recent space invaders videos he no longer does the hard code the rootshare and does the UD rootshare.. but i could not use the name rootshare in UD guess its protected. so went the root name but now its not mounting and i get that error

hi im unable to mount remote s hares i have on my main server... a rootshare called "root" and its mounted but when any of my servers try to mount to it i get this error Mar 9 10:08:20 backupserver kernel: CIFS: VFS: \\192.168.0.3 failed to connect to IPC (rc=-13) Mar 9 10:08:20 backupserver kernel: CIFS: VFS: cifs_mount failed w/return code = -13 i have tried removing all shares and re adding doesnt help here is a diagnostic from my backup server i wanting to connect to the main server backupserver-diagnostics-20230309-1010.zip