djg85

Or set the notifications to pick up on errors only rather than report on the state every day regardless. I have alerting enabled however these are just providing daily array updates and with the array status being the last word in the subject line it doesnt really jump out at you on a mobile client so I don't tend to look at them everyday. Thought I'd double check whats set up as I don't recall ever getting a specific failed disk notification for this box and sure enough, alerts are off. Array notifications and warnings were on. No idea why I've not got the most important notification type enabled. Ah well time to check the other servers to see if I've missed that as well 😧

Ah I get it now. I ignored that in this case as the drive I was formatting was new and didn't have any data on it (common misunderstanding indeed trurl). Guess something had thrown things off with the other drive the second time I went to rebuild as I don't recal getting the format option the first time now that I think about it. Makes sense how I have ended up where I am at now. Hopefully there isn't anything wrong with this 5TB drive afterall and I can just add the data back in. Will bear that in mind going forward, suprised I've not been daft before and wiped things 😳 Thanks for your help and prompt responses ☺️

But if its a new drive does it not need to be formatted before it is added to the existing array? The old "Bad" drive had already been removed and only drive I was prompted to format was the replacment which didn't have anything on it relating to this array.

Everything was emulated fine as far as I am aware as it was a few days before I actually noticed the redballed drive. I got asked to format the "new" disk 8 (8TB) when I went to start the rebuild which seemed normal. Cancelled the rebuild as soon as I saw the errors yes then started it again after moving the drive giving the errors to another bay (as you can see this has not gave any issues since). I still have the existing disk (5TB) which I was going to repurpose somewhere else. The New disk 8 should show as having about 4TB free assuming the data on the failed drive was written back to the new drive from parity. So I'm assuming somethings gone wrong during the rebuild and new drive was somehow picked up as an additional drive rather than replacment for an existing drive, am I right? I've replaced failed drives loads of times so the only difference here was adding the additional parity drive at same time (and of course the errors on the other drive causing me to stop/start the process again early on). Guess the question now is, am I ok to simply mount the old drive through unassigned devices and copy its contents to the replacment drive (direct or via shares?). Going by the two screenshots it looks to me like the contents of that drive are missing given the difference in free space.

