RobJ

Thanks, I've adjusted it. I've also added the Docker settings move, the VM Manager, and the custom notifications. Let me know if you see anything else moved or added.

Testing V6, and found the new syslog download button at the top, thank you! And leaving the one on the bottom is a nice touch, syslogs are so long! I appreciate the addition of a download button for the SMART attributes, but forgive me, I really would prefer a download button for a complete SMART report with all sections, unparsed, unprocessed, untouched from its capture. Any way that could make it into V6 before it's final? And while I'm asking, any chance for the diagnostic dump too?

Thanks, I was hoping I hadn't dreamed it. Sure thought I saw it on someone's Network Settings page. Seemed like such a good idea, simple to select, and an easy way to deal with a nuisance issue.

Done and done. And thank you. Feel free to suggest more improvements!

Thanks, as soon as I have time, I'll turn User Shares on and go there, and document it in the guide. I did NOT know that! Great feature, thanks for letting me know, I'll add it to the guide.

Thanks, I'm sure you are right, but I feel I don't have sufficient experience to write one. As you can see in the Learning about Dockers section, I cheated! I just pointed to what others had written, which seems well written but doesn't completely answer the question. The LimeTech Docker Guide gives a brief intro to them, then shows you how to create them. Jon's User V6 Manual says why they are better, and describes many characteristics of them, but I still don't have a good clear and simple description. After a fair amount of reading, my sense is that a Docker Container is a pluggable layered sandbox, pre-configured, prefilled with sand and toys. Is that anywhere close? I have yet to see the word 'sandbox' used anywhere, in connection with Dockers. It's more than a layer, it's more than a sandbox, it's more than a combination plugin. It sounds a lot like a VM! But I know it isn't. But then again, I haven't used them yet, which is why I would prefer to hear from a Docker user. How would you define a Docker?

I really don't know where to put this, so for now it's here, in the Forum Feedback board, seems sort of related. I needed a thread for anyone to place corrections and suggestions for the new guide to upgrading from v5 to v6. Upgrading to UnRAID v6 It's ready for beta'ing, before the masses upgrade to v6.0 Final. It's understood that v6 is still in beta, and is still changing, so this guide will have to change too. It's weak in some areas for sure, but here are a few areas I'd like immediate feedback. * Minimum RAM for running v6 - certainly that depends mostly on how much you add/install to your unRAID system, but we need a minimum for those running lean, just a simple NAS. In the past, we have generally recommended 1GB as a good minimum, but some have run with only 512MB. Tom or Jon has posted a minimum of 2GB in their Hardware Recommendations, but I'm a little concerned that many unRAID users who haven't upgraded yet and have 1GB will be dissuaded from upgrading. It does not seem to me to be a good reason not to upgrade. Certainly, we want to provide them with reasons why adding more will be good for them. I'd really like to hear from any users that have upgraded to v6 and still have only 1GB, what limitations and issues have you seen, if any? * I thought I saw somewhere in someone's picture of v6 settings a way to change from eth0 to eth1. It's not in mine, so did I dream it? Or does it only appear if you have multiple NIC's? * I don't have User Shares turned on, so that's probably why I couldn't find any Mover settings. Where are they and what are they? * We used to advise users about certain performance improvements, one of them being the 'blockdev --setra 2048' loop. Is that still useful at all in v6? Are there any performance tips, tunables tweaks that might be recommended to new upgraders? * It's especially weak in the Dockers sections, and in the VM's sections. I'm hoping users with appropriate experience in either will help out, add whatever they think should be there. * Would like advice as to how to notify users of this guide. I think I may have 'spammed' enough places, mentioning this guide, but I am thinking of adding a link to it in a post in each release announcement, if that seems right to others? If not, any advice? I'm sure there are holes and inaccuracies in the guide. I appreciate any help to fix them. I decided to add credits at the bottom to all those who have helped or whose words I've used. Frank1940's help was especially great.

