Poi_Holic

Thanks to everyone who shared their settings. I'd like to report a successful iGPU detection result with BIOS 2.2. My setup: Motherboard: Enginetech-branded Supermicro X11SCA-F, revision 1.01A CPU: Intel Xeon E-2146G / UHD Graphics P630 BIOS: 2.2, dated September 8, 2023 BMC: 01.74.15, dated June 24, 2024 OS: Unraid, booted in UEFI mode Previously, attempts to enable the iGPU left the system stuck at the startup screen, requiring a CMOS reset to regain BIOS access. Unfortunately, I didn't record the exact combinations used in those earlier attempts. The following combination now boots successfully: Primary Display: PCI Primary PCIE: OnBoard Internal Graphics: Enabled Option ROM execution → Video: UEFI Onboard Video Option ROM: EFI Before this change, Primary Display and Internal Graphics were both Auto, and both video Option ROM settings were Legacy—even though Unraid itself was already booting in UEFI mode. After saving and rebooting, Unraid detects: Intel UHD P630 [8086:3e96], bound to i915 ASPEED AST2500 [1a03:2000], bound to ast /dev/dri/card0, card1, and renderD128 No BIOS/BMC update or JPME2 jumper modification was needed for this result. SR-IOV and Above 4G Decoding remain disabled. So far, this confirms successful boot and detection of both graphics devices with their drivers loaded. Actual hardware transcoding and continued BMC KVM operation still need verification. Since several settings changed together, I can't isolate which one resolved the startup issue. Hopefully this helps another X11SCA-F owner running BIOS 2.2!

但是官方文件是这样说的： 关于parity " In Unraid parity is always maintained in real-time and a bit more detail on the access pattern to the drives is described under Manual/Storage Management with their performance implications." 关于Parity check “If you have at least one parity device assigned, clicking Check will initiate a Parity-check. This will march through all data disks in parallel, computing parity and checking it against stored parity on the parity disk(s). You can continue to use the array while a parity check is running but the performance of any file operations will be degraded due to drive contention between between the check and the file operation. The parity check will also be slowed while any such file operations are active. By default, if an error is found during a Parity-check the parity disk will be updated (written) with the computed data and the Sync Errors counter will be incremented. If you wish to run purely a check without writing correction, uncheck the checkbox that says Write corrections to parity before starting the check. In this mode, parity errors will be notated but not actually fixed during the check operation. A correcting parity check is started automatically when starting the array after an "Unsafe Shutdown". An "Unsafe Shutdown" is defined as any time that the Unraid server was restarted without having previously successfully stopped the array. The most common cause of Sync Errors is an unexpected power-loss, which prevents buffered write data from being written to disk. It is highly recommended that users consider purchasing a UPS (uninterruptable power supply) for their systems so that Unraid can be set to shut down tidily on power loss, especially if frequent offsite backups aren't being performed. It is also recommended that you run an automatic parity check periodically and this can be done under Settings->Scheduler. The frequency is up to the user but monthly or quarterly are typical choices. It is also recommended that such a check is set as non-correcting as if a disk is having problems there is a chance of you corrupting your parity if you set such a check to be correcting. The only acceptable result from such a check is to have 0 errors reported. If you do have errors reported then you should take pre-emptive action to try and find out what is causing them. If in doubt ask questions in the forum.”