• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Hoopster

  • Rank
    Advanced Member
  • Birthday


  • Gender
  1. Yes, several times. This MB has a clear CMOS pad that is jumpered with a conductive material (I have used a screwdriver blade) with the battery removed. Not a terribly elegant way of doing it and I can only suppose it is working. Since there is no video and no post to BIOS, who knows? ASRock wants me to try a known good freshly flashed BIOS chip. Sent from my iPhone using Tapatalk
  2. OK, this is a strange one. I upgraded my main server to an ASRock C236 WSI and Xeon E3-1245 V5 in December. Initially, it had no video output and did not post and enter BIOS. It turns out there were three bent pins in the CPU socket which when straightened fixed the issues. The server has been running 24x7 since then with no issues and has been through several reboots for config tweaks and updates. Yesterday, just to test capabilities, I decided to try S3 sleep on the server. Apparently, that was a bad idea. It is enabled in BIOS and I installed the Dynamix S3 Sleep plugin. First test worked, sort of. The server went to sleep when issued the sleep command. I pressed the power button to wake it up and it woke up (GUI and SSH/Telnet worked), but, no video on monitor. The second test was a disaster. Server went to sleep and this time I tried to wake it with a WOL packet to NIC. Nada. No video. No GUI. No SSH/Telnet. Just spinning fans. I had to hard reset. Still nada. No video and no BIOS post just as with my original issue with this board. I removed board from case and tried it with a different PSU, just to verify that the PSU was not the cause. Same issue with a different PSU. I removed the MB from my backup server and tried it with both PSUs. Video output and BIOS posted with both. That board and i5 is now back in my main server. The C236 WSI appears to be "dead." Power LED shows power to the board, but, only the fans spin when the power button is pressed. I have contacted ASRock and they are sending me a couple of newly-flashed BIOS chips. If that does not work, they will accept an RMA of the board for repair. I have no idea how a couple of sleep/wake cycles could have caused this, but, maybe the board has had a flakey BIOS from the beginning and this was just a trigger. Frustrating to say the least.
  3. I take it there has been no movement on a darker theme? I find myself spending less time on the forum (not that that is a bad thing :)) because the white is just too bright and makes it harder for me to read posts. I have the unRAID GUI set to the dark theme as well. The third-party theme suggested earlier in this thread by BetaQuasi seems to be a good one. Is that something that an individual user has to pay for ($30) in order to use or can it be implemented as a forum option?
  4. I recently upgraded my main server from an i5 to a Xeon and repurposed the "old" parts as a backup server.. I agree with the other comments that an i5 is underpowered for your stated use case. I was able to run 1 light VM max (multiple installed, but, just one running with light use) with the i5 while also doing normal NAS functions and one Plex stream. Anything beyond that is too much for the 4-core non-threaded i5. The Xeon/i7 is a different story.. Much more flexibility, horsepower and overhead for simultaneous VM/Plex tasks. See my sig for both system specs.
  5. Only backup to Crashplan Central (cloud storage) requires a subscription. Backup from one computer to another is free.
  6. My last parity check was with version 6.3.1 four days ago. It was 4 minutes faster than parity checks run with 6.2.4. I have always seen very consistent parity check times on all versions of unRAID 6.x.x. I have been through three CPUs (two 4-core i5s and the current Xeon 4-core/8-thread CPU) and three different motherboards in that time. Parity checks have always been within 2-3 mintues of the prior time. This is the biggest variation I have seen in a while and it is 4 minutes faster. I have yet to run a parity check with 6.3.2.
  7. Agreed, no way he gets what he wants new for under $400, but, the Ryzen chips will certainly alter the price/performance considerations many of us are used to. If they deliver as promised at the prices quoted, I imagine there will be a lot of interest in the unRAID community in Ryzen-based single CPU (or dual) 8-core/16-thread systems for multiple VMs/heavy Docker use/transcoding. I will certainly be keeping an eye on them.
  8. Only happened once. Once I toggled security on and off after setting up the share, it has remained accessible without the authentication prompt.
  9. There are also the upcoming AMD Ryzen chips (Feb 28 release) which look very appealing. Eight cores and 16 threads for as little as $320. See http://wccftech.com/amd-ryzen-lineup-pricing-confirmed-8-cores-low-320 for some tantalizing details.
  10. Can you post the UD log when this happened? Here are the contents of the log: Feb 05 07:43:52 Adding disk '/dev/sdi1'... Feb 05 07:43:52 Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdi1' '/mnt/disks/Crucial SSD' Feb 05 07:43:52 Successfully mounted '/dev/sdi1' on '/mnt/disks/Crucial SSD'. Feb 05 07:43:52 Partition 'Crucial CT480M500SSD1 1307092A4C45' is not set as sharable and will not be shared... Feb 05 07:43:52 Device '/dev/sdi1' script file not found. 'ADD' script not executed. Feb 07 09:52:12 Error: No valid smb users defined. Share '/mnt/disks/Crucial SSD' cannot be accessed. Feb 07 09:52:12 Defining share 'Crucial SSD' on file '/etc/samba/unassigned-shares/Crucial_SSD.conf' Feb 07 09:52:12 Adding share 'Crucial SSD' to '/boot/config/smb-extra.conf' Feb 07 09:52:12 Reloading Samba configuration... Feb 07 09:52:12 Directory '/mnt/disks/Crucial SSD' shared successfully. Feb 08 11:28:31 Reloading shared dir '/mnt/disks/Crucial SSD'. Feb 08 11:28:31 Removing old config... Feb 08 11:28:31 Removing SMB share file '/etc/samba/unassigned-shares/Crucial_SSD.conf' Feb 08 11:28:31 Removing SMB share definitions from '/boot/config/smb-extra.conf' Feb 08 11:28:31 Reloading Samba configuration.. Feb 08 11:28:31 Successfully removed SMB share 'Crucial SSD'. Feb 08 11:28:31 Adding new config... Feb 08 11:28:31 Error: No valid smb users defined. Share '/mnt/disks/Crucial SSD' cannot be accessed. Feb 08 11:28:31 Defining share 'Crucial SSD' on file '/etc/samba/unassigned-shares/Crucial_SSD.conf' Feb 08 11:28:31 Adding share 'Crucial SSD' to '/boot/config/smb-extra.conf' Feb 08 11:28:31 Reloading Samba configuration... Feb 08 11:28:31 Directory '/mnt/disks/Crucial SSD' shared successfully. Feb 08 11:28:41 Reloading shared dir '/mnt/disks/Crucial SSD'. Feb 08 11:28:41 Removing old config... Feb 08 11:28:41 Removing SMB share file '/etc/samba/unassigned-shares/Crucial_SSD.conf' Feb 08 11:28:41 Removing SMB share definitions from '/boot/config/smb-extra.conf' Feb 08 11:28:41 Reloading Samba configuration.. Feb 08 11:28:41 Successfully removed SMB share 'Crucial SSD'. Feb 08 11:28:41 Adding new config... Feb 08 11:28:41 Defining share 'Crucial SSD' on file '/etc/samba/unassigned-shares/Crucial_SSD.conf' Feb 08 11:28:41 Adding share 'Crucial SSD' to '/boot/config/smb-extra.conf' Feb 08 11:28:41 Reloading Samba configuration... Feb 08 11:28:41 Directory '/mnt/disks/Crucial SSD' shared successfully. Attached are the diagnostics. medianas-diagnostics-20170209-1608.zip
  11. If you go this route with the MB + CPU + RAM please note that the board/CPU combo requires *unbuffered (non-registered)* RAM. The Kingston part number you need is KVR21E15D8/16 if you want 16GB ECC unbuffered RAM modules. I have a C236 based server MB (ASRock C236 WSI) and the Xeon E3-1245 V5 (integrated GPU) and am running the Handbrake docker. My setup has no issues with a couple of Plex transcoded streams while simultaneously doing a Handbrake transcode. Passmarks (as has been mentioned) are the best measure of suitability for Plex workloads and my CPU, or the non iGPU, 1240 you have specified are 10k+ passmark CPUs and very good transcoding workhorses.
  12. Toggling the security fixed the problem, but, here is my current UD share file for the affected device: Crucial_SSD.conf
  13. Thanks johnnie.black. I just accessed my server via OpenVPN and toggled security as you suggested. I now have access to UD share without authentication prompt. I will try local access when I return home, but, that appears to have done the trick. Thanks again. Enviado desde mi iPad utilizando Tapatalk
  14. Just installed UD after upgrading to unRAID 6.3.0. I have an SSD on which I have installed my VM and it is running well. I eventually plan to move my dockers off the cache drive as well and on to the UD SSD. I have shared the drive (currently have no security enabled while testing) and it shows up in my Windows 10 clients as a Samba share. However, every time I try to access it, I get a Windows network credentials prompt to enter credentials for my unRAID server. I have tried both my unRAID and Windows logons to no avail. I cannot access the contents of the shared UD SSD from Windows clients. The unRAID shares all show up as Samba shares as well, but, none of them prompt for credentials and I have full access to the contents from the Windows clients. I have read the 6.3.0 announcement thread and noted there are, apparently, some issues with Samba authentication in 6.3.0; however, unlike others, all my unRAID shares (public and private) are accessible, it is just the UD shared drive that is causing me issues. Any ideas? I am sure it is something simple I am overlooking. I even tried clearing all unRAID credentials in Windows Credential Manager.
  15. Avast locked up my Win 10 VM as well. I am running Sophos Home (free) without issue on my Win 10 VM.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.