BRiT

Your choice on continuing to use a ticking time-bomb. Live as dangerously as you want.

Options still available are to replace the Marvell controllers.

If by Linux you mean the unraid server itself, which includes Dockers, it does all file operations natively and does not go through Samba/CIFS.

The only usable option I have seen is to entirely ignore or block users with animated avatars, because of the forum's lack of display avatar options.

The one you named (squid) are not paid by the company. Only the following 4 @limetech, @jonp @eschultz and @SpencerJ as listed on this page: https://unraid.net/about Everyone else is just a member of the community.

I mentioned this in the previous thread about this very topic ... It's close to well over a year, and then it was only because of a power outage that was nearly an entire day. One of the earlier thread that even had an actual poll ...

As shown earlier to someone else, you need to click on a few more places. In particular on the right hand side of your core 2/6, and core 1/5 and core 3/7 columns.

Is there any way of setting the default power mode of the video card? It's fundamentally broken and the fault of the video card if it doesn't boot into an idle mode by default (as tested by booting into your PC BIOS). This is only something Nvidia and the video card manufacturer can fix through changing settings in the card's BIOS.

Upgrade unRaid to latest RC 5. Early RC Kernels have large issues that can cause system stability issues. Try that first.

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.

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.

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.

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?