limetech

Administrators
 View Profile  See their activity

  • Posts

    10185

  • Joined

  • Last visited

  • Days Won

    196

 Content Type 

Report Comments posted by limetech

    Log File: idmap_hash_initialize: The idmap_hash module is deprecated and should not be used.

    in Stable Releases

    Posted

    On 12/8/2021 at 11:28 AM, Holmesware said:

    I don't know why Unraid did this is. Someone please post so we all can know.

    It's historic... waaay back when AD was first integrated there was no such warning.  'hash' was selected because it uses an algorithmic method of mapping SID's to UID/GID's which didn't require maintaining a database file which would have to be kept on the USB flash device.

     

    On 12/8/2021 at 11:28 AM, Holmesware said:

    eg. scans:x:1092:100:ftpuser 1092 is what you need to start above.

    In Unraid OS users created via the Users webGUI menu item are assigned sequential UID's starting at 1000 and all users are put into the 'users' group (GID 100).  The 'nobody' user (UID/GID 99/100) is used for 'guest' access to Public shares.  There should be no UID's above 1000 other than created named users.

     

    On 9/19/2022 at 12:15 PM, Holmesware said:

    This is the definitive answer and solution to this issue.

    Maybe...

     

    On 9/19/2022 at 12:15 PM, Holmesware said:

    This can be done by winbind and the 'rid' idmap backend (there are
    other backends). If you do use the 'rid' idmap backend, it uses this
    formula:

    But your example is using 'tdb' backend which requires maintenance of a tdb database file.

     

    On 9/19/2022 at 12:15 PM, Holmesware said:

    * CAUTION * Making these changes you will have to re-apply all permissions on files/folder that are Domain related
    * CAUTION * All Unraid servers in your Domain will need the same exact settings

    Those statements really should be BOLDED because changing the backend is going to be painful for some users, or an outright security issue.

     

    AD integration is pretty complex.  One thing we can do before coming up with a definitive answer is that we can patch the Samba code to get rid of that syslog entry.  We also want a solution that lets an Unraid server function as an AD Domain Controller (something not possible when we first integrated AD).

    MacOS Optimization

    in Prereleases

    Posted

    On 9/18/2022 at 7:04 AM, wow001 said:

    [global]

       vfs objects = catia fruit streams_xattr

       fruit:nfs_aces = no

       fruit:zero_file_id = yes

       fruit:metadata = stream

       fruit:encoding = native

     

    Please try

    fruit:metadata = netatalk

     

    or comment out that line (default for that value is 'netatalk')

     

    MacOS Optimization

    in Prereleases

    Posted

    On 9/18/2022 at 7:04 AM, wow001 said:

    [global]

       vfs objects = catia fruit streams_xattr

     

    In general you DO NOT want this line in the [global] section  because if you add a plugin which needs to stack a share-level module (such as the Recycle Bin plugin) then the presence of 'vfs objects' at the share level supersedes the setting in the [global] section.  Besides that exact string is already included in every share section.

     

    • Thanks 1

    MacOS Optimization

    in Prereleases

    Posted

    4 hours ago, foux said:

    For me, without any additional settings, TimeMachine is working "as before" : ie first backup works without issues. Then the first few backups works, and suddenly impossible to create additional backups (macOS can't mount the backup image)

    Need diags when this happens.

    Unraid OS version 6.11.0-rc series

    in Prereleases

    Posted

    Version 6.11.0-rc5 2022-09-12

    Bug fixes

    • Ignore "ERROR:" strings mixed in "btrfs filesystem show" command output. This solves problem where libblkid could tag a parity disk as having btrfs file system because the place it looks for the "magic number" happens to matches btrfs. Subsequent "btrfs fi" commands will attempt to read btrfs metadata from this device which fails because there really is not a btrfs filesystem there.

    Base distro:

    • cracklib: version 2.9.8
    • curl: version 7.85.0
    • ethtool: version 5.19
    • fuse3: version 3.12.0
    • gawk: version 5.2.0
    • git: version 2.37.3
    • glibc-zoneinfo: version 2022c
    • grep: version 3.8
    • hdparm: version 9.65
    • krb5: version 1.19.3
    • libXau: version 1.0.10
    • libXfont2: version 2.0.6
    • libXft: version 2.3.6
    • libdrm: version 2.4.113
    • libfontenc: version 1.1.6
    • libglvnd: version 1.5.0
    • libssh: version 0.10.4
    • libtasn1: version 4.19.0
    • mcelog: version 189
    • nghttp2: version 1.49.0
    • pkgtools: version 15.1
    • rsync: version 3.2.6
    • samba: version 4.16.5
    • sqlite: version 3.39.3

    Linux kernel:

    • version 5.19.7
    • CONFIG_BPF_UNPRIV_DEFAULT_OFF: Disable unprivileged BPF by default
    • CONFIG_SFC_SIENA: Solarflare SFC9000 support
    • CONFIG_SFC_SIENA_MCDI_LOGGING: Solarflare SFC9000-family MCDI logging support
    • CONFIG_SFC_SIENA_MCDI_MON: Solarflare SFC9000-family hwmon support
    • CONFIG_SFC_SIENA_SRIOV: Solarflare SFC9000-family SR-IOV support
    • patch: quirk for Team Group MP33 M.2 2280 1TB NVMe (globally duplicate IDs for nsid)
    • turn on all IPv6 kernel options
      • CONFIG_INET6_*
      • CONFIG_IPV6_*

    Management:

    • SMB: remove NTLMv1 support since removed from Linux kernel
    • startup: Prevent installing downgraded versions of packaages which might exist in /boot/extra
    • webgui: VM Manager: Add boot order to GUI and CD hot plug function
    • webgui: Docker Manager: add ability to specify shell with container label.
    • webgui: fix: Discord notification agent url
    • webgui: Suppress info icon in banner message when no info is available
    • webgui: Add Spindown message and use -n for identity if scsi drive.
    • webgui: Fix SAS Selftest
    • webgui: Fix plugin multi updates
    • Like 12

    NVME drive missing after upgrade to 6.11.0-rc2

    in Prereleases

    Posted

    On 9/4/2022 at 9:18 AM, VideoVibrations said:

    Unfortunately, the issue remains on RC4.  Diagnostics are attached.

    dangertoes-diagnostics-20220904-1217.zip

     

    I couldn't find a "quirk" patch for that device, but I found a similar one:

      

    	{ PCI_DEVICE(0x10ec, 0x5762),   /* ADATA SX6000LNP */
		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
				NVME_QUIRK_BOGUS_NID, },

     

    so I added this quirk in next release:

      

    	{ PCI_DEVICE(0x10ec, 0x5763),
		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
				NVME_QUIRK_BOGUS_NID, },

     

    (Your device is 0x10ec:0x5763).  Probably should work, but suggest you test first ;)