onkelblubb

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

onkelblubb's Achievements

Noob

Noob (1/14)

1

Reputation

1

Community Answers

  1. So i was able to fix it. Disconnect any device (no usb stick oder nvme or sata drive) Deactivate secure boot is now possible (IT WORKS!) Restart USB Boot is now with UEFI possible If you want also to clean secure boot, i was need to update back to newest version of bios and clear tpm and secure boot clear the secure boot is back to setup mode . Thanks Gigabyte for this buggy implementation.
  2. I was nearly an hour to test every option activate an deactivate secure boot, tpm and ttp. Nothing works. I flashed back to F21 Bios (before this "enhanced security boot" releasenote comes) and nothing changed. I testet a fresh new stick with unraid, and also signature issue. If i go to bios deactivate secure boot, it comes directly after save and boot up again. I open an reguest to Gigabyte to clearify why its not possible to deactivate secure boot. (i order in next minutes an asus board, i found a few z690 unraid guys but alway with asus boards). Other ideas?
  3. Ok, maybe i found issue behind CSM issue. I will dry with the dedicated gpu, but UEFI issue will still exist after CSM will work proberly. Found this : "you can't enable legacy compatibility mode (CSM) on this motherboard if you are using the iGPU - I guess something about it prevents you. Essentially you need a GPU card if you want to support legacy compatibility mode."
  4. Hello, after an Hardware change my Unraid will not boot. Old System: x570 Gigabyte Gaming X Mainboard is an Gigabyte z690 Gaming X latest F23b Intel 13600k CPU with onboard GPU Bios Settings UEFI Boot Settings Harddisk Legacy Secure Boot "off" VT-D / Virtual "on" USB Legacy "on" If i activate CMS Bios dry it but comes back with UEFI and and this erros Signature error. If i dry to deactivate secure boot also not work. EFI Ordner on Stick was renamed with to EFI instead of "EFI-". UEFI the Stick is in view an dry to boot but following errors comes up: · Secure Boot Violation · “invalid signature detected. Check Secure Boot Policy in Setup” If on intels IGPU CSM not more working? Very frustrating situation. Any Ideas?
  5. Redis volume path "/data" <-> "/mnt/user/appdata/redis/data" thats works for me: (my Nextcloud config.php) 'memcache.local' => '\\OC\\Memcache\\APCu', 'memcache.distributed' => '\\OC\\Memcache\\Redis', 'memcache.locking' => '\\OC\\\Memcache\\Redis', 'redis' => [ 'host' => 'redis-host.example.com', 'port' => 6379, ], Br
  6. In Safe mode comes no erros, i go back to the stable version. Thanks for try to fix the issue.
  7. Attached the update, notice error come up beforce i start the array. diagnostics-20201011-2036.zip
  8. Attached the diagnostics diagnostics-20201007-1951.zip
  9. Hello, my first post, i had the following issue, this problem exists since the beginning of my setup with my unraid server. Mysystem: x570 Gigabyte Ryzen 3600 64 GB ECC Samsung Memory Nvidia Geforce 1660 Super Broadcom HBA 9400-16i QNAP 1-Port 10G PCIE-Ethernet Card FANTEC SRC-4240X07 Chasi Unraid Version 6.9.0.29 6 x 16 TB Seagate IronWolf Pro 2 x NVME 512GB Transcend Gen3 1 x 240GB SSD 1 x 256GB SSD 1 x 1TB SATA Array Drives 240, 256GB SSD Parity 1TB Sata Cache 2x NVME Drives ZFS Pool: 6x16 RAIDZ1, terra /mnt/terra Migration planed (7x 14 TB Seagate IronWolf Pro) Installed Plugins: - Community Application - Nerd Tools - ZFS Plugins - Unassigned Devices SMB Conf: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [Plex_Media] path = /mnt/terra/PLEX/ browseable = yes guest ok = yes writeable = yes read only = no create mask = 0775 directory mask = 0775 [Nextcloud] path = /mnt/terra/Nextcloud browseable = yes guest ok = yes writeable = yes read only = no create mask = 0775 directory mask = 0775 [VM] path = /mnt/terra/vms browseable = yes guest ok = yes writeable = yes read only = no create mask = 0775 directory mask = 0775 This standing i my logs, this currently comes every second and it flooding my logs: Oct 5 20:55:45 ****** emhttpd: error: share_luks_status, 6411: Operation not supported (95): getxattr: /mnt/user/appdata Oct 5 20:55:45 ****** emhttpd: error: share_luks_status, 6411: Operation not supported (95): getxattr: /mnt/user/domains Oct 5 20:55:45 ****** emhttpd: error: share_luks_status, 6411: Operation not supported (95): getxattr: /mnt/user/isos Oct 5 20:55:45 ****** emhttpd: error: share_luks_status, 6411: Operation not supported (95): getxattr: /mnt/user/system Oct 5 20:55:46 ****** emhttpd: error: share_luks_status, 6411: Operation not supported (95): getxattr: /mnt/user/Share Does anyone have an idea what I can do Thanks for any idea