BRiT

The reason I said to do it one at a time is you obviously have something wrongly mapped on at least one of the dockers. There's no reason to need more space on the actual docker.img. Everything that requires large amounts of space should be mapped through outside the docker container. If you dont review and correct the wrong mapping(s) you will continue to have your original issue.

Correct the share settings for the disk shares or dont enable disk shares at all.

Delete docker.img and recreate, adding dockers back in from My Dockers list, except this time actually look at each mapping of each docker to make sure its still not fraked up like before. The flow is similiar to that, might not be exact, but it's close enough for anyone to just poke around and get it going.

Not useless at all when you don't own any nvidia hardware.

It seems to mirror the purpose of "go". Its hooked in via one of the rc.d scripts if my memory hasn't failed me. I haven't seen anyone use it and I see more hooked in via rc.local.shutdown. Apply ECC Bits as needed for this memory dump.

Yes. Yes. No.

Question: What's the point of switching from Public to Secure? Did you restrict users as well when setting it to Secure? If not, then every user still has the same access, so what does it get you?

If you have COAX run into the rooms, look into using Bonded MOCA 2.0 or the newest Bonded MOCA 2.5 adapters. https://www.gocoax.com/ Many have had success in using those new 2.5 adapters at The Tivo Community Forums: https://www.tivocommunity.com/community/index.php?threads/moca-2-5.571180/ However, they seem to be out of stock, not sure when new stock will be available. I'm using multiple sets of the Motorola Bonded 2.0 adapters to connect the 3 bedrooms and living room into the server and rec room networks: https://www.amazon.com/Motorola-Adapter-Ethernet-2-Pack-MM1002/dp/B078HMDDVS/ref=sr_1_4?keywords=moca+2+bonded&qid=1562421653&s=gateway&sr=8-4

No, but substantially more complex and will be wiped out upon any reboot.

Different kernel, which goes back to manufacturer responsibility to provide working drivers.

It's up to the hardware manufacturer to provide drivers that work in Linux. They seem to have fallen behind on some kernels.

Did you or anyone else set direct io to No?

Docker container or VM for perl and do all your work in there?

1. Yes. 2. Yes. Just never do a copy involving /mnt/disk# and /mnt/user unless you know exactly what you're doing (see user share file copy issue that could overwrite a file with itself and ends up at 0 bytes).

Many users dont run Plex at all, or if they do they likely use AppData Backup once a week which will stop the dockers before doing the backup, so I'm not surprised more aren't experiencing your issue.

There is support for persistent syslogs since 6.7.0. Enhanced syslog handling. On Settings/Network Services page click on Syslog Server. Here you can designate this server to receive system logs from other Unraid OS servers, or forward this servers syslog to another local or remote server. Also, if there are stack traces or dumps in the logs, they would be slightly different considering all the changes since then.

I think anyone from the community who may try to help you now will ask that you post your Diagnostics file from the time after the server experiences the issue and before it's rebooted to recover.

Now that you're back at a sanity point, try the following commands, to show by connection in a tree format. You might need additional information from a basic 'lspci' to add context to the tree format (-t), sometimes it might only display the ids, but sometimes it will include enough info when -v is also specified. lspci -tv

Try booting into Safe Mode / Maintenance Mode.

All individual drive are accessible in normal Linux if your boot USB drive is lost. The only complication is if you're using encryption.

Product viability is determined by SMART reports. However, I'm proactive with array health instead of reactive. I'd rather do maintenance on my schedule than having to do emergency procedures. Assuming a drive didn't cause severe issues to cause immediate replacement... I used to replace drives around when their warranty ran out at 4 to 5 years, and before the severe issues could happen. However drives seem to have substantially shorter warranty periods now, so my approach is to replace a drive when I can double their size or close to 5 years, whichever comes first. I replaced 4TB drives with 8TB before 5 years. Added benefit was shortening parity check times. My drives are around 2.5 years now, so likely will replace sometime late 2021 to early 2022 if they dont release 16TB before then.

Never rebooted since removing the line?

You could attempt a reboot to get back to sanity and then at the beginning of a normal system boot up there might be a devices list in the syslog, hopefully something more than what the lspci command provides. All the syslog included are just that error message over and over.

Post your entire Diagnostics zip file, not just a syslog. Read the FAQs if you're unaware of what Diagnostics is.

Yes, just need two different servers. 😛