• Content Count

  • Joined

  • Last visited

  • Days Won


Frank1940 last won the day on June 28

Frank1940 had the most liked content!

Community Reputation

628 Guru


About Frank1940

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. First. Begin by measuring the physical size of the PS and see if it is a standard size. Some OEM manufacturers use non-standard components to lock you in to using replacement parts from them! Second, you are looking for a PS with a single +12V rail. (Unless, you plan on installing a serious GPU card into your server, there is no need for a second rail.) Look for a manufacturer with a known reputation for building a quality supply. Allow approximately +2.5 amps per HD for the surge when the drives spins up. (Unraid has several sets of situations when it will spin up all of th
  2. You do need a blank disk to format for use in the array BUT it needs to only be large enough to hold all of the data on one your two existing data disks. In other words, if one of those disks has only 1.9TB of data on it, you could get a 2TB disk as the first data disk for your array. Copy all of the data from the old disk to the new one. You do realize that you are going to need a 4TB Parity disk if you are wanting to use the data recovery option of Unraid? I would like to suggest that you buy a new 4TB drive and move the data over using it. When the data on the second OMV
  3. This is why I am hoping that these type of discussions could wait until LimeTech has implemented their security enhancements on the Unraid side in 6.10.0. @ljm42 is showing one approach (which LimeTech might build on) and @Hammer8 is showing another one. ( @Hammer8--- Yes, you have turned off SMBv1 with this entry in the smb-extra.conf file. However, you could also have it enabled with the setting that @ljm42 showed but the entry in the file will cancel that!) Otherwise, I am afraid that we could end up in a situation like exists in Windows where there are more than than one way to accomp
  4. I have noticed that too. I suspect that is is being caused by the fact that SMBv1 is not turned off (yet) on the Unraid servers. (Contributing may that the fact that Network Discovery is on on Windows...) I do think that I know how to turn off SMBv1 on the server but I am waiting to see exactly how LimeTech is going to be handling this when they release 6.10.0... By the way, I did try to add a network location that pointed directly to my Unraid server as you indicated that you wanted. It said that this was not allowed and I would have to point it directly to one of the shares
  5. You should really initiate a automatic shutdown of your server about 30 seconds after the normal time that the power might be out if the power outage/disruption might last if it was caused by the Power Provider doing a normal load switching function. (In my case that is 10 seconds after the interruption first occurs! IF it last longer than thirty seconds, it will be out for hours!!!) For the longest UPS battery life, @ChatNoir is correct. Shutdown quickly so you can repeat the process a second time if you restart the server too soon...)
  6. Connect a monitor and keyboard to the server. If it (ever) boots to a Command Line log-in prompt, log in and type: diagnostics that will save the Diagnostics file to the logs folder in the root of the boot drive. Upload in a new Post. If you (ever) get to a GUI interface, Go to Tools >>> Diagnostics Click and read. Again upload the entire file. IF you don't get that far, take a picture of the monitor screen or write a detailed report of its contents.
  7. Windows 10PRO (not sure about HOME), if you go to Control Panel >>> Programs and Features. Then click on "Turn Windows features off and on" in the left panel. Then scroll down until you find "Services for NFS". Not sure why one would want to use it unless one was a dyed -in-the-wool Linux user... PS: it is actually easier to get SMB to work in a secure mode than to use the insecure mode (~2010 security level) that Unraid defaults to. See here:
  8. Try turning the bad Ethernet port off in the BIOS. If that doesn't work, post back with more details about your MB/Ethernet setup. Hopefully, someone will have a solution for you. (You need to get down to one working Ethernet Port...) OF course, it is always possible that voltage surge damaged more than just the Ethernet port!
  9. Keep trying USB ports until you find one that works... You might want to try the 'SAFE GUI' boot option.
  10. Boot up the server with a Monitor and Keyboard attached. When the Boot menu comes up, select the GUI Boot Option. You can then work from the GUI on the monitor and setup the Ethernet ports.
  11. check the cooling inside of your case. Clean if dirty. Make sure that all fans are actually running!
  12. I have reread your post a second time. You might want to consider requesting a Moderator to move this to 'Bug Reports'. My reasoning being is that is this card is working in 6.8.X but is not working in 6.9.X is a good indicator that there is a bug in the new driver. Of course, you will have to provide the Diagnostics Files ( Tools >>> Diagnostics ) and any other logs files that are needed to provide complete background information.
  13. Are you pinging with IP addresses or URL's ( If IP addresses work but not URL's, you need to set up DNS service in the Settings >>> Network Settings page. Be sure to turn on 'Help' for this page. (One widely used DNS server is ) If this does not provide the solution, post up the complete Diagnostics file in a new Post. Tools >>> Diagnostics
  14. Please start by reading this section of the manual: To be more precise, a 'Parity Rebuild' does not restore 'Data'. It reconstructs the contents of the entire drive which includes the formatting and all of the data. IF you format any drive in any OS (that I am aware of), you will lose any data on the drive. Furthermore, if that drive is in an Unraid array (as data drives are), the formatting is operation modifies the Parity drive so that parity will now reflect that the drive has bee
  15. Be careful at this point. A Rebuild should be fine but Mr Murphy is always present during this operation. I do believe that the Tools >>> New Config path is the way to proceed. However, I have not really used that tool much so I am not really able to help you there. Here is the section of the Unraid Manual which discusses it: If you have more question post back with them