[[6.5.3] global disk utilization notifications not working]

For me, changing global and individual setting generates in both cases (many) or one notifications.

 

[[6.5.3] global disk utilization notifications not working]

Make sure system notiifications are enabled.

It can take up to one minute before a notification is sent, after changing the threshold.

 

[Global Share Setting image gone]

Does it work when you start your system in safe mode?

 

[After upgrade to 6.5.3, server stuck in reboot loop]

Uninstall the preclear plugin.

 

[[6.5.2] Vertical scrollbar appears then dispears over and over]

Can't reproduce the issue, have you tried to clear the browser cache or use a different browser?

[[6.5.2] Vertical scrollbar appears then dispears over and over]

The browser will automatically add the scrollbar when the content is longer than the height of the screen and will automatically hide the scrollbar when content fits.

 

You can change to "tabbed" view to minimize content length and get better fitting, see settings -> display settings.

 

[[6.5.2] Multiple unclean shutdowns]

Unclean shutdown is most of the time a hardware issue, e.g. failing RAM or PSU.

Better open a new topic under general support to further address your case. Your diagnostics don't show anything unusual.

 

[[6.5.0] Upgrade to 6.5.1]

6 hours ago, ken-ji said:

Just a thought but maybe we can either:

* dynamically make a new tmpfs mount of the sensible size  - say 256M /tmp/unRAID and download and extract the image there.

* download to a cache/array share (worst case)

 

Good proposal.

 

The existing flash backup utility does something similar. It checks if enough memory is available to create the ZIP file in RAM, otherwise it looks for one of the predefined shares and stores the ZIP file on disk.

 

The OS update routine can have some checks too before downloading the ZIP file.

 

[[6.5.0] Upgrade to 6.5.1]

The download fails several times.

 

Try to download the ZIP file directly from Limetech and copy the bz* files to your flash device. Then reboot the system.

[Unable to stop docker service (6.5.2-rc2)]

Okay, found the issue. There is a regression error in preserving the file name (my mistake).

 

Made a PR to correct.

[Hard [GUI, Webinterface] CRASH 6.5.2 RC2]

As @johnnie.black mentioned this is not a unRAID bug, but either your flash device is failing or a problem with the USB port.

 

[6.5.2-rc1 breaks Windows 10 VM vdisk creation for me...]

Please start your system in safe mode and restest. This is to make sure the packages and plugins which are now installed do (not) cause the issue.

 

[6.5.2-rc1 breaks Windows 10 VM vdisk creation for me...]

I can create a Windows 10 VM as before. Do you have a screenshot of what your are (not) seeing?

 

[Not all dockers starting after restart]

The log shows all containers as succesfully started with docker attaching them to the network interface.

 

Are it always the same containers not starting or is this random?

 

[Not all dockers starting after restart]

Your syslog tells otherwise

Apr 30 13:27:36 Unraid-Server root: +==============================================================================
Apr 30 13:27:36 Unraid-Server root: | Installing new package /boot/config/plugins/ca.docker.autostart/ca.docker.autostart-2018.03.22-x86_64-1.txz
Apr 30 13:27:36 Unraid-Server root: +==============================================================================
Apr 30 13:27:36 Unraid-Server root: 
Apr 30 13:27:36 Unraid-Server root: Verifying package ca.docker.autostart-2018.03.22-x86_64-1.txz.
Apr 30 13:27:36 Unraid-Server root: Installing package ca.docker.autostart-2018.03.22-x86_64-1.txz:
Apr 30 13:27:36 Unraid-Server root: PACKAGE DESCRIPTION:
Apr 30 13:27:36 Unraid-Server root: Package ca.docker.autostart-2018.03.22-x86_64-1.txz installed.

Please reboot your system and make fresh diagnostics.

[Not all dockers starting after restart]

You are using the "CA Docker Autostart Manager" to start the containers, not the standard unRAID startup sequence.

 

[Not all dockers starting after restart]

What is the output of

cat /var/lib/docker/unraid-autostart

 

[Array contains 1 invalid disk (s) 6.5.1 RC6]

Sorry for this inconvenience 

 

It is supposed to look like this

 

[Upgrade banner needs confirmation]

I added a confirmation window which allows the user to proceed or cancel.

 

[Array contains 1 invalid disk (s) 6.5.1 RC6]

19 minutes ago, Squid said:

Good catch.  I never would have noticed on my system. 

 

From my system:

 

@limetech

mdNumDisks="23"
mdNumDisabled="1"
mdNumInvalid="1"

23 is correct (22 data + 1 parity).  Both disabled and Invalid though are incorrect.  I originally did play with Dual Parity, decided against it for various reasons.  Would've done a new config as what I was using for Parity 2 did get reused as a data drive.  A quick glance through other user's diags shows Parity 2 status as always being DISK_NP_DSBL when not installed.

 

 

This is correct. A missing 2nd parity disk is seen as invalid. GUI should ignore this, but I overlooked this when adding the new parity info on the dashboard (I run a dual parity system obviously).

[Array contains 1 invalid disk (s) 6.5.1 RC6]

6 minutes ago, chatman64 said:

 

I have the same problem with 6.5.1 rc6> when I go back to 6.5 it is gone.

 

rc6 shows a next scheduled date and time for parity check. This works fine for people having two 2 parity disks, but shows an error message instead for those with a single parity disk, which can be ignored.

 

[Array contains 1 invalid disk (s) 6.5.1 RC6]

Yes, nothing wrong. A minor display glitch only.

[Array contains 1 invalid disk (s) 6.5.1 RC6]

It is only a display thing, because you don't have a second parity disk. Will be corrected in next release.

[unRAID OS version 6.5.1-rc6 available]

You may want to add to the change log of rc6:

• linux kernel version 4.14.34

 

[6.5.1-RC5 missing csrf token]

There is a missing csrf_token when the first container is created. Made a correction for this.