BRiT

Again, sorry to see such bugs affect anyone. The good parts of the discussion starts on page 5 of this thread, with some trying normal file and directory permissions before trying the immutable attribute (chattr +i). I have all my movies/shows/videos set as +i but leave the metadata info and pictures from scrapers left as modifiable since they can easily be recreated.

You could take precautions as listed in the malware prevention topics, especially the "chattr +i" command.

Pedantic nitpic on the help text, the default setting is "No" and not "OFF" looking at the UI.

And that is why some folks no longer bother to reply to threads with varioous items to try.

Fully specify the config location.

Post in the emby forums. They likely have better support for that specific situation.

Of course not. I'm a Lazy Dev. I forget that not many folks around this forum is aware of that knee-jerk reaction joke. It shows up all the time on the graphical/game related forums. Frankly, developers' time is better spent developing than it is documenting, unless it's a fundamental breaking change that requires manual steps to adjust.

Lazy Devs.

No. I did not forget that RC does not mean Release Candidate here. Other's have. That's why I asked why they don't ask for features.

Why? It's not like RC(s) here mean feature freeze that goes along with Release Candidate.

Try using a usb2 port instead.

The pressure needs to be on Oracle (current owners of Sun Microsystems IP) to get them to change the license terms on ZFS. Not until the terms are adjusted will you see the attitude towards it from Linux Kernal developers change.

The lines dealing with extraction, since bzroot has 2 sections you need to deal with first part and then skip that section to get to the last part: echo -e " ----- Extract BZROOT microcode" dd if=/boot/bzroot bs=512 count=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=bzrootmicrocode echo -e "----- Unpack BZROOT" dd if=/boot/bzroot bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') | xzcat | cpio -i -d -H newc --no-absolute-filenames

Maybe 6.7.0 addresses the issue of impossible updates.

I suggest others re-read the above concern before handwaveing it away as a non-issue. (Copied it because it was well expressed)

Sure ... just handwave away legitimate concerns especially ECC Ram that was mentioned earlier.

Snippets of the syslog usually do not help, that is why the troubleshooting FAQ says to post full diagnostics zip file.

The price of Pro is so cheap I'm surprised anyone purchases less.

You'd have to escape out the space in the directory name somehow. Two choices are using double-quotes around entire name or use backslash-space sequence: "/mnt/user/Movies/Home Movies" /mnt/user/Movies/Home\ Movies

First Unassigned Devices needs to be integrated into base unraid distribution since it currently limits by number of devices. Then the same handling can be standardized across assigned and unassigned drives by the core developers.

Maybe retest with urandom as the source sync? dd if=/dev/urandom iflag=fullblock bs=1MB count=20000 of=20gbte The fullblock flag is needed otherwise you might not write the same amount of data when dealing with random syncs and entropy in linux systems.

Interesting breakdown in the cause of the issues for those who like tech details. I suppose it's not worth the development and quality assurance time to have it be a user configurable behavior?

If you track it up to some command "docker-containerd-shim" you can determine which exact docker container it is by matching container id prefixes. Notice how "9e837294036f" matches between the output of Docker Process and the overall Process output: ps -axf 13248 ? Sl 0:00 \_ docker-containerd-shim 9e837294036f29839277d497a83be3e1996df00ba63af497daacbb78229062f2 /var/run/docker/libcontainerd/9e837294036f29839277d497a83be3e1996df00ba63af497daacbb78229062f2 docker-runc docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9e837294036f emby/embyserver:latest "/init" 7 weeks ago Up 31 hours EmbyServer

ps -auxf or the following if the above expands too wide to be seen on your terminal screen, and try to find the 'sh' process by process id and see what process tree it belongs to. ps -axf

As stated in other threads, Stop your plex docker and any other dockers that may be scanning the system until after your unbalance operations finish.