kpc180

Members
  • Posts

    39
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kpc180's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I am having a similar issue, but setting the share to public didn't do anything (it has always been public). Any podcast I download using ABS makes it so I don't have permission to edit, delete, or move it when I navigate to it using file explorer or even Krusader. If I run the Docker Safe New Perms it fixes it. But am I doing something wrong from the get go with my config settings or something? I don't have this issue with any of the arr or other dl dockers I use. (also my knowledge of permission and stuff is pretty dang shallow)
  2. Well that's simultaneously embarrassing and evidence of my simpleton claim. THANKS!
  3. Hello, I used to be able to access my unraid gui and dockers while at home the same way I access them on 2 pcs on the same network using this IP (http://192.168.1.18/Main). I can still do it on the computers no problem, but my phone tells me it's unreachable. I am not sure what changed but it has been a while now. I'm also a simpleton so if you could dumb down any help that would be great! Thanks!
  4. Hey guys, I had a a disk go into error state (disk 6 not the parity drive) during a parity check and am wondering what the next steps I should take are. I'm afraid you'll need to explain it to me like I'm 5! I have attached diagnostics. The system is still running - parity check paused itself. Do I turn off all VMs and Dockers right away? Should I replace the drive? Thanks for any help you can offer me! unkevin-diagnostics-20230101-0721.zip
  5. Unfortunately I can't get the system to boot. The fans spin, the drives make some small noises like they are on. I replaced the PSU and the RAM and no luck. Pretty sure it must be the mobo or cpu. The mobo though is not displaying any error qleds nor is it making any beeps.
  6. Hey my Unraid server has been running great for months, but I believe I have run into hardware issues (which I know isn't an Unraid issue) and was hoping someone here may have some guidance based on their knowledge and experience. This month it randomly started having unclean reboots while I wasn't around. I thought I tracked down the cause to a specific docker, and uninstalled it. It worked well for quite a while and then it started happening again. Then while I was at my desk recently it happened again and I heard it just kind of die and start back up. Then it happened again and now it won't come back online. It sounds normal when it starts (normal fans, and normal clicks, no warning beeps), but when I plug in the hdmi monitor nothing shows up - no mobo splash - nothing. The mobo doesn't show any Qled errors. I figured it was a bad PSU so I bought and replaced the unit and power cables. No luck. I have removed it from the battery backup - and tried different plugs in the house with the same result. I suppose now I'm down to the motherboard needing replaced or possibly the ram? I run 2 16 ddr4. I've tried starting up with just each one individually - and then also reseated. Same thing - no splash no nothing. Any advice one way or the other? Is it likely time to replace a mobo? (ASUS ROG Strix Z490-H Gaming Z490 LGA 1200)
  7. Hey, I've set up a windows 10 vm - and I use Teamviewer to access it remotely from a multi-monitor set up. I suppose I don't understand VMs well enough to know if I can get a multi-monitor situation on it. In the past I've used a a few headless adapters on the host computer's video out ports and Windows/teamviewer picked that up as monitors and I was good. Can I do the same thing with the ports coming off the unraid motherboard and it affect the vm at all? I'm doubting it. Clearly I'm a beginner! Any help would be appreciated! (And I do want to stick with Teamviewer)
  8. Sorry - it was what looks like 2 "warning" level events: Nov 5 14:23:43 unKevin nginx: 2020/11/05 14:23:43 [error] 8706#8706: *1457547 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.171, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.18", referrer: "http://192.168.1.18/Main" Nov 5 14:23:43 unKevin php-fpm[8680]: [WARNING] [pool www] child 13228 exited on signal 7 (SIGBUS) after 82.110109 seconds from start
  9. Ok - thanks for the help guys - the 3rd parity check just finished with 0 errors. So I'm thinking I'm in the clear? However, I checked the logs periodically and there was 1 warning or error on there I didn't understand - though I don't think it had anything to do with the parity check. unkevin-diagnostics-20201107-0803.zip
  10. Will do! Also - During parity checks - is it unwise to have active downloads and run dockers like Sonarr and Radarr?
  11. Ok I replaced the cable and ran the parity again. It showed 1 error very early on in the scan but then no more errors the rest of the scan. Not sure what the means, nor what I should do now - if anything? Thanks for your help! unkevin-diagnostics-20201105-0923.zip
  12. Thanks - I have replaced the sata cable for disk 1. I checked the logs and no errors are showing up. So now you advise running another parity scan correct? The parity is 14tb so it will take a couple days. Anything I should be looking for in the meantime? Or avoid doing?
  13. Hey, my monthly parity completed today and it reported errors for the first time - 39 errors. I do not recall any unclean shut downs (I did do a clean power down during Zeta). I also forgot the system was running the check and was moving, renaming, deleting files quite a bit during it - which may have added to it? Regardless, I'm pretty hopeless when it comes to reading the reports and logs so I'm hoping one of you may be able to tell me if all is well or if I have a fire on my hands! unkevin-diagnostics-20201103-0956.zip
  14. Thanks, that makes me feel a bit better. But so I'm clear there isn't an option or something obvious I'm missing which would check to see if a disc went offline and then emergency stop unraid so that nothing tries to read/write to it and puts it in Error mode - and prevent a need for a rebuild?