You need help? We've got lots of helpful people! So take a deep breath, and try to relax. If you are worried about data loss, we can reassure you that it's very rare here. Many problems turn out to be simple issues, like a loose or bad cable or connector. NEW! Try the Fix Common Problems plugin! But first, some guidelines that will both help us help you and help you get the help you need sooner! Almost always, the most important thing you need to do is capture your complete syslog, BEFORE YOU REBOOT! We usually need to see what went wrong BEFORE the reboot, because once you reboot, it's lost! [For Unraid v6.0-rc4 or later] If networking is working, browse to the Unraid webGui, go to the Tools tab, click on the Diagnostics icon, then click on the Download button (Collect button if v6.0). After the diagnostic data collection is complete, it will save a diagnostics zip file to your computer, to the download location you specify or is configured in your browser. This zipped file is ready to attach to a forum post. It contains a copy of your syslog with DOS friendly line endings, copies of SMART reports for all drives present, copies of your system and share config files, and a technical file describing your array, including all of the content on the Main screen. Once you obtain this diagnostic dump file, you can skip the next paragraph because you already have the syslog, and you can skip capturing the SMART reports below, because you already have them too! If networking is not working (and you have Unraid v6.0-rc4 or later), then if you can login at the console command prompt, you can type diagnostics, and you will get the same diagnostics.zip file in the /boot/logs folder. You can then shut down with powerdown and take the flash drive to another computer. [For v6.0-betas through -rc3, OR if you only want the syslog] If networking is working, browse to the Unraid webGui, go to the Tools tab, click on the Syslog icon, then click on the Download button. (Prior to v6.0-beta15, it's at the bottom.) After clicking the Download button, it will save syslog.zip to your computer, which is a zipped file containing syslog.txt, which is a copy of your syslog with DOS friendly line endings. The zip file is ready to attach to a forum post. (Since syslogs are highly compressible, we appreciate them being attached as zip files!) If no network, then you will have to capture the syslog from your server console. Please see Capturing your syslog, and use the 'All Unraid versions' method. Move the flash drive containing the syslog to your workstation, where you can attach it to a support post. Is it a problem with a hard drive? Then we will probably need to see a SMART report for each drive giving errors. If you don't have the diagnostic dump file from above, please do so via Tools-> Diagnostics, and make sure each SMART report is available to be attached with the syslog. In some problem cases, a drive is not responsive, so you cannot request a SMART report until AFTER rebooting. Just remember to get that syslog before you reboot! Time to create a new support topic! A new one please, don't hijack someone else's topic. Browse to the unRAID forums, and go to the General Support board in the unRAID V6 section, or other board as appropriate, such as Docker, KVM, hardware build, etc. (Make sure you did not go to the General Support board in the v5 section!) Click on the New Topic button in the upper right. Enter a descriptive subject that summarizes the problem. Remember, we have seen a lot of problems, many very similar, so your subject should try to be a little different. First, tell us the exact version of Unraid, the plugins and addons you have loaded, and what hardware you are using. You can tell us about your hardware either here in the post, or in your signature. Now describe the problem, what exactly goes wrong, what errors you saw (exact words please!), what you were doing at the time, what steps you have taken to fix it, anything that helps us fully understand the problem. The sooner we understand what the real problem is, the sooner you get the right help. If you have it, attach your diagnostics zipped file. If not, attach your syslog and SMART reports (if any), preferably zipped. If it's too big, you MUST zip it. If it's useful, attach any screen captures or pictures you have made. You may wish to zip everything into one file, or if too big, into separate zip files. Preview it, then post it. If you've been asked to post a diagnostics file (or anything in addition), DO NOT add it to a previous post: Please create a new post with the requested information! Yes, we've asked for a lot of information, but it's to help you. Please don't make us beg! We're just volunteers, with limited time and lives of our own! Do you believe you have found a bug? Create a support thread in Bug Reports, and describe the problem according to the guidelines above, and tell us why you believe it is a bug in unRAID. Some additional guidelines - * Syslogs need to be complete if possible, not just excerpts. We often need to see where the errors start, and we may need to see how the drives and subsystems are set up. * Please don't process the syslog in any way. We do not want syslogs in a .rtf, .doc, or .pdf format. We want it intact in its original raw text form, just the way you captured it. * Make sure you have upgraded to the latest version, if possible. It's frustrating to spend time helping someone, only to discover it was a problem long fixed. * Please don't ever say "latest version", of anything! Always specify the exact version number of whatever software you are referring to. We can't know which versions you were aware of, and we don't know if you are referring to the latest official version, or the latest beta or RC. And in a month or 2, or worse a year from now, no one will know which version you were referring to. * Try starting in Safe Mode, without any plugins or other addons. Does the problem still occur? Then repeat testing with and without various plugins and addons. * Are you overclocking? Don't! Try restoring all CPU and memory timings and voltages to their stock settings, then see if the problem still occurs. * If you take a picture, make sure it's viewable, no glare. * If you try to capture part of the webGui screen, temporarily drag the browser borders in, to make a much smaller picture. * Is the problem repeatable? We need to know that, so please test, and if repeatable, report the steps that cause a repeat. * If the system crashes completely and there is no way to capture a final syslog, then start a tail on the unRAID console or Telnet session (tail -f /var/log/syslog). * Once the problem is solved, modify your original post, and insert [solved] at the beginning of the Subject line. Moderators: feel free to lock a solved topic. PLEASE do not privately ask the moderators or other users for personal support! Helpful moderators and users are just users like yourself, unpaid volunteers, and do not provide official support, so it is better to ask support questions on the forum instead. That way, you get the benefit of having answers from the whole community, instead of just one person who may or may not know, or may be wrong, or may be unavailable. Plus, you will probably get faster help. And, other users in the community can benefit by learning from your problem and its solution. Moderators: please feel free to edit this post.

