Dynamix - V6 Plugins

Falcosc · June 7, 2022

There is no shutdown after

"Disk activity detected. Reset timers."

If you don't have more logging you need to check how to improve the logging situation.

kalidus · June 7, 2022

20 minutes ago, Falcosc said:

There is no shutdown after

"Disk activity detected. Reset timers."

If you don't have more logging you need to check how to improve the logging situation.

How can i do that? There are no more log options to check

Edited June 7, 2022 by kalidus

Falcosc · June 7, 2022

Maybe you should share the full log before we start to blame unraid for logging issues. There should be a lot of output about stopping array.

I use scripts to log to my NVMe drive, but needed to do write additional shutdown scripts to stop logging during shutdown to avoid unclean shutdown.

That was my issue:

May 26 17:15:08 server s3_sleep: Shutdown system now
May 26 17:15:08 server shutdown[24407]: shutting down for system halt
May 26 17:15:08 server init: Switching to runlevel: 0
May 26 17:15:08 server s3_sleep: System woken-up. Reset timers
May 26 17:15:08 server init: Trying to re-exec init
May 26 17:15:09 server unraid-api[8833]: 👋 Farewell. UNRAID API shutting down!
May 26 17:15:10 server kernel: mdcmd (66): nocheck cancel
May 26 17:15:11 server emhttpd: Spinning up all drives...
May 26 17:15:11 server emhttpd: read SMART /dev/sdd
May 26 17:15:11 server emhttpd: read SMART /dev/sde
May 26 17:15:11 server emhttpd: read SMART /dev/sdb
May 26 17:15:11 server emhttpd: read SMART /dev/sdc
May 26 17:15:11 server emhttpd: read SMART /dev/nvme0n1
May 26 17:15:11 server emhttpd: read SMART /dev/sda
May 26 17:15:11 server emhttpd: Stopping services...
May 26 17:15:11 server emhttpd: shcmd (190242): /etc/rc.d/rc.libvirt stop
May 26 17:15:11 server root: Waiting on VMs to shutdown
May 26 17:15:11 server root: Stopping libvirtd...
May 26 17:15:11 server dnsmasq[8614]: exiting on receipt of SIGTERM
May 26 17:15:11 server kernel: device virbr0-nic left promiscuous mode
May 26 17:15:11 server kernel: virbr0: port 1(virbr0-nic) entered disabled state
May 26 17:15:11 server avahi-daemon[8044]: Interface virbr0.IPv4 no longer relevant for mDNS.
May 26 17:15:11 server avahi-daemon[8044]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
May 26 17:15:11 server avahi-daemon[8044]: Withdrawing address record for 192.168.122.1 on virbr0.
May 26 17:15:11 server root: Network a67b7b9b-bef4-488b-b243-c9e5f391a3b1 destroyed
May 26 17:15:11 server root: 
May 26 17:15:14 server root: Stopping virtlogd...
May 26 17:15:15 server root: Stopping virtlockd...
May 26 17:15:16 server emhttpd: shcmd (190243): umount /etc/libvirt
May 26 17:15:16 server s3_sleep: ----------------------------------------------
May 26 17:15:16 server s3_sleep: command-args=-q
May 26 17:15:16 server s3_sleep: action mode=sleep
May 26 17:15:16 server s3_sleep: check disks status=no
May 26 17:15:16 server s3_sleep: check network activity=no
May 26 17:15:16 server s3_sleep: check active devices=no
May 26 17:15:16 server s3_sleep: check local login=no
May 26 17:15:16 server s3_sleep: check remote login=no
May 26 17:15:16 server s3_sleep: version=3.0.8
May 26 17:15:16 server s3_sleep: ----------------------------------------------
May 26 17:15:16 server s3_sleep: included disks=nvme0n1 sdb sdc sdd sde
May 26 17:15:16 server s3_sleep: excluded disks=sda
May 26 17:15:16 server s3_sleep: ----------------------------------------------
May 26 17:15:16 server s3_sleep: killing s3_sleep process 14216
May 26 17:15:16 server unassigned.devices: Unmounting All Devices...
May 26 17:15:16 server emhttpd: shcmd (190245): /etc/rc.d/rc.samba stop
May 26 17:15:16 server wsdd[30446]: udp_send: Failed to send udp packet with Network is unreachable
May 26 17:15:16 server wsdd[30446]: Failed to send bye with Network is unreachable
May 26 17:15:16 server winbindd[30451]: [2022/05/26 17:15:16.991808,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
May 26 17:15:16 server winbindd[30451]:   Got sig[15] terminate (is_parent=0)
May 26 17:15:16 server nmbd[30439]: [2022/05/26 17:15:16.992354,  0] ../../source3/nmbd/nmbd.c:59(terminate)
May 26 17:15:16 server nmbd[30439]:   Got SIGTERM: going down...
May 26 17:15:16 server nmbd[30439]: [2022/05/26 17:15:16.992430,  0] ../../source3/libsmb/nmblib.c:922(send_udp)
May 26 17:15:16 server nmbd[30439]:   Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable
May 26 17:15:16 server nmbd[30439]: [2022/05/26 17:15:16.992456,  0] ../../source3/libsmb/nmblib.c:922(send_udp)
May 26 17:15:16 server nmbd[30439]:   Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable
May 26 17:15:16 server winbindd[30927]: [2022/05/26 17:15:16.993900,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
May 26 17:15:16 server winbindd[30927]:   Got sig[15] terminate (is_parent=0)
May 26 17:15:16 server winbindd[30449]: [2022/05/26 17:15:16.994062,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
May 26 17:15:16 server winbindd[30449]:   Got sig[15] terminate (is_parent=1)
May 26 17:15:18 server emhttpd: shcmd (190246): rm -f /etc/avahi/services/smb.service
May 26 17:15:18 server avahi-daemon[8044]: Files changed, reloading.
May 26 17:15:18 server avahi-daemon[8044]: Service group file /services/smb.service vanished, removing services.
May 26 17:15:18 server emhttpd: Stopping mover...
May 26 17:15:18 server emhttpd: shcmd (190248): /usr/local/sbin/mover stop
May 26 17:15:18 server root: Forcing turbo write on
May 26 17:15:18 server kernel: mdcmd (67): set md_write_method 1
May 26 17:15:18 server kernel: 
May 26 17:15:18 server root: ionice -c 2 -n 7 nice -n 19 /usr/local/sbin/mover.old stop
May 26 17:15:18 server root: mover: not running
May 26 17:15:18 server emhttpd: Sync filesystems...
May 26 17:15:18 server emhttpd: shcmd (190249): sync
May 26 17:15:19 server emhttpd: shcmd (190250): umount /mnt/user0
May 26 17:15:19 server emhttpd: shcmd (190251): rmdir /mnt/user0
May 26 17:15:19 server emhttpd: shcmd (190252): umount /mnt/user
May 26 17:15:19 server emhttpd: shcmd (190253): rmdir /mnt/user
May 26 17:15:20 server emhttpd: shcmd (190255): /usr/local/sbin/update_cron
May 26 17:15:20 server emhttpd: Unmounting disks...
May 26 17:15:20 server emhttpd: shcmd (190256): umount /mnt/disk1
May 26 17:15:20 server kernel: XFS (md1): Unmounting Filesystem
May 26 17:15:21 server emhttpd: shcmd (190257): rmdir /mnt/disk1
May 26 17:15:21 server emhttpd: shcmd (190258): umount /mnt/disk2
May 26 17:15:21 server kernel: XFS (md2): Unmounting Filesystem
May 26 17:15:21 server emhttpd: shcmd (190259): rmdir /mnt/disk2
May 26 17:15:21 server emhttpd: shcmd (190260): umount /mnt/disk3
May 26 17:15:21 server kernel: XFS (md3): Unmounting Filesystem
May 26 17:15:21 server emhttpd: shcmd (190261): rmdir /mnt/disk3
May 26 17:15:21 server emhttpd: shcmd (190262): umount /mnt/cache
May 26 17:15:21 server root: umount: /mnt/cache: target is busy.
May 26 17:15:21 server emhttpd: shcmd (190262): exit status: 32
May 26 17:15:21 server emhttpd: Retry unmounting disk share(s)...
May 26 17:15:26 server emhttpd: Unmounting disks...
May 26 17:15:26 server emhttpd: shcmd (190263): umount /mnt/cache

"s3_sleep: Shutdown system now" is a bug

and

"server root: umount: /mnt/cache: target is busy." was my fault (it was my syslog to nvme script

Edited June 7, 2022 by Falcosc

kalidus · June 7, 2022

1 hour ago, Falcosc said:

Maybe you should share the full log before we start to blame unraid for logging issues. There should be a lot of output about stopping array.

I use scripts to log to my NVMe drive, but needed to do write additional shutdown scripts to stop logging during shutdown to avoid unclean shutdown.

Here's my log. I can't manage to see what's wrong. XXXX parts are just for ID's, ip's and such. Thank you!

syslog

Falcosc · June 7, 2022

Looks good, no issue.

Looks like S3 Sleep plugin did correctly detect that there is disk activity and does prevent sleep.

If you try to shut down in this state, you will get an unclean shutdown.

So I don't see any issue with the plugin.

You now have to look to what is causing disk activity on your cache drive. But this is something unrelated to the plugin and maybe worth an own topic.

You will find lots of documentation online about how to detect which processes are causing disk access.

You probably need the nerd plugin to add necessary tools to find out which process is causing disk access.

Once you found the process which is accessing the disk, you may need help of other people to understand what kind of process it is.

But in the end it is not related to s3 sleep plugin.

kalidus · June 7, 2022

1 hour ago, Falcosc said:

Looks good, no issue.

Looks like S3 Sleep plugin did correctly detect that there is disk activity and does prevent sleep.

If you try to shut down in this state, you will get an unclean shutdown.

So I don't see any issue with the plugin.

You now have to look to what is causing disk activity on your cache drive. But this is something unrelated to the plugin and maybe worth an own topic.

You will find lots of documentation online about how to detect which processes are causing disk access.

You probably need the nerd plugin to add necessary tools to find out which process is causing disk access.

Once you found the process which is accessing the disk, you may need help of other people to understand what kind of process it is.

But in the end it is not related to s3 sleep plugin.

As i said, i researched all of that and there is absolutely no disk activity, open files, dockers, vms, scheduled tasks interfering.... I also said that the plugin caused an unclean shutdown, i didn't force it.

Theres some posts of other users with the same problem in this and other forums so, forgive me but categorically saying it's not the plugin just by seeing a log seems precipitate for me. However, i can't certify if it is or not. Thanks anyways.

Edited June 7, 2022 by kalidus

kalidus · June 7, 2022

6 hours ago, HDT said:

Does anyone know if the TRIM SSD plugin, by default, trims all SSD's regardless if their file system is XFS or BTRFS?

Or, does it only trim XFS SSD's since I've read that performing TRIM on a BTRFS SSD can be bad?

There is no way to exclude BTRFS in the settings of this plugin.

Maybe this can help you::

bonienl · June 8, 2022

I created a new plugin Dynamix Encryption Key, which is inspired by the excellent unraid-newenckey script of @doron

When disk encryption is used then under Disk Settings a new section is added, which allows the user to change the existing key to a new passphrase or new keyfile.

The plugin is available in CA.

Dantheman · June 8, 2022

I tried to install the plugin, but receive this error.....

plugin: installing: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.encryption.key.plg
plugin: downloading https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.encryption.key.plg
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.encryption.key.plg ... failed (Invalid URL / Server error response)
plugin: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.encryption.key.plg download failure (Invalid URL / Server error response)

Other plugins are updating, so i think it's not on my side.....

bonienl · June 8, 2022

I temporary removed the plugin, investigating an issue at the moment.

Dantheman · June 8, 2022

Thanks for the update and hope you can fix the issue...

Freddy23 · June 9, 2022

Is there a known issue with CPU spiking with Dynamix Cache Directories? It keeps hitting 2 of 12 cores to about 80% every 11 seconds. Once I disabled the folder caching function it stopped. I only noticed because it was causing my fan to speed up and down and got quite annoying.

I heard there was an issue if "Scan user shares" was enabled, but I have it set to "No"

JonathanM · June 9, 2022

15 minutes ago, Freddy23 said:

Is there a known issue with CPU spiking with Dynamix Cache Directories? It keeps hitting 2 of 12 cores to about 80% every 11 seconds. Once I disabled the folder caching function it stopped. I only noticed because it was causing my fan to speed up and down and got quite annoying.

I heard there was an issue if "Scan user shares" was enabled, but I have it set to "No"

Reduce the number of cached selections. Only cache locations that absolutely need it. You are probably trying to cache too many entries, especially if you selected appdata.

mmwilson0 · June 10, 2022

Hello, is there anyway i can troubleshoot Dynamix Fan Auto Control? In the last few months my fan's have been running extra loud compared to what they used to. I have the array powered off, processor and mainboard are showing 31 & 33 degrees, respectively. All the hard drives are under 34 degrees, but the fans are still spinning at medium-high speed.

Settings are screenshotted in the attachment, let me know if there is any other information i can include for diagnostics.

comet424 · June 11, 2022

@mmwilson0 probably the HwmonX has changed.. re detect.. and see if its changed from hwmon0 to like 1 or 2 for each of the 6 pwms that normally fixes it for mel

comet424 · June 11, 2022

a feature request id like to see is.. not to use "SDx" to define hard drives.. but use there UID numbers.. if you pull a UD drive.. and reboot unraid. then the SDx get all jumbled at times in the exclude drives so a drive you wanted excluded is now moved a hard drive or 2... be nice to have (array 1 drive) uid # not (array 1 drive) sda as tomorrow sda could be array 2 drive

but if it could go to each unique id of a hard drive... then it wouldnt bugger up... same with the "hwmonX" it changes if you pull a UD drive out and you reboot.. now a hwmon1 is either hwmon0 or hwmon2 be nice if there was a way to fix it.. that it never changes

itimpi · June 11, 2022

17 minutes ago, comet424 said:

a feature request id like to see is.. not to use "SDx" to define hard drives.. but use there UID numbers.. if you pull a UD drive.. and reboot unraid. then the SDx get all jumbled at times in the exclude drives so a drive you wanted excluded is now moved a hard drive or 2... be nice to have (array 1 drive) uid # not (array 1 drive) sda as tomorrow sda could be array 2 drive

but if it could go to each unique id of a hard drive... then it wouldnt bugger up... same with the "hwmonX" it changes if you pull a UD drive out and you reboot.. now a hwmon1 is either hwmon0 or hwmon2 be nice if there was a way to fix it.. that it never changes

The system never uses the sdX designations to identify drives. In the main array it is by serial number, and If you want it under UD then you CAN already get UD to always use the same identifier for each drive by simply setting the name to use explicitly.

comet424 · June 11, 2022

under fan exclude you see its sdk sdj sdl well they always change if i were to add a drive to the array... and if you add a UD drive and reboot well exclude the check marks are off by 1 or 2 or 3 depending how many UD drives you add and do a reboot for whatever reason..

so if i have array 1 to 7 checked off and you add 2 UD drives and you reboot things.. then array 1 is checked 2 3 is unchecked 4 5 6 7 could be checked off.. it picks and chooses

what i mean about uid

beside Disk 1 instead of it looking for SDJ it be nice if it was UID cuz

so Disk 1 (sdj) would be Disk 1 (UID #)

this way fans wouldnt bugger up every time a any hard drive you plug into the server and then you happen to do a reboot causes the fan list bugger up...

so like

excude

Disk 1 UID#

Disk 2 UID#

Disk 3 UID#

this way it be always linked to the UID number not a SDx number

as i guess the Fan Speed Exclude only looks at "SDx" not "UID"

and is there a way to fix that HwmonX issue i notice too?

comet424 · June 11, 2022

and about the UD and identifliers.. what i mean

is if i have what you see in above pic... if i have 2 USB drives plugged in.. and reboot.. it will then uncheck those check boxes.. same if i add a drive to the array

but also mostly the Hardware monitor keeps changing when you remove a UD from the system.. so if you have 2 UD drives pluged in and HWMON2 is set.. when you pull the 2 drives out and reboot.. HWMON2 changes to HWMON0 and buggers up the fans... and or sometimes the disk1 etc wil sometimes uncheck and re check others..

and say if i add another Disk to the array.. so Disk8 it buggers up the fans checked off cuz its not doing UID but the SD and the orders change,, so each time you add an Disk either a cache or a Disk will missup what you have already set

Edited June 11, 2022 by comet424

mmwilson0 · June 11, 2022

6 hours ago, comet424 said:

@mmwilson0 probably the HwmonX has changed.. re detect.. and see if its changed from hwmon0 to like 1 or 2 for each of the 6 pwms that normally fixes it for mel

Thanks for the suggestion @comet424, i tried uninstalling and reinstalling System Temps and Fan Auto Control, and went through the detect on all PWM's... but the fans still dont seem to be being controlled by the plugins at all. Any other thoughts? They sound like they're running at a steady 75%, which they didn't always used to do. If i was downloading and extracting heavily then the fans used to scale up and down appropriately, but currently my home is just one loud "blowing" noise from the fans

ruihere · June 12, 2022

@bonienl I have AMD Ryzen 5 5600U and it failed to detect the temperture sensor drivers. Is there a way I can know my sensor drivers? thanks!

Masterwishx · June 12, 2022

i Think that after reboot autofan is not started automatic but was enabled on pwm3,pwm4 .

What should be done to start it automaticly after reboot ?

comet424 · June 12, 2022

@mmwilson0 try in your bios and if it has like settings for manual and automatic fan controls try the opposite is set for.. i know i had to do that for my asus x570 boards i think i have manual

i know the HWMON keeps changing if i pull or add an un assigned drive

it start of as

hwmon1 but after a reboot it could be hwmon0 or 2 so far no one has an answer to my question how to force it to be 1 not toggle itself

so i always have to click the DETECT and then apply... cuz of the hwmon change each time you reboot if you add remove a unassigned drive

Edited June 12, 2022 by comet424

spl147 · June 12, 2022

2 hours ago, Masterwishx said:

i Think that after reboot autofan is not started automatic but was enabled on pwm3,pwm4 .

What should be done to start it automaticly after reboot ?

look in the autofan config dir, for multiple config files, delete then all except the one that currently reflects your setup, and remove any numbering from the file name, reboot and it will auto start.

i can not believe this plugin has gotten 0 support for so long! it has alot of issues!

spl147 · June 12, 2022

1 hour ago, comet424 said:

@mmwilson0 try in your bios and if it has like settings for manual and automatic fan controls try the opposite is set for.. i know i had to do that for my asus x570 boards i think i have manual

in bios fans should be set to 100% or full speed so auto fan can ramp them up and down 100%.

if they are set to 50% in bios, the auto fan at 100% will only be 50% of the fans output

Dynamix - V6 Plugins

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

bonienl

bonienl

bonienl

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation