Leaderboard

As I approach the end of my 2nd year using unRAID I've felt the need to express my mass appreciation to Lime Tech and the community as a whole. I started using unRAID in February of 2016. Issue after issue on my Windows Server build led to an eventual collapse of my 10 TB RAID array and the loss of all the data. At the time it felt pretty terrible as I stayed up late into that night trying to salvage what data I could only to finally accept there would be no salvage. Within the first 2 months of using unRAID I already felt like my server meltdown was the best thing that could have happened to me. Since then unRAID has provided tools to do powerful things easily and every issue I have ever had the community has resolved within days if not hours. I currently work at a computer network company and am happy to have evangelized the hell out of unRAID as I was the first person there to use it. We now have many who have done things from replacing their ESXi build, that was a more complex system than they needed, to running their server and desktop off the same machine to save on cost and space, keeping their spouse happy. So thank you Lime Tech for making a product that fuels my home server hobby and thank you to the community for making that hobby (mostly) stress-free.

Has anybody run into this issue with the WD White Label drives? I thought I'd share my ordeal just in case anyone else stumbles upon this problem. Had a helluva time finding this issue online for some reason. I recently found the need for more storage space and after researching a bit, chose the 8TB EasyStore from Best Buy for shucking. I drove on over, it was $200, great stuff. Came home, followed a visual guide to take it apart, also easy and quick! I noticed it had a white label, which seemed odd, but whatever, this was the drive, right? Made in Thailand with 256MB cache, that's the one! So I removed an older drive from my computer and stuck this one in, only to find it didn't spin up. Crap. I googled around for awhile only to find that this model is the WD80EMAZ rather than the expected WD80EFZX. A lot of forums had people saying they were the same drive, same specs, everything... anyway, I thought maybe it was the PSU I was using (I had to RMA my newer one, using a much older one) so I reassembled the WD and used DC power. Worked immediately. I noticed a couple people on reddit and slickdeals complaining that these drives wouldn't power on with SATA and only worked externally, but tons of other people saying "no problems here I have 3/6/51824 of these in my tower since [the big bang] and they're fine." I really didn't want to reassemble it and go back to Best Buy to exchange it for... what, maybe another of the same? Maybe a real red? The box doesn't list which internal drive you're getting. So I kept searching and found this PDF from HGST, a company WD owns detailing a "power disable feature" found on some of their drives. This feature uses the 3.3V pin to send a hard reset signal to the drive, a pin which I believe was never utilized by hard drives before this. Anyway, as the PDF states, my PSU was basically forcing the drive into a constant "reset" state, preventing it from spinning up at all. The external board it came with must just bypass this. My "solution" was to pull the 3.3V (orange) wire from that particular sata connector and cap/tape it off (shown in linked pics). Look at that, immediately spun up and working. I've seen other people say use a molex to sata adapter as that also ignores the 3.3V line, but I've also seen a lot of posts about these melting, so do with that what you will. Unfortunately, I can't figure out how to make it work in my NORCO SS-500's. Pics: https://imgur.com/a/PHSYH

From what I've read only Haswell and Broadwell chips are affected, lucky for me I've skipped those generations, all my CPUs are older Sandy/Ivy Bridge or newer Sky/Kabylake chips.

The simplest and easiest and fastest way probably is to start new i would follow the guides this guy makes

Stop array, settings, network settings, enable bridging:yes

Yep. /mnt/cache/system/libvirt/libvirt.img

yeah, again you need to specify the .img

How many dockers do you have installed? It appears that you may have installed krusader a bunch of times, specifying a different config location each time. All but the current config should probably be deleted. You could also delete your current docker.img and set it to /mnt/cache/system/docker/docker.img with a size of 5GB, and delete the docker folder in the root. If krusader is your only docker, maybe the best thing to do would be to remove it, then clean out all the leftover junk, then reinstall it to /mnt/cache/appdata/krusader/ When I said set the isos share to cache:yes instead of cache:prefer, that setting will move the isos share to the array disks, following any rules set for the isos share. There is no need for it to take up space on the SSD. Since you only have 1 VM, the easiest thing to do would probably be to save the XML text from the edit XML screen, delete and recreate the libvirt.img file with the settings you want, then create a new VM and paste in the XML to recreate the VM. Your tree graphic is very hard for me to follow for some reason, I can't quickly determine which folders are at the root. I think I interpreted it correctly though. If you allow mover to relocate isos to the array, then the only permanent root folders on the cache drive would be appdata, domains, and system. Any other folders would be created and moved automatically to the array by data written to shares that are set to cache:yes

Just tried HTTPVAL = true, forwarded port 80 to my exposed http port 90 > 80 and it did the trick. Hopefully they fix this so i can close back up port 80. edit: for anyone else that needs to know where to edit this, it's under advanced settings

this looks like exactly what happened to me. httpval fixes it all.

Yes. 4GB is really tiny to fit unRaid, the qemu virtual management functions, and the VM itself. No slack for anything to breath. Not sure why you ended up with all that on your cache drive, I think you may have separated some stuff out to root folders that is normally in subdirectories. isos for sure could be set to cache:yes instead of prefer, the other folders I'd need to see content to have an idea what happened and whether they need to be moved. Krusader should be under appdata, if you set the krusader docker to /mnt/cache/appdata/krusader and before it was set to /mnt/cache/Krusader that would explain that folder. For neatness sake you could have the docker img file and libvirt img file both in the system folder. Did you keep the 100GB setting for libvirt.img? That is freakin' HUGE, I have 126MB used in a 1GB allocated libvirt.img file with 10 VM's currently defined.

applying this "fix" forces us to port forward http (tcp 80) through our router to access the nginx service so it can be evaluated by letsencrypt. Make sure you have http and https available externally.

Change host path 1 to /mnt/ instead of /mnt/cache/, and host path 2 to /mnt/cache/appdata/krusader/

You're mapping /UNRAID to /mnt/cache instead of /mnt/user

docker template information historically did not update, thus if you created the container some time ago you would have an out of date template missing the newer env var's that have been added. in later versions of CA this is now fixed and updates to the templates are now dynamically pushed out, but its a catch 22, you need to run FCP in order to pick up the xml change that enables the dynamic updates to work, but as you have now gone from scratch again you should now have the latest template and this will now auto update, so you shouldn't see the issue again :-).

Bedtime for me, I'll check back tomorrow if needed.

If i understand correct, you want to remove a drive and add a new? If the drive you want to add is not bigger or atleast the same size as your parity, you could just replace them and rebuild parity. or?

I had to do the exact same thing. I've been looking into this for the past few days and apparently this is the only way of doing things "properly" on 6.4. Also, if you want to for your dockers to communicate with eachother at a certain point, don't for get that you have to select the same network when assigning the IPs

This is the second part of a series of videos where we will take a detailed look at the best 'must have' plugins. This video looks at the Dynamix family of plugins. This video looks at the following plugins, The Trim plugin (and why trim is important). The Cache directories plug, The Active streams plugin, The Sleep plugin, The System temperature plugin, The Date and Time plugin, The System info plugin The System stats plugin

They re-enabled it for some providers. It is unclear what the long term action will be. But we already have a PR on github to add the option of http validation through port 80

One solution is to use the plugin Unassigned Devices in unRAID. That allows you to mount additional disks that aren't part of the array. This gives you a way to run unRAID and copy data from other disks. Another solution is the one I mentioned - have unRAID format one data disk and then connect that disk to your current machine (assuming it runs Linux) and copy data to it. The variant with Unassigned Devices means you can build parity while copying. But on the other hand, the copying will be slower because of the extra work of concurrently updating the parity disk.

Great. Much appreciated!