RobJ

The UNC flags indicate UNCorrectable sectors. This was only a selection of the associated error lines. There should also be exception lines indicating 'media error'. You've got more bad sectors. Sorry.

In a way, that's good, and we can hope that that explains the surprising pending sectors. Another clean Preclear should prove it.

If this were the result after your very first Preclear, then the drive is probably fine, but you would want to monitor it for a year. But above, it looks like the pending sectors showed up AFTER a Preclear, and that should never happen. While the drive looks fine at the moment, I'm not ready to trust it, and I would recommend Preclearing it twice more, only trusting it if it stays perfect through both. Seems too coincidental, but is there any chance the drive previously Precleared perfectly, then just after that finished, you detected a power outage or power spike or nearby lightning strike?

Stopping the array: This is the order emhttp triggers events. In bold, the triggers this plugin uses. Thanks, you work fast! I've been dabbling with an event driven, plugin friendly version of CacheDirs, and I had selected 'started' and 'stopping_svcs', so that CacheDirs is the last thing started and the first thing stopped, with the array. Seems like a better option for most users than editing the go file, and handles shutdown too. If response is delayed from Tom, there is 'driver_loaded', but may need a flag file to avoid a possible second start, plus insertion into the shutdown sequencing somewhere. Probably too simple an idea, but could it just start when the plugin starts, and stop when the plugin is told to stop? Again, might need a flag somewhere if plugin is otherwise stopped and restarted (eg. when updated), and still may need a way to detect a true system shutdown, not just someone temporarily stopping the plugin. Your 2 event requests would be better.

Since you are about to trash that parity info, I can't think of any reason to do a parity check. I'd stop it, replace the drive, and start the rebuild now, save some hours.

Just my opinion, but #3 is clearly the best. #1 is not an option, sorry. With those pending sectors, it probably cannot be used to rebuild any other drive that failed, so you don't really have full parity protection now. #3 restores your parity protection the quickest. Once finished, the pressure is off, and you can do whatever you want when you want. But yes, it means a delay in your intended use for the 4TB drive.

Might be nice to have the specific triggering event be selectable per device, so start and stop can be customized, to meet the device's own requirements. For example, that would make it easy to have an 'always on' app disk, using the system 'started' and 'stopped' events, instead of the array starts and stops. And devices could find a way to precede or follow other devices or other processes. Might also be nice to have updated docs on the event system, what events are currently available, and precisely when they occur, and precisely what assumptions can be made about the system when they occur. All I could find so far is this.

The "Raw_Read_Error_Rate=8" is not a problem, because the raw value for that attribute is meaningless. What's important is the VALUE for it, 200, which is perfect. What IS a problem is the "Current_Pending_Sector = 2". As was stated above, that HAS to be zero. If this SMART report occurred right after a Preclear then that is a bad sign. Preclear it again, and if Current_Pending_Sector stays non-zero, I would not use that drive, it can't be trusted.

Just a caution before you throw out the drive too quick, pending sectors may or may not be bad. The numbers you showed do indicate the drive needs some repair work, but do not mean the drive is bad, until after testing it. Technically, 'pending' means 'pending full testing', which happens once you tell the drive you don't care about the current data stored there. You do that by writing to it, so that the drive now knows you are OK'ing overwriting the current data. It then can thoroughly test the sector to see how safely it saves test patterns, and if good, saves the data you requested to be saved there and unmarks it as pending. If it decides the sector cannot be trusted, then it is remapped to a good spare sector. A sector is marked as a 'current pending sector' when it fails to be read correctly, even after applying the error correction info. That can happen either because of weak or damaged magnetic media under the sector, or because of electrical activity (spikes and outages while writing) that have scrambled too many bits in the sector. I tend to call the latter ones 'soft errors', because the physical sector is completely fine, and testing will prove that. If you have had a power outage or sparking or other serious power issues, then the 64 sectors may just be soft errors, and the drive be perfectly fine, once tested and rebuilt.

Drive looks fine, no issues. Popular pass counts are one and three, I run just one pass, but many like 3 passes. Just means the pre-read found a sector where the data was scrambled enough that the ECC (error correcting) info could not fix it. But further testing found that the sector media underneath the sector was good, so good data is now written there. If in doubt, run another pass.

You definitely do not want to use it for your parity drive! If you have time, you might try one more pass on the fourth drive, but connected to a different port. If it still is a slow writer, that won't usually matter too much as an unRAID data drive, since typically you are archiving data to it, not using it for applications. It will be best reserved for old backups, and files that rarely change, operations that involve few writes but many reads.

There's now a case-in-point, concerning the value of re-formatting your v5 flash drive when upgrading to v6, see here.

There do not appear to be any issues evident with any of the drives, apart from a slower write speed for the fourth drive. The only difference is that the fourth drive reads a little faster than the others, but writes half as fast as the others. For the fourth drive, preread time was 11 hours vs. 11.5 hours for the other drives, and postread time was 21 hours vs. 21.5 hours for the others. Write speed was 20 hours vs. 10 hours for the others. You can examine the complete SMART reports for each drive, to see what their firmware is (in the 'INFORMATION SECTION'). Perhaps one of the drives has a different firmware version. If you did all 4 drives simultaneously, then there may be differences in the drive controllers and busses used. It would still be hard to explain writes being much slower and reads faster though.

Nice page, thanks! I'm going to point to it. So much of the wiki is old, written for v4 and v5, which are all 32 bit. Limited memory is probably the reason.

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.