Jump to content

  • Unraid OS version 6.9.0-rc1 available

    limetech

    By limetech (edited)

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    Besides bug fixing, most of the work in this release is related to upgrading to the Linux 5.9 kernel where, due to kernel API changes, it has become necessary to move device spin-up/down and spin-up group handling out of the md/unraid driver and have it handled entirely in user space.  This also let us fix an issue where device spin-up of devices in user-defined pools was executed serially instead of in parallel.

     

    We should also now be able to properly support SAS device spin-up/down (finally) and with extraordinary help from @doron we are almost there.  SAS devices are generally designed for enterprise environments where device spin-down is rare, and many devices have inconsistent behavior surrounding this functionality.  This release itself does not include SAS device spin handling built-in but @doron is providing a plugin where we continue to address some nagging details.  We expect to have this ironed out before stable release.

     

    Along with re-work of device spin control, we have also integrated spin-up/down and temperature monitoring for unassigned devices.  We have coordinated with @dlandon to ensure proper integration with the Unassigned Devices plugin.  If you've read this far, and you are using the Unassigned Devices plugin, please remove it first before upgrading and then re-install UD via Community Apps.

     

    Since we have not identified any data loss bugs related to the user-defined pools feature, I have removed the -beta designation and we now enter the -rc phase.  Our plan is for this to be relatively short and limited to squashing bugs.  We are in the process of writing up more thorough release notes in preparation for stable release.

     

    A lot of exciting changes and features are coming to Unraid OS and I want to thank everyone for participating in our Pre-release program!

     

     

    Version 6.9.0-rc1 2020-12-09 (vs -beta35)

    Base distro:

    • aaa_elflibs: version 15.0 build 27
    • hdparm: version 9.60
    • icu4c: version 68.1
    • intel-microcode: version 20201118
    • kernel-firmware: version 20201130_7455a36
    • nginx: version 1.19.5
    • openssh: version 8.4p1
    • pam: version 1.5.1
    • php: version 7.4.13
    • samba: version 4.12.10
    • xfsprogs: version 5.9.0

    Linux kernel:

    • version 5.9.13
    • md/unraid: version 2.9.17
      removed spinup group spinup/spdindown support (functionality moved to emhttpd)
      added configurable sync start offset
    • added iSCSI kernel support:
      CONFIG_ISCSI_TARGET: Linux-iSCSI.org iSCSI Target Mode Stack
      CONFIG_ISCSI_TARGET_CXGB4: Chelsio iSCSI target offload driver
      CONFIG_LOOPBACK_TARGET: TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module
      CONFIG_NVME_TARGET: NVMe Target support
      CONFIG_NVME_TARGET_LOOP: NVMe loopback device support
      CONFIG_NVME_TARGET_PASSTHRU: NVMe Target Passthrough support
      CONFIG_TARGET_CORE: Generic Target Core Mod (TCM) and ConfigFS Infrastructure
      CONFIG_TCM_FILEIO: TCM/FILEIO Subsystem Plugin for Linux/VFS
      CONFIG_TCM_IBLOCK: TCM/IBLOCK Subsystem Plugin for Linux/BLOCK
      CONFIG_TCM_PSCSI: TCM/pSCSI Subsystem Plugin for Linux/SCSI
      CONFIG_TCM_USER2: TCM/USER Subsystem Plugin for Linux
    • added USB/IP kernel support:
      CONFIG_USBIP_CORE: USB/IP support
      CONFIG_USBIP_VHCI_HCD: VHCI hcd

    Management:

    • emhttpd: implement spinup group spinup/spindown; add spinup/spindown callouts
    • emhttpd: get rid of poll_attributes event
    • emhttpd: fix disk "SMART controller type" not being honored when reading temperatures
    • rsyslog: fix broken "Mirror syslog to flash"
    • webgui: Fix wrong docker run URL reference
    • webgui: Fix crash when reading very large log files (limiting output to 1000 lines).
    • webgui: Fix dismiss all notification
    • webgui: Fix Started VMs not appearing in dashboard
    • webgui: VM manager: add virtio-win-0.1.190-1
    • webgui: Notifications: Fix gap on white / black
    • webgui: Do not show CA profiles in Add Container list
    • webgui: support spin-up/down and temperature monitoring of unassigned devices
    • webgui: VM manager: Fix: Changing from VM VNC graphics to GPU passthrough
    • webgui: Change Icon for Motherboard Info from cog (settings) to info

    Edited by limetech

    • Like 22
    Go to reports Prereleases

    User Feedback

    Recommended Comments



    Vr2Io

    Vr2Io 405

    Posted (edited)

    using the Unassigned Devices plugin, please remove it first before upgrading and then re-install UD via Community Apps.

     

    Does this will lost all UD setting ? Best have method to retain config data.

    Edited by Vr2Io
    • Like 1
    mikeyosm

    mikeyosm 36

    Posted

    What if we have already installed the latest UD plugin? Still need to remove it?

    dlandon

    dlandon 1,417

    Posted

    47 minutes ago, Vr2Io said:

    using the Unassigned Devices plugin, please remove it first before upgrading and then re-install UD via Community Apps.

     

    Does this will lost all UD setting ? Best have method to retain config data.

    No.  All UD configuration settings are retained.

    • Like 3
    • Thanks 1
    dlandon

    dlandon 1,417

    Posted

    26 minutes ago, mikeyosm said:

    What if we have already installed the latest UD plugin? Still need to remove it?

    No.  If you have the latest version, you are good to go.

    • Like 6
    • Thanks 2
    lzrdking71

    lzrdking71 9

    Posted (edited)

    20 minutes ago, limetech said:

    Yes, along with updating libvirt

    Any idea if this BSOD bug with qemu 5.0 and windows vm's was fixed in the included qemu 5.1?

    https://www.youtube.com/watch?v=9VSP3aPlOFk

     

    Update: Looking through the comments on that linked video, looks like the answer is yes.

    Edited by lzrdking71
    SimonF

    SimonF 1,283

    Posted

    Beginning of startup missing from syslog.

     

    First entry after reboot.

     

    Dec 10 18:05:53 Tower root: This plugin requires Dynamix webGui to operate

    limetech

    limetech 3,357

    Posted

    35 minutes ago, SimonF said:

    Beginning of startup missing from syslog.

     

    First entry after reboot.

     

    Dec 10 18:05:53 Tower root: This plugin requires Dynamix webGui to operate

    In webGUI Tools/Syslog right?  That window displays only the last 1000 lines.  This releases includes a little more debug info I'm outputting the log and it's probably sending it over the limit.  The file itself /var/log/syslog is intact.  We'll see about adding pagination.  Thanks for the report.

    SimonF

    SimonF 1,283

    Posted

    4 minutes ago, limetech said:

    In webGUI Tools/Syslog right? 

    Yes, my log file is around 2300 lines.

    turnipisum

    turnipisum 16

    Posted

    I'm hitting the update button 🤞

    • Like 1
    limetech

    limetech 3,357

    Posted

    19 minutes ago, SimonF said:

    Yes, my log file is around 2300 lines.

    You can type this command to increase it: 

    sed -i 's/1000/3000/' /usr/local/emhttp/plugins/dynamix/include/Syslog.php

    That will set limit to 3000.

    • Like 1
    • Thanks 1
    turnipisum

    turnipisum 16

    Posted (edited)

    All seems good on the update but i did get call trace on boot. Everything seems to be running fine and didn't lock up.

      

    Dec 10 19:15:26 SKYNET-UR kernel: ------------[ cut here ]------------
