brent3000

I dont know what country your in but check if the Drive can be RMA'ed if its a new one, else if its not showing in the BIOS its possibly dead, Based on the brands as well Seagate did have a FW issue some time ago and one of my drives dropped off from the system and i did a FW update to it and it was back good as new, maybe check on the drive if any FW else RMA time hahah

Handy thing to test, create a share for each drive and just send data to that drive, process of elimination. If your using a drive which has the Cache mode enabled it should only ever be hitting the one drive before the mover kicks in, If the drive isnt showing up in the BIOS thats clearly a red flag there, have you done a preclear on any of the drives at all or just a straight load? I always do a drive write+read on it first to make sure the whole drive is ok (if the drives are new or within warranty its an easy way to rule out faults) Other thing could possibly be the SATA cable, make sure its a SATA6G cable when you connect it to the system, also is the BIOS running in RAID at all? (dont think it would matter but I always turn it off if its not needed) edit: just checked you don't have a cache drive, so its going direct to the parity drive and the drive its writing data to, so always two drives being hit

Looks like something is playing up with the SATA controller/drives/cables is this all new hardware? (mobo and cables) I had a similar issue and ended up being a few things compounded causing the issue for me Jan 3 11:03:44 Server kernel: ata6: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata4: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata5: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata4: COMRESET failed (errno=-16) Jan 3 11:03:44 Server kernel: ata6: COMRESET failed (errno=-16) Jan 3 11:03:44 Server kernel: ata5: COMRESET failed (errno=-16) Jan 3 11:03:44 Server kernel: ata6: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata5: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata4: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata6: COMRESET failed (errno=-16) Jan 3 11:03:44 Server kernel: ata5: COMRESET failed (errno=-16) Jan 3 11:03:44 Server kernel: ata4: COMRESET failed (errno=-16) Jan 3 11:03:44 Server kernel: ata6: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata4: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata5: link is slow to respond, please be patient (ready=0) Jan 3 11:03:44 Server kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 3 11:03:44 Server kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 3 11:03:44 Server kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514) Jan 3 11:03:44 Server kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 3 11:03:44 Server kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514) Jan 3 11:03:44 Server kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Also not sure if for any reason but you 'should' try and use your SATA6G ports (would prob be good to have the parity drive at least on it) as it looks like all your drives are running on the Sata3G ports (based on P8H77-V the white ports should be the sata6 ones) Unless unraid slows them all down to the slowest drive speed maybe.

Are you using swag or letsencrypt? I did some tests with my one and worked fine, ONe of the fixes listed on the links you posted suggests there was an issue with the ports not being passed across. I assume via the web etc its all fine when going directly to the website and downloading the I know it was covered in SI's video but i assume you dont haver a port clash and also the config file has loaded correctly into swag?

Would I be correct in saying that when running the older version the 'auto' part of this stops working?

It should look like the attached But for some reason there is no country flag showing on the peers page. This is taken from my other rutorrent install which was done on a standalone box. EDIT - did a quick google and it seems this may be an issue, not sure if anyone is abit to test it with more docker skills than me https://github.com/linuxserver/docker-rutorrent/issues/103

Did your fix happen to also fix the flags not showing in the peers page?

So I'm still getting used to the whole docker thing and getting the hang of it 'ok' so far, but i have a question, Recently I have received two docker updates for rutorrent and i for the life of me cant find any details on the logs or changes which triggered the update? Now i thought it would be listed or added to this page https://hub.docker.com/r/linuxserver/rutorrent/ but looking at the 'Versions' section its showing nothing recently being done? Am i missing something or are not all docker updates published?

This is how rutorrent is build the GUI is simply a current session settings, See https://github.com/linuxserver/docker-rutorrent/issues/170#issuecomment-660497151 If you dont wanna go edit settings you may want to look at another app like deluge or something similar, but changing the data with any good text editor should be your best bet for it

Yes but as above it didnt work and I think it was just the assumption that if the port mapping changed it would change on the screen, it seems thats not the case due to the Host and Container references being different in how they appear on the docker page. I did get this working now to how I would need it and deff need some more playing to get my head around it as it seems docker needs alot more changes than I thought than simply enter a field when its out of the norm slowly but surely haha updated the link and seems my other apps now work and use the ports without any issues

How would I do that? I tried adding the port like cam above showed in his screenshot but its still showing '80' as the port in the allocations? Or is this set somewhere else?

Hi, Looking at https://filebrowser.org/cli/filebrowser it seems the command is filebrowser -p to set the port, how do we get this to apply on the boot or in the settings? Looking in the database it seems the port is set to 80 but I cant see how to run the -p command to set the port? Edit - Seems changing the post argument seems to be the way to apply a custom port, following the above (under advance) you can apply a -p xxxx for the port number. I had to do some playing with the system reloading a few times but my one is now working on NOT port 80. Not sure if that can be set as a normal port variable using the above one cam showed as an example? Edit 2 - So made the changed, the application will work and load on the custom port but the docker is still hooked on port 80 in the allocations, not sure how we change that setting at all or where that is set?