Not sure if this is a bug (I'll call it my own stupidity for now for doing two things at once) but thought I'd see if anyone else has done this or had the same issue and the best way to resolve. All started with a drive redballing a few days ago. Was the second time the drive had done this however I'm not sure if there is anything wrong with the drive as such or the bay (SMART results shows no issues and last time it failed a preclear was fine which is why it got tossed back in). Anyway thought seeing as it had failed for a second time I'd swap it out with another drive, test the "failed" drive and pop it back in again at a later date if everything passed. It was a 5TB WD Red and as they are quite hard to obtain now I've started replacing them with 8TB drives. Another drive had gave a few hundred errors but hadn't redballed yet so I thought it would be a good idea to add a second parity drive at the same time before the situation got worse. I swapped the redballed 5TB drive (ending 3FX5 in below screenshot ) with an 8TB (ending 7UTY in second screenshot below). I popped the 8TB into another bay as well in case this was causing the issue with the old drive and also stuck in another 8TB drive as well (ending B47D). UnRAID detected both drives so I added one as a second parity and the other to replace the existing redballed drive. Hit the button to start the rebuild and away it all went. Few minutes later I'm checking things and can see another drive has given over 6M errors however hadn't redballed yet. In a panic that this would cause carnage with a rebuild (and certain the bay had an issue and not the drive), I cancelled everything and popped the suspect drive into another bay. After making sure everything was still assigned to what it should be I started the rebuild again and there were no errors. However I noticed once the rebuild was complete that the replacment drive was showing as having very little used space (drive it replaced had about 3.7TB data on it). Can see there have been about 15M writes to the drive (similar number to the new parity drive) so somethings happened but I don't know what. Looking at the free space on the other drives not a lot has changed so I'm assuming the second parity drive has been added ok however the failed drive was not rebuilt but everything marked as ok anyway. So I have the following questions: Am I correct in assuming the 3.7TB of data is now missing (should a parity check not flag up an issue/inconsistancy?). Am I OK to add the old 5TB drive back through Unassigned devices and copy its conents back to the array? Is this a weird bug (that you are allowed to add an additional parity drive as wel as rebuild a failed drive at the same time) or is it something else I did that caused this? I rebooted the machine after the drive redballed. I'm pretty sure I did the same again after all the errors were seen with the other drive but haven't since the rebuild was run. Attached logs and screenshots below of issue in case this helps. **EDIT: Syslog will probably be usless. It's stopped when the drive kicked off all the errors and when I try and open the current syslog I get the following: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 134107168 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(401) : eval()'d code on line 73 ** When redball drive first seen: Issue seen after rebuild complete + second parity drive added: crofs02-diagnostics-20181105-1243.zip

Oops! Been a while since I've had to copy files during an update (or restore)! Many thanks johnnie.black :). Copied my docker config across and have an issue with docker not able to see the configs for anything but thats another issue and I'm sure I've seen some posts about it somewhere. Thanks again

OK, so yanked the USB out and did a clean install of 6.4.0. Copied over my key and disk.cfg. Updated network.cfg with the correct IP details and booted up. I get the web UI now however only the cache and boot disk show. The parity and data drives have been unassigned although do still appear in the dropdown when I select a disk to assign a drive. The array status is "Array Stopped - stale configuration". If I add all the drives again they are all treated as new disks so the parity drive will need rebuilt. What can I do to avoid this and get all the drives to show as before? I trust the parity as it had been checked not too long before the update and there had been no errors or disk warnings prior to the upgrade. Also whats the best/quickest way of adding existing plugins/dockers back? The data was stored in a .apps folder on cache drive before and should still be there. I just dont want to need to go through configuring everything again. This upgrade has turned into a nightmare and I still have another one to do

I was running the latest 6.3.x release and updated to 6.4 a few days ago. I get the following when I restart: The error is the same no matter what boot option I chose in the boot menu. I am running UnRAID under ESXi 6.5 and using PLOP to boot to the USB. USB is detected fine in ESXi and as it starts to boot into UnRAID I don't think there is anything wrong with the USB itself. I also took a copy of it's contents prior to restarting (but after running the upgrade) and there were no errors during the copy. Any ideas on what I can try to resolve this? The server is in a bit of an awkward place to get to the USB which is why I haven't tried putting 4.3.x back on again yet. Posted in the release thread but got no response and I can see someone else posted the same in one of the beta forums, again with no response so I'm hoping there is a fix of some kind

And here was me being parranoid and removing some of the "known" problematic plugins mentioned in this thread prior to rebooting Anyone else using ESXi have issues updating? I get the same error whether I try and boot into safemode or not. Everything was running fine before the reboot/upgrade. I'm on ESXi 6.5.0 and PLOP.

Yeah - I wondered about that. I'm especially curious to know if anyone else has tried the RC (1 or 2) as a VMware ESXi guest. A responder in reply #11 in this thread had issues. I'm wondering if that was addressed. Thanks. John I've got the same issue with the logs reporting USB resets since upgrading to rc2 however have not noticed any performance issues. It seems to give the error every 30-40 seconds. I've not got anything running from the flash drive so can't comment on access/read times from that. I'm currently running without any plugins/dockers as I had issues getting docker to work before the upgrade. Interestingly the upgrade from a previous beta (think it was 15) to rc2 has cured the docker issue I had (my list of template containers was blank despite having several template repositories present on the main docker page). I'm running ESXi 5.5 so it is not only 6 that is affected by the usb resets. I'm also running two unRAID VM's from the same ESXi instance with the other being on 5.0.5 which has no issues.

Just setup a new box with 6.0-beta14b and having issues with Docker. Not used this before as this is my first V6 unRAID install (other machine is on V5). Everything seems to be working however whenever I click on "Add container" then click on "Select a template" I get no options in the dropdown menu. If I click on "Check for updates" I notice the following errors appear in the log.. Mar 15 14:12:00 GARFS02 php: /usr/local/emhttp/plugins/dynamix.docker.manager/dockerupdate.php Mar 15 14:12:00 GARFS02 php: Updating templates... Mar 15 14:12:05 GARFS02 php: #012Warning: unlink(/tmp/tmp-38262951.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157#012 Updating info... Mar 15 14:12:05 GARFS02 php: Done. If I add multiple template repositories I get the same kind of error with one line for each added url. The only difference between the lines is the tmp-xxxx.tar.gz filename. I've followed the guide from http://lime-technology.com/forum/index.php?topic=37732.0 and used repository links from http://lime-technology.com/forum/index.php?topic=37958.0. I've attached an image showing the Docker tab and settings. I've not got a cache drive on this machine yet however will be adding one when it arrives tomorrow. At the moment I'm pointing docker to the first drive on the array and have tried both "docker" and "docker.img" with no success. In both cases the file is created and shows on disk1 but I'm still unable to add docker containers. Also tried checking for updates on the plugins tab but the status for both Dynamix and the server OS are "no update". Dynamix is showing version as 2015.02.25. Not really sure where to go with this so any help would be appreciated

I miss the warning message about running a beta every time I fire up the GUI Well done Tom on finally getting 5.0 out. I was unlucky in purchasing RAID cards that had no 4.7 support so I've had to use the betas all along. Although in all honesty I never had any issues caused by bugs, just human/hardware faults (like when I let someone lift the server and "boomeranged" the usb stick with my unRAID install ). Thanks Tom for providing a new key within 24hours!! Upgraded to 5.0 from 16c last night and all went well. Had to build the parity drive due to other issues recently but that completed at a not to bad 80something MB's and for the first time in about 3 months I have a protected array So... What's planned for unRAID 5.1

So thought I'd resurrect my thread seeing as it's still a work in progress Turns out only one drive was causing issues although it looked like it was just starting to show signs of old age so I'm using it for something else that won't bother me if the drive suddenly dies I've retired the seven 1TB drives I was using and now have a few empty slots for bigger drives in the future. I should have probably mentioned the other reason I thought I had a few failing drives in my original post... Parity speeds are slow, real slow. Now I know I have one of the SuperMicro boards that has had issues but 50-60MB would be fine for the odd parity check tome (although 90-120 would be better ). The slow I'm talking about is in the region of 200-300KB/s. I decided to just start over when swapping the drives out so went from RC8a to 12a. Everything has gone fine so far in copying all my data to the new disks although it took forever partly to do with a port somewhere in the network deciding to drop to 100MB. Both the programs I used for reading the drives only had a progress bar and didn't actually show the transfer speed so I was "irritated" to put it nicely when I noticed the issue (which was about 6 drives in to the 8 I was copying over) Anyway... All my data is back but not protected. I've swapped the WD green drive that was the original parity drive for an existing WD red and that hasn't made a difference. I'm also pretty sure the drive has been moved to another slot as well so that's not the issue either. I've not got any read/write issues on any of the drives and can get over 70MB/s when I read and about 50-70MB/s when I write without a parity drive added. Just tried doing a read with the parity check running in the background and the file transferred at about 50-60MB/s. The system has 24GB of RAM installed but I've got 3GB assigned to the unRAID VM so I don't think the >4GB issue will apply to me. Just upgraded to 15 (not 15a) and issue still the same. I've not got any plugins running (haven't even got unmenu re-installed yet!). Any ideas whats causing this? syslog attached syslog_20-06-13_2030.txt

