Frank1940

I would suggest going to this Webpage: https://unraid.net/support And go here: When you contact them, give details about your purchase and and the Active GUID that is showing up on Main >>>> Boot Device Then click on Boot(Flash) to get the page with the GUID.

You have asked a question to which there is no 'right' answer! Many of us run a parity check once a month. It is always our hoped-for- goal to find no errors. Once you have an error(s), you have a potential for a data loss. And you should address the problem at once. You also want to find problems before a second problem occurs. (Once, you have two source of errors on an array, the likelihood of a data loss just jumped astronomically.) Here is link to an old thread that has a look at the problem from a statistical viewpoint. You can read the comments of forum members at that time. Most of the still apply! https://forums.unraid.net/topic/50504-dual-or-single-parity-its-your-choice/ About the long time to run the parity check. Have a look at Parity Check Tuning plugin. It allows to break these long running operations up into chunks that can be run during more convenient hours. Remember that this test is intended to catch problems at their beginning before they become major headaches. PS---- I know that the annual failure rates that I used in the Tables is much higher than we see today! (Thanks for some blessings!!!) But there were a few drives back then that did have annual failure rates of 10%. Today, a drive that has annual failure rate of 2% is the outlier.

Just be thankful that you have a solution to make your old printer/scanner to still work. (A while back there was another user with the similar problem. As I recall, he also found a work-arround.) SMBv1 is all but gone as it has security issues especially for home users. Most people have long abandoned it so getting help to fix issues is now a problem.

Upgraded both servers and no problems. Well, one very minor one, I had to reboot a Windows client after I try to access a server too quickly after it came back online and something went wrong in the login client-server handshaking.

I would suspect that it is browser related. What works in one browser does not work in another browser...

You might only need a new battery. Inexpensive replacement batteries are available for most UPS models.

Is the MB an older one? If it is, I would suggest replacing the CMOS battery.

I am not sure this will answer your question BUT google security issue on opening port 25 and read the AI summary. Apparently, the current recommendation is to use port 25 only as a last resort. see below: I also checked to see what port that I had my Unraid e-mail Notifications for. It was using port 465. (This setting is the default for the Yahoo mail server.)

Start with this link in this thread: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561581 Then read the next two posts. (The entire thread provides an explanation of how SMB, Samba, Windows and Unraid work together to provide connectivity. Understand that MS intends that Windows SMB will only work if the environment is completely secured from security risks!)

If you do move ahead with a new server, consider retaining that old box as a backup server for the main server. Remember that there are a lot of ways to lose data other than a drive failure– Fire, flood, lightening, theft of equipment, Malware, malicious behavior of a user, power supply malfunction are a few that quickly come to mind.

How are your transcoding? I would think that Plex could use a GPU to do the transcoding much more efficiently... (Point of Disclosure– I do not use Plex. I use Unraid to store my media and KODI clients to play content. In this case, the client does any transcoding necessary. I use a mysql Docker to maintain a common database that all of the KODI clients use.)

For a quick AI overview, Google iperf test If you need more help, Google iperf test procedure IF the AI is not enough, look at the links below the AI infor....

The other big thing that I see are the single quote (instead off double quotes) around myunraid.net

Line break are a big problem as the term does not result in the same ASCII character being used for different OS.. Windows = CR LF UNIX = LF MacOS = CR Where CR is Carriage Return Where LF is Line Feed or New Line (All of these are commands originally intended in use by teletype machines. There probably aren't twenty of these still working order left in the world!) This can cause a lot of problems with straight text configuration files written/edited with one OS and subsequently interpreted by a second OS!

@JorgeB, Could you alert the proper person on the Unraid design team to fix this? Thanks!