• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Frank1940

  1. It is still a good idea to reserve both the MAC and IP addresses in the router for static address that you have assigned on the server. That way both ends know exactly what behavior is programmed for that MAC address. (I do believe the preferred practice is to ALWAYS do static assignments on the router end...!!! Remember that the DHCP assigned address will be there until the next time it is renewed.) Are you using the static IP address to get to the Unraid server rather than the server name ('ih-nas01')? Be sure that you clear the browser cache as 'old' data there can sometimes cause problems.
  2. What happened at this point? What I am assuming is that this is the original boot disk with the three files (listed) deleted. (Double check this!!!) Make sure that you have a monitor attached to your server. Now boot the server with that flash drive. 1-- Does the monitor boot to the point where you have a login prompt on it? If not, get a sharp in-focus picture of the monitor screen and post it up up in a new post in this thread. 2-- If yes, then try the GUI, do you get a login prompt? (IF not, what is the error message from the browser?) IF you get the login prompt on the GUI, enter root as the 'Username' and hit the <ENTER> key in the 'Password' field. (This enters a blank password.) If this does not work, try to login from the Username and password prompts on the console/(monitor). That should work. Then type this at the command prompt: diagnostics After it finishes, type: powerdown Remove the flash drive and upload the diagnostics file in a new post. EDIT: Quicker way to shutdown server is a quick push ~ one second) of the power button. This will result in a clean shutdown. (A +5 second push will force a shutdown which will result in an 'unclean' shutdown. Using it is not an end of the world situation with Unraid, so use it if you have to for any reason.)
  3. One more point-- I would get CMR Drives rather than SMR drives. They have the potential for much better write performance. 7200RPM drives also increase both full-array read and write performance BUT you have to be planning ahead to get the full benefit. All the drives have to be 7200 RPM. One slow drive will be a bottleneck. However, that bottleneck will only last until that slow drive is out in the mix. (A 5400RPM 2TB will only slow things down until the array operation moves past that 2TB point.)
  4. I am going to be a bit of a contrarian here. It appears that you have 18TB of storage space on your current server. How long did it take you to fill it? To replace that first disk with one of 16TB, you will have purchased three 16TB drives at that point and you will add a minimum of 13TB of additional storage to your server. That is all well and good. Now, lets assume that you have a second drive fail. (Don't know the age of your drives and, of course, no one can predict if and when a drive will go belly-up, but it will happen!) You will then be adding another 13TB-to-14TB of storage. You could easily end up with a server that is only a third filled. Hard drives in Unraid servers seem to last 5 to 8 years. Do some analysis of so that by the time you get to the point with your current up-sized drives are starting to fail, they aren't half empty. It might make sense to go with 16TB or it might make sense to with 8 or 10 TB drives.
  5. Now, I am NOT running Active Directory. I have the share set up like this: When I go to this share (logged-in as the User with the read-only permission) and select a file at random, I can not delete the file but I can copy it back to the client computer. This is the expected behavior. What are you seeing? I admit that I don't have a good handle on what the Domain server does but I have the feeling that it may be not be passing what you think is your login information on to the Unraid server but using secondary login to group individual users who have identical permissions to a resource together as a group. Hopefully, someone (with a much better understanding) will jump in and provide more details. It would be helpful if you would post up a screen of your share security setup as I have done.
  6. It sounds like you don't have an Internet connection from your server. This may (or may not) to simple to troubleshoot depending on your skill level, I would suggest that you follow the advice of @ljm42 at the top of this page and start a new thread in the General Forum.
  7. Try going to Tools >>> About >>> Update OS and try from there.
  8. Go to Settings >>> Scheduler >>> Mover settings and enable 'Mover Logging:'. Run Mover again and then get the Diagnostics to upload. Be sure to disable again after capturing the diagnostics as Mover Logging will really spam the syslog if there are no problems!
  9. here:
  10. You do have to knock down the existing SMB connections from the Windows client to the server. Two ways that I know of: 1--- reboot the client. 2-- type the following command using the Command Prompt on the client: net use * /delete Shutting off the WiFi should prevent that link from reoccurring. However, that is not the only way, that it can happen. See this post and the next several that follow it: There is also a way to force the Windows client to log onto the server at client bootup. (You should only need one login from each client computer to a server! You set the permissions for that user for every Share on the server.) What you do is use the Windows 'Credential Manager' and set up a 'Windows Credential' that will log you into the Unraid server every time Windows starts. There is a PDF file in the first post of this thread that will explain how to do the this: Look for the section called: "Setting Up the Unraid Server and the Windows 10 Client". (BTW, you might want to read the entire document as it looks at how SMB users are really only a set of rules and that means that a single set of rules could easily apply to more than one client computer. In a typical household, there might be two sets of rules--- parents and children. You set up those users on your Unraid server and assign the access privileges for each share. Then on each Windows client computer, you set up the Windows Credential to log that computer as one of the two users depending on who uses that computer.)
  11. Looked at the case in this picture. I would be tempted to remove that big blank front panel. Also block those two 5-1/4" unused slots. (If appearance is an issue, use black electrical tape.) Remember all air should come in at the front of the case in front of the disk drives. All air flow (fans) behind the disks drives should be an exhaust. The PS may be a problem but generally if everything else is setup properly, the disk drives will stay cool.
  12. When was the last time you cleaned that case? I know it is a dirty job but that alone will often solve hot case temperatures!
  13. Post up a diagnostics file after you have had the problem and give us the times and date when the transfer started (approximately) and when the problem started (as close as possible).
  14. OK-- I found the diagnostics file that you posted in this thread. However, I did not find any indication of the problem, you talked about in the first post. But that file was taken after a reboot. Are you still having the problem? If you are, please post another Diagnostics file which shows the problem. One thing I did notice is that most of the disks in your array are formatted with reiserfs file system. reiserfs has problems when disks get full where file access times increase dramatically! (The problem will never be addressed because the person who was the principal developer of reiserfs was convicted of murder back in about 2010.) Many folks have converted from reiserfs to XFS. There is a set of procedures to do this conversion. You can find it here:
  15. I said to a new post. The quote above is a new post in this thread. You were requested to do the posting of the diagnostics file in a new post because if you don't, no one will ever know that you did it. (In other word, editing a post does not bump the thread. Adding a new post to that thread bumps it.)
  16. You can also try having all of the fans in the back of the case actually blowing/sucking the air out of the case. Make sure that there are air intakes on the front of the case. From your picture it looks like there are two fans in the front of the case. Those should blow air over the drives. The crosswise mounting of the disk drives may mean that these fans may not be providing moving air directly to the drives. (depends on the construction of the mounts.) You might also want to consider using a 4-in-3 or 5-in-3 adapter for those three 5-1/4" drive bays. (Make sure that with the present configuration that those bays are not providing a short circuit path for most of the front-to-back air flow!)
  17. Quick Google found this: A lot of files are replaced during a version upgrade so it not truly a coincidence. All the activity can cause a flaky flash drive to crash. Or it could be something going on. IF worse comes to worse, it is a simple procedure to update the Unraid license to a new flash drive. I hope you followed the advice given to make a complete backup of the flash drive before you started. IF you did not, try to make one before you start the repair. In particular, the /config directory is very important.
  18. You have a problem with your Unraid Flash/Boot Drive. Pull it from the server and run chkdsk on it in a PC.
  19. One more thing, make sure that you have Windows Explorer set up so that it only displays file names. Displaying things like thumbnails take a long time to load across a network. You can right click on the mapped drive, select 'Properties', Select 'Customize', Then from 'Optimize this folder for:' pick 'General items' from the dropdown list, and apply to all subfolders.
  20. There is the Dynamix Cache Dir plugin that is intended to help in these situations. I have it installed and it seems to work on my media stores (~ 2500 items). Be careful as to how many items you are caching because it caches the info in RAM and it can get 'bumped' if the system needs more RAM for another task. (Next time, you go to use it, it has to rebuilt everything...)
  21. If you have a computer that can use both connections and you prefer to always use a wired (Ethernet) connection, go to Settings >>> Network and Internet >>> Wi-Fi There, toggle Wi-Fi 'off' and this problem will be solved. (Today, a lot of desktop computers are providing a wireless option and this setting will prevent the situation that @Jimjam described. If the computer is a laptop, you probably will want to leave the Wi-Fi option 'on' and never use a Ethernet connection.)
  22. I would remove them and tag with information as to their physical location in the case. Then put them in warm dry environment and thoroughly dry them out. If you want, you could then put them in a desiccate material for a couple of days to remove any remaining moisture. Then I would install each drive into a USB housing and use the manufacturer's testing program to run a long read test on each drive. I would use another computer to do this. If they can be read, then copy the data off. After you recover all data possible, you can decide what to do with any drives that tested good and you recovered all the data from. (Any drive with data loss, I would toss at that point.) You could subject these drives to an extended write-read process (e.g., three cycles of Unraid Preclear-- plugin or Docker) to see if they pass that. PS-- Pitch the power supply, you don't want to take a chance that it might damage something that survived the initial problem because it is defective.
  23. That is true as far as I know. Just make sure your password is reasonably secure-- ten characters at a minimum. See here for why: