Squid

Up for me now... But GitHub's status still states that it'll be hit or miss

If you only have two disks, then you would assign the larger one as parity if they are different sizes or if they're the same size then it doesn't matter which is which. Logging off til the morning, but if something comes up as unmountable then wait for someone else to take over before you do anything else Sent from my SM-T560NU using Tapatalk

You can always do it manually Format a fresh USB ( less than 32G ) as FAT32. Name the drive UNRAID Extract the contents of the zip file downloaded from LT's website onto the flash Run as Administrator the make_bootable.bat script

Extremely unlikely. Make a new USB stick with LT's USB Creator Tool. It should at least get you to a webUI. If that works, then copy from the old flash to the new one the Basic.key file and boot again. It will either give you the ton of errors again or it will walk you through transferring the key. If it transfers, then reassign your drives. If it gives you all the errors again, then register the flash as a trial and contact Limetech to manually transfer the registration over to the new stick.

Can you still access the shares over the network as before? If so, whitelist your server in your ad-blocker running on your browser. If not, post your diagnostics

Try running Tools - New Permissions against the particular share. If in doubt about what you're doing, then run Tools - Docker Safe New Permissions if you have Fix Common Problems installed

Rename the .key file from Basic.key to be Basic.oldkey Reboot.

https://status.github.com/messages

lol Kinda hard to miss that one. I would edit /config/disk.cfg on the flash and change startArray="yes" to be startArray="no" Probably won't fix the problem, but maybe it'll get you into the webUI. My guess is that the .key file is messed up due to the file corruption you had.

from the command prompt diagnostics Then post the resulting file saved on the flash drive here

Git works. Its GitHub.com (the front end) that's failing at the moment. Once the posting states service back to normal I'll figure out what I need to do, if anything.

From GitHub's Status: Net result is that CA is currently down until they resolve this (along with manually installing any other plugin) Humorously enough, the outage happened at the exact same time as two typos: One which blacklisted the entire app library (which was fixed 30 seconds afterwards, but GitHub is stuck deploying the incorrect version), and a CA update of which GitHub is also serving up an incorrect version of the .plg preventing new installs / updates.

Try changing the access mode from RW to be RW:Slave or RW:Shared (Folder may also already have to exist - not sure)

Might be better to ask what you're trying to do, as everything outside of /mnt/ is stored in RAM. IE: if you're trying to have a container access a folder in RAM instead of appdata, then just give it a host path of something like /tmp/containerName/