• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About s449

  • Rank
  1. Thank you for the response! I enabled mirror to flash. So I assume once this happens again, I can grab the log file from the flash and post it here.
  2. The configuration is the one I posted above: Is there anything I should change? Thanks!
  3. Hello! Looks like it happened again. A lot sooner than usual. Attached are the logs with syslog server enabled. Thanks!! apollo-diagnostics-20210515-2151.zip
  4. Sounds good! I enabled syslog: I'll post again next time it happens. Thanks for the help!
  5. This started happening maybe 3 months ago. Possibly since the 6.9 upgrade. I'll notice Plex is offline. Then I try to log into my server's UI and any docker containers inside and outside the network and none of them load. If I try to SSH into my server it says the host is down. No errors or warnings on my push notification app. My server is never doing any tasks or anything to cause it, it seems to be just idling. The only fix I've found is I log into the IPMI interface and reboot my server. Everything is always fine when I reboot but because it's an unclean shutdown it starts a parity ch
  6. I assume this is a complete non-issue but figured I'd ask anyway. My old Kingston 16GB USB 3.0 drive kicked the bucket. I went out and bought the only USB 2.0 drive I could find, a SanDisk Cruzer 32GB USB 2.0. I installed Unraid from a 2 week old backup .zip using the USB creator and moved over the registration. The only odd thing is Unraid acknowledges 30.8GB of space, but the file size is 15.4GB. Is this a boot drive or vfat file system limitation? If it helps, it's plugged directly into the motherboard USB 2.0 slot. Thanks!
  7. Only one of my remote users is having issues the past week or two where on different TVs (Roku TV), iOS, and a Macbook some episodes won't play or will get stuck at the 33% mark. They tried it on two networks in different houses. We also tried on a new Plex account and same issues. It's really a long shot because this is so oddly specific and I'm not even sure what kind of debugging I can do, but does anyone have any ideas if this sounds remotely familiar to other common issues? Once again none of my other users using varying devices, some of them using the same platforms, are having issues. M
  8. I ended up making this folder: appdata\binhex-rtorrentvpn\rutorrent\user-plugins\tracklabels\labels which didn't exist before. And did what I outlined before and after restarting ruTorrent it works! I made a backup in case a docker update breaks it, as you mentioned. If so then I can copy that script. Thanks for the help!
  9. This isn't an important issue but I was curious if there was a way to upload icons for more specific labels? I just prefer using, for example, the word "movies" which doesn't trigger an icon over "movie" (which does). I also have other words I'd like icons on. In other seedbox installs of ruTorrent I managed to find the folder that contained these icon files and it was as simple as copy/pasting the movie.png file and renaming it to movies.png. I couldn't find that folder in this docker, though. Best I could find is this folder that does contain all those icons: https://github.com/Novik/ruTorre
  10. Ah okay. So basically the connection just got loose? I think it was the tape mod then. Snipping the 3.3v wire should be better. Thanks! I’ll let it rebuild.
  11. So in the past few days I successfully removed disk 1 from the array. Rebuilt parity using New Config with no errors. Ran another parity check and still no errors. All my disks reported no short SMART errors, no filesystem errors, I checked a number of times. I also installed my new power supply and I'm not using any adapters, all drives plugged straight into the PSU. I was covering the 3.3v pins using Kapton tape and the drives were being recognized. Everything looked fine and felt like it was running as good as ever while I was spending all day downloading a lot of data that I lost.
  12. So my hard drives (including disk2) were plugged into a Molex to Sata power cable. I took that cable out and have them plugged into a Sata extension power cable. After doing so I ran another parity check and it just finished with no sync errors and no read errors on any of my drives. Sounds like you could be right and disk2 was a power issue. It could even be that disk1 from my past threads was also a power issue. Regardless, my higher quality replacement PSU should arrive tomorrow with it's 10x Sata power slots and I'll be omitting all extension cables to my rig; all
  13. Thanks for the reassurance that it could be PSU! I double checked with a PSU calculator and it recommends 379W. If I max out my drives it would be 401W. But for all I know this 400W PSU isn't delivering 400W. I'd still want to aim for 500W+ to be safe. Right now with my re-cabling and removing Molex to Sata, things seem pretty stable but I'll wait until the parity check finishes in 18 hours to confirm no read errors on disk 2. I ended up un-shucking and returning the replacement drive to Best Buy since all said and done I really wouldn't need the extra space post-RMA. I
  14. I was thinking of replacing the power supply one day anyway for a more efficient and better one than my EVGA N1 400W. I can do a whole power supply and cable overhaul if it really seems to be the real root of all these issues. SATA cables are pretty cheap although would you think it's more of a power cable issue than a data cable issue? My only concern is what would the best way be to connect these drives and avoid the 3.3v pin issue? Right now I have my two SSD's connected direct to SATA power, then my parity disk and disks 1-3 on a Molex to 4x SATA power cable. Then my disk 4 (an