limetech

I don't remember why either What breaks when you revert that change?

We just turned on CONFIG_WATCHDOG=y because that was a necessary precondition to get the nct7904 driver to be compiled. We didn't turn on any of the actual drivers that activate watchdog support.

We are following instructions on the bottom of this page: https://github.com/novnc/noVNC/blob/master/docs/EMBEDDING.md You can see where we do this starting on line 229 of /etc/rc.d/rc.nginx Do you think this should be tweaked some more?

@cortana - please type this in a Terminal session and then reboot. If still no local video post diags again: touch /boot/config/modprobe.d/amdgpu.conf

Yeah just a min, actually about 15. I put it on the wrong branch 😆 Ok good to go now, sheesh

This release contains bug fixes and minor improvements. Refer to Summary of New Features for an overview of changes since version 6.8. To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. Thank you to all Moderators, Community Developers and Community Members for reporting bugs, providing information and posting workarounds. Please remember to make a flash backup.

There is a plugin causing this.

Should be fixed in 6.9.1 They added a kernel dependency we didn't have included before.

I suggest you just hold off until 6.9.1 is published. Will probably solve the problems you are seeing.

There are messages in your system log I've never seen before. Please make sure plugins are up to date. If issue persists please try safe-mode boot.

Changed Status to Open Changed Priority to Minor

Please try GUI safe-mode boot.

Yes that's the fix

Changed Status to Solved

Executing any kind of SMART operation increments both number I/O's to the device (in this case Reads) and number sectors transferred (in this case sectors read). This is true whether device is in standby or not. HOWEVER, I have a fix for this coming in 6.9.1

This is a feature request.

Spinning control was changed in 6.9 to handle multiple pools and SAS devices. Some plugins are incompatible with these changes, as noted, Dynamix Auto Fan Control. We're looking into fixing the plugin.

tldr: the issue is the '4' at the end of the docker image file name. Rename the file from 'docker4.img' to 'docker.img' and it'll work. In 6.9 we added the 'Docker data root' config setting. This lets you select how to keep the Docker persistent state (image layers): In a btrfs-formatted vdisk loopback-mounted at /var/lib/docker. In this case the name of the image file must be 'docker.img'. In an xfs-formatted vdisk loopback-mounted at /var/lib/docker. In this case the name of the image file must be 'docker-xfs.img'. In a specified directory which is bind-mounted at /var/lib/docker. Further, the file system where this directory is located must either be btrfs or xfs. Docker will use either the 'btrfs' storage driver in the case of btrfs-formatted vdisk/directory, or the 'overlay2' storage driver in the case of xfs-formatted vdisk/directory.

How are you managing your public ssh key? That is, ssh requires existence of /root/.ssh directory which contains the file authorized_keys. Do you have some lines in your 'go' file that accomplishes this?

Doesn't hurt

Hi @JorgeB - do you know of a kernel bug report related to this?

Something very odd happening which should be "impossible". I suggest you restore the flash device from backup using the Flash Creator tool. Then try the upgrade again but boot in 'safe mode'.

Please click on the the Log icon on right side of webGUI menu bar. This will open a window with the system log 'tailed' - meaning as messages are generated they will appear in that window. If server crashes click in the window and select/copy/paste the contents here. Another way to monitor the log is to open a Terminal window and type this command: tail -f /var/log/syslog

Yes user share file system is crashing: Mar 4 11:00:12 Unraid1 shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. I've been looking at this for a while and don't see an obvious culprit. There is a whole lot of 'noise' in the system log because there are quite a number of plugins installed. Can you get rid of some of those? A danger with plugins is that they can modify the base OS and even install down-rev versions of packages. I'm not saying this is the case but it makes analyzing a lot more difficult.

Do not use hdparm directly to spindown devices.