Jump to content

Frank1940

Members
  • Content Count

    7439
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by Frank1940

  1. Depending on your hardware, 'watching' parity operations can slow parity operations down. (It seems like the GUI can soak up quite a few CPU cycles...)
  2. First before you start editing the Registry, read this post and see if you have things setup this way: https://forums.unraid.net/topic/43381-unraid-keeps-not-showing-up-in-the-network-folder-on-windows-10/?tab=comments#comment-906336 Notice the setting for Network discovery. I suspect that this has to be on. The default was changed from 'on' to 'off' when I got one of the MS security updates a number of months back! Editing the Registry is is something nobody likes to recommend since doing is definitely not idiot-proof!!! So I doubt if anyone is simply going to say "go ahead, nothing bad can happen..." You might want to make a backup of the Registry before you start. You want to be sure you go down the right path and triple check that path to verify you are at the proper point. You have to type accurately (You made a mistake in your reply when you typed "AllowInnsecureGuestAuth" by adding an extra 'n'). (Cut-and-paste is probably a better way to go. But avoid copying the 'line feed' at the end of the instruction--- Those things can really screw things up!) I actually have the feeling that this entry was added to 'turn off' insecure access in one of the Windows updates. I would also bet you have different versions (1909, 2004, etc.) and variety (Home, Pro, Edu) on your two computers. If they differ in any way, the two Windows installations can and often do behave differently! Unfortunately, I have been dealing with Windows SMB issues for so long and made so many teaks that I have no ideal of which ones are now truly necessary.
  3. Read the first few pages of this thread. Be sure that you Unraid server is the Local Master. Be sure that the Workgoup names match on the server and on the Windows client. https://forums.unraid.net/topic/89452-windows-issues-with-unraid/ You can also try to access the server with the IP address by entering it in address bar of Windows Explorer as \\192.168.1.252 Also make sure that these are turned on: and this:
  4. This is an area in which I have no expertise. Pinging @JorgeB
  5. You could stop the current parity check and add the second parity disk. When you restart, a new parity sync will start and both parities will be rebuilt.
  6. In the lower right hand corner of the GUI, you will see a link named "Manual". Clicking on it, and following the obvious choices will get you to this: https://wiki.unraid.net/UnRAID_6/Storage_Management#Replacing_disks
  7. The development of the ReiserFS ceased in about 2009 when the developer was sentenced to prison for murdering his wife. The problem which has risen since that time has to do with the increased capacity of modern hard disks. The file allocation time becomes increasing longer as the larger capacity disk fills up. You can continue to use it but be aware but you may well have problems in the future.
  8. This could be done but I have never heard of anyone actually doing it. Personally, I would do the upgrade from version 5 first. After getting it working, then copy the contents of the boot drive to a prepared flash drive. Then on the first boot of that new drive you will be requested to upgrade the license. See here for details: https://wiki.unraid.net/UnRAID_6/Changing_The_Flash_Device
  9. It has been along time since Version 6 first came out. The conversion from version 5 to version 6 has a few landmines that have to be avoided. Here is a link to the Wiki on doing the conversion. https://wiki.unraid.net/index.php/Upgrading_to_UnRAID_v6 Now, not of it is applicable to every upgrade but it covers virtually all of the problems that were encountered by the hundreds (or even thousands) who have already done it. Be sure to notice that there is a link to the "short and sweet' instructions at the top of the Wiki. Those are the instructions for the folks who were running a simple NAS.
  10. Confirmed for Firefox (81.0.2) Does not happen with version 6.8.3.
  11. Remember that your 'static' IP address is being provided by normal DHCP process as far as Unraid is concerned. I am assuming that your router is using the MAC address of the server NIC and assigning it the reserved/static IP address via DHCP. About doing it. If you are concerned at all, than make a backup of the boot/flash drive before you start. You can do this from the Main tab, Clicking on "Flash" under 'Boot Drive', then on the 'Flash Device Settings' tab, click on the "FLASH BACKUP" button.
  12. The problem is usually on the Windows end of the equation. Remember that Windows often will update itself and 'break' something. Many times folks are not even aware that the update has happened. Plus, you will want to check to see that you don't have a Windows Credential that will automatically log you onto the server. ( Enter credential manager into the search box on the Taskbar.)
  13. @AcerbicMaelin, I would suggest going one step beyond what @jonathanm is suggesting! (I did both of my servers a couple of years ago now.) I actually made up a table of steps to convert each hard drive-- complete with the disk descriptors that I would be using for that set of drives involved in each conversion. I checked off each step as I went. This is not something, you will being doing in an hour or two. It will take you the better part of a week depending on how full your drives are. Without a written outline of each step and check-off of each step as your proceed, it is so easy to get confused...
  14. By the way, the user, root, is not allowed as a SMB login because of security issues.
  15. Read the 5th paragraph in this post: You might want to read the balance of the thread if you want a really good discussion of some of the "gotcha's" in SMB. Using the IP address to gain access to the server is a workaround to establish a second connection that usually works.
  16. I, personally, am not a Samba programming Guru. I only want to know the rules of what works. I know a lot of the rules. I will play using those rules... That is the limit of my expertise. IF you want to know more, you will have to start googling and reading what true experts know. You should probably be going to the Samba support forums and the Samba software development group to ask your questions. You should first realize that there is a SMB security layer on top and a Linux security layer on the bottom and the Samba layer is in between. (The same can be said of the files systems. And these two file systems don't really map one-to-one. If you know where to look, you can find some real issues--- starting with Linux being case sensitive and Windows not being so!)
  17. I am not a real-dyed-in-the-wool- Linux Guru but I suspect that what you are seeing the Samba process running on the Unraid server. Samba is running as the user nobody in the users group.
  18. I would suggest that you google linux user nobody and read the various posts. As I understand it, if you access the server without a valid password, you are given 'guest' access privileges and not assigned the user name of 'nobody'. (In fact, I would suspect that you have less privileges than 'nobody'. Be sure to read that link that I provided where LimeTech goes through much of what is happening behind the scenes. ) I understand that this 'guest' type of access can be turned off but doing so would require that you have to log on to have even read access on SMB shares. LimeTech has choose not to impose the restriction as it would really break a lot of simple file sharing setups! Furthermore if you look at the members of the group 'users', you will find that the user, nobody, is not a member of that group. You have to understand that all of these 'conventions' have been developed over many years and with much careful thought put into them by a great many people. What us casual users have to do is to understand the rules and not expect things to work as how we would want them to. Unraid expects to find that all SMB files will have the following owner/group and permissions assigned to every file: -rw-rw-rw- 1 nobody users And the following to each directory: drwxrwxrwx 1 nobody users If it differs from the pattern, you can expect to have issues at some point.
  19. The user, nobody, is the owner of this share. The name describes who this owner is. As I understand, there is no 'nobody' user. So he does not really exist except as a place holder. So the write permissions are controlled by the Group and Other permission bits. Since they are turned off for this directory, you will not be able to write to it. Remember that Samba is running on top on Linux and your access to files is through Samba. At the top, are your SMB permissions to the resources that Samba has access to using the Linux file permissions that are underneath the Samba layer. If the Linux permissions deny Samba access to a resource, you can't access it regardless of your SMB permissions. (Understand that Samba is a Linux process that provides SMB services...)
  20. In the permissions scheme for directories, the execute bit must be set in order to change (cd) to the directory. Not have it 'set' can lead to wonky behavior. There is a tool which will fix all of these problems with permissions called New Permissions. Tools >>> New Permissions (It is normally installed when you install the Fix Common Problems plugin.) You can use the Unraid-supplied Permissions tool but you have to be careful not to run it on certain system files/directories used by such things are Docker and VM's. (I understand that it will normally exclude these directories but I have not have occasion to use it for many years so I can't speak from experience.) Most of the time, the reason that folks end up with wrong permissions is that there is a Docker, Plugin or VM that is setup wrong. You should be able to figure out what application generated these files and directories and that is the place to start. I am going to include a link here about SMB 'users' and the many gotcha's that folks will encounter. The reason I am doing this is that Windows throws-up cryptic error messages when SMB issues happen. https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392
  21. You might want to consider using this method. It, basically, employs the same scheme of using an alternative way of writing to the array.
  22. Why are you so insistent to find it through the use of the command line? You could easily grab it from the GUI. (Just look for it on the Main page..) Once the assignment is make during boot-up, it will never change. Point of disclosure: It has been forty years since I last did much Unix(Linux) command line work and I don't remember enough of it to even begin to start to construct an expression to extract that information from the syslog. The starting point would probably be the use of grep...
  23. Start here: https://forums.unraid.net/topic/74208-apc-smartups-setup/ If you don't find anything that makes it work, try googling APC UPS not working unraid.net EDIT: Or return it and get a Cyberpower UPS. (I seem to recall that they are more compatible.) I understand that the apcupsd package that is used in Unraid has nothing to do with the APC company. You can also try the NUT plugin.
  24. AMEN!!! @scott4740 See here for explanation. And good luck. Today, split levels cause more problems than they will ever prevent since hard drives are now larger than 250GB! https://wiki.unraid.net/Un-Official_UnRAID_Manual#Split_level PS--- Most Free does its level best to do exactly what split level setting is trying to prevent!