Frank1940

Probably... Specially if it a Linux user password. I also see a file named smbpasswd in the config folder and it may contain passwords for that function. One thing to try is to clear you browser cache. You may also have to reboot the server to get everything back in sync. In your case, I am wondering if you might have a problem with your Flash Drive. (The fact that the GUI changed it for the command line--- as it should--- and not for the GUI.) You can check this in a Windows machine with chkdsk (Apple has an equivalent function). You can get a clean shutdown of your server a one second push of the power button. DON'T hold it down for much longer as that will force an unclean shutdown! By the way, do you have a backup of your Flash Drive? If not, copy the contents of the entire drive to a folder somewhere besides on the server. If you are doing this while the server is running, stop the array first. This sets a flag that the array was stopped so that parity will not be checked when the server is started up if you have to use the backup to rebuilt the Flash Drive.

That is correct as the unRAID OS runs entirely from RAM by setting up the entire Linux OS on a RAM disk. The Linux password files are stored in that file system and NOT on the Flash Drive! You should be able to log into the GUI using your 'old' password. If not, you will have to delete both the passwd and the shadow files in the config directory and (probably) reboot you server. You will now to be able to login using root with no password will be required. Then set your password to whatever you want from the GUI and always use the GUI to make the change in the future. (unRAID is now designed to be administer from the GUI and not the command line...)

If you want to know that transfer speed between any computer and your server(s), there is a little program available which will measure the speed both ways. It does not even require installation! Download it, click, and run. You can find it here: http://www.totusoft.com/lanspeed1 There are both Windows and Mac OS versions available. As with any program that you download from the web, you should exercise some caution but I have used this without any problem. You should run the first time as a 'warm-up' to make sure that all of your drives on the server are spun up. Then make your measurements for comparison. You also have to select a share on the server as it writes a file there. (It will automatically deleted that file when the test is down if you so desire--- A good choice by the way!) You can use the default small file size to begin with but I have found that using large file sizes (>5000MB) will give a better indication of the true transfer speed.

Thanks I'll dig around and see what I can find. Odd that to started up the one time fine and now won't again. I found the post from Joe L. to fix his script:

I agree 100%. As I said, I was introduced to it and quickly decided that I would never attempt to use it on my own. But when someone puts a command together (as JoeL did in this case), I will use it with joy as it can do thousands of individual edits in a file with a single command. (That is the reason I decided never to use it on my own. A slight error in formatting can reek havoc in a file...)

As I recall (from about thirty years), sed means Stream EDitor and is very powerful Unix-developed tool. The command is a one-liner that you can copy-and-paste to the command line if you use PuTTY and that one line makes all of the modifications to the file.

As I recall, they are buried somewhere in the thread for JoeL.'s script. It is after the introduction of beta versions of version 6. (As I recall, it was actually an change in the fsdisk script/utility---which is a part of the Linux kernel--- that broke it...) EDIT: As I recall, the modification required the use of the Linux utility sed to do the work. That might be a good term to search on!