I'm not aware of any issues however I did have to do a few "unclean" reboots as some of my plugins were miss-behaving so it could be something to do with that. Although if a few drives show the same sort of thing at the same point I'd be more inclined to think one of my controllers started playing up. I've not really had any issues with the H200's since I got them (other than my first post in this forum were I found out they were incompatible with 4.7 lol). Bit irrelevant now seeing as I've got a few 3TB drives so would have had to upgrade anyway. Both cards were on different firmware though. Something I didn't realize until I moved my 3TB drives just after I had done the manual testing. Seems the 3TB support was in a newer firmware so they are both running off the same version now which should hopefully cause less bother in future I don't have any backups. Most of the contents of my unRAID setup are media rips and while the thought of having to re-rip my collection is not a pleasant one it would not be the end of the world. The whole point in me choosing unRAID was because there was the failsafe of the parity drive (assuming only one drive fails at a time) and of course the ability to still read individual drives in a failure, something which I'm now thankful for Well four 3TB drives have just arrived so just need to figure out the best way of setting this up. Going to start a new array and ditch the 1TB drives (and I think my 2TB Seagate - 5YD6TH26). Any other drives showing worrying signs of imminent failure? Fortunately they all seem to be reading so I should be able to recover everything I need. I've got an external E-SATA caddy that I can just slot the drives into but would it be quicker somehow mounting the drives outside the array and copying direct from one drive to another?

