pmpj218

Members
  • Posts

    45
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    San Francisco, CA

Recent Profile Visitors

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

pmpj218's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. I hope it's not totally unhelpful, but I've attached diagnostics of my server after I booted up just now. I upgraded to 6.4.0 a couple of weeks ago, and it seemed pretty uneventful. I noticed a couple of days ago that my server was off, so I turned it on to see that had an unclean shutdown. I started the array to trigger a parity check, and I let it run overnight. I just got home from work, and wanted to check to see if it went well, and noticed my server was off again. I turned it on again and downloaded the diagnostics to post here. Not sure why this is happening. Haven't started the array at the moment. Any help would be appreciated. Joe unraid-diagnostics-20180201-2109.zip
  2. Nevermind. I noticed the new template had some fields that I didn't have before. So, I tried installing from scratch and it works. The web ui is quite different, so I must've not updated in awhile.
  3. I've been running this fine for awhile until I updated the sabnzbd docker today. Wasn't sure what to post to help troubleshoot, but this was in the latter part of the log file. Please let me know what I can do to help get this back up and running. Thanks! 2017-10-22 16:44:51,317 DEBG 'sabnzbd' stderr output:2017-10-22 16:44:51,316::INFO::[SABnzbd:1380] Starting web-interface on 0.0.0.0:80902017-10-22 16:44:51,318 DEBG 'sabnzbd' stderr output:2017-10-22 16:44:51,317::INFO::[_cplogging:219] [22/Oct/2017:16:44:51] ENGINE Bus STARTING2017-10-22 16:44:51,619 DEBG 'sabnzbd' stderr output:2017-10-22 16:44:51,616::ERROR::[_cplogging:219] [22/Oct/2017:16:44:51] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x2b0e75b016d0>>Traceback (most recent call last):File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 207, in publishoutput.append(listener(*args, **kwargs))File "/opt/sabnzbd/cherrypy/_cpserver.py", line 167, in startself.httpserver, self.bind_addr = self.httpserver_from_self()File "/opt/sabnzbd/cherrypy/_cpserver.py", line 158, in httpserver_from_selfhttpserver = _cpwsgi_server.CPWSGIServer(self)File "/opt/sabnzbd/cherrypy/_cpwsgi_server.py", line 64, in __init__self.server_adapter.ssl_certificate_chain)File "/opt/sabnzbd/cherrypy/wsgiserver/ssl_builtin.py", line 56, in __init__self.context.load_cert_chain(certificate, private_key)SSLError: [SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2699)2017-10-22 16:44:51,823 DEBG 'sabnzbd' stderr output:2017-10-22 16:44:51,822::INFO::[_cplogging:219] [22/Oct/2017:16:44:51] ENGINE Serving on http://0.0.0.0:80802017-10-22 16:44:51,823::ERROR::[_cplogging:219] [22/Oct/2017:16:44:51] ENGINE Shutting down due to error in start listener:Traceback (most recent call last):File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 245, in startself.publish('start')File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 225, in publishraise excChannelFailures: SSLError(336245134, u'[SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2699)')2017-10-22 16:44:51,825 DEBG 'sabnzbd' stderr output:2017-10-22 16:44:51,823::INFO::[_cplogging:219] [22/Oct/2017:16:44:51] ENGINE Bus STOPPING
  4. The rebuild finished with no errors. Thanks for taking the time to look at my issue.
  5. Changed out the cable. Attaching new diagnostics. unraid-diagnostics-20170411-2157.zip
  6. Thanks. Just to make sure, after I replace the SATA cable, how do I run a SMART report before rebuilding the disk? Do I do it before or after I start the array?
  7. I just got an alert that one of my data disks has a read error. I did just replace my cache drive because that drive was dying as well, so I'm wondering if I should just reseat the drive in to the drive cage and/or reseat the power/sata cables first. Or should I do something different? Attaching diagnostics file as well. Thanks. unraid-diagnostics-20170410-2126.zip
  8. Nevermind, I can't read. I enabled the alerts.
  9. Is there a reason I can't check the email boxes next to Notices, Warnings, and Alerts? I would think I want those via email, but the check boxes are disabled.
  10. I also never looked at the dashboard because I always just assumed that a green dot on the main screen meant it was okay. On the dashboard, the cache drive has a yellow triangle warning icon there. Just checked my alert settings and they weren't working... probably since I turned on 2-step verification on my Google account. It's working now, but which alerts should I be making sure I get?
  11. Thanks for looking at this. I ran preclear on all these disks, 3 passes, but it was probably over two years ago. I would have used this 2TB disk as a replacement if one of my array disks failed. I'm kind of glad this happened. Would it make sense to get an SSD for cache? I'll shop around for some backup drives for my array, too.
  12. Since I was messing with my box already yesterday, I tried adding a second parity drive. After the parity built, I couldn't start docker again. I tried deleting the docker image and starting over, but no luck there. Any help is appreciated. Attached diagnostics again. Thanks! unraid-diagnostics-20170406-1634.zip
  13. I swapped out my cache drive with something I had, and re-added the docker containers and that seemed to work fine. It still looked like I got some errors on that drive though. I'll buy a new cache drive soon and replace it. Thanks for your help!
  14. Okay, sorry didn't know about the diagnostics. I've attached the them. And I upgraded from 6.3.2. And I only just started noticing that one of my docker apps wasn't working (Sonarr) last week. I just figured I'd try to update to see if it would fix it. unraid-diagnostics-20170405-1319.zip
  15. I was having issues with Docker, so I decided to update to 6.3.3. Upgrade seemed to work fine. But now I can't start Docker. I've attached my syslog, which has a bunch of errors, but I'm not sure what they mean. Thanks for your help. unraid-syslog-20170405-1304.zip