There are a couple of Mod's that HAVE to be applied to JoeL's script for it to run under 6.?. JoeL. knows that the script needs work but it has not been done. (Unfortunately, since all of the old direct-links-to posts on this new board are now broke (they worked for the first few weeks), I can't point you to them. I would suggest that you use the default script that is included with the current plugin and see if it works.

This appears to be a new drive. I know I would not be happy to have 232 reallocated sectors on a disk with less than 150 hours. You didn't provide us with any history of how this disk acquired those first 72 hours. (I assume that you put them on or you got a disk that someone else returned as defective.) If it were me, I would return the disk as DOA or take advantage of a thirty days return policy.

Install the 'Fix Common Problems' plugin. Then turn on the 'Troubleshooting Mode'. After the time you get a GUI failure, look in the logs directory/folder of the Flash Drive and upload the most recent files. Before rebooting, try to get a diagnostics file from the command line.

See attached for what mine looks like. you seem to have a lot of spce allocated to Bluffers and it does even show up on my system. It is important to remember that when the OS 'requests' memory for some process if it is not available, it will dump something from memory. The GUI Process (I believe it is emhttp) is not restartable and it is dumpable! So when it is shutdown, you have lost the GUI period...

Do you have the Tweaks and Tips plugin installed. If you do, on the 'Tweaks' tab, set the Disk Cache 'vm.dirty_background_ratio' (%): to 2% and the Disk Cache 'vm.dirty_ratio (%): to 4%. This will free up a lot of memory for other use by other processes. Use help to see what these settings do. Remember that the default for these settings were developed for Linux systems running with 1GB of memory...

Could be an out-of-memory issue. How much memory is in your system and what plugins/Dockers/VM's are you running? How many disks are you trying to clear simultaneously? Does a monitor/keyboard attached directly to the server still work? If so, type diagnostics on the command line and that will write the diagnostics file to the logs directory/folder on the Flash Drive. Post it up in a new post.

Two ports, four ports or eight ports? Are you planning on using virtualization? Is cost a consideration? Two port cards are widely available. Just read the reviews as quality appears to be an issue with certain cards. You can look at my systems in my furniture but beware that many four port cards requires that you turn off virtualization in the BIOS with those CPU's that support it. (On any four port card, look for a BIG heatsink. Most of the time these cards are used on systems where only one of two drives are in use at a time. This is not the case with unRAID!)

Do you recall reading this instruction on how to count the 'turns' or 'loops' You have got me thinking. You said you did ten wraps around the clamp. That would put 11 wires inside of the closed clamp. So you should be dividing the reading by 11 NOT 10! (You do the loops/coils because most of these units have very poor accuracy at the low of their measurement range!) So your Max VA = 9.45/11 X 117.5 = 101VA That is the figure, I would be working if I truly believed that your meter was capable of reading instantaneous peak current. What I would use would be this figure 114VA. Where did I get that. A very conservative estimate of peak starting current for hard drives is 2amperes per drive. You have three drives so 2A/drive X 12V X 3drive = 72VA and 3.85A/11 X 117.5 = 41.125VA Total instantaneous VA requirement on drive spinup is 72VA + 42VA = 114VA So the numbers are actually in fairly close agreement. (Your newer drives probably have a slightly lower peak current draw than drives with older designs did.) But you have to ask yourself about what plans you have for expansion of this server and how are you going to do it. Are you going to add more drives or Are you going to replace the current drives with larger capacity drives? That 230W PS is going to limit what you might want to with regard to the first option. You also have to keep in mind that 230W limit when you are looking at the ampere ratings on the individual voltage buses as their total wattage often exceeds the power rating of the PS and that rating is a hard limit. Exceed that rating and most PS simply shutdown!

The way to count 'loops' is the number of wires in the center when the clamp is closed. (I.e., when you put the wire through when you made your first measurement that was a 'one loop' coil. If you would take that wire, wrap around and put it through the center portion again, that is two loops.) @jonathanm said much the same thing but this concept is rather confusing to most laymen.

A few years back that was a real problem with some of the new green PS's not being compatible with the the stepped approximation wave forms. It seems that this issue has been resolved. And the stepped approximation waveform will cause the transformers in the PS to run a bit hotter which is a concern. In my opinion, if you are in the situation where the number of times that you on the UPS is only a few times a year and you actually initiate shutdown with a two minutes of power outage, the use of a stepped approximation UPS will not cause any problems. You are looking at the time to when the batteries are exhausted. That type of calculation is a waste of time in the real world. That run time is usually wildly optimistic and will decrease with time as the batteries age. You should be concerned more with the instantaneous peak power that you server requires when it spins up all of your drives simultaneously. Measuring it is very difficult as it last less than two seconds. (You can try to find what the peak current is for your drives but many manufacturers don't provide it. A rule of thumb is about 2amperes per drive. Why is that number important? Because if the power rating of the UPS is exceed for a few milliseconds, it will instantly shutdown to protect its power switching transistors. My suggestion in determining when to shutdown your server after a power outage is this. How long is the power out when it comes back on within a reasonably short time and stays on. In my area, if it is out thirty seconds, it will be out for, at least, a couple of hours. So I have my time on battery set at thirty seconds. One more factor to be considered. Let's say you have the time set for 70% of remaining battery. You have a power outage and the server shuts down as a result. The power comes back on, you decide the things are back to normal and restart the server. And the power down goes out again a few minutes later. The UPS battery will probably not have enough reserve to shut the server down again. (It takes more than eight hours to completely recharge those batteries.)

+1

I hadn't check the logs, but that last check was noncorrect: Apr 30 08:12:28 Tower kernel: mdcmd (51): check nocorrect When you in the the Main page look under "Array Operations" You will see an button named "Check" Double check that the box that says "Write Corrections to Parity " IS checked to get a correcting check. Now click that button you will get a 'correcting check'. I personally would stop the current parity check (won't harm a thing but the loss of a bit of time) and restart it making absolutely sure that everything is 'checked' correctly to get a correcting parity check this time!