Dec 10 19:15:26 SKYNET-UR kernel: WARNING: CPU: 3 PID: 7743 at drivers/iommu/dma-iommu.c:471 __iommu_dma_unmap+0x7a/0xe8
Dec 10 19:15:26 SKYNET-UR kernel: Modules linked in: nfsd lockd grace sunrpc md_mod nct6683 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha bonding atlantic igb i2c_algo_bit r8169 realtek mxm_wmi wmi_bmof edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd btusb glue_helper btrtl btbcm rapl btintel r8125(O) ahci bluetooth libahci ecdh_generic ecc nvme i2c_piix4 nvme_core ccp k10temp i2c_core wmi button acpi_cpufreq [last unloaded: atlantic]
Dec 10 19:15:26 SKYNET-UR kernel: CPU: 3 PID: 7743 Comm: ethtool Tainted: G           O      5.9.13-Unraid #1
Dec 10 19:15:26 SKYNET-UR kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./TRX40 Creator, BIOS P1.70 05/29/2020
Dec 10 19:15:26 SKYNET-UR kernel: RIP: 0010:__iommu_dma_unmap+0x7a/0xe8
Dec 10 19:15:26 SKYNET-UR kernel: Code: 46 28 4c 8d 60 ff 48 8d 54 18 ff 49 21 ec 48 f7 d8 4c 29 e5 49 01 d4 49 21 c4 48 89 ee 4c 89 e2 e8 90 df ff ff 4c 39 e0 74 02 <0f> 0b 49 83 be 68 07 00 00 00 75 32 49 8b 45 08 48 8b 40 48 48 85
Dec 10 19:15:26 SKYNET-UR kernel: RSP: 0018:ffffc90001b7ba40 EFLAGS: 00010206
Dec 10 19:15:26 SKYNET-UR kernel: RAX: 0000000000002000 RBX: 0000000000001000 RCX: 0000000000000001
Dec 10 19:15:26 SKYNET-UR kernel: RDX: ffff889fd593e820 RSI: ffffffffffffe000 RDI: 0000000000000009
Dec 10 19:15:26 SKYNET-UR kernel: RBP: 00000000fed6e000 R08: ffff889fd593e820 R09: ffff889f7effdb70
Dec 10 19:15:26 SKYNET-UR kernel: R10: 0000000000000009 R11: ffff888000000000 R12: 0000000000001000
Dec 10 19:15:26 SKYNET-UR kernel: R13: ffff889fd593e810 R14: ffff889f99db6800 R15: ffffffffa012a600
Dec 10 19:15:26 SKYNET-UR kernel: FS:  000015297c8f9740(0000) GS:ffff889fdd0c0000(0000) knlGS:0000000000000000
Dec 10 19:15:26 SKYNET-UR kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 10 19:15:26 SKYNET-UR kernel: CR2: 000015297ca8b425 CR3: 0000001f7d09c000 CR4: 0000000000350ee0
Dec 10 19:15:26 SKYNET-UR kernel: Call Trace:
Dec 10 19:15:26 SKYNET-UR kernel: iommu_dma_free+0x1a/0x2b
Dec 10 19:15:26 SKYNET-UR kernel: aq_ptp_ring_free+0x31/0x60 [atlantic]
Dec 10 19:15:26 SKYNET-UR kernel: aq_nic_deinit+0x4e/0xa4 [atlantic]
Dec 10 19:15:26 SKYNET-UR kernel: aq_ndev_close+0x26/0x2d [atlantic]
Dec 10 19:15:26 SKYNET-UR kernel: __dev_close_many+0xa1/0xb5
Dec 10 19:15:26 SKYNET-UR kernel: dev_close_many+0x48/0xa6
Dec 10 19:15:26 SKYNET-UR kernel: dev_close+0x42/0x64
Dec 10 19:15:26 SKYNET-UR kernel: aq_set_ringparam+0x4c/0xc8 [atlantic]
Dec 10 19:15:26 SKYNET-UR kernel: ethnl_set_rings+0x202/0x258
Dec 10 19:15:26 SKYNET-UR kernel: genl_rcv_msg+0x1d9/0x251
Dec 10 19:15:26 SKYNET-UR kernel: ? genlmsg_multicast_allns+0xea/0xea
Dec 10 19:15:26 SKYNET-UR kernel: netlink_rcv_skb+0x7d/0xd1
Dec 10 19:15:26 SKYNET-UR kernel: genl_rcv+0x1f/0x2c
Dec 10 19:15:26 SKYNET-UR kernel: netlink_unicast+0x10c/0x19d
Dec 10 19:15:26 SKYNET-UR kernel: netlink_sendmsg+0x29d/0x2d3
Dec 10 19:15:26 SKYNET-UR kernel: sock_sendmsg_nosec+0x32/0x3c
Dec 10 19:15:26 SKYNET-UR kernel: __sys_sendto+0xce/0x109
Dec 10 19:15:26 SKYNET-UR kernel: ? exc_page_fault+0x351/0x37b
Dec 10 19:15:26 SKYNET-UR kernel: __x64_sys_sendto+0x20/0x23
Dec 10 19:15:26 SKYNET-UR kernel: do_syscall_64+0x5d/0x6a
Dec 10 19:15:26 SKYNET-UR kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 10 19:15:26 SKYNET-UR kernel: RIP: 0033:0x15297ca13bc6
Dec 10 19:15:26 SKYNET-UR kernel: Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb bc 0f 1f 80 00 00 00 00 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 11 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 72 c3 90 55 48 83 ec 30 44 89 4c 24 2c 4c 89
Dec 10 19:15:26 SKYNET-UR kernel: RSP: 002b:00007fffc535d018 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
Dec 10 19:15:26 SKYNET-UR kernel: RAX: ffffffffffffffda RBX: 00007fffc535d090 RCX: 000015297ca13bc6
Dec 10 19:15:26 SKYNET-UR kernel: RDX: 000000000000002c RSI: 000000000046f3a0 RDI: 0000000000000004
Dec 10 19:15:26 SKYNET-UR kernel: RBP: 000000000046f2a0 R08: 000015297cae41a0 R09: 000000000000000c
Dec 10 19:15:26 SKYNET-UR kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000000000046f340
Dec 10 19:15:26 SKYNET-UR kernel: R13: 000000000046f330 R14: 0000000000000000 R15: 000000000043504b
Dec 10 19:15:26 SKYNET-UR kernel: ---[ end trace 91c54fcae68e89eb ]---

     

    Edited by turnipisum
    Richard Aarnink

    Richard Aarnink 8

    Posted

    Updated from beta 35. Everyting seems to work. Paritycheck is triggered after updating to rc1. In the System Log however I have several wrong csrf_token messages

     

    Dec 10 20:37:24 RichTech nginx: 2020/12/10 20:37:24 [error] 11802#11802: *5432 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.11.1, server: , request: "POST /plugins/community.applications/scripts/notices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.10.210", referrer: "http://192.168.10.210/Dashboard"
    Dec 10 20:37:24 RichTech nginx: 2020/12/10 20:37:24 [error] 11802#11802: *5425 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.11.1, server: , request: "POST /webGui/include/DashboardApps.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.10.210", referrer: "http://192.168.10.210/Dashboard"
    Dec 10 20:37:39 RichTech rc.docker: webserver-intern: started succesfully!
    Dec 10 20:37:39 RichTech rc.docker: webserver-intern: wait 4 seconds
    Dec 10 20:50:17 RichTech kernel: i2c /dev entries driver
    Dec 10 21:22:34 RichTech root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token
    Dec 10 21:22:34 RichTech root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token
    Dec 10 21:22:55 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token
    Dec 10 21:23:56 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token
    Dec 10 21:24:56 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token
    Dec 10 21:25:57 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token

     

    kroms

    kroms 0

    Posted

    I'm not sure if this is supposed to happen, but the upgrade seems to have changed my drive temperature warning/critical settings.   

    trurl

    trurl 3,068

    Posted

    1 hour ago, Richard Aarnink said:

    Paritycheck is triggered after updating

     

    1 hour ago, Richard Aarnink said:

    wrong csrf_token

     

    SimonF

    SimonF 1,283

    Posted

    @limetech :we have also integrated spin-up/down and temperature monitoring for unassigned devices.

     

    I am not seeing any spindown commands in the syslog for my two UD devices sdb and sdi

     

    sdl for my second pool is working fine.

     

    root@Tower:/usr/local/sbin# lsblk -So NAME,TYPE,MODEL,VENDOR,TRAN
    NAME TYPE MODEL            VENDOR   TRAN
    sda  disk Cruzer_Fit       SanDisk  usb
    sdb  disk Hard_Drive       Sony     usb
    sdc  disk SSD_PLUS_480GB   ATA      sata
    sdd  disk CT500MX500SSD1   ATA      sata
    sde  disk HUS724030ALS640  HGST     sas
    sdf  disk HMRSK2000GBAS07K HITACHI  sas
    sdg  disk HUS724030ALS640  HGST     sas
    sdh  disk HUS724030ALS640  HGST     sas
    sdi  disk HUS724030ALS640  HGST     sas
    sdj  disk HMRSK2000GBAS07K HITACHI  sas
    sdk  disk ST4000NM0023     SEAGATE  sas
    sdl  disk ST3320310CS      ATA      sas
    sr0  rom  BD-RE_BU40N      HL-DT-ST usb

     

    I am only getting failures for my SAS drives in the array.

     

    Dec 10 21:57:59 Tower emhttpd: spinning down /dev/sdl

     

    Dec 10 21:59:22 Tower emhttpd: sdspin /dev/sdj down failed: 5

     

    when do you think the scripts will be available for device specific commands as we should be able to replace the hdparm versions for

     

    sg_start -r --pc=1 device_name for spinup and pc=3 for standby.

     

     

    doron

    doron 131

    Posted

    @SimonF, a new version of the SAS spindown plugin is coming shortly, supporting 6.9.0.

    • Like 1
    Rav20

    Rav20 0

    Posted

    Log file getting spammed tun: unexpected gso type, was on 6.8.3 - I thought this was resolved?

    sivart

    sivart 3

    Posted

    My drives (SATA) are not spinning down. When I manually spin down a drive, it spins up right away.  I can see in the log that it does in fact try to spin down the drive.  This was working on beta35.

    limetech

    limetech 3,357

    Posted

    2 hours ago, kroms said:

    I'm not sure if this is supposed to happen, but the upgrade seems to have changed my drive temperature warning/critical settings.   

    Yes that's expected, sorry about that.

    klogg

    klogg 16

    Posted

    Upgrade went well, but seeing winbindd is spamming the log. Any guesses?

      

    Dec 10 19:09:01 Marvin winbindd[8494]: [2020/12/10 19:09:01.457311, 3] ../../source3/winbindd/winbindd_misc.c:429(winbindd_interface_version)
