marcoNLD
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by marcoNLD
-
-
exactly the answer i was looking for. thx for leaving this post here and answering it yourself
-
CrushFTP is running
You should be able to access it on port 8080 or 9090 (unless you changed it)
CrushFTP admin username is 'crushadmin'the PW is the one you entered at install. if you havent changed it.
check yours at your docker
docker/edit -> scroll down and expand view
the PW is shown there
dont forget to use the port mapping yourlocalip:port
-
your CPU and MOBO should be fine for the task
PCIe 3.0 and 40 pcie lanes.
check your manual to see where card placements are supported.
sometimes they use different slot configurations that might not make any sense.
i have a 1060 running in my x99 based server. no issues.
alsoo have a 760 in there for plex transcoding.
i am no expert by all means but maybe check out spaceinvader one youtube channel.
watching his videos got me where i am today.
-
i might do that
(if i knew how) and the watercooling bit.
the H1xxi series watercooling have usb connectivity aswell.
read out temps and speeds. maybe even control fans.
sounds a bit over the top but i have the H110i GT AIO watercooler in my server
anyways. great plugin
-
works like a charm with my RM850i. awesome plugin.
would be great if you got it into the CA too. then fix common problems plugin wont show the error anymore. (silenced it)
maybe as a followup. make it compatible with the watercooling AIO's??
defo a must have plugin for corsair PSU users.
great work
-
update on the crash issue
after installing new memory and staying on version 6.3.1 my system runs like a well oiled machine
very responcive and fast.
no issues whatsoever.
i think in my case it was memory related.
next step is upgrading hardware
just bought a dell H310 controller with cables and a new WD red 4TB to replace my parity drive
if that upgrade is running fine i will upgrade the OS to the latest version.
again, so far the systems runs fine again
-
i downgraded to unraid 6.3.1. and then i couldn't even boot.
turned out i had faulty memory.
now with the memory stick removed im running ok
so far the system is responsive and i have been running it for 1 day now.
not sure is the hard crashes are memory related.
i will post my diagnostics here too. maybe someone can find something that is useful
-
i have these hard crashes too. A week ago i came home to find my server unresponsive. after reboot my system wouldn't boot up in unraid.
i inserted my USB boot drive into a windows machine and got the 'you need to check this volume' so i did
after this i made the drive bootable again and iserted it in my server
server booted up and i got into the WEBGUI. started the array and started the parity check
all well and all until 2 days later. same happend out of the blue. no warning no nothing. just a hard lockup
after going through the same procedure as before i got into the system yet again. making this photo.
Now again my system is unresponcive and wont even boot.
maybe it has something to do with my hardware. will have to wait till next week.
-
sorry confusing treat
my bad
-
thank you @John_M for your response.
but what i get from your answer is that there's nothing major going on with my system.
The bios is the latest version. bios 1604.
yeah i know, an old board but its what i had available.
thanks again.
it's people like you that keep these projects fun.
-
thx @trurl for creating this, newbie as you noticed
will search aswell but i already looked for this solution.
hence the fact i posted the diag.log.
maybe someone can put me in the right direction.
and BTW, i am a newbie with little to none linux experience.
i can build and maintain a windows PC. already proud i made this server
-
i have the same error and no idea where or how to correct it.
my system runs fine
so if anyone will check i would be very happy.
(if i knew how) and the watercooling bit.
[Support] binhex - Radarr
in Docker Containers
Posted
same here
[v4.0.4.5922] NzbDrone.Common.Exceptions.RadarrStartupException: Radarr failed to start: Error creating main database
2022-02-01 12:37:37,309 DEBG 'radarr' stdout output:
Press enter to exit...
2022-02-01 12:37:38,309 DEBG 'radarr' stdout output:
Non-recoverable failure, waiting for user intervention...