I don't think I saw whether you made sure your network chipset supports it, and has the g flag turned on. Have a look at this older wiki page, perhaps something will help you.

I'm a bit red-faced here! I knew about the Help button, used it a bit on the Main screen, but had no idea how extensive the help is for most of the settings pages! Never even tried it(!), needed a hint from Frank1940. I'll rewrite some of it now, and add Frank's suggestions ...

bonienl, I've been working on a guide to the v6 upgrade, found here - Upgrading to UnRAID v6 I wanted to compile in one place all of the v6 related info that a v5 user faces when trying to upgrade (there's a lot to deal with), and the guide includes two large areas you are directly involved in. If or when you have time, would you mind reviewing the Settings section. It's essentially done, but subject to review and any final improvements. You are welcome to rewrite anything yourself if you choose. The other area of yours is the Plugins section, but I haven't gotten to it yet. You are welcome to write something yourself if you like, or I'll get to it, synthesizing summaries for the most important plugins with appropriate links, and then I'll request your review again. By the way, you are listed in the credits because I have used some of your words already, but I forget where. You (and anyone else) are welcome to critique anything you see on the page. The more critiques now, the better it will be later. I'm hoping the guide will lighten the support load, once the full user base begins the upgrade. But I do understand if this is not of interest to you, we all have busy lives.

Thanks Squid, that explains it. This certainly is not a satisfactory situation, a visible refresh that does not appear to do anything, and a hidden refresh that does make changes but is apparently set too long to be effective. Two independent refreshes that are not in sync... Can't wait to see it! Thanks for all your work here, bonienl!