Dec 10 19:09:01 Marvin winbindd[8494]: winbindd_interface_version: [nss_winbind (22681)]: request interface version (version = 31)
Dec 10 19:09:01 Marvin winbindd[8494]: [2020/12/10 19:09:01.457470, 3] ../../source3/winbindd/winbindd_getgroups.c:63(winbindd_getgroups_send)
Dec 10 19:09:01 Marvin winbindd[8494]: winbindd_getgroups_send: [nss_winbind (22681)] getgroups root
Dec 10 19:09:13 Marvin unassigned.devices: Updating share settings...
Dec 10 19:09:13 Marvin unassigned.devices: Share settings updated.
Dec 10 19:09:32 Marvin emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkall
Dec 10 19:10:01 Marvin winbindd[8494]: [2020/12/10 19:10:01.502999, 3] ../../source3/winbindd/winbindd_misc.c:429(winbindd_interface_version)
Dec 10 19:10:01 Marvin winbindd[8494]: winbindd_interface_version: [nss_winbind (25008)]: request interface version (version = 31)
Dec 10 19:10:01 Marvin winbindd[8494]: [2020/12/10 19:10:01.503079, 3] ../../source3/winbindd/winbindd_getgroups.c:63(winbindd_getgroups_send)
Dec 10 19:10:01 Marvin winbindd[8494]: winbindd_getgroups_send: [nss_winbind (25008)] getgroups root
Dec 10 19:11:01 Marvin winbindd[8494]: [2020/12/10 19:11:01.548048, 3] ../../source3/winbindd/winbindd_misc.c:429(winbindd_interface_version)
Dec 10 19:11:01 Marvin winbindd[8494]: winbindd_interface_version: [nss_winbind (26459)]: request interface version (version = 31)
Dec 10 19:11:01 Marvin winbindd[8494]: [2020/12/10 19:11:01.548217, 3] ../../source3/winbindd/winbindd_getgroups.c:63(winbindd_getgroups_send)
Dec 10 19:11:01 Marvin winbindd[8494]: winbindd_getgroups_send: [nss_winbind (26459)] getgroups root
Dec 10 19:11:54 Marvin ntpd[1800]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Dec 10 19:12:01 Marvin winbindd[8494]: [2020/12/10 19:12:01.593320, 3] ../../source3/winbindd/winbindd_misc.c:429(winbindd_interface_version)
Dec 10 19:12:01 Marvin winbindd[8494]: winbindd_interface_version: [nss_winbind (27619)]: request interface version (version = 31)
Dec 10 19:12:01 Marvin winbindd[8494]: [2020/12/10 19:12:01.593448, 3] ../../source3/winbindd/winbindd_getgroups.c:63(winbindd_getgroups_send)
Dec 10 19:12:01 Marvin winbindd[8494]: winbindd_getgroups_send: [nss_winbind (27619)] getgroups root
Dec 10 19:12:01 Marvin winbindd[8496]: [2020/12/10 19:12:01.593602, 3] ../../source3/winbindd/winbindd_samr.c:597(sam_name_to_sid)
Dec 10 19:12:01 Marvin winbindd[8496]: sam_name_to_sid
Dec 10 19:12:01 Marvin winbindd[8496]: [2020/12/10 19:12:01.593636, 3] ../../source3/winbindd/winbindd_rpc.c:281(rpc_name_to_sid)
Dec 10 19:12:01 Marvin winbindd[8496]: name_to_sid: ROOT for domain
Dec 10 19:12:01 Marvin winbindd[8496]: [2020/12/10 19:12:01.593862, 3] ../../source3/passdb/lookup_sid.c:1605(get_primary_group_sid)
Dec 10 19:12:01 Marvin winbindd[8496]: Forcing Primary Group to 'Domain Users' for root
Dec 10 19:12:01 Marvin winbindd[8496]: [2020/12/10 19:12:01.594069, 3] ../../source3/winbindd/winbindd_rpc.c:281(rpc_name_to_sid)
Dec 10 19:12:01 Marvin winbindd[8496]: name_to_sid: ROOT for domain
Dec 10 19:12:01 Marvin winbindd[8496]: [2020/12/10 19:12:01.594317, 3] ../../source3/passdb/lookup_sid.c:1605(get_primary_group_sid)
Dec 10 19:12:01 Marvin winbindd[8496]: Forcing Primary Group to 'Domain Users' for root
Dec 10 19:12:12 Marvin winbindd[8496]: [2020/12/10 19:12:12.723325, 3] ../../source3/winbindd/winbindd_misc.c:289(winbindd_dual_list_trusted_domains)
Dec 10 19:12:12 Marvin winbindd[8496]: winbindd_dual_list_trusted_domains: [ 8494]: list trusted domains
Dec 10 19:12:12 Marvin winbindd[8496]: [2020/12/10 19:12:12.723374, 3] ../../source3/winbindd/winbindd_samr.c:343(sam_trusted_domains)
Dec 10 19:12:12 Marvin winbindd[8496]: samr: trusted domains
Dec 10 19:13:01 Marvin winbindd[8494]: [2020/12/10 19:13:01.640867, 3] ../../source3/winbindd/winbindd_misc.c:429(winbindd_interface_version)
Dec 10 19:13:01 Marvin winbindd[8494]: winbindd_interface_version: [nss_winbind (28794)]: request interface version (version = 31)
Dec 10 19:13:01 Marvin winbindd[8494]: [2020/12/10 19:13:01.640986, 3] ../../source3/winbindd/winbindd_getgroups.c:63(winbindd_getgroups_send)
Dec 10 19:13:01 Marvin winbindd[8494]: winbindd_getgroups_send: [nss_winbind (28794)] getgroups root
Dec 10 19:13:01 Marvin winbindd[8496]: [2020/12/10 19:13:01.641526, 3] ../../source3/winbindd/winbindd_samr.c:754(sam_rids_to_names)
Dec 10 19:13:01 Marvin winbindd[8496]: sam_rids_to_names for MARVIN
Dec 10 19:13:01 Marvin winbindd[8496]: [2020/12/10 19:13:01.641860, 3] ../../source3/winbindd/winbindd_samr.c:1084(sam_sequence_number)
Dec 10 19:13:01 Marvin winbindd[8496]: samr: sequence number

     

    Niklas

    Niklas 73

    Posted

    Spin down works here but this spins them up from time to time. What could be the cause?

     

    Quote

    Dec 11 01:41:41 Server emhttpd: read SMART /dev/sdg
    Dec 11 01:41:41 Server emhttpd: read SMART /dev/sde
    Dec 11 01:41:44 Server emhttpd: read SMART /dev/sdf

     

    limetech

    limetech 3,357

    Posted

    1 minute ago, Niklas said:

    Spin down works here but this spins them up from time to time. What could be the cause?

     

     

    I/O to the devices



    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
    Add a comment...

    ×   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.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...