When you in the the Main page look under "Array Operations" You will see an botton named "Check" If you click that you will get a 'correcting check'. ( You have to uncheck the box that says ' Write corrections to parity' to get a non-correcting check.

Are there any issues with the LSI 9207-8i not being able to spin down drives?

I am in the process of converting the format on my Media Server. (The Spec's are below.) I normally use the reconstruct write (aka, turbo write) method of writing to the array but I decided that read, modify, write (aka, the default) method as I thought the extra head movement on the source drive could slow things down to the point where the default method might be faster. I converted the first two disks using the read, modify, write method. I used the Mirroring Procedure using rsync. Here is the rsync summary of the transfer information for the second disk: 1,449,822,135.370 Bytes 42,192,398.57 Bytes/Sec The resulted in a transfer that took more than 10 hours. While this was going on, I researched the question of which might be faster. There was speculation that reconstruct write would be faster but still slower than the normal speeds seen from this writing method. But I could not find any real numbers. I decided that I would try the reconstruct write method on the next disk. The amount of data transferred was greater but the time was only about eight hours. Below is the rsync summary for that disk. 1,704,756,941,912 Bytes 65,036,030.45 Bytes/Sec The transfer speed was approximately 54% faster than the default read, modify, write speed! I did observe one thing--- the write speed did appear to me to become slower as the disk filled up. I would assume that the writes at this point were moving to the inner tracks on the disk. So if you are trying to speed up your conversion process have a look at using reconstruct write. The disadvantages that I can see are (1), you will have to have all of the disks spun up for the entire conversion process instead of just three disks, and (2) the speed gain may not be as much for arrays with older smaller-capacity disks. EDIT: Another data point for reconstruct write (aka. turbo write): 2,254,789,286,418Bytes 72,300,171.31 Bytes/sec Total time for data transfer of 2.27 TB of data was less than 8-1/2 hours.

What you had a power hit where the power was interrupted for a fraction of second to as much as two seconds. This seems to happen when the power company equipment is attempting to eliminate voltage surges from propagating through their system. (Some of the digital clocks will have a small capacitor in them that will supply enough power to bridge these types of interruptions.) Folks have had good luck with both Cybrpower and APC. Look at the reviews at places like amazon and Newegg for both manufacturers have had models with issues. I would be looking at a unit with a power rating greater than 700VA and plan on shutting down after about 30 seconds on battery. (With your history of service, it is out for 30 seconds, you can't afford a UPS to bridge the probable outage time!) As to pure sine wave vs the simulated since wave, several years back there were a few high efficiency Power Supplies that didn't like the simulated ones. But I have not heard of that problem with modern PS in the last few years. Your outage pattern indicates that if the UPS works, it won't do any 'damage' to your PS having to deal with that few minutes (at max) once or twice a year. (The transformer may start to heat up a bit...) Which you choose depends on your tolerance to the FUD (Fear, Uncertainty, Doubt) factor...

You have three syslogs files (because the master syslog is being filled with those USB events) in your diagnostics file but the initial one occurred BEFORE the first entry in the earliest log file. You may have to reboot the server and grab a new diagnostics file after the first few occurrences . What we need to see if there is a clue to what triggered the first one. By the way, are you passing a USB port through to a Docker or VM?

You can get the files needed for the Gurus by going to 'Tools' >>> 'Diagnostics' and that will download a zipped file to your download folder of your browser. Upload that file with your next post. You can also tell us what USB devices are connected to your server. (You have a least one-- your Flash Drive with unRAID on it.) By the way, it is best to use a UBS2 (NOT a USB3) port for your boot drive. The speed of the Flash Drive is not that important as unRAID runs completely from RAM from the time it first boots.