Thanks for the reply's guys. I've not been ignoring you, have just been trying to figure this out. Parity is a write off - think there might actually be a bit of an issue with this drive but I've not run any tests on it yet. Gives me a chance to swap it with a WD Red as they perform better than the green drives. I've gone for the good old fashioned troubleshooting method of shoving the drives in an external esata caddy one by one. I've got 4 drives making slightly more noise than I'd like, one wouldn't read two days ago but seems to be working quite happily again now. Most of the failing drives are old 1TB ones that I was planning on replacing soon anyway so hopefully I should be able to recover the data from them before they fail outright. I did notice something crazy earlier today with drive SDO (5YD6TH26) where it showed a few million reads/writes, had no temperature displayed next to it (but was showing as spun up) and had a few errors marked (this was all from the unRAID main page). The logs showed a load of errors for the drive as well but yet it didn't redball it. The drive showed when I connected to it through windows but when I went into it it was empty. Re-booted the server and it was showing again as normal. I thought I had a copy of that syslog but I don't seem to be able to find it now . Hopefully the current syslog and smart logs for all the drives give some ideas. I'm hoping to get 3 or 4 3TB WD REDS to replace all the 1TB dinosaurs and possibly a 2TB Seagate drive that I think may be starting to cause bother. On a plus note I'm now on 12A and seem to have managed to get the box to join the domain which is an added bonus (although can only write to shares as the domain admin which is no good but that's a whole separate thing!). I'm also running without any plugins now as it is a fresh install. Only installed unmenu which I don't really see as a plugin. Was wanting to move most my plugins to another VM so that's another sort of tick out of all of this. unraid_logs_30-05.zip

