Frank1940

Members
  • Content count

    4466
  • Joined

  • Last visited

  • Days Won

    4

Frank1940 last won the day on February 23

Frank1940 had the most liked content!

Community Reputation

148 Very Good

2 Followers

About Frank1940

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  1. New life for 4.4.2 system Issue

    This may be true now but I will tell you that you will not be able to upgrade the system by clicking on the 'UpdateOS' button under the Tools menu. That is because everything has to be done in RAM. (There is no physical cache drive with a cache file on it to roll unused processes out to when RAM become short.) While LimeTech has never made a definite statement on RAM requirements for version 6, I can tell that experience has shown that 4GB is about the minimum amount unless you enjoy random problems after a few plugins are installed that provide increased functionality that most folks enjoy having.
  2. Moving partitioned drive into array

    I believe the answer is 'No'. I am basing this response on the fact a partition which was placed on HD's by a certain MB manufacturer's BIOS caused all sorts of problems with assigning drives to the array.
  3. Empty config and syslinux folders on usb

    Do you have a copy of your .key file for that Flash Drive? If you do it will make it a lot easier to get a new one. Basically at this point, you are going to need a new Flash Drive. Use a name-brand USB2 Flash Drive with a capacity between 8GB and 32GB. (New is preferable, but lightly used would also be a good choice.) Download the latest version of unRAID and load it up on that Flash Drive using the instructions that LimeTech provides on their site. If you have the old .key file, read here on how to get a replacement key: https://lime-technology.com/replace-key/ IF not, send a E-mail to them and explain what the situation is. They usually bend over backwards to help their customers. You will need the GUID number of the Flash Drive, and you can find it by booting up the new flash drive in your server and on the Main tab, look under the Boot Device, and click on 'Flash'. Now, you have to be able to figure out which specific hard drives were assigned as parity drive(s), cache drive(s), and data drives. Cache can be the one that is the most difficult. (Finding the parity is actually pretty easy, it will be the one that is not formatted.) You want to know the manufacturer and last four digits of the serial number of the parity and cache drive if you can determine them.) Hopefully finding the cache drive will be easy if you have one. If you don't know which drive is the parity drive, assign all of the drives as data drives and start the array. The one that is not formatted is the parity drive. Stop the array and reassign it as parity (Making any other changes needed) and restart the array. (STOP--- if you have more than one drive unformatted and get things sorted out. Don't format any drive without deliberate considering why it is necessary as formatting will guarantee that if there was data on that drive, you will lose all chances of recovering it!)
  4. Making an older AMD GPU available for my VM

    I question your even looking at trying to use this CPU to setup a VM. That thing just barely has enough horsepower to run a a base unRAID NAS. See here: https://www.cpubenchmark.net/cpu.php?cpu=AMD+Athlon+64+X2+Dual+Core+4200%2B It will actually have performance issues if you attempt to run a simple dual parity NAS setup.
  5. Empty config and syslinux folders on usb

    First thing. Do not panic. You have not lost any data (on the server's HD's) due to a problem on your flash drive. Second thing. Do you have a backup of your flash drive? If you do, we can start from that. Do you have a up-to-date printout of your drive assignments? Third thing. Pull that Flash Drive and copy everything that you can off of it into a folder on your PC. Fourth thing. Run a chkdsk on the Flash Drive on your PC and see what that recovers. Let's see where we are at this point.
  6. SMB shearing issue

    Normally, installing a new HBA will be transparent as unRAID 'remembers' disk assignment by the serial number of the drive. However, there are a very few HBA's which 'fool around' with the reporting of the serial numbers. It is best to print out a copy of the disk assignments (using the Main tab) and have it handy. (As with all Murphy's Laws, "proper prior prevention prevents problems".) You will probably not need it. As a further note if you are using single parity, if you know which are the parity and cache disks, the data disk disks can be arbitrarily assigned to any disk slot and parity will be preserved.
  7. help a complete noob

    IF you get these speeds through out your transfer you will be doing good. Remember that it is calculating and updating parity as it saves the data. so everything will always be parity protected. The fastest speeds are when you are copying large files. When the file sizes are small, there is a lot of OS overhead with file creation and disk space allocation. For the fastest transfers, go to Settings >>>> Disk Settings and set the 'Tunable (md_write_method):' to "Write Reconstruct". This will keep all of the disks spun up during file writing but it is fastest than the other two choices. (The other choices will only require that the parity disk and the one being written to be spun up.)
  8. SMB shearing issue

    Good to hear. Just remember that in the Windows Explorer it should be \\198.162.1.75 (Note the back slashes!) to see your shares. The forward slashes //198.168.1.75 are used in your browser and should bring up the GUI. Folks often miss fail to notice the difference and then find that things don't work...
  9. SMB shearing issue

    Windows 10 has been a real bear with regard to SMB. And it is not helping that besides the named releases (Home, Pro, etc) that are also the numbered release versions (1709, 1703, etc) and all of them are a bit different when it comes to SMB and security. It seems that what works with one combination does not work with another one! Using Windows explorer (the File manager), in the box to the left of the Search Box, enter \\192.168.1.75 and see what you get. If that does work, install the 'Local Master' plugin (it is referenced in the first post of the "Windows issues with unRAID" thread) and see if your server is really the Local Master. If it is, you will next want to see what computer your Windows10 machine thinks is the Local Master. There is an utility that you can run on your Windows computer that will provide with information about your current networking configuration from that computer's viewpoint. It is called LANscan and you can find it by googling 'Scottie's LANscanner v1.68'. I know that many folks are reluctant to download programs from the Internet and you may want to do a bit of resource first. (I would definitely get it directly from Scottie's website and make sure that you scan it for any bad stuff.) Here is one more item to be check out with Windows10 computers: https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016
  10. I don't quite see what you are doing but I can tell the mv requires a complete Linux path down to the files that it is going to move. Here is a link to the manual for that command: http://man7.org/linux/man-pages/man1/mv.1.html Your command as present proposed will only move files from a top level directory on disk16 named 't' (which would by definition in unRAID also be a user share). By a complete path I mean some like this: /mnt/disk16/Music/t/* It has been years since I have used mv but from reading the description, it will probably only move files and not directories, so it will probably move only the files in the directory but not any sub-directories or their contents. IF you are not familiar with the Linux command line, you should either get a good reference book or avoid using it except when you can cut and paste command examples from experts (with some very minor editing by you). Linux generally assumes that you know what you are doing and does it with any questioning/warning.
  11. Dockers will not stop

    Since you have identified the Dockers with issues, have you tried the support threads?
  12. SMB shearing issue

    Why did you add this? Access by root to shares is not allowed in unRAID for security reasons. I would even question at this time these two additions: ntlm auth = yes NTLMv2 auth = yesv Plus the "yesv" should not be there.... To begin to resolve your problems, let's move forward in baby steps. First, go through this thread: https://lime-technology.com/forums/topic/53172-windows-issues-with-unraid/ It has enabled a lot of folks to fix SMB problems. Pay particular attention to the sections on determine which computer on your network in the Local Master. You really want your unRAID server to become the Local Master. It does require that your server be on 24-7 but it solves a lot of issues that folks have with SMB. Second, don't try to secure shares until you can get public access of the files on the server working. Third, if you are still having problems, tell us what version of Windows, you are using. And post up your Diagnostics file: Tools >>>> Diagnostics
  13. My imagination?

    If you use this method, I would do a parity check thee-to-seven days later just to make sure that everything is still OK. (99+% pf the time it will be but you always want to catch the odd chance that the new HD is a victim of infant mortality.)
  14. Random Shut Downs Getting Very Frustrating

    Take your time in doing your research. Pay particular attention to exactly what you want to be able to so with your VM's. The closer, you want to come to the capabilities of a stand-alone desktop, the higher the requirements (and cost) on the hardware will be.
  15. Random Shut Downs Getting Very Frustrating

    Looking on Amazon, it appears that there are still new MB's available for the AM3 socket should that prove to be the problem.

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.