-
pmpj218 changed their profile photo
-
[Plugin] CA Fix Common Problems
Can anyone help take a look at what might be a fix for this error I'm getting? Thanks. /boot/config/unraid_notify.cfg corrupted Your flash drive has possible corruption on /boot/config/unraid_notify.cfg.
-
[Support] binhex - SABnzbd
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.
-
[Support] binhex - SABnzbd
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
-
pmpj218 started following Syslog repeated error - RC4 , Disk Read Error , Can't start Docker and 7 others
-
Can't start Docker
Nevermind, I can't read. I enabled the alerts.
-
Can't start Docker
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.
-
Can't start Docker
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?
-
Can't start Docker
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.
-
Can't start Docker
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
-
Can't start Docker
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!
-
Can't start Docker
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
-
Can't start Docker
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
-
Power Supply Deals
CORSAIR Builder Series CX430 430W ATX12V v2.3 80 PLUS BRONZE Certified Active PFC Power Supply - $16.99 after rebate. Free shipping.
-
Preclear.sh results - Questions about your results? Post them here.
Okay. I will run one again on /dev/sdh and see what happens. Are the other two—/dev/sdf and /dev/sdi—good to go? How about /dev/sdg? Is there something I need to do to remedy this: "Postread detected un-expected non-zero bytes on disk". Is that even why it didn't pre-clear? Thanks again.
-
Preclear.sh results - Questions about your results? Post them here.
Hi. I'm new to this, so please let me know if there's any more info I need to provide... I just ran the script on four drives that I've previously used in another Windows system. Three were successful, and one wasn't. Can someone check to see if the three that passed are okay for me to add to my array? And what can I do about the one that didn't pass? Any advice/insight would be greatly appreciated. Thanks! Here are the reports that were generated for the drives that passed: ========================================================================1.11 == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdf == WDC WD10EADS-00M2B0 WD-WMAV50178120 == Disk /dev/sdf has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 4:00:27 (69 MB/s) == Last Cycle's Zeroing time : 3:33:16 (78 MB/s) == Last Cycle's Post Read Time : 8:22:23 (33 MB/s) == Last Cycle's Total Time : 15:57:11 == == Total Elapsed Time 15:57:11 == == Disk Start Temperature: 27C == == Current Disk Temperature: 26C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 120 0 ok 26 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ========================================================================1.11 == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdh == WDC WD20EADS-00S2B0 WD-WCAVY1278318 == Disk /dev/sdh has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 10:22:55 (53 MB/s) == Last Cycle's Zeroing time : 6:30:27 (85 MB/s) == Last Cycle's Post Read Time : 17:22:20 (31 MB/s) == Last Cycle's Total Time : 34:16:47 == == Total Elapsed Time 34:16:47 == == Disk Start Temperature: 29C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Load_Cycle_Count = 164 165 0 ok 108209 Temperature_Celsius = 125 123 0 ok 27 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 23 sectors are pending re-allocation at the end of the preclear, a change of 23 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdi == WDC WD20EADS-00S2B0 WD-WCAVY1312744 == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 10:48:55 (51 MB/s) == Last Cycle's Zeroing time : 6:36:02 (84 MB/s) == Last Cycle's Post Read Time : 17:17:47 (32 MB/s) == Last Cycle's Total Time : 34:43:50 == == Total Elapsed Time 34:43:50 == == Disk Start Temperature: 29C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 124 123 0 ok 28 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ And here's the one that didn't pass. ========================================================================1.11 == invoked as: ./preclear_disk.sh -A -M 4 /dev/sdg == == Disk /dev/sdg has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 11:13:12 (49 MB/s) == Last Cycle's Zeroing time : 6:53:20 (80 MB/s) == Last Cycle's Post Read Time : 17:43:03 (31 MB/s) == Last Cycle's Total Time : 35:50:40 == == Total Elapsed Time 35:50:40 == == Disk Start Temperature: 27C == == Current Disk Temperature: 27C, == ============================================================================ No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================