Frank1940

I still have two on them left in my Media server. They are both now over seven years old (poweron hours) and still going strong. I have one that is four years old that was pulled and replaced by a 6TB drive. I have it on the shelf as an emergency cold spare. Apparently, they do pretty well after the voluminous percentage of 'bad actors' have expired. I seem to recall that I had five of them are one time. I also have three Hitachi Deskstar 7K1000 in my Test Bed server that are close to nine years old. Unraid with its disk spindown feature seems to be pretty easy on HD's...

Am I correct in assuming that this is a brand-new piece of hardware? If this is the case, I would suggest that you run a 24 hour memtst from the Unraid boot menu. Also, in the future, please post any captured syslogs as straight text (*.txt) files. They are much much easier for the Gurus to read in that format. There is also a Syslog Server included in Unraid. For instructions in how to use it, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601

Yes, those are the ones!

Change these two variables and the user will now be root.

Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-545988

Be aware of this as a possible problem: https://support-en.wd.com/app/answers/detail/a_id/15954

You also have to factor in file size because of file creation overhead.

See Here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601 Also, overclocking of Unraid servers is not recommended. I am not sure what the recommendation would be for underclocking. Try running with stock settings as that is typically the most stable setup. Rack type boxes usually are designed to run in harsh environments but most of them are quite noisy. 😉 Addressing the noise issue is tricky as 'moving air' (think wind) is noisy by itself. (Designing fans that can move large volumes of air quietly against static pressure is difficult. There are some companies that have quiet fans that do so but one almost needs to be an engineer to select which of their products is best suited for a particular application.)

Let me make a suggestion at this point. Look for the temperature plugin on the plugins tab of the GUI. You will find the link to the support thread for that plugin. You should really make your query there. I believe that Z490 is a new chip set. So what version of Unraid are you using. The most recent Beta version has a newer Linux kernel which has support for many of the new chip sets.

Can we assume that you checked to make sure the CPU cooling fins were clean? One thing to consider is the PS. There have been several instances over the past several months where replacement of the PS has clear up situations such as you have described. With 17 data drives, it would probably be difficult to borrow one from a friend. You might want to consider purchasing one from a vendor with a generous return policy. (If you do order one make sure it has a single +12V rail and adequate current rating to accommodate 36-to-48A current surge when all of the drives spin up.)

I waited a while before posting up here as I am not a true expert in walking someone through the steps required. What you want to do can be done. Read through this section on converting file systems on an array: https://wiki.unraid.net/index.php/File_System_Conversion#Mirror_each_disk_with_rsync.2C_preserving_parity Particularly the section entitled "Mirroring procedure to convert drives" Read and understand the steps 10 through 16. The steps detail how to reassign a disk from one position to another. Since you have dual parity, you will have to rebuild parity because the Parity2 calculation is disk location dependent! So don't click the box for Parity is already valid . Personally, I would copy out those steps, paste the text into a text document and print out the instructions. Then mark up the copy, crossing anything that does not have to be done for your somewhat simpler procedure and change the numbers to the exact disk#'s (and disk serial number--using the last four numbers is usually sufficient.) that you will be working in the reassignment. Then make a check mark as you do each step.

It makes no difference. A basic Unraid install only requires about 500MB of storage space. (I ran my first system on a 1GB flash drive. Even today, I am only using a 8GB one.) I would imagine that a 4GB of flash drive storage would handle the most complex Unraid system ever setup.

The question you really need to ask is why you want to do this. OCD is the only reason that I can think of. You should realize that these 'shares' will exist only if you are using Dockers and/or VM's! I don't use VM's so I don't see the ones that were created you decided to create a VM. (I only see appdata. Someone who does not use either a Docker or a VM will not see any of the ones that you mentioned.) Now, you do realize that they are only 'shares' because they are top level directories on a disk. They are not visible to the outside world unless you made a conscious decision to export them. (Bad idea-- by the way!) Furthermore, these are system files that have to persist across a reboot, so they have to stored on permanent media. This has be be either a hard disk or the boot drive which is a flash drive. The files can get quite large and could have significant read/write activity. Not really that great from a reliability standpoint for a flash drive. Most folks will store these on a cache drive and many of those will use a SSD (particularly if they are using VM's!). Plus, I am not sure what the size for the VM images files could be. (The flash drive is limited to being 32GB or less in size.) If you really intent on moving things around, I would suggest that you google unraid.net move VM folder then unraid.net move appdata folder I don't know if those two strings will find everything you need but you can modify them to get you want you for each directory. Remember if you run into a problem, it will make it very difficult for anyone to help you...

This would be a better choice and use the eSATA port. https://www.amazon.com/Mediasonic-ProBox-HF2-SU3S2-SATA-Enclosure/dp/B003X26VV4/ref=psdc_160354011_t1_B078YQHWYW

Yes. The only reason left to run the preclear operation is to 'weed out' any hard disk that have an infant mortality issue. (I always do it but I usually purchase disks well in advance of installation as I always have a cold spare ready to go.) The only clarification I will make to your question is a nit-picker. When Unraid does it, it is actually a clear operation. And one more minor thing, when Unraid rebuilds a disk, it does not do a clear first. It only does that when you add a new (additional) disk to the array.