ontarian_frog

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by ontarian_frog

  1. Unfortunately, I'm not savy enough to venture into the realm of replacing the kernel myself, therefore will wait it out for now. I don't need gpu transcoding that bad, since my cpu (R9 3900) can handle it. We can always use a VM meanwhile. This is what I figure needs to happen: 1. Slackware needs to update to kernel 6.3 (6.2 is EOL) 2. zfs 2.x isn't compatible with kernel 6.3 at the moment. This could take a while. 3. Other issues I'm not aware of. 4.... Profit? I can't remember where I read it but it was said that arc support would come in an unRAID 6.13 release, therefore it might be a little while before we see that.
  2. Ok, I rechecked all cables and parity rebuild started. No errors so far at 1%. It had failed at .5% earlier. Keeping my fingers crossed. This is going to take about 20hours
  3. Hi, I royally screwed up this morning. I woke up with disk 1 in error state, I suspected a power cable. Got the hard drive back up, but rebuilt the parity instead of the drive. I had a sudden realization after I started the rebuilt. So good thing I have a back up. How would I go about checking the reliability of the drive before I wipe it and restore the files? tower-diagnostics-20221227-0846.zip
  4. Thanks for the advice. That's what I'll do, I'll take the 3tb drives out. They have low hours on them and if I need them and I'll put one or two in until I can get more 14tb drives. I'll try to sell the rest for peanuts.
  5. Hi folks, I have 3 Exos X14 hard drives coming. Currently, I have 6x SAS 3TB drives (1 of those is parity). Should just use the X14 drives exclusively or keep the 3TB ones running also? Pros vs Cons?
  6. All I had to do to use my nvidia card was add --gpus all in the extra parameters. The other variables are handled by the docker image. You don't need them anymore. To test if it works, open the unraid terminal and run this command: docker exec -it jellyfin nvidia-smi
  7. Edit: well the reset worked. Hard to believe, since I had done a proper reboot earlier! I forgot to mention, I did reboot before posting. I just tried to access the nvidia plugin and the gui became unresponsive. I don't know what would be using all the memory, dashboard with Docker off sits at 38% ram used. Because the gui was unresponsive and I couldn't get a shell, I did a reset. It triggered a parity check of course. The system came back on good, I can access the shell now. Checked the log since reboot, all good, no memory errors or nvidia errors. I'll wait until the parity check is over and then I'll open a shell just in case and try to turn Docker on. Hopefully everything is good now.
  8. Hi folks, I'm usually good at fixing things myself, but I'm in over my head at this moment. I tried to look log into qbittorrent and it failed. I logged into the Unraid gui and the docker page didn't come up, it was just showing the loading animation. I tried to disable Docker to delete the docker.img file and start rebuilding, but all I see are these lines (image.png) I tried to login using ssh and manually delete the file but the terminal doesn't let me use the keyboard after the password prompt. Then I tried to download diagnostics and it just hangs and won't download. I was however able to download the syslog from the gui. Do I need to nuke the whole thing at this point or are there things to try before I go nuclear on my install? Please advise. tower-syslog-20221031-1310.zip