With apologies, this is my second post here that's not plugin related, but I'm not sure where Dynamix issues should be posted. I'm reluctant to post minor things in the main release announcement thread, and it's probably covered already somewhere in the Defects thread, but I only found bits and pieces related to it here and there (but perhaps the bits and pieces add up to a whole, so old news). Please ignore if you have already fixed this. The attached picture shows all 4 cases of the spin/temp display 'regression', drives that are spinning with and without temps, and drives not spinning with and without temps. Drives 8, 9, and 10 are spinning, forgot to verify spin status of drives 1, 2, and 3. Note: this is just a display problem, not the "drives won't spin down" problem, all my drives do spin down correctly. Refreshing the page never seems to correct the above, not manually through the browser page reload or clicking the Refresh button, or automatically through the page update countdown timer.

I would like to request a few things, hopefully before v6 goes final, but whenever you have time. When viewing a support post, saw there was a need for a SMART report, and went looking, found nice options for viewing various SMART report sections but no way to download a complete SMART report. I imagine it's already on your to-do list, but a button to download it would be nice, listed with the other SMART options. I suggest a file to download named "smart_modelname_timestamp.txt", zipping is not necessary. (A file name without any spaces *may* be a little more trouble free for the newest users.) I went looking for a way to download the syslog and finally found it at the bottom of the Tools/syslog. May I please request that the button be moved to the very top, immediately visible to any user? It is nicely implemented, saves a "syslog.zip" locally, containing a "syslog.txt" with DOS friendly line endings, easy for users to attach and easy for helpers to analyze. The only improvement I could suggest is adding a timestamp to the "syslog.txt" file name, eg. "syslog_20150331.txt". My biggest request though is an enhanced download for troubleshooting purposes, a zipped file containing the syslog, a SMART report for EVERY drive that it can see (in or out of the array), and possibly other diagnostic and log files. Name it something like "servername_timestamp.zip", and add it to the Tools buttons, as something like "Download Diagnostics" or "Troubleshooting". In addition to the syslog and all SMART reports, I would like to see (when you have time to consider it) a text file included (name it "Main.txt"?) that is a text version of the Main screen, containing the same complete layout of all drives and their numbers and status indicators. Include all columns but the View column, and use 3 letter codes for the ball colors (Red, Blu, Grn, Gry, Yel, Ong, etc). By the way, it would be nice to be able to call for the generation of this report from the command line, on those rare occasions when network access is lost, but you still have a working console. Edit: just realized this may not be the right place for this post. Sorry. Will move it where you suggest.

You may be right, I'm going to have to think about that. It was my feeling that many veteran unRAID users would balk at reformatting. I'd like to hear more views, from both fresh users and veterans.

I don't think they are ready to announce it yet, but they have been working hard on it for awhile. By the way, I've now copied a little of yours, will copy more later. Thanks, you are now listed in the credits. You (and anyone else) are welcome to work on it too! Very true, I've mentioned both of those in the wiki page.

Nice work Frank! I've actually been trying to do the same, on the wiki, Upgrading to UnRAID v6, woefully incomplete. With your permission, I may pull a few things from your work? I'll try to give credit, as I'm also planning to draw from the comments of a number of other users too. I'm hoping to make it a comprehensive resource, but yours is already fine for many users, all they need.

I noticed 4 items, but cannot say if any of them are directly related. I can confirm what you have said, preclear of sdg is apparently successful, but is not identified as cleared. I suspect the problem with the Parity drive is 'confusing' UnRAID. * BIOS is a little old, from 2010. Syslog shows a number of ACPI workarounds, a little more than normal. If you can find a newer BIOS for that board, it *might* help. * You have IDE emulation turned on for 2 of your SATA drives. When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode. Performance to Disk 3 and your Cache drive should be slightly faster, and a little safer. * You have stations all over the web attempting to connect to your machine, so I have to assume you have it set in the router's DMZ (sic?). Most failed, but some telnet attempts appeared successful, both local and from outside your net. A serious sniffing attempt was made from 42.116.99.53, using various user names and ports. I'm not an expert here, but this sounds incredibly dangerous! * Parity drive (sdh) is not configured correctly. It is a 4tb drive but is configured for 2.1tb, as if >2tb support was not available when drive was prepared. Usable space on it is 1.99tb, usable space on the true 2tb drives is 1.81tb. On array start (each time), the system appears to recognize that something is wrong, and rewrites the GPT entries to the Parity drive, reports unknown partition on it, but does NOT proceed to build parity, apparently accepts it as correct! When you added the new drive as Disk 9, the GPT entries were again written to sdh (the Parity drive), then an MBR written to sdg (new Disk 9). It's possible the GPT writing to sdh caused an execution path that bypassed the already precleared test for sdg. Perhaps the discovery of unknown partition on sdh set a flag that affected the testing of sdg. You might email Tom and link this post.

