• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Frank1940

  1. On the boot drive that you created, double check and make sure the there is a folder named EFI- and not EFI If the folder is named EFI- then the boot drive has been setup as BIOS boot. IF that is not the case, connect up a monitor to the server and have a look at the boot process. You might want to take a picture of any error message that you get. (I think that MB is a server-type motherboard and you may have to read the manual to be able to set it up so you can watch the boot process.)
  2. I do not use Plex but I would suggest that you read the support thread for the Plex Docker that you decide to use. I think you would want to set up to use a 'cache only' share for that metadata and make double sure not put it in the docker.img file. Docker does create a 'cache-only' appdata share and I would assume that might be appropriate spot for it. But double check on the support forum...
  3. Try stopping the array from the Main tab and time how long it takes for the array to stop. That will tell you if the 'Shutdown time-out' value is correct.
  4. It is difficult to tell exactly how you are setting up your copies. However, one thing to avoid is setting up two separate copy operations that use the same hard disk on either end of the operation. IF you do it will introduce delays caused by mechanical head movement and disk rotational latency. Another source of delay is transfers of small files. Large numbers of small files require a a lot of file overhead operations that materially affect transfer speeds once the onboard RAM cache is filled. Remember that using the network as it is a prime bottle neck because of its speed. (I have observed this effect myself when I do the monthly data backup of the computers in my home. I generally start all of the computer to doing their backups at the same time and walk away and get breakfast. I do it this way because I don't want to sit waiting for one to finish before starting the next one-- only talking a few GB of data here on each computer.) Another possible source of slow transfers can be the use of SMR disks rather than CMR disks. (I know this is a source of debate but theoretically SMR write speeds are slower than CMR.)
  5. There is also the mc File manager that can be run using the built in Terminal program. If you need assistance in using it, google linux mc tutorial I, personally, have never had occasion to use the Unassigned Devices plugin but there is a support thread for it. Remember it is just a tool for mounting devices so that you can access them from Unraid. What I don't know it where it mounts the devices on the Linux file system. I will ping @dlandon who is the developer of the plugin for you. What you could do to setup an Unraid share(s) for the various share(s) on your Win10 server. Then use Windows Explorer to copy the files across to the Unraid server. This would be as fast as doing the copy via an SMB share mounted using Assigned Devices. (Unassigned Devices can be used to attach actual physical drives on the Unraid server for whatever reason that the user may want to use them for. That connection could be either SATA or USB. (Of course, this would mean that you would have to remove the drives from the Windows server...)
  6. This sentence is confusing to me. Where are the drives physically at? In your Windows computer or on the Linux server? In Unraid, you will find this displayed on the Main tab: The circled red portion is the logical designation that Unraid uses to identify the position of a disk in the array. The green circle is the serial number of the actual physical drive assigned. The black circled entry is assigned by the Linux OS as it boots up. (I believe is is done in order of detection...) (This black circled designation would be used if you want access to the disk from the Linux OS command line.) One more thing. You can not simply assign a disk from a Windows computer to the array and expect its data to be readable. Unraid needs to first format that disk (thus erasing all of the data) using one of these three file systems-- XFS, BTRFS or ReiserFS--- before it is added to the array. You must copy the data from the Windows disk (mostly formatted with NTFS) to a drive previously formatted in one of these three formats. I believe that the Unassigned Devices plugin will read data from NTFS disks. It is also possible to mount SMB shares with Unassigned Devices and copy them across the network.
  7. Let me start by saying that I have been using 'Preclear' to stress test and detect infant immortality failures for years-- the script, the plugin and the Docker. I still have a version of the preclear script on my Test Bed server. Furthermore, I have not added any additional disks to either array for several years now. As a result I have no personal knowledge of any problems of precleared disks requiring a separate preclear when added to the array. First, my comment about that prescript script. It was originally written by @Joe L. back before 2010 as I recall. It has required patching over the years to continue working with the various releases of Linux. There are several versions of it available from various posts on the forum. One problem is that unless you look at the script (and in some cases look for actual changes to the code), you don't know what 'version' you are dealing with. If you are using the script and having problems, good luck with getting any issue addressed! If you are using either the plugin or the Docker, there are support threads for both of these and you should be asking about any problems you are having in those threads!
  8. I am going to make a comment here while pinging @JorgeB who is much more of a Guru than I am. The problem with Marvell controllers is that they mostly work. (However, that is like using a parachute that mostly works.) When they don't work (or work right), the problems are varied and differ widely in their symptoms. If you decide to use one, just realize that when you have an array, disk or data problem, switch to another HBA card, preferably one made by LSI.
  9. Unraid identifies drives by their serial numbers. I just write the last four digits of the number of each drive. That way, I know exactly what drive I am assigning.
  10. The thing I would do is: 1--- Replace the two parity disks with the 18TB drives. (If you have any tendency to paranoia, you might want to do one disk at a time...) 2--- At the juncture, pause and think a bit. You can't possibly need/use all of that additional storage instantly. Modern hard drives are (apparently) very reliable devices. The one thing to really be concerned about is buying into two possible scenarios: (A) a bad design change in a series of drives and (B) a bad manufacturing lot that has a manufacturing flaw that cause an abnormal high failure rate. (Both of these have happened in the past!!!) 3--- In light of the above, purchase and add each new 18TB data drive as you actually need them. (And always have a cold spare drive on hand!!!) Should you require more space instantly, you could do replace two disks at once. But if you do this, a single read failure on any of the 22 disks will cause the rebuilt to fail. (That is the reason why many folks use dual parity!) 4--- Another item to be considered is that one (or more) of your 10TB data drives may fail in the future before you have completed the conversion of the 6TB drives. (Doing this expansion, will require hundreds of hours of all the disks be spun up which will increase the possibility of a disk failure.) You would seem prudent to replace it with a 16TB drive rather then a 10TB unit. This would give you another 6TB of storage each time it happens. (Even if the 10TB drive were under warranty, you could always sell it.) I hope that you are running periodic parity checks on this server to (hopefully) check problems before they become major issues. (I often wonder how folks deal with the decrease in array performance during these parity checks when the checks times are over 24 hours.) I am hoping this is a stupid observation on my part. You do realize that an Unraid server is not a fail-safe device and is not a replacement for a backup of irreplaceable data! That are a lot more ways to lose the data on a server besides hard disk failures. (Many of those ways involve physical damage/destruction of the server itself! With dual parity, the probability of data from these causes is higher than from disk failures on a well maintained server!)
  11. What did the 250GB (I assume you mean GB--gigabytes-- and not Gb--gigabits) of data consist of? Was it 250GB of 1KB files or a few 25GB BluRay .ISO file? Unraid's file over head on HD's will be a major performance hit for large numbers of small files. (I have a very cheap SSD cache drive and I see see write speeds of 90MB/s for Bluray ISO's directly to the cache.)
  12. Interesting observation. On my Test Bed Server, the 'Shutdown' button on the Main tab does not complete the shutdown process. It appears to do most of the 'grunt' work (meaning that the array apparently stops as a parity check is not initiated on restart) and the console monitor display goes blank, BUT the fans never turn off. A quick depression of the power button does not change the status. I have to depress and hold the power button until the fans finally shut off. At this point, a push of the power button will restart the server. The 'Reboot' button on the Main tab seems to work fine. As anyone else made a similar observation? I am puzzled if this is something unique in my system or are others of you seeing the same behavior?
  13. I looked at your Diagnostics file and didn't find any error messages in it. But that was not surprising as it came after a reboot of the server. I did notice that the SMART reports for the two drives (that I looked at) reported a max Temperature of 41C at some time in the life of each drive. That is a bit higher than most of us would like to see. Describe your setup in a bit more detail. Do you have a UPS for the server? Does the server auto restart when power is restored? (Not a really good idea by the way!) What I would suggest at this junction is to setup the Syslog Server. (Use the Mirror to Flash Drive option since it should finish in less than a day.) Directions for doing so can be found here: Then start the array which should start the Parity check. IF it locks up, upload that syslog file. I would really suspect that the parity check will finish without an error since it does not seem likely (from looking at the plugins.txt file in the diagnostics) that there was any disk activity at the time when the power finally failed.) Now having said that, there a possibility that the outage was accompanied by a power surge which might have damaged some thing.
  14. Connect up a monitor and keyboard to the server. Then see if you have a login prompt. IF you do, log in and type: diagnostics That will save the Diagnostics file to the logs folder/directory of your flash drive. Then type: poweroff That should shut the server down and you can remove the flash drive so you can plug it into your PC. Now upload the entire Diagnostics file with your next post. IF neither of these works, you can try a one-second push of the power button. That should do a normal shutdown. If that should fail, you can push the power button until a shutdown is forced. (This will be an another unclean shutdown...)
  15. There are a couple of vendors on e-bay who are based in the USA that have provided hundreds of used boards (apparently, from retired server farms) and have good reputations. They also update many of the boards to the latest IT-Mode software. These boards do cost a bit more... LSI is now a part of Broadcom and they are still selling the older LSI chip sets to people who want to buy them. (Broadcom is supplying actual boards that use the latest chip sets and you can find them on their website.) Manufacturer(s) in China have copied the old LSI boards (down to the paper labels in some cases) and are selling them as new LSI boards. I call these 'counterfeit' as the names of the these manufacturers are not provided. The quality of the remaining components required are unknown and those buying one is a bit of a gamble. So if you buy one, the vendor who sells it to you is your only point of contact for remedy if you have an issue.
  16. Be careful and vet the vendor carefully as you are 'buying' the vendor and not the board. Try to buy from a vendor in your country as you will have more options for resolution if the product is not as represented. (Buying LSI boards is a bit of a minefield as LSI no longer exists as a separate corporation. Buying 'new' boards is a real issue as there are manufacturers making counterfeit older model boards with the LSI logo.)
  17. Make that the backup is not to a drive (or folder) on the array. Keep a backup on your PC. If you have a USB failure, you may not be able access the backup on the array.
  18. You might want to have a look at replacing the case. That way, you may be able to reuse the hardware in your present server. There is a whole section of the Forum devoted to Hardware and cases are a big item there. Look here: You would probably be looking at rackmount cases as vertical tower cases with high drive slot counts are a disappearing item. Dell does have a reputation for using non-standard size components and I am not sure what you may find with regard to that motherboard and power supply. Best to measure and see if they are standard size.
  19. Actually, you can do it more than that but not with the Automatic Web tool. IF you should ever need a second replacement (within the one year period), you would have to contact Customer Service and explain the situation.
  20. After this initial panic phase has passed, have a good look at that flash drive. If only the plastic case is destroyed and the chip is still attached to the plug, you might be able to get the files off of the remnants.
  21. The portion that is bold is the directions to generating and downloading the Diagnostics file to your computer. Attach the entire file .ZIP file to your next post. It will contain the log file was well as other files that are used that the Gurus use in diagnosing problems with Unraid. Let's address one issue at at time. (Makes it easier to solve problems that way!!!) The cache drive should wait until you have resolved the errors with disk 2.
  22. This is a choice that only you can make. How fast are using up Storage space? It took me about ten years to accumulate 18Tb of 'stuff' on my Media Server (out of a current total of 24TB). What I tend to do when deciding on what should be my parity size for a potential upgrade is to look to see what the total additional storage space I will get with a certain size parity drive setup without increasing the drive count. I also figure that I will have old data drives fail and their replacement (as I plan on purchasing future data drives based on the parity drive size) will add the additional storage as the years go by. In the case of my Media Server, I can see no reason (as an example) to make my parity drive size of 14TB as the first data drive replacement would provide sufficient storage space for a minimum of three years (to a possible six years). And I already have three 3TB drives in that server that are over six years old. So I can expect that these drives will need to be replaced in the few years. SO I would be adding storage capacity faster than I was using it up. With my current 6TB parity setup, I can go to 36TB of data before I need another major jump in parity size. That is a good five to seven years down the road! One thing I am reasonably certain of is that cost jumping to whatever new parity size will cost less than it does today. Back in 1989, When I bought my first hard drive of 10MB (that's right!!!) for cost of (approximately) $500.00, I never dreamed that in 30 years there would 18TB drive for $400! (The PC I installed it in had two 5-1/4" floppy disk drives and those floppy disks had a capacity of 720KB.) Back in those days, the very idea of an individual needing that much storage space was simply inconceivable. I doubt if there was any data processing center in the entire world, in those days that had that much data stored (and if they did, it would have been on magnetic tape).
  23. If you have a 12TB parity, look for a 12TB data drive to replace that 10TB. You already have to buy the first 10TBs so the cost for the extra 2TB is only the difference in cost between the two drives. (I have always considered warranties as tool of the marking department. They imply nothing about the reliability of the drive model itself. Its length is a tradeoff of increasing current revenue vs future warrant costs.) (I started out with 1TB drives, moved onto 3TB drives and finally to 6TB drives. Each time, I made the shift, the cost of the new larger drive was about the same of the initial cost of the previous drive. I realize that there was an artificial 'sweet' spot created when folks were shucking 8TB USB drives but that I still think that was a marketing tool to dump certain excess inventory of certain models of 8TB drives. They could bury any drive model inside that USB case as long as it was an 8TB drive!) EDIT: Plus, if you do exercise the warranty on a drive, you will most likely get a "refurbished" drive. If you spin your Unraid drives down, they seem to last a long, long time once they get by the infant 'mortality' stage. Google 'bathtub curve' if you want to see what the failure curve of hard drives looks like. Oh, one more thing, Unraid does not use its array drives in quite the same way as a normal RAID setup. So the 'Enterprise' drives do not seem to be really required for long drive life. Plus, I again suspect this designation is more of a marketing tool than a true indicator of a superior design. It is old "FUD" marketing (Fear, Uncertainty, Doubt) ploy. IBM first used it 60 years when third party vendors were finally allowed -- A government-mandated consent decree as I recall-- to install tape drives onto IBM mainframes.)
  24. You need to think this through before you make this move. Do you really have a need for additional storage space in the next 12-to-18 months? I would never have jumped to a 12TB parity drive when I had 10TB data drives (or I never would have purchased a 10TB data drive when I had a 12TB parity drive)! If you buy a new parity drive, I believe that largest drive you can get is 16TB at this time. Perhaps by the middle of next year you might be able to get a 20TB drive which makes more economical sense when replacing data drives to gain additional storage space--- $$/TB of additional storage space. (If spend $300 for a drive to get an additional 2TB of storage space, you pay $150/TB. If you pay $400 for 6TB of additional storage space, you pay $67/TB!)
  25. Your Re-allocated sector count is 8. The drive has 33,410 hours (~ 3yrs, 10 months) of power-on hours-- and elderly dive but not unduly so. The question you probably need to be able to answer is were all of these sectors found in the last Parity check or have they been accumulating over a period of time. Now, I am a very conservative, semi-paranoid type of person. What I would do is replace the drive. I would then run that old drive through three preclear cycles and see what happens to it. If the count didn't increase, I would probably keep it as an emergency spare. (As a point of reference, I have a drive in my Media Server with 74220 hours (8y, 5m, 17d, 12h) with no re-allocated sectors so far! And, by the way, that drive is one of the infamous Seagate ST3000DM001 drives! Of course, originally, I had four or five of these Seagates and this is the last one left...)