JorgeB

Thanks, that makes sense.

This should work even if in RAID mode, though like jonathanm mentioned IT mode would be better and RAID mode might require you to create individual raid volumes, also please post the diagnostics: Tools -> Diagnostics

I didn't know this, so booting in safe mode won't help if it's misconfigured, @bonienlis this correct and if yes anything that can be done about this?

Default for the cache pool is raid1, please post the diagnostics: Tools -> Diagnostics

If you already tried all this using a different board would be the next thing I would try.

No devices are being detected, this is a hardware issue, check the LSI BIOS, Unraid won't detect any disks until they are detected there. That's enough to connect all disks, assuming it has an expander backplane.

Link detected: no On all NICs.

Yes, but the main culprit appears to be this one: nobody 20324 47.4 3.5 10036260 1181400 ? SNsl Jun09 2054:52 | | | \_ /usr/local/crashplan/bin/CrashPlanService Try shutting sown CrashPlan when it happens again.

Nothing out of the ordinary there, what exactly is FCP warning about? You should also post the diagnostics: Tools -> Diagnostics

Please post the diagnostics: Tools -> Diagnostics

Yes it is, there's filesystem corruption, you'll need to back it up manually and re-format, then restore the data.

Best bet it to use the exiting docker/plugin support thread.

Yes.

That's encouraging and similar to my findings, and I was hoping it would work for everyone else before @hotio's comments, but it still might work for most, or everyone in case he was mistaken. The loop# used can change and it's not important, just make sure it's the one where the docker image is mounted. This will happen every time you move the docker image to a btrfs filesystem/share with COW set to "auto" (enable), it can be ignored for this, you could recreate the image to get rid of the warning but then it would resume the amplified writing.

You're welcome, and if you don't mind going to tag it solved.

If all the other drives are OK sounds like a good idea.

Yes, that's one the plugins that I though could be causing issues, if misconfigured, though booting in safe mode should not load it.

Then I would recommend redoing the flash drive, backup current one, re-do it with the USB tool, then restore only super.dat (disk assignments) and your key, both on the config folder, if OK you can then start restoring the other files to find out which one is the problem or just reconfigure the server, if redoing the flash doesn't work you likely have a hardware problem.

Not necessarily bad, just not working correctly with your hardware, also like mentioned make sure it's on a USB 2.0 port.

That is not a disk problem, Unraid is losing connection with the entire NetApp enclosure.

On any unmountable drive, or any drive showing filesystem issues on the log.

Shares are just top level folders, you can delete on the CLI.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

That's what user shares are for, they show the data from all the drives where that share exists, basically they "pool" the data from all the drives.

Assuming 16TB as the maximum current available disk size, array capacity can be up to 448TB, larger as larger disks become available.