Frank1940

Members
  • Posts

    9771
  • Joined

  • Last visited

  • Days Won

    16

Frank1940 last won the day on March 5

Frank1940 had the most liked content!

6 Followers

Converted

  • Gender
    Male

Recent Profile Visitors

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

Frank1940's Achievements

Veteran

Veteran (13/14)

947

Reputation

87

Community Answers

  1. Read here and see if this answers your questions: https://man7.org/linux/man-pages/man8/umount.8.html I suspect it waits because of the problems with unclean shutdowns that folks have with the array not being able to be stopped before a forced shutdown is initialized. (The force shutdown was required because otherwise the system would remained trapped between running and shutdown or rebooted. Even though a forced shutdown is messy and forces a parity check on restart, that was deemed preferable to the suspended state.)
  2. I looked at your Diagnostics and made the following observations: The "video" share exists on all your disks. The minimum free space on this share is Zero bytes. It should be set much larger than the largest file you expect to be written to this share! The "video2" share exists only on disk9 The minimum free space for this share is approximately 1TB. Notice that disk9 is common to both of these disks. Check its status as to its free space. I would also set the 'Minimum free space' setting to more reasonable value for both shares. The setting is found here:
  3. I would start by test RAM. (There is a boot option to check non-ECC RAM in Unraid's Boot Menu.)
  4. You want to look carefully at the Power Supply. Check the ratings very carefully. (For servers, a single +12V rail is preferred. Amperage on that +12V should 2.5A to 3A per hard drive...) Being new does not remove that PS from being flaky. (A few back, I had a brand new replacement PS that only lasted a week before it started acting flaky! Being the only thing that had been changed recently made troubleshooting easier.)
  5. Because it was your first post-- Probably within minutes of you signing up! Now onto your problem. We will need the Diagnostics file. That screenshot would also help. Try to post both up in new post in this thread.
  6. @Defuse, The few times I have been in this situation what I do is to delete the file first. The Dynamix File Manager is idea for this type of work. Then, when you copy the file to Unraid, it will end up on the cache drive.
  7. This is a Bump post. I have added a couple of new pieces of information to the first post of this thread in this in 2024. You might want to review them...
  8. You need to research the scanner as much as possible. You are looking for what version of SMB your scanner will support. (Many of these require SMBv1 or NT1.) Many installs of Unraid only support SMBv2 and higher. It is possible to turn on in Unraid these earlier versions but there are security risks involved in doing so. Also try connecting to your Unraid server via SMB by using its IP address. (I understand that the Local Master function of SMB only works when SMBv1 is enabled.)
  9. Start by looking at this thread: I know this is not answering your questions but I don't know if anyone today has the answers you are looking for. @Joe L. has not been online since 2019 and was MIA a few years before that.
  10. If a share has no contents then it can be deleted from the Shares tab. You can use Dynamix File Manager to delete any contents if needed. You don't have to delete a Testing share that you create. You can just turn off both the SMB and NFS export of the share. Once you stop exporting it, you can't see it from any client computer. The advantage to not deleting it is that is there should you want to do further/additional testing in the future. (My Backup server has two or three of these 'test' shares that were created to test various different networking ideas. I just stop exporting in case I ever need to use them again.) The choice is yours-- delete or stop exporting.
  11. This will work for Windows 11. (No explerience with Mac...) 1--- Right-click on a blank area of Desktop. New >>> Shortcut 2-- On the next screen, type \\server-name or \\IP-Address Click Next. (Obviously, you would not use "server-name" but the actual name of your server!) 3-- On this screen, you can either accept the proposed name for this Shortcut or change it to one that you would prefer. Click Finish. 4-- Test by double clicking on the new Shortcut and it should open Windows File Explorer. (You might have to login first...) In the next step, you will add it to Windows File Explorer: 1-- Right click on your new shortcut. Click on "Pin to Quick Access." You can find it here in Windows File Manager: Your done with adding it to Windows File Manager. However, you can edit the shortcut-- change its icon, name, or a number of other things --by right-clicking on it and selecting Properties.
  12. @LRBP, I look at your diagnostics and I didn't see any reason why things are not working as they should. Only thing that I noticed is that you have two different users assigned to each of your two shares on this server as shown below: (The Anonymizer does conceal the actual share names and Share Access user names!) The point that I am trying to convoy is that you can only access one of these shares at a time as your Windows client computer will allow on one of these Share Access users to log into your server at a time. So as soon as you login using one Share Access user to one share (say, T....g), attempting to access the other share (In this case, p---s), you will get an error message. There is no provision in Windows to logout of a server. (Expect that command line command which I don't really consider a part of normal Windows...) I am not saying that what you are doing is wrong. In fact in real situations, you often want to do exactly that--- Restricting what Shares each client computer is allowed to access! But in a testing situation, it is very restrictive in what types of tests you can perform. Just be aware of the situation as you test. One more point of information. Because we are dealing with Samba on the Unraid side and SMB on the Windows (with the error message being generated by Windows), when there is a failure to successfully complete a file sharing operation, An error code is generated by the the error message by one, or both processes, and sent to the other one. The other then tries to figure out what went wrong to generate an English language version of the error code. In our case, this is Windows and it does not have table of what codes Samba sends so that it can do this. It typically makes a wild stab at the answer. That result is usually meaningless and provides with us with little insight as to what is the problem truly is. (Like asking your dog what is wrong when they have a problem.) Often solving these problems is a case of trying different approaches until we find one that works-- testing various combination of parameters one at a time until a set that works. Personal observation: I have setup six different Windows computers on my home network and two Unraid servers (the last one-- a brand new Windows 11 computer fresh-out-of-the-box --over this past New Years weekend) using the method in the PDF file and never had a bit of problem outside of cockpit error. To add to the complexity, the six Windows machine are setup to be peer-to-peer client/servers. This portion is what required the Network Neighborhood approach. If you have only a single Unraid server on your network, I think I have another approach to integrating your server into Windows File Explorer which will get around a potential problem with Network Neighborhood solution in Windows 11. One thing that seems to becoming a factor is that the Windows Network Profile type must be set to 'Private'! Apparently, MS has made some 'tweaks' to their default settings for the 'Public' type which is giving problems with connecting to servers. (I don't know what the default is for Wired LANs but I would suspect that it is 'Public' for Wireless connections.)
  13. You have to realize that this info is stored in free RAM. As I recall, it has a very low priority on RAM usage. When it fills up (or more RAM is required by other processes), it will toss away the oldest data. This can cause constant disk spin up. (I use the Cache Directories plugin on my Media server-- but not my Backup server --but I scan less than 5000 items out probably 500,000. I have a very simple setup. It seems to work well for my use case.) You can throw RAM at it by increasing installed RAM. You can look at limiting it to caching the items that you really want to see regularly. In my opinion, it will never work well if you are trying to cache 400,000 items. (This script was written back around 2010 and I don't believe that its code base has changed much since then except to fix issues cause by updates to the kernel.)
  14. When presented with this manual login box, look for a check box where Windows offers to save the credentials. Check it...
  15. Now is a good time as any. Remember to post it up in a new post in this thread so we know that you have done it and can easily find it.