Leaderboard

I updated the plugin. Uninstall the original and install this one. https://raw.githubusercontent.com/dmacias72/NUT-unRAID/master/plugin/nut.plg I have not fully tested everything. I did test pulling the plug and it notified and shut down the server. So if someone wants to help out and test. I Stop the array first and any other write functions/scripts before testing. I would monitor from an ipmi or physical console then try different shut down scenarios. change log ###2017.05.26 - add master/slave options - fix runtime display format ###2017.05.24 - add dropdown options for battery and timers - add killpower flag condition to shutdown script ###2017.05.22 - fix shutdown scripts - move default nut conf files ###2017.05.20 - fix manual config settings ###2017.05.19 - fix reload button - add start conditions to rc script ###2017.05.17 - add manual mode, reload and config editor to settings page - reformat settings page, hide unused vars - add vars, rewrite, combine and move scripts - add snmp settings from Ambrotos fork - untested - add UPS summary, UPS details page and dashboard page - add dynamix plugin api - remove depreciated code - restructure and repackage plugin - rename nut plugin package to difer from nut package

Your problem is on the Windows side of the equation. As @remotevistor said, you can not gain access by trying to logon as root. It is prohibited for security reasons. In fact, you should clear any logins from your Win10 computer to your server unless you are restricting access to shares. As I recall, once you have established a successful login from this computer, Windows will do it automatically for you! All of my computers are Win7 and I have only played superficially with Win10 using my Granddaughter's computer but I think the two are very similar. As I said earlier, look at the Security properties for this mapped drive and see what you find. You can also search for credentials and/or Credentials Manager and see what credentials are setup on this machine. You may well have to delete credentials to get things back to square one. Here is a post from LimeTech that discusses user share problems. You might want to read a number of additional posts that follow. You can also google the problem and see if other Win10 users have reported a similar issue...

You should login with anything other than root .... The Samba configuration is deliberately set up to restrict root access from the network.

Using either PuTTy (or a monitor and Keyboard), enter the command: ls -al /mnt/user/ You should get something that looks like this: root@Rose:~# ls -al /mnt/user/ total 4 drwxrwxrwx 1 nobody users 33 May 21 02:30 ./ drwxr-xr-x 7 root root 140 May 18 09:35 ../ drwxrwxrwx 1 nobody users 305 Apr 5 08:15 Backup/ Notice that the 'owner' of the share Backup is nobody and the 'group' is users. now type this command ls -al /mnt/user/Backup/. (Note that I am using the name of one of my share (Capitalization is import to Linux! so be sure to observe it.) If you have any data files they will look like this: -rw-rw-rw- 1 nobody users 178259492 Oct 20 2016 Nathaniel-Ashley-Wedding.pdf This is a data file because it begins with - instead of a d and observe that the owner and group are still nobody and users. If it is anything else, you will a problem with permissions. Now, you may need to navigate further down the directory tree until you get to data files. If you find this condition, you have a problem with the settings on Krusader or some other plugins/Dockers that you are using to store files on the array.

I found the answer... shutdown the Docker. In the /appdata/homebridge directory, DELETE the folder "persist". Re-start Docker and it should appear.

Rebuilt a 2TB drive onto a new 4TB drive (ancient 2TB started showing bad sectors) using 6.3.4 - completed without issue, quickly

i know i posted something on the forum but I cant find it by using search/advanced search... I can see my posts when I go to my profile activity (17 pages).. but cant seem to search within them.

The plastic piece on the back of the drive bay (the piece that can be removed to make room for a video card) can be notched very easily. A few guys have done it here, myself included. I used a dremel and a razor blade, literally took less than a minute and wasn't very difficult. I have an LSI card in my DS380, and with the notch cut, it fits perfectly. RE: fans. Cooling is the biggest problem in this case; the thousands of posts in the hundreds of threads spanned across the web, along with product reviews on various vendor sites, will confirm that. I added two additional fans on the opposite side of the case to blast air crossflow across the drives, and then have the fans in the stock locations doing evac duty. Even with this setup I have heat issues, although my server is in a cabinet (a cabinet that is vented with fans, but still an enclosed space). In open air I have no heat issues whatsoever, so I can't blame the case 100% on this. I am relegating this case to backup server duty. My main system is moving to a larger case with better cooling. My DS380 will sit in my garage with Nidec and Sunon fans where fan noise won't bother me, and will come on once a month to do an rsync with my main server, and then automatically shut down. Its a fantastic little case that requires some modification to make it better.

For those that run Kodi, create or edit the smb.conf for the user that kodi runs under: ~/.smb/smb.conf -- [global] client min protocol = SMB2 client max protocol = SMB3 client lanman auth = no client plaintext auth = no client NTLMv2 auth = yes --

Figured it out. Incorrect syntax. -- min protocol = SMB2 guest ok = no null passwords = no lanman auth = no restrict anonymous = 2 encrypt passwords = yes server signing = mandatory ntlm auth = no --

Jobine: Switch to the advanced docker view (switch in upper right part of the docker screen) and select 'force update' See if that works. Brian

Good catch, Best Buy had these on for around the same price a few weeks ago, I grabbed one then, they are totally shuckable.

@Zonediver The SMART data is one dimension of drive health. It has its limitations. Just because the smart report looks ok, it doesn't mean the drive is healthy. If you saw something that led you to do more investigation (which may or may not have been what the data was telling you), and you identified some slow sectors in the process that you believe are bad enough to look to replace the drive, there may have been some serendipity involved. But it is good if you found a drive issue. The "raw" values that appear on the smart report, are, with a few notable exceptions, not something a person can understand without technical specs not made available by the manufacturers. They are likely bit masks (first 3 bits mean this, next 2 bits mean that, etc., etc.) that vary by manufacturer and even by model. Turning this concatenation of bits into a decimal number is meaningless. These raw values are translated into a normalized scale, where normally 100 is "good" and the threshold for going bad is defined. Smart tracks both the current normalzed value and the worst the normalized value has ever gotten. Some attributes have raw values that are usable - things like reallocated sectors and current pending sectors - which are absolute counts and have been used in that consistent way for every drive I have looked at. These are some of the most useful attributes to track. Most important in the SMART attributes is not the absolute value, but a comparison over time. For example, having a drive with 1000 reallocated sectors that are rock solid and never increase with time, is probably better than having a drive with 20 reallocated sectors, and that number if growning with every parity check. I do not have a particularly warm place in my heart for WD or Seagate drives (although I have been pretty happy with the 8T Seagate archives given their price and my experience with them to date). I believe that the HGST's are the highest quality, and if cost were no object, I'd been buying those.

It's tailored to unRaid, and takes the approach of waiting for an attack to happen against certain files and when that happens stops all smb write access regardless of how inconvenient that may be to you. IE: It's your absolutely last line of defense, and should never be your first and/or only... https://github.com/Squidly271/ransomware.bait/