Dynamix - V6 Plugins


Recommended Posts

I discovered a typo bug a few weeks ago but forgot to mention it.. when you have the System Temps plugin running, and it's setup to show the cpu temp at the bottom of the Unraid screens; hovering the mouse over the temp says "Procesor" and not "Processor" (with 2 S's).

Link to comment

hi,

i find that after restarting my server there seems to be some (? run-away ?) sh process linked to folder caching. it easts cpu cycles in regular peaks and does not ever stop. i have folder caching enabled (but not for /mnt/user, because that eats even more power). killing the process gets the cpu usage down to 'normal' idle levels. it reappears after reboot though. any tips on what i am seeing here?

Link to comment

hi any ideas how to run fan control on Terramaster F5-221?

 

already done \boot\config\go:

# sensors

modprobe it87 force_id=0x8620

 

but did not see the fan arrays.

clicking on fan detect there is nothing happen.

 

i have replaced the original fans with noctuas, but them still to loud on 2000 pwm...

 

root@BruRaid:~# sensors
it8620-isa-0a20
Adapter: ISA adapter
in0:           1.08 V  (min =  +0.59 V, max =  +0.61 V)
in1:           1.50 V  (min =  +1.97 V, max =  +0.50 V)
in2:           2.14 V  (min =  +0.58 V, max =  +1.88 V)
+5V:           4.27 V  (min =  +1.18 V, max =  +3.50 V)
in4:           2.18 V  (min =  +0.96 V, max =  +1.24 V)
in5:           2.26 V  (min =  +0.18 V, max =  +1.60 V)
in6:         420.00 mV (min =  +0.40 V, max =  +1.62 V)
3VSB:        480.00 mV (min =  +0.60 V, max =  +0.48 V)
Vbat:          3.19 V
temp1:        +33.0°C  (low  = +52.0°C, high = -52.0°C)  sensor = thermal diode
temp2:        +31.0°C  (low  = -113.0°C, high = -54.0°C)  sensor = thermal diode
temp3:        +31.0°C  (low  = -12.0°C, high = -90.0°C)  sensor = disabled
temp4:        +31.0°C
temp5:        +31.0°C
temp6:        +31.0°C
intrusion0:  ALARM

acpitz-acpi-0
Adapter: ACPI interface
MB Temp:      +38.0°C  (crit = +100.0°C)

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +39.0°C  (high = +105.0°C, crit = +105.0°C)
Core 0:       +38.0°C  (high = +105.0°C, crit = +105.0°C)
Core 2:       +39.0°C  (high = +105.0°C, crit = +105.0°C)

 

 

 

