Frank1940

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.

Why is my GUI Slow and/or unresponsive? This problem has been traced to an anti-virus program suite and its settings in several cases. The link below will take to two posts which provide a rather complete descriptions of the problem and its solution. While you might not be running Avast, I have no doubt that other antivirus products will have a similar issue in the future. You should definitely investigate this area if you are having any type of problem with a slow, misbehaving or unresponsive GUI. EDIT: Keep reading in the thread as there is continuing investigation into the issues with Avast.

These problems are difficult to troubleshoot. You might want to open the case and see how much dust and dirt on the CPU cooler fins, fans and intake vents. Clean if necessary. Check that all of the fans are running. Then install the 'Fix Common Problems' plugin. Goto its settings and turn on its 'Troubleshooting Mode'. After the crash occurs, upload the last diagnostics file and the last log file from the 'logs' directory.

Just how did you locate them-- brute force or are there some clues as to which post in a LONG thread is the proverbial 'needle'.

Rob-- How do you want to handle this? Here is the link for this one: Delete the portion of the link that jumps to the message number but leaving the topic number seems to work to get you to the right thread. You then have to manually search for for the actual message. I would almost suggest that we use private messaging to get things repointed to the right place on the new board rather than cluttering up this thread.. EDIT: Here is a link to a way to a (relatively) quick way to permanently fix those links that point to post on the old forum:

Please don't feel that way. This whole issue can be confusing and you are not the first one (and you won't be the last one) to have problems. I am glad that you have it straighten out now.

I believe that the 'rules' associated with the Time Zone in the options account for (what we call in the USA) 'Daylight Savings Time'. The problem often is that sometimes 'Local' custom/regulation superseded the general rules and thus the automatic adjustment will result in the wrong time.

Now let's see what experiences other folks in that same time zone have had. (Sometimes, the 'rules' are wrong but I doubt that this is the case here since it appears that most of Western Continental Europe is in that time zone.) EDIT: Post up manufacturer and model number of Motherboard.

First thing. Please tell us what time zone you are in. Second thing. Double check that you have setup the Time and Date options correctly in your BIOS. I seem to recall that there was a case or two where this type of problems were traced to issues with that.

More specifically with the amount of memory allocated for use by Linux for storing files to be written to the hard disks at a later time. If the IO stream is heavy with many different write requests, it also attempts to order those writes so the head-travel distances are minimized. All of this is intended to increase the perceived responsiveness of the OS to the users. One bad side effect of this is that if there is a power failure on a system without a UPS, all of the data in that buffer will be lost! (BTW, all modern OS's have this type of feature built-in and turn-on by default.)

You might want to install the 'Tips and Tweaks' plugin and then adjust the values for "Disk Cache 'vm.dirty_background_ratio' (%):" and " Disk Cache 'vm.dirty_ratio (%): " to values like 2% and 4% on the 'Tweaks' tab. The Help menu will provide you with more information. I am certain that the default values were intended for computers with 1 or 2GB of RAM and those percentations are way too high for the amount of RAM that most are using now.

You could also try the echo command in the go file and see what happens. Print out the present /etc/hosts file for reference, add the line and reboot the server. Then look at the file again and verify that the file was properly updated.

A better alternative might be to request that LimeTech provide for the appending of a user generated hosts file to the default one that LimeTech provides. This could be done in much the same manner as is currently done with the smb-extra.conf file. Of course, this will require that someone with a truly vested interest in acquiring such an feature make the request and support that request with valid reasons for its need.

You have to understand that unRAID does NOT run from the Flash Drive. The OS is stored in the files on that Drive and the actual OS is loaded into RAM --- think of it as a RAM disk --- and that unRAID uses those files in RAM to actually run the system. (Basically, unRAID uses Flash drive to initially load the OS into RAM and grabs some information from a few files in the config folder to modify some default settings. This takes most MB's about two minutes to do. The Flash Drive is basically unaccessed by the OS until you are ready to shut the system down. It will then write a Flag bit to a file in the config folder to indicate a proper shutdown.) If you want to modify a built-in configuration file, you have to do it every time that the OS loads. Most folks who do this simply copy the modified file from the RAM disk file to a folder on the Flash Drive and put a line in the go file as Squid suggested. Another way to thing about it is that the Flash Dive in unRAID is what the DVD Installation Disk is to Windows. And that RAM Disk is to unRAID as the hard drive (C:\) is to Windows!

Nano is confusing on what actually causes the file to updated. On exiting, You have to agree to save the changes. Use the following command to see if the date and time have been updated ls -al /etc

It is actually a part of the operating system that gets installed in the RAM of your server as it unzips the bz* files in the root of your Flash Drive. You need to go the command line to actually find the hosts file at /etc/hosts. To get to the command line, log in on the console or via a PuTTY session from your PC. You will need to learn some Linux Commands at this point to do but a google search should get a link to a introductory text.

Yes, it will do the job. You can 'map' a share on the unRAID server as a windows drive (complete with a drive letter) and use it like it is a local drive. I will point out that access times will be a bit slower than a local drive. You could easily set up an unRAID server to try it out using a trail license to see if everything works to your satisfaction. (I will point out that I am a serious amateur photographer and what I do is copy all of my original photo files to the server as a permanent original. I then copy back to my PC the ones that I am going to 'photoshop' and work on them from there. What you would want to do with the finished product would be up to you at that point but I would suspect that you would want to copy them back in separate 'finished' folder to the folder that contains the originals to preserve that portion of your work.) One thing that I want to point out is that your server should NOT be your only backup. You really need a secondary backup scheme preferably one that is off-site. I see that this advice has also been recommended by ptmurphy. I repeat only because it can't emphasized too much!

Try this: https://www.cyberciti.biz/faq/howto-linux-renew-dhcp-client-ip-address/ Drop the sudo prefix, you are already logged in as Super User Found with Google....

Post up your diagnostics file. "Tools" >>> 'Diagnostics' Have you done a setup under "Shares". Setup at least one 'User' share and then click on the new share's name and under "SMB Security Settings", Export it as a 'Public' share. You also mentioned that evilmonkey dc as being an ap(p?). It has an IP address that that would imply that it has its own physical network connection to your router. That report from LANscan says you have four devices (Computers, Phones, Tablets, BluRay players, etc.) that are currently connected to your SMB workgroup named WORKGROUP. I just saw your latest post. Do you have two RJ45 jacks on your server? Have you tried both ports. I do believe that unRAID only uses eth0 by default unless you have set it up differently. Get a command prompt on your Windows' computer. (I can get one by typing 'Command' after clicking on the Start button on my Win7 computer.) then enter ping 192.168.1.5 and you should get a response back from your server. EDIT: Another thought. the IP address of 192.168.1.5 is a bit dangerous as a static IP address to use unless you have properly setup your router to reserve that address. I would have picked one like 192.168.1.243 which is highly unlikely to ever be needed the DHCP processor in your router.