msryhajw

I am using Homepage docker container and have it all setup but do not want to expose API credentials clear text - I have created an env file to load these at docker runtime using –env-file .env - is it possible to use this in the docker setup in Unraid as although I can set variable I have 30 or so to maintain. I refererence for the setup I am testing. Thanks in Advance for any help

Changed Status to Closed

Tested OK in Safe mode with GUI

Test also in Chrome latest version (same issue)

@limetech Thanks, tried this with the same issue when upgrading again. What I have also noticed is the 4 PCIe NVME running on a HyperX card do not show in 6.10 RC1 - only the one assigned as a cache drive shows. They all appear correctly in 6.9.2 and biurifcation is set in the bios to x4x4x4x4. If BZmodules is corrupt and I install the backup to go back to 6.9.2 I don't understand why it corrupts each time I install 6.10 RC1. At least 2 of us have had the same issue now.

I had the same issue - reported a few threads up ...

I have attached the diagnostics. I still get the timeout errors USB4-6 and 'Cannot find device "Bond0" I don't have any files in the 'previous' directory - it is empty. Is there another way to rollback? Can I overwrtie the new stick with the 6.9.2 image and then copy the config folder over? TIA server-loki-diagnostics-20210811-0739.zip System specs: Supermicro SC846 Chassis Supermicro X10DRI-T 256GB RAM Asus NVME Card (4 x EVO 860 NVME) in PCIe Slot Nvidia Quadro P2000 in PCIe Slot LSI 9300 HBA in PCIe Slot

Just upgraded and server isn't accessible now and will not get a DHCP IP address and comes back with a 169 address instead of the 192.168.1.x. I have no GUI access but can enter the shell via IPMI. I get a lot of errors now stating Cannot find device "bond0" and timeouts from USB Device 4-6 Is there anyway to roll this back to 6.9.2 without losing my setup as nothing has changed with the server other than the upgrade and nothing is working now

Changed Status to Retest

Thanks but the device is still not shown in the device list after running those commands. For now I will drop back to the last stable release until the next beta.

root@SERVER-LOKI:~# fdisk -l /dev/sdd Disk /dev/sdd: 12.75 TiB, 14000519643136 bytes, 27344764928 sectors Disk model: WDC WD140EMFZ-11 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: B3E66232-1151-469F-AA0C-1224F6EEEABA

If anyone encounters this again it turns out that Supermicro are aware of the issue: https://www.supermicro.com/support/faqs/faq.cfm?faq=21114 Question I am having problems booting X8DTN+ motherboard from a USB . I have a PCIe raid card and a PCIe HBA card on the board. If both cards are installed, it will not boot to USB. However if I remove one of the cards (doesn’t matter which) it will boot to USB. I have tried using different slots with the same result. Answer Please disable the OpROM for the card that does not have the OS. Say HBA is used for data drive, then disable the OpROM for that PCI-e slot. Disable under BIOS >> Advance >> PCI/PnP Configuration >> Slot# PCI-E Option ROM >> disable the slot which HBA is installed in.