Frank1940

Members
  • Posts

    9707
  • Joined

  • Last visited

  • Days Won

    15

Frank1940 last won the day on June 1 2023

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)

935

Reputation

86

Community Answers

  1. By the way, in my opinion, the Split level setting should be left at "Automatically split any directory as required". The reason being that the other parameter settings causes more problems than they solve with modern hard drives. They are so large that changing storage location for new files from one drive to another drive occurs so seldom that if a split were to occur that does give an issue, it can be corrected by moving a few files. More important is the "Minimum free space:" parameter. It should be set to be larger than any file that is expected to ever be written to the share. (It is one of those problem areas I was talking about. The 'Split level' parameter overrides the 'Minimum free space' parameter and it can eventually cause a write operation to fail when a file that is forced to be written this disk won't fit!) PS--- this parameter was added back in the days when a large HD was 500GB. The problem occurred when folks were saving material from DVD copies in a folder and file configuration. As you may realize the movie's video is in several .VOB files of exactly 1GB in size which must be played subsequently. If these .VOB files get split across two disks, there will be a pause in playback which could occur in the middle of a word! OF course, this was totally unacceptable...
  2. IF you turn on the help (or click on the 'Split Level', you will get this:
  3. NO! It is not off by default. BUT, it is stored on the RAM disk. (Unraid sets up the Linux installation on a RAM file system.) You can find it by going to: TOOLS >>>> System Log It is not stored on physical storage because there is no really good place to put it. (Believe me this has been debated before and every location has its drawbacks!) In case, you did not know it, there a manual for Unraid. You can locate it by clicking on the DOCS on the top of every Unraid webpage or on the 'Manual' link at the bottom right-hand corner of every GUI page.
  4. I run back through your numbers and it does appear that there some discrepancy. Make sure that there aren't any lost-and-found files anywhere. Make sure that you refresh the browser window. I don't recall ever seeing any mention of this type of issue before... Now, there is one more thing I want to caution you about. You stated that you would moving files from Disk Share to Disk Share. That is fine. But moving files from Disk Share to User Share (and vice verse) will eventually result in some files being truncated to zero file length. (This happens when the copy operation is copying a file from and writing it to the same disk.) mc will allow you to do this. The 'Dynamix File Manager' plugin will not allow you to do this. If this does not fix it, post up your Diagnostics file in a new post in this thread.
  5. First thing, you need to click the 'Compute' link (shown by the arrow), to find the amount of storage actually used by the share. When you do that it will show the storage used and what each disk that contains files associated with that share stored on it. Second thing, as I recall, the circle is the amount of total space that is available to the share on the array. If it is less that the total space on the array, this is because the share has restrictions on what disks it can use for storage of data when it does a write operation. To check/change this setting, click on the Share name on the Shares tab and look for this section: The two settings are circled. I seem to recall that you should only use one of them-- not both for the same share. Either include certain disks or exclude certain disks. (I would do the one which would have the fewest number of selections.)
  6. What type of support are your requesting? You have provided us with zero information about your setup. The diagnostics file uploaded in your next post in this thread would be the starting point. How long was the server up before this crash? What was the status of the server? Power on? GUI or no GUI? Files available or not? Anything on the monitor screen (if you had one attached)? Any new plugins or Docker containers? Were there any power interruptions? Does the server reboot/restart successfully? (It will probably run a parity check on restart if you had a parity drive assigned.)
  7. What happens if you just restart the server? (Unraid is completely reinstalled every time it boots up. Any changes from the install defaults are stored in the /config folder on the flash drive.) You do need a quality flash drive. We need a bit more info to be able to help you. The diagnostics file contains this information. Upload it in a new post in this thread.
  8. See here: If this doesn't work, you might want to try setting things up so that you are not fighting the security measures that both MS, Linux and Unraid are trying to implement to protect user data. Read the first post in this thread and the attached PDF: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/ Granted that it takes some time to set things up but you will then not be playing wack-a-mole with trying to bypass security enhancements.
  9. It is very usual for parity rebuild after a unclean shutdown. Especially since it was the result of a power failure. (I am going to paraphrase your statement-- It kind of defeats the purpose of a UPS.) The parity drive not being assigned is a bit of anomaly. Do you know if there was any disk activity at the time of the power failure? If so, do you know what was being written to the server? You will want to check to see if this information was correctly and fully transferred to the server before the shutdown. If not, you will have to deal with this situation. (There is a way to find those files written about the time when the shutdown occurred but it is a bit tedious.) Any writes to the array while you did not have a parity assigned should have proceed normally. (You don't actually need a parity disk assigned for Unraid to work. In fact, it is often recommended that when one is first 'loading' an array with a massive amount of data to unassign the parity drive(s) until the loading is finished. Then assign parity and allow it to build to provide protection.) Let the parity check rebuild finish. Check to see that it did not find any other issues. Then have a look at the data on your server. One more thought. Unraid is not a backup. It can be a part of your backup solution. You need another copy of any data that is irreplaceable on some other device.
  10. There is one thing that everyone who is talking about the cost of the licenses and the cost of upgrading from one class of license to another--- Here is what may be a big reveal!!! There have been several increases in the cost of licenses over the years and when those prices were increased, the cost to upgrade from one class of license to another was increased at the same time. Was there a window of opportunity to purchase and upgrade at the old price? To be honest, I don't remember. But, if there was, it was a very short period of time! And there was the same moaning and belly-aching at those times. If you wondering why the pricing hasn't be announced, consider that fact that the announcement of the new plan was forced on LimeTech because someone found a snippet of code in the current release of either in Unraid itself or one of the plugins. Unfortunately, this apparently happened before all of the details of the new plan were in place. In other words, you have what could be called 'insider' information in the Securities world. (It is also unlawful to use this information to make a trading decision but it does happen more often than one would hope. So think about how you might use this to your advantage. Remember that in cases of insider information, not everyone has the necessary resources and/or smarts to figure out a way to be on the plus side at the end of the day.)
  11. I also believe that HD manufacturers still provide a utility disk for their drives and this will usually contain a program to perform read-write tests to every byte on the entire disk. Look on their websites for this. I believe that we are down to two manufacturers as a result of mergers and acquisitions now and I would think that their utilities would work on their acquisitions. The long smart test will do the read portion but the write is not performed.
  12. Today's Plus license could be a good option for a lot of folks who want in on the Lifetime license at a minimum license cost and risk. Twelve disks in an array. Think of a server with two 20TB parity drives, a single ssd cache disk and nine data drives. You could easily have a server with a 180TB of storage space! That would be a really great backup server. (That is enough room for about 7200 Blu-Ray movies. and I can't think of why most people would need 520TB of storage that a PRO license would provide...)
  13. You should know this from a bit of thinking. It will cost at least as much as the current upgrade cost to PRO from what level of license you have and will be less than the new cost of the new PRO/Lifetime. You will know this as soon as the formal announcement is made. Whether you will have a window of opportunity to be able to make such a purchase will be your real problem. My SWAG (Stupid Wild A$$ Guess) would be that the new PRO/Lifetime purchase cost is a bit less than the total cost of a five year upgrade option. (This based on the fact that most of the people commenting in this thread have had their licenses less than five years...)
  14. Yes those variables are the 'numbers' for nobody (=99) and users group (=100). This should allow to do anything you want to the resources under /mnt It is not the container that is the only security problem. It is the fact that now all of the members of the users group now have access back to the root of the file system as well as the anonymous user-- nobody. This is called an "elevation of privileges" in security language. Some of us run our Unraid servers in a secured environment so this is not a big security issue unless one of the client computers is compromised.