• Unraid OS version 6.9.0-rc2 available


    limetech

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

     

    Hopefully spin-up/down sorted:

    • External code (docker containers) using 'smartctl -n standby' should work ok with SATA drives.  This will remain problematic for SAS until/unless smartmontools v7.2 is released with support for '-n standby' with SAS.
    • SMART is unconditionally enabled on devices upon boot.  This solves problem where some newly installed devices may not have SMART enabled.
    • Unassigned devices will get spun-down according to 'Settings/Disk Settings/Default spin down delay'.

     

    Updated to 5.10 Linux kernel (5.10.1).

     

    Updated docker.

     

    Fixed bug joining AD domains.

     


     

    Version 6.9.0-rc2 2020-12-18 (vs -rc1)

    Base distro:

    • bind: verison 9.16.8
    • docker: version 19.03.14
    • krb5: version 1.18.2

    Linux kernel:

    • version 5.10.1

    Management:

    • emhttpd: fix external 'smartctl -n standby' causing device spinup
    • emhttpd: enable SMART on devices upon startup
    • emhttpd: unassigned devices spin-down according to global default
    • emhttpd: restore 'poll_attributes' event callout
    • smb: fixed AD join issue
    • webgui: do not try to display SMART info that causes spin-up for devices that are spun-down
    • webgui: avoid php syntax error if autov() source file does not exist

    Edited by limetech

    • Like 8
    • Thanks 4


    User Feedback

    Recommended Comments



    I will be upgrading to this RC. @limetech said there will be a 'more thorough release notes in preparation for stable release', is there anyway we can see (even if incomplete) these notes to prepare for upgrading to an rc version. Does anyone have a list of checks/changes I should do in preparation to upgrade from 6.8.3 stable to 6.9rc2?

    Link to comment
    Share on other sites
    1 hour ago, SimonF said:

    I am guessing you see temps on 6.8?

     

    What do you get if you run smartctl -A /dev/sdX with sdX being the name of the cache drives?

    Yes im am getting temps on 6.8. 

     

    I have restored back to 6.8 now and unfortunately didnt note it down however it was a short 3 line response telling me my smart is enabled... however as i said not what i expected.

     

    This gui also showed this in disk settings:

     

    SMART support:Available - device has SMART capability.

    SMART support:Disabled

    Edited by Mkultra
    Link to comment
    Share on other sites
    4 minutes ago, Mkultra said:

    temps on 6.8. 

    You need to open terminal window to run the commands, but if it works on 6.8 it should work on 6.9.

     

    This is one of my SATA SSDs Run the command on both 6.8 and 6.9. Suggest if you still have an issue raise a bug report for it under 6.9 with diagnostics. 

     

    root@unraid:/boot/config/plugins# smartctl -iA /dev/sde
    smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build)
    Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Device Model:     Samsung SSD 860 QVO 2TB
    Serial Number:    
    LU WWN Device Id: 5 002538 e49b445e2
    Firmware Version: RVQ01B6Q
    User Capacity:    2,000,398,934,016 bytes [2.00 TB]
    Sector Size:      512 bytes logical/physical
    Rotation Rate:    Solid State Device
    Form Factor:      2.5 inches
    Device is:        Not in smartctl database [for details use: -P showall]
    ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
    SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
    Local Time is:    Sat Dec 19 20:16:13 2020 GMT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    === START OF READ SMART DATA SECTION ===
    SMART Attributes Data Structure revision number: 1
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
      9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       6674
     12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       5
    177 Wear_Leveling_Count     0x0013   077   077   000    Pre-fail  Always       -       183
    179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
    181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
    182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
    183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
    187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0032   052   037   000    Old_age   Always       -       48
    195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       -       0
    199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       -       0
    235 Unknown_Attribute       0x0012   099   099   000    Old_age   Always       -       1
    241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       429167919447
     

    Link to comment
    Share on other sites

    yes it looks like that on 6.8 however on 6.9 ther terminal gave me short 3 line response telling me Smart status is enabled 

     

    Link to comment
    Share on other sites

    this is what i get on 6.8

     

    smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build)
    Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF READ SMART DATA SECTION ===
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
      5 Reallocate_NAND_Blk_Cnt 0x0032   100   100   010    Old_age   Always       -       0
      9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       4314
     12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       15
    171 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
    172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
    173 Ave_Block-Erase_Count   0x0032   093   093   000    Old_age   Always       -       106
    174 Unexpect_Power_Loss_Ct  0x0032   100   100   000    Old_age   Always       -       4
    180 Unused_Reserve_NAND_Blk 0x0033   000   000   000    Pre-fail  Always       -       43
    183 SATA_Interfac_Downshift 0x0032   100   100   000    Old_age   Always       -       0
    184 Error_Correction_Count  0x0032   100   100   000    Old_age   Always       -       0
    187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
    194 Temperature_Celsius     0x0022   067   038   000    Old_age   Always       -       33 (Min/Max 0/62)
    196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
    197 Bogus_Current_Pend_Sect 0x0032   100   100   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
    202 Percent_Lifetime_Remain 0x0030   093   093   001    Old_age   Offline      -       7
    206 Write_Error_Rate        0x000e   100   100   000    Old_age   Always       -       0
    210 Success_RAIN_Recov_Cnt  0x0032   100   100   000    Old_age   Always       -       0
    246 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       26188475856
    247 Host_Program_Page_Count 0x0032   100   100   000    Old_age   Always       -       433658808
    248 FTL_Program_Page_Count  0x0032   100   100   000    Old_age   Always       -       599037965

    Link to comment
    Share on other sites

    It may be a controller issue with the new kernel(unlikely if disks are seen), create a new bug request and post diagnostics from 6.9. As your smarctl output looks similar to mine my sata SSDs on 6.9rc2

    Edited by SimonF
    Link to comment
    Share on other sites
    43 minutes ago, thecode said:

    Can someone comment what versions of Libvirt & QEMU are used in this release?

    Libvirt version: 6.5.0

    QEMU version: 5.1.0

     

    • Thanks 1
    Link to comment
    Share on other sites

    If you don't see device temperatures upon reboot, just click "spin up all" and everything should be fine until I can release -rc3.

    • Like 3
    Link to comment
    Share on other sites

    Thanks for the help guys, Im swapping out a motherboard/cpu on this machine next week so i may just wait until thats done! Maybe rc3 will be ready to put through its paces by then anyway :)

    Link to comment
    Share on other sites

    I still can't join AD server, this is the error I get.

    
    
    ErrorWarningSystemArrayLogin
    
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.668700, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.668712, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:04:00 Storage winbindd[12390]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.674433, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.677730, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.681872, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.683674, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.689713, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.689731, 0] ../../source3/libads/kerberos.c:139(kerberos_kinit_password_ext)
    Dec 19 19:04:00 Storage winbindd[12390]: kerberos_kinit_password_ext: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.689797, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.689846, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.689862, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:04:00 Storage winbindd[12390]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.693688, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.695374, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.697871, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:00 Storage winbindd[12390]: [2020/12/19 19:04:00.702137, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:00 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:01 Storage avahi-daemon[11274]: Service "Storage" (/services/smb.service) successfully established.
    Dec 19 19:04:01 Storage winbindd[12390]: [2020/12/19 19:04:01.597715, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:01 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:01 Storage winbindd[12390]: [2020/12/19 19:04:01.597774, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:04:01 Storage winbindd[12390]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:04:01 Storage winbindd[12390]: [2020/12/19 19:04:01.597787, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:04:01 Storage winbindd[12390]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:34 Storage emhttpd: shcmd (283): /usr/local/emhttp/webGui/scripts/update_access
    Dec 19 19:06:34 Storage sshd[12176]: Received signal 15; terminating.
    Dec 19 19:06:35 Storage sshd[13075]: Server listening on 0.0.0.0 port 22.
    Dec 19 19:06:35 Storage sshd[13075]: Server listening on :: port 22.
    Dec 19 19:06:36 Storage emhttpd: Stopping services...
    Dec 19 19:06:36 Storage unassigned.devices: Unmounting All Devices...
    Dec 19 19:06:36 Storage emhttpd: shcmd (287): /etc/rc.d/rc.samba stop
    Dec 19 19:06:36 Storage winbindd[12388]: [2020/12/19 19:06:36.987180, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
    Dec 19 19:06:36 Storage winbindd[12388]: Got sig[15] terminate (is_parent=1)
    Dec 19 19:06:36 Storage winbindd[12390]: [2020/12/19 19:06:36.987210, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
    Dec 19 19:06:36 Storage winbindd[12390]: Got sig[15] terminate (is_parent=0)
    Dec 19 19:06:37 Storage emhttpd: shcmd (288): rm -f /etc/avahi/services/smb.service
    Dec 19 19:06:37 Storage avahi-daemon[11274]: Files changed, reloading.
    Dec 19 19:06:37 Storage avahi-daemon[11274]: Service group file /services/smb.service vanished, removing services.
    Dec 19 19:06:37 Storage emhttpd: Starting services...
    Dec 19 19:06:37 Storage emhttpd: shcmd (292): /etc/rc.d/rc.samba start
    Dec 19 19:06:37 Storage root: Starting Samba: /usr/sbin/smbd -D
    Dec 19 19:06:37 Storage root: /usr/sbin/wsdd
    Dec 19 19:06:37 Storage smbd[13273]: [2020/12/19 19:06:37.223818, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
    Dec 19 19:06:37 Storage smbd[13273]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
    Dec 19 19:06:37 Storage root: /usr/sbin/winbindd -D
    Dec 19 19:06:37 Storage winbindd[13286]: [2020/12/19 19:06:37.255490, 0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache)
    Dec 19 19:06:37 Storage winbindd[13286]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
    Dec 19 19:06:37 Storage winbindd[13286]: [2020/12/19 19:06:37.255915, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
    Dec 19 19:06:37 Storage winbindd[13286]: daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections
    Dec 19 19:06:37 Storage emhttpd: shcmd (293): cp /tmp/emhttp/smb.service /etc/avahi/services/smb.service
    Dec 19 19:06:37 Storage avahi-daemon[11274]: Files changed, reloading.
    Dec 19 19:06:37 Storage avahi-daemon[11274]: Loading service file /services/smb.service.
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.265212, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.265238, 0] ../../source3/libads/kerberos.c:139(kerberos_kinit_password_ext)
    Dec 19 19:06:37 Storage winbindd[13288]: kerberos_kinit_password_ext: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.265319, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.265382, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.265399, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:06:37 Storage winbindd[13288]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.275441, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.275460, 0] ../../source3/libads/kerberos.c:139(kerberos_kinit_password_ext)
    Dec 19 19:06:37 Storage winbindd[13288]: kerberos_kinit_password_ext: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.275497, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.275539, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.275548, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:06:37 Storage winbindd[13288]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.284310, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.284375, 0] ../../source3/libads/kerberos.c:139(kerberos_kinit_password_ext)
    Dec 19 19:06:37 Storage winbindd[13288]: kerberos_kinit_password_ext: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.284502, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.284637, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:37 Storage winbindd[13288]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:37 Storage winbindd[13288]: [2020/12/19 19:06:37.284668, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:06:37 Storage winbindd[13288]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:38 Storage avahi-daemon[11274]: Service "Storage" (/services/smb.service) successfully established.
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.277683, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.277709, 0] ../../source3/libads/kerberos.c:139(kerberos_kinit_password_ext)
    Dec 19 19:06:42 Storage winbindd[13286]: kerberos_kinit_password_ext: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.277803, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.277855, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.277867, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:06:42 Storage winbindd[13286]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.289816, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.289841, 0] ../../source3/libads/kerberos.c:139(kerberos_kinit_password_ext)
    Dec 19 19:06:42 Storage winbindd[13286]: kerberos_kinit_password_ext: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.289893, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.289938, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.289947, 0] ../../source3/librpc/crypto/gse.c:211(gse_context_init)
    Dec 19 19:06:42 Storage winbindd[13286]: gse_context_init: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.299479, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.299494, 0] ../../source3/libads/kerberos.c:139(kerberos_kinit_password_ext)
    Dec 19 19:06:42 Storage winbindd[13286]: kerberos_kinit_password_ext: kerberos init context failed (Included profile file could not be read)
    Dec 19 19:06:42 Storage winbindd[13286]: [2020/12/19 19:06:42.299527, 0] ../../lib/krb5_wrap/krb5_samba.c:3549(smb_krb5_init_context_common)
    Dec 19 19:06:42 Storage winbindd[13286]: smb_krb5_init_context_common: Krb5 context initialization failed (Included profile file could not be read)

     

    Link to comment
    Share on other sites

    Thank you for the update this has seemed to resolve the issue with my container not being able to see smartctl. My temps are showing again however the Telegraf log is showing a different error now but the temps are in fact showing.

    2020-12-19T22:22:49Z W! [inputs.smart] nvme not found: verify that nvme is installed and it is in your PATH (or specified in config) to gather vendor specific attributes: provided path does not exist: []
     
    

     

    Link to comment
    Share on other sites

    This is an issue on RC1. I have not tested on RC2, since my networking setup has since changed, but if you didn't know about this, it probably applies to RC2 as well.

     

    Firstly, if we're enabling VLANs, and put an IP on a VLAN, but don't want an IP on the whole untagged interface, there probably should be an option for "no IP" rather than just letting "automatic" give it a 169 address. It's a minor annoyance that leads to the 169 address showing in the top right corner, as opposed to the real, set IP in the VLAN interface.

     

    The problem this creates is that in this scenario, where there's an auto 169 address on the untagged interface, and the "real" accessible web UI IP on a tagged VLAN on the same interface, installing things like plugins fails, because the 169 address has no internet connection, so Unraid can't connect to the internet.

     

    My guess is the best way to handle that would be to try the next IP in line on a VLAN should the main interface IP fail to resolve internet, until it hits one that works, instead of just giving up after the first fail. And/or let us "disable" IP assignment on an interface, or subinterface, so that instead of trying the untagged VLAN on a port, it knows to skip it, and use the tagged VLAN IP instead.

    Link to comment
    Share on other sites
    4 hours ago, Brandon87 said:

    No longer able to boot into GUI MODE since 6.9. Just hangs with black screen and blinking cursor. Was working fine on 6.8.3

    I discussed this problem in the forums weeks ago.  There is no fix as far as I know, and no plan to fix it.  I was told basically:  "It just happens sometimes".  

     

     

    Link to comment
    Share on other sites
    6 hours ago, TechGeek01 said:

    This is an issue on RC1. I have not tested on RC2, since my networking setup has since changed, but if you didn't know about this, it probably applies to RC2 as well.

     

    Firstly, if we're enabling VLANs, and put an IP on a VLAN, but don't want an IP on the whole untagged interface, there probably should be an option for "no IP" rather than just letting "automatic" give it a 169 address. It's a minor annoyance that leads to the 169 address showing in the top right corner, as opposed to the real, set IP in the VLAN interface.

     

    The problem this creates is that in this scenario, where there's an auto 169 address on the untagged interface, and the "real" accessible web UI IP on a tagged VLAN on the same interface, installing things like plugins fails, because the 169 address has no internet connection, so Unraid can't connect to the internet.

     

    My guess is the best way to handle that would be to try the next IP in line on a VLAN should the main interface IP fail to resolve internet, until it hits one that works, instead of just giving up after the first fail. And/or let us "disable" IP assignment on an interface, or subinterface, so that instead of trying the untagged VLAN on a port, it knows to skip it, and use the tagged VLAN IP instead.

    This is exactly how networking works. When any process decides to access something, the network stack consults the routing table and determines what interface and router to use. If your untagged interface (regardless of IP) does not have a gateway defined then it will not get used to reach the internet. A lot of times before people had multiple VLANs with gateways configured (statically or dhcp), this would make it so the lastest interface to come up and be added to routing table would get used as the internet connection - even if the last interface to come up doesn't have a working internet.

     

    I suppose a missing feature of unraid is the ability for us to define/tweak the desired table, including overrides for DHCP enabled interfaces and other suck configurations.

     

    Link to comment
    Share on other sites
    9 hours ago, JaseNZ said:

    Thank you for the update this has seemed to resolve the issue with my container not being able to see smartctl. My temps are showing again however the Telegraf log is showing a different error now but the temps are in fact showing.

    
    2020-12-19T22:22:49Z W! [inputs.smart] nvme not found: verify that nvme is installed and it is in your PATH (or specified in config) to gather vendor specific attributes: provided path does not exist: []
     
    

     

    This error is due to the absence of the 'nvme-cli' package in the container, and thus the 'nvme' command. You have to install the missing package through the "Post Arguments" parameter of the container (Edit/Advanced View).

    Here's the content of my "Post Argument" param for reference, properly working with nvme devices, to be adapted of course to your specific configuration if required :

    /bin/sh -c 'apt-get update && apt-get -y upgrade && apt-get -y install ipmitool && apt-get -y install smartmontools && apt-get -y install lm-sensors && apt-get -y install nvme-cli && telegraf'

    Edit the parameter according to your needs, the container will restart and you shouldn't have the error message in the log.

    Edited by Gnomuz
    • Thanks 1
    Link to comment
    Share on other sites

    hello,

    i am having problems with my conbee 2 stick since RC1 and RC2. i use the marthoc/deconz docker, in .35 after boot, all my lamps and switches are connected and the mesh is working like it should be. but with rc1 and rc2 after reboot all devices are disconnected, maybe 1 is connected, the mesh network does not rebuild anymore and i am not able to get them connected again, in the logs i can see many of this "error APSDE-DATA.confirm: 0xE1 on task".

    i tried to reset the network, i tried to reconnect the stick, but this error stay. if i downgrade to .35 after reboot the mesh notwork is instant complete back up and working without any issues, reconnects or replugging the conbee 2 stick.

    Edited by M2k
    Link to comment
    Share on other sites

     Hello,

    I switched from the beta35 to the RC1. After switching to the RC1, the server is simply shut down at irregular intervals. Deactivating S3 did not help either. In the end the server shut down in under a minute, so that I had problems getting back to the beta 35. RC2 runs fine. :)

    Edited by Locutos
    Link to comment
    Share on other sites
    1 hour ago, shaunmccloud said:

    Is anyone else getting a kernel panic on boot of RC2?  I'm currently rolling back to RC1 due to this.

    i just did get kernel panic. Not at boot, but when booted

    Edited by Tulip
    Link to comment
    Share on other sites
    32 minutes ago, Tulip said:

    i just did get kernel panic. Not at boot, but when booted

    It is possible I was getting it after it booted, but over IPMI remote console it changed so fast I couldn't to much.  6.9 RC1 is back up and running at least.

    Link to comment
    Share on other sites

    Successfully updated to 6.9rc2 from 6.8.3 without issues. Had to do some small changes in my setup to take full advantage of the multi-pools but everything is working great without any issues. Thanks limetech!

    Link to comment
    Share on other sites

     

    All vm disappear from the vm menu in unraid 6.9 RC2 I can confirm that they are not started as I cannot ping them so it not that they are running and not visible I tried to recreate them from qcow2 and it would not let create new either. A roll back fixes. Could these be due to 

     

     

     

     

    unraid.png

    Link to comment
    Share on other sites

    Upgraded from 6.8.3. HighPoint RocketRAID 2840a controller recognized in System Devices, but none of the attached SATA drives (my entire array) are. Controller and drives all recognized in 6.8.3. Had to downgrade.

    Link to comment
    Share on other sites



    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.