Can you attach a zip file of all the preclear reports? I'm afraid I won't have time until evening, but someone else may. Hi Rob! Thanks for getting back to me. Attached are the pre_clear reports. Some are older. The drive I was trying to clear is /dev/sde No problems at all in any of the preclear reports. Drive is perfect, and correctly precleared. I'm out of ideas. DO you happen to have the syslog for the session where it rejected it? Perhaps a clue will be there. If no syslog from then, would it be possible to try adding it again, and grab the syslog after, and attach it here?

Can you attach a zip file of all the preclear reports? I'm afraid I won't have time until evening, but someone else may.

Thank you for that. I've updated the Setting up CPU and board temperature sensing wiki page with your info. Please feel free to edit, expand, and improve it. bonienl, I also updated the Perl info on the page (in Step 6), but I'm not positive on the Perl and Slackware versions, or the V6 support as to the whole page. When you have a chance, could you look over the page and either make any corrections and improvements, or suggest them to me?

You have only mentioned a single segfault, what other errors have you seen? By the way, without knowing your hardware, I'd stay with the simple Preclear command, without the -b, -r, and -w options.

The V6 section doesn't seem to have a Plugins board. Would you prefer the Plugin Design board in the Development section? It seems to have a number of other V6 plugins.

Joe L, there's a bug in Cache_dirs, primarily affecting users with the -w option and no includes, no -i option. I discovered it when comparing syslogs from the same user (and confirmed after viewing a number of other syslogs), where Cache_dirs would start at differing points of the drive mounting process. In one syslog, Cache_dirs initiated during the mounting of Disk 10, within seconds of the mounting of Disk 1, resulting in a cached directory list of 3 folders, what it found on the first 9 disks only and not the Cache drive. In another syslog of the same server, it initiated after the last drive and the Cache drive, resulting in a cached list of 7 folders. When it initiates, it builds a cached directory list from what it can find at that moment, and never checks again until restarted. I don't fully understand the problem (because I found exceptions), but it appears that the "at now + 1 minute" is the cause. I assume someone thought that the "now + 1 minute" meant one full minute from now, but it actually means schedule it at the top of the next minute, which could be only seconds away. So most Cache_dirs (but not all) are started at the top of a minute (eg. 17:48:00, not 17:48:13). The simple way to fix that would be to change the command to something like "at now + 2 minutes", which would result in a minimum of 60 plus seconds. My preference however would be 3 to 5 minutes, in case of long transaction replays. A better solution though would be to test for the disks_mounted event, which occurs after all array disks are mounted, and the cache drive mounted, and the User Share system setup. Since mounting is rather quick, this problem has probably not affected many users. It should only affect users with a longer mounting time that started near the end of a minute. After examining a number of syslogs, I would like to strongly recommend always using the -i option, to limit the folders cached to only those truly desired. Using the -w option alone results in ALL top level folders on all array disk being included PLUS all top level folders on the Cache drive. I saw a number of cases where almost certainly unwanted folders were being cached, which wastes memory (especially in 32 bit versions), and may cause the desired directory entries to be flushed out occasionally.

You are trying to thoroughly test the drive, so cutting back on the testing seems a little counter-productive, but yes the preread is the least useful part of the testing, so skipping it shouldn't affect the result and would save time.