I have probably a mountain of issues here so hopefully all is not lost My unRAID box has been off for a few months while work has been getting done on the flat and I'm just at the point now of firing everything back up again. I had a drive redball a few days ago however I know there is nothing wrong with the drive as I'd forgotten the backplane was faulty. I've since run an extended smart test on the drive which came back fine (although I didn't realize it would take hours to complete lol). So I set the "new configuration" and re-assigned all the drives (checking the parity is valid option) and everything started up again fine.. This is where I remembered the second issue the box was having before its long holiday. A parity check started when I started the array and this was running between 800k-2MB and a loud clicking noise could be heard within the chassis. I've got 16 drives (14 excluding parity/cache) and have no idea which one is failing. I checked the syslog however this didn't give any answers on the bad drive. What was even more worrying was the amount of errors about bad parity (the check box had somehow been selected to correct parity - something I don't recall having checked before I started the array. I immediately cancelled the check and stopped the array. While only a few minutes passed between starting and stopping the array I am now worried I have a potentially compromised parity drive. So my questions are.. 1. What would be the easiest and quickest way to identify the failed drive? 2. Once the drive is identified what would be the least destructive way of replacing the drive assuming the parity drive has bad data? 3. Am I safe to upgrade to 12a before I try and fix the above or should I wait until everything is sorted. System Specs: unRAID 5.0 rc8a (running within ESXi 5.1) Supermicro X9SCM Xeon E1230 24GB RAM (3GB assigned to unRAID) 2x Dell H200 RAID cards

I've got the X-Case RM420 (Norco 4220) which has the older style fan wall (80mm fans). I've been wanting to replace this for the 120mm version but could not find a UK supplier (or somewhere that would supply the part to the UK for a reasonable cost) so I gave up on this. Problem is one of my 80mm fans is starting to fail and I want to try to reduce the noise of the server so I'm revisiting the idea of replacing all the fans and the wall with a 120mm design. Does anyone know any good suppliers of the fan-wall part to or within the UK? And what are the quietest fans that will work well with this case? Do you really need the two 80mm exhaust fans in the mobo bay or would I be best replacing these as well? If so what would the best replacements be? The case doesn't have to be silent but I'd like to try and reduce the noise without compromising cooling.

Thanks for the advice johnc. Looks like the big three were all causing the hang. Had to install the new versions of sabnzbd/sickbeard/couchpotato to get everything working again. Maybe the links have changed for updates or something. Sickbeard wouldn't install properly so I had to change the source for the updates/install (fortunatly theres a dropdown for that in the plg file linked above ). Still no idea why it all randomly failed, not as if I updated anything recently . Thanks again for all the help

Wouldn't you take a massive performance hit by using the same drive for two purposes? Also I think there would be a much higher chance of breaking the unraid. I passed through one of my SAS controllers directly to the Unraid install and it works great

Thanks for the quick reply dgaschk. I changed my go file to yours and rebooted but server still hanging on starting. I noticed the following line was present in my go file before I changed it: cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c Included current syslog which doesn't seem to be showing anything unusual at all now (or at least nothing I can see). Last line is: Jun 26 21:50:05 nas01 sudo: root : TTY=console ; PWD=/tmp ; USER=nobody ; COMMAND=/usr/bin/python /usr/local/sabnzbd/SABnzbd.py -d -s 0.0.0.0:8081 --config-file /mnt/cache/.apps/sabnzbd --pid /var/run/sabnzbd > /dev/null 2>&1 syslog2.txt

Hi Guys, hope someone can help with the issue I'm currently having. I had to reboot the server a few hours ago as several of my plugins randomly stopped responding (sabnzbd/couch potato/sickbeard). I made the dumb mistake of trying to stop the array from my phone which caused the webserver to hang. Could still ping the box ok so dialed in with putty and managed to run a reboot command . Problem I have now is the server array status seems to be hanging on "Starting..." and the only share available is the flash drive. Shares were working fine prior to the reboot. I had a look through the syslog and couldn't really see anything that bad (although I must admit I've never really had a good proper look through these before so am a bit clueless ). Can see Plex doesn't seem to be starting and then theres a few segfaults. I'm assuming the segfaults are causing the issue but have no idea where to start with this. I've included the syslog. Currently running 5.0 b12a. Any ideas on how to sort this out? syslog.txt

Doh!! Was debating trying the latest beta or stable build before I set out on this adventure.. Stable build obvioulsy won but I shouldnt have been so parranoid . Just had a chance to test the card again with latest beta and all the drives are detected . Not had a chance to actually set anything up though, that fun will come at the weekend . Thanks for the help guys

Hi guys, first post on here so go easy on me . I've done a bit of searching on the forum and while I found one post about a H200 I've not found anything that tells me if it is compatible with unRAID or not. I've been using a Dell PERC 5/i and H200 on another box running server2008 however it's not ideal for what I want to do. I'm in the process of setting up another machine I've just put together from a mix of old and new parts and seeing as this is a blank canvas I'm hoping to play about with unRAID to see if this would work well for the other machine as well. I've shoved another working H200 card in the new box to go with the existing onboard sata ports (the mobo is an Asus P5B Deluxe). I've currently got 6 drives connected to the onboard sata which all show fine in the devices tab of the server configuration utility. However none of the H200 drives show. The drives are all detected before unRAID loads (the H200 splash screen shows the drives as being present). Is there something I'm missing or need to do to get these drives to show? Is the H200 compatible with unRAID? I'm using the stock Dell firmware on this card. I was thinking of trying to flash it to the LSI firmware but havn't really found any posts about this being done for my card (only the 5i/6i). I'm setting this up on 4.7. This is my first time setting up unRAID so my apologies if I'm being a n00b or missing out something obvious