Jump to content

Frank1940

Members
  • Content Count

    5867
  • Joined

  • Last visited

  • Days Won

    8

Frank1940 last won the day on May 7

Frank1940 had the most liked content!

Community Reputation

299 Very Good

2 Followers

About Frank1940

  • Rank
    Advanced Member

Converted

  • Gender
    Male

Recent Profile Visitors

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

  1. Unraid actually installs itself on a RAM disk every time it boots. (The installation does not take very long since only the Linux components necessary for Unraid to function are installed to this RAM disk. It even scans your hardware to load the proper device drivers during the installation.) From what I have observed, plugins and Dockers apps are also installed in RAM even though they may have the configuration settings stored on a physical device. Thus, once the system has booted, it does not really need access to a physical device to run except to store any changes that you make to Unraid to meet your requirements--- Share names, share settings, server name, IP addresses, etc.) By the way, Unraid was designed this way to reduce the read/write cycles to the flash drive. (It extends the life of the flash drive to minimize this type of activity.) If you need a cache drive, you need to use a seperate SSD or HD assigned to the cache drive slot. Should you decide to install a cache system that are several setup options. The 'Help' icon on the toolbar will give a short explanation of the choices.
  2. IS the flash drive plugged into a USB3 port? USB2 (usually has a black plastic insert) is preferred over USB3 as some systems have difficulties booting with USB3 ports.
  3. This is a different error message. Is the share you are attempting to copy to, have the Share Security set to anything but 'Public'? Do you have any shares on the server set to anything but Public? SMB has some real Gotchas when it comes to users and share access. You can read about the problem here: Be sure to read the next several posts as there are more things to trip up the unsuspecting user.
  4. In a NEW post, attach your Diagnostics file. Tools >>> Diagnostics
  5. Unraid is not RAID!!! The is the first thing you have to get squared away. Unraid can use either one or two parity disks to guard against one or two disk failures (respectively). It will use a cache disk to speed up uploading of files. It will also use that cache disk to store VM images and Docker information. There is a plugin which will allow you to mount disks outside of the array. I think you would find a lot more information yourself if you were to read the this section of the version 6 User's Manual which you can find here: https://wiki.unraid.net/index.php/UnRAID_Manual_6#What_is_unRAID.3F After you have had a chance to read , at least, the "What is Unraid" section, you will find some of your questions and, perhaps, some of the confusion cleared up. At that point, we will be very willing to clear up anything that you are still having questions about.
  6. Try googling that error number and see if any of those solutions will work for you. (I would start with the MS forum results before I went to the broader Internet.) One more quick thing. Does the problems seem to be only on larger files? Try some files in the <100KB range and see if it persists.
  7. What are you doing to remedy this situation? IF you are setting up the Notifications ( Settings >>> Notification Settings ), are you setting up a notification method-- Either SMTP or an Agent)? Are you remembering to click on the "Apply' button at the bottom of each page when you have finished your setup?
  8. You need to provide much more detail before anyone can provide much help. First, what version of Windows are you using (Home, Pro, etc) and which release (1703, 1809, 1903...)? Second, are you browsing to the server using File Explorer or are you using a mapped drive? What messages is Windows giving when it fails to work? A screen capture would be nice here!
  9. If you are truly concerned about data corruption you should have a MB with ECC memory installed. Many of us feel that most 'Bit-rot' problems are actually memory issues (ex., bit-flipping due cosmic radiation, static discharge, or power surges) as modern hard drives are designed to have detect and correct any disk errors as they occur on-the-fly. If the HD can not correct the issue, it reports a read error.)
  10. Try googling unraid dell r520 as Google does a much, much better job of searching this forum than the forum's search engine. (While I could post up a couple of links, you should more quickly find what you are looking for if you searched the result yourself. )
  11. Both of my keys have the level as part of the the file name i.e., pro.key and the other older that I upgrade is plus.key
  12. You might want to try googling this problem (using a portion of the error message like: AER: Multiple Corrected error ) Apparently, it error is coming from something problem with one (or more) of your pcie slots.
  13. IS this diagnostics file from a period of time when you had the problem? What I would like to suggest to you is to run a series of tests using the GUI where you access the PLUGINS tab and the APPS tab (trying to install a new plugin). Note the date and time for each when you do this. Then generate the Diagnostics and post them up in your next post. Then the Gurus know exactly where to look in the syslog to see if there are any clues.
  14. Open up the shares in Windows using File Explorer and see if the 'missing' files are there. It is my understanding that excluding a share from a disk only prevents writing new files to that disk. Existing files can still be read. What could be happening is that Plex is attempting to access those files in a read-write mode and that might not be allowed. EDIT: you might want to read through this thread:
  15. I think what step 17 is referring to double check/verify that you have requested the format changes to the proper disks on the setup screen BEFORE you click 'Apply'. Because if you didn't, you will lose all of the data on an 'innocent' drive as soon as it starts the format procedure. As I recall, this is a point at which it is actually quite easy to make a mistake. That was why I had a table prepared with what the settings were to be on each step and I checked-off each step as I did it!