Hey everyone, new user here so bear with me.
I started the unRAID v6 trial and I recently installed the preclear plugin so I assume I have the latest version - I can check for the specific version when I get home. I have two new 8TB WD Reds in my server and I am trying to run preclear on both of them (at the same time) but I am running into a problem. Before I go into detail, the problem I am having is that at some point during preclear my server disappears from the network (at least I think it does). I can log into the server directly (not ssh or telnet, but by hooking up a monitor & keyboard) but can't run any commands.
Here is a list of events:
Start running preclear on both drives. Everything is fine, I can see the pre-read % going up.
Telnet into the server and run "tail -f" on the syslog, because this is the second time I am trying to preclear after a failed attempt.
Go to bed when pre-read % is at around 25%.
Wake up, preclear status page says pre-read is at ~6 hours and ~35%. By this point it has been ~12 hours since I started the preclear. The server is no longer on the network, so this information is old. I came to the conclusion that the server is no longer on the network because I can't access any web gui pages, and when restarting my router I do not see the server try to grab an IP address. Before restarting the router the server was still in my DHCP table.
My telnet session that is running "tail -f" on the syslog stopped updating shortly after I went to bed. Before I went to bed, It was regularly updating. I couldn't see any abnormal output - it looked the same as it had been before I went to bed. I assume it stopped because it couldn't access the server on the network? Would a telnet session automatically close if the server stopped being accessible on the network?
Try to log into the server directly. Once logged in I can't seem to run any command. I can type things in the terminal, but hitting enter just takes me to a new line. Trying to ctrl-c or ctrl-z does not do anything except produce "^C" and "^Z" in the terminal that can't be erased.
I am currently at work so I can give more specifics on what the terminal and "tail -f" command output looks like when I get home. I know this might not be a preclear issue, but I figured that I would at least post to see if anyone here knows what is going on. Relevant system specs is CPU:Ryzen 5 1600, RAM: 16GB 2400MHz DDR4.
My next step will be to try preclearing one drive at a time because I read a few pages back that someone was having trouble trying to preclear more than one drive at a time. I will also try to monitor more log files (in addition to syslog).