root@BruRaid:~# sensors-detect
# sensors-detect version 3.6.0
# System: retsamarret 000-F5221-FBA002-0001 [Default string]
# Board: retsamarret Default string
# Kernel: 5.15.43-Unraid x86_64
# Processor: Intel(R) Celeron(R) CPU J3355 @ 2.00GHz (6/92/9)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8613E Super IO Sensors'                        Success!
    (address 0xa20, driver `to-be-written')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.1: Broxton (SOC)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at f040 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: i915 gmbus dpb (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x49
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No

Next adapter: i915 gmbus dpc (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus misc (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Driver `to-be-written':
  * ISA bus, address 0xa20
    Chip `ITE IT8613E Super IO Sensors' (confidence: 9)

Note: there is no driver for ITE IT8613E Super IO Sensors yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

Unloading i2c-dev... OK

root@BruRaid:~#

 

image.thumb.png.8beb91b2c5eec766439b76c2fc66fa27.png

 

image.thumb.png.4cd82b4fff11f802802392754fbd91dd.png

 

Link to comment
6 hours ago, x0fflin3 said:

hi any ideas how to run fan control on Terramaster F5-221?

 

already done \boot\config\go:

# sensors

modprobe it87 force_id=0x8620

 

but did not see the fan arrays.

clicking on fan detect there is nothing happen.

 

i have replaced the original fans with noctuas, but them still to loud on 2000 pwm...

 

root@BruRaid:~# sensors
it8620-isa-0a20
Adapter: ISA adapter
in0:           1.08 V  (min =  +0.59 V, max =  +0.61 V)
in1:           1.50 V  (min =  +1.97 V, max =  +0.50 V)
in2:           2.14 V  (min =  +0.58 V, max =  +1.88 V)
+5V:           4.27 V  (min =  +1.18 V, max =  +3.50 V)
in4:           2.18 V  (min =  +0.96 V, max =  +1.24 V)
in5:           2.26 V  (min =  +0.18 V, max =  +1.60 V)
in6:         420.00 mV (min =  +0.40 V, max =  +1.62 V)
3VSB:        480.00 mV (min =  +0.60 V, max =  +0.48 V)
Vbat:          3.19 V
temp1:        +33.0°C  (low  = +52.0°C, high = -52.0°C)  sensor = thermal diode
temp2:        +31.0°C  (low  = -113.0°C, high = -54.0°C)  sensor = thermal diode
temp3:        +31.0°C  (low  = -12.0°C, high = -90.0°C)  sensor = disabled
temp4:        +31.0°C
temp5:        +31.0°C
temp6:        +31.0°C
intrusion0:  ALARM

acpitz-acpi-0
Adapter: ACPI interface
MB Temp:      +38.0°C  (crit = +100.0°C)

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +39.0°C  (high = +105.0°C, crit = +105.0°C)
Core 0:       +38.0°C  (high = +105.0°C, crit = +105.0°C)
Core 2:       +39.0°C  (high = +105.0°C, crit = +105.0°C)

 

 

 

root@BruRaid:~# sensors-detect
# sensors-detect version 3.6.0
# System: retsamarret 000-F5221-FBA002-0001 [Default string]
# Board: retsamarret Default string
# Kernel: 5.15.43-Unraid x86_64
# Processor: Intel(R) Celeron(R) CPU J3355 @ 2.00GHz (6/92/9)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8613E Super IO Sensors'                        Success!
    (address 0xa20, driver `to-be-written')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.1: Broxton (SOC)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at f040 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: i915 gmbus dpb (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x49
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No

Next adapter: i915 gmbus dpc (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus misc (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Driver `to-be-written':
  * ISA bus, address 0xa20
    Chip `ITE IT8613E Super IO Sensors' (confidence: 9)

Note: there is no driver for ITE IT8613E Super IO Sensors yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

Unloading i2c-dev... OK

root@BruRaid:~#

 

image.thumb.png.8beb91b2c5eec766439b76c2fc66fa27.png

 

image.thumb.png.4cd82b4fff11f802802392754fbd91dd.png

 

ok, so this is the second time i have replied to this question! there is no driver for the fan controller on your board!!!!! NO DRIVER NO CONTROL!

 

Driver `to-be-written': * ISA bus, address 0xa20 Chip

`ITE IT8613E Super IO Sensors' (confidence: 9)

 

Note: there is no driver for ITE IT8613E Super IO Sensors yet.

Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Link to comment

I have a S3 Sleep question, why do I need to manually disable write cache on my disks?

 

Because if the drives are spun down, and the plugin executes this

mem >/sys/power/state

Unraid will send a cache flush and the drives spin up again for no reason (or just to write cache, which would be strange if it is delayed by 15 minutes)

I use this post sleep command to remove write cache

printf /dev/sd%s\\n {b..e} | xargs -n 1 hdparm -W0


Would it make sense to add this to the sleep plugin configuration, or is my unraid wrongly configured? I didn't find this setting on the GUI. And I don't notice any performance issues on write. But the additional spin up was just unnecessary.

Link to comment
On 5/24/2022 at 6:01 PM, itimpi said:

The script I use is:

#!/bin/bash
#noParity=true
logger "overnight powerdown"
powerdown

In User Scripts.  The #noparity line stops the shutdown happening if a parity check is running.

 

I then use a custom schedule of:

15 0 * * 1-6

to shutdown at 15 minutes after midnight except on Sundays (as I have a special task running then that needs the server active).

 

Why not using sleep plugin ?

is any problem with it ?

also after   cat powerdown 

 

image.png.08125c166d1932e1fec9a796f04db551.png

 

is it deprecated ?

 

im trying to setup my server to shutdown and up like from 8:00 - 1:00 or 0:00 and having parity check on 1th every month at 0:00

so i need eather to check if parity or diable shutdown on 1th ...

 

Having MSI H87M-G43 in bios setup entered 8:30 for boot up and pcie enabled for wol but its not working from bios ,also having date from 1-31 but what date i need to enter for every day ?

The wol working from wol app in smartphone but need ethtool -s eth0 wol g , ethtool -s eth1 wol g run commands in terminal befor shutdown ...

So i dont know what is better to use sleep plugin or just script for shutdown ... 

 

 

 

Link to comment

Hi! like another users, im having unclean shutdowns and parity check with the s3 plugin. Has this issue been adressed yet?

 

  • no dockers/vm at the moment
  • triggers are array unactivity with counters only, because status trigger detects activity every minute and never sleeps (XXXXXX s3_sleep: Disk activity on going:). Even tried the spin down button, no luck.
  • domain,isos, appdata and system set to cache prefer.

 

Thank you!

Edited by kalidus
Link to comment
On 6/4/2022 at 2:25 PM, Masterwishx said:

and how to start up automatic from shutdown if i dont have DD-WRT on TP-Link routher but having oracle free cloud server so one option to wol from this ...

You need some kind of low powered device in your network which is always on to forward the WOL. I use an old rasperyPi which uses ~1W

And because I'm lazy and don't want to implement WOL on any device, I use https://github.com/nikp123/wake-on-arp

 

@kalidus

There is no known issue so far, we only know about unsupported combinations of features.

Write your logs to flash and check which thing is stopping unraid from powering down.

 

If you don't use shutdown at all, because you only work with sleep, then you may be effected by this:

https://github.com/bergware/dynamix/issues/59

 

Link to comment

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.

  • Like 1
Link to comment
34 minutes ago, Falcosc said:

@kalidus

There is no known issue so far, we only know about unsupported combinations of features.

Write your logs to flash and check which thing is stopping unraid from powering down.

 

If you don't use shutdown at all, because you only work with sleep, then you may be effected by this:

https://github.com/bergware/dynamix/issues/59

 

Thanks for your answer, but unfortunately is not my case. In fact, the only log i get is repetead again and again...:

Jun 7 18:02:20 XXX s3_sleep: Disk activity on going: sdd

Jun 7 18:02:20 XXX s3_sleep: Disk activity detected. Reset timers.

 

i have no pre or post scripts, no disk activity at all, no files being opened, no IO activity, no dockers, no vms...

Link to comment
1 hour ago, Falcosc said:

The reason for unclean shutdowns can be found in the log as well. For example, in my case it was failed to unmount, and then I found the process.

This is the only thing i get in the flash log:

19:17:32 XXXX s3_sleep: Disk activity on going: sdb

19:17:32 XXXX s3_sleep: Disk activity detected. Reset timers.

Edited by kalidus
Link to comment
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 by kalidus
Link to comment

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 by Falcosc
Link to comment
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

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.