duelistjp

figured it out I had installed mover tuner then removed it when I realized it wasn't what I wanted I uninstalled it. had to reinstall it tell it to disable running mover on a schedule then uninstall it and now there is no /mnt/none folder being created. I don't use a cache so no need for it.

was able to login normally then yesterday was having problems with logging in to unRAID. locally I can sometimes get to the page sometimes get http 500 error. but when I get to the page when I try to login nothing happens. if I enter a wrong password it says invalid but nothing happens if I hit the right one. I figured it was just a little weird so I rebooted using the terminal and things worked again but today the same thing is happening. Dockers are still going fine and all that. I just can't login on the server main page. only odd thing that happened lately was I accidentally filled the first drive in the array to the brink but have since fixed that and my client now preallocates the file space so it shouldn't happen again. any ideas what is wrong and how to fix it? edit my roots was completely filled with tons of stuff in /mnt/none/ any idea why stuff would be put in there? once I emptied out a bit of space in there I could restart nginx and login. its copying files I think should be on the original array to this for some reason and I don't know why I can see it increasing in size the longer it runs solved it is the mover putting files in /mnt/none. why would mover be doing that? I did install mover tuning a few days ago so I figure I screwed something up there

i'm having trouble every week or two where i start getting a ton of stuff in the queue showing red saying release wasn't grabbed by radarr, skipping. any ideas why? only thing i've found that seems to help is removing from queue and blacklisting the release. it is annoying as i also have to handle the already downloaded files and if i don't catch it immediately the downloads ssd gets completely filled.

i'm having trouble every week or two where i start getting a ton of stuff in the queue showing red saying release wasn't grabbed by sonarr, skipping. any ideas why? only thing i've found that seems to help is removing from queue and blacklisting the release. it is annoying as i also have to handle the already downloaded files and if i don't catch it immediately the downloads ssd gets completely filled.

i'm trying to set this up. i can access it via novnc webpage. i go to steamlink on an client. i can see the computer. the network test runs fine. it shows the computer and my controller etc. when i click start streaming it goes to a blue screen showing connecting to steamheadless that never seems to complete. on some clients it seems to go indefinitelt and on some it seems to complete and goes to a black screen with spinning wheel for a bit before it seems to crash and restart the app. also what needs to be done to give it access to my intel igpu if anything

having trouble with this. i installed the docker and it hangs and eventually times out on the scan controllers page. here is the part of the error message that looked relevant without the entire stacktrace. Lucee 5.3.10.120 Error (application) Messagetimeout [90000 ms] expired while executing [/sbin/parted -m /dev/sds unit B print free] StacktraceThe Error Occurred in /var/www/ScanControllers.cfm: line 1964 1962: <CFFILE action="write" file="#PersistDir#/#exe()#_parted_#DriveID#_exec.txt" output="/sbin/parted -m /dev/#DriveID# unit B print free" addnewline="NO" mode="666"> 1963: <CFIF URL.Debug NEQ "FOOBAR"><cfmodule template="cf_flushfs.cfm"></CFIF> 1964: <cfexecute name="/sbin/parted" arguments="-m /dev/#DriveID# unit B print free" variable="PartInfo" timeout="90" /> 1965: <CFFILE action="write" file="#PersistDir#/#exe()#_parted_#DriveID#.txt" output="#PartInfo#" addnewline="NO" mode="666"> 1966: <CFSET TotalPartitions=0> called from /var/www/ScanControllers.cfm: line 1853 1851: </CFIF> 1852: </CFLOOP> 1853: </CFLOOP> 1854: 1855: <!--- Admin drive creation --->

i am trying to instal iotop and when i click apply it opens up a white window labeled package manager but nothing shows up

the backblaze personal backup container directs here if you click support. i try to start it but the webui does not respond. the log says [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... any idea what is wrong

alright. i had moved a few drives internal to set things up before converting the old server into a jbod to minimize downtime. moved it back to the sas backplane tonight hopefully that error will stop

here is the diagnostics rosewill-diagnostics-20230314-1018.zip

Mar 13 22:56:40 Rosewill kernel: ata5: COMRESET failed (errno=-16) Mar 13 22:56:41 Rosewill kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 13 22:56:42 Rosewill kernel: ata5.00: configured for UDMA/33 Mar 13 22:56:50 Rosewill kernel: ata5: link is slow to respond, please be patient (ready=0) this keeps showing up in my log. can anyone help me know what it means and if there is any action i need to be taking in response to it.

i've decided to put up with some inconveniences and not do it but have strongly considered virtualizing unraid in the past because vms and containers have to stop when the array is down but a good number of them i don't really need the full array. strongly considered virtualization to handle my main storage array i don't want to mess with zfs on but then have other things doing the vms and containers i don't need to have go down every time i need to restart the array

those drives finished fine and with a 3rd small one i cleared as well for this. ran this a second time in a jbod i attached to the server rather than internal to the mobo on a sata port. it failed within an hour of starting the post read. am starting the rma process. but have also started running memtest from passmark about 4 hours in now and will let it run till after work tomorrow but my gut says the ram is fine

makes sense. certainly wasn't intentional but glad the terminal still works for mounting these as network is slow for transferring 40TB of data

well i figured out how to mount it using fstab and am currently transferring data off them. don't know how i did that. is there a reason UD doesn't support mounting things that way though. is it just uncommon enough to not be worth doing or is there a reason mounting such drives is bad