Sparkie

OK, I will wait until a new kernel is out then try again. In the meantime I have contacted ASRock Technical Support and posted the error messages from the System log. I will report back if they answer with anything meaningful. Cheers, Sparkie

Just an update on TPM issues under Windows 11 for ASRock X399 mobo's. I have this same Mobo and processor in my Windows 11 System. Running tpm.msc reports tpm is working fine with no errors. The ASRock forums report no TPM issues under Windows 11. So wondering if this might be a Linux issue for some reason. Windows 11 is happy with the TPM. Linux/Unraid is not. Cheers, Sparkie

No joy on the Bios Upgrade, same TPM error under the syslog. I guess I will close things our from here and contact the Mobo manufacturer to query if they are experiencing any issues with TPM like I am seeing. I am scratching my head over this one, this is a very popular motherboard. I am finding it strange that no one is reporting TPM issues with this Mobo under Windows 11. Maybe I am missing something. Anyway thanks for all the help on the internal boot and the great advice. Cheers, Sparkie

LoLight & JorgeB: Thanks for all your help and feedback. I am finally at point where I have greater confidence in my internal boot setup. My USB Flash showed as failed which just happened before I went down the internal boot path. Put the flash drive into my windows 11 machine and ran CHKDSK which detected errors and repaired. Put back into my server and all is well with that. Regarding fTPM on AMD motherboards - Specifically my ASRock X399 mobo is running a Threadripper 2950X. Sadly my mobo is an ASRock Fatal1ty x399 Gaming. Picked that one because it had 8 SATA ports. But is does not have a SPI Header to add an external TPM module. According to AMD there was an issue with some fTPM implementations as follows but not a complete loss of TPM functionality: AMD has determined that select AMD Ryzen™ system configurations may intermittently perform extended fTPM-related memory transactions in SPI flash memory (“SPIROM”) located on the motherboard, which can lead to temporary pauses in system interactivity or responsiveness until the transaction is concluded. Update and Workaround Update: Affected PCs will require a motherboard system BIOS (sBIOS) update containing enhanced modules for fTPM interaction with SPIROM. AMD expects that flashable customer sBIOS files to be available starting in early May, 2022. Exact BIOS availability timing for a specific motherboard depends on the testing and integration schedule of your manufacturer. Flashable updates for motherboards will be based on AMD AGESA 1207 (or newer). The specific issue here is related to "pauses in system interactivity" not a broken fTPM functionality. So I assume my fTPM is somehow broken. But that being said it is possible but not unlikely that ASRock introduced some 'bug' when they implemented AGESA into their firmware update before 3.8, if that is even a thing, implementing AGESA that is. My mobo is at bios version 3.8. There is a bios update to 4.01 (beta 2023/5/5) which updates AGESA to SummitPI-SP3r2 1.1.0.7. They have a later 4.03 (2024/1/26) which I assume includes 4.01AGESA update. They have a later 4.05 (Beta 2026//3/9) which updates the Secure Book Key (2023/KEK-DB-PK), but I will hold off on that one for now. I will update the BIOS to 4.03 and report back. Again thx for all the help getting to this point. Cheers, Sparkie

oK, as per your instructions I have reconfigured the server to boot of the mirrored ssd's. See below: I chose not to incorporate a data component to the boot pool, just boot only. Not much space to really justify. But I am seeing under pool devices the following; Don't know if Device 'bootdata' was a leftover from the old configuration, no big deal to leave it alone I would assume. Here are the properties: Assume that this might be a leftover from previously but did not want to delete just in case. If this is a leftover then I can delete if you recommend. The Unraid USB Flash Drive is showing under Unassigned Disk Devices. Here is the message list from the Onboarding Wizard: The wizard tried to modify the bios (I assume to the mobo bios) but showing failed, but checking the bios it was successful. Here was what was automatically configured: (Maybe the mobo saw the two new 'hdd' boot devices and automatically added them?) Anyway it's working just fine. Boot Option #1 - 1st SSD Boot Option #2 - 2nd SSD Boot Option #3 - USB Flash Drive The TPM licence move option is not showing under Registration, so TPM is not working. So can't go any further there at this point. Cheers, Sparkie ps. There was no continuation of the Onboarding Wizard after reboot under internal boot. Don't know if that was supposed to happen. I assume not.

Thanks, will do. Sparkie

Hey Loligh: Thanks for the great advice. Luckily I came up with a second SSD which was installed in the case but not plugged into my Mobo on my Windows 11 PC. So given that great news I will proceed as recommended and report back. Yeah, I take your point on the fTPM. I read somewhere that should I upgrade the bios on the server mobo I would most likely have licencing issues. So the SPI header solution is probably the way to go. So I will report back here once I get everything sorted with the SSD internal boot. Cheers, Sparkie

Thanks for your response. Answers below. Originally they were in the array and used for two parity drives. I upgraded those two parity drives to 2 - 8tb replacing the two 4tb drives. So there is no data of any importance on those drives. They were parity drives so I would assume they were filled with parity data. I did not wipe them assuming the onboarding wizard would clear them out. So when the onboarding wizard finished and rebooted the server the two 4tb drives were listed as available and needed a format (specifically the "bootdata" partition, which I proceeded to do. I do have a 512GB SSD as shown on the previous posted image which I could repurpose for internal boot. Would like a 2nd 512GB but they are crazy expensive now. I assume from your comment that I should probably delete the hdd boot pool and go back to the USB Flash Drive? I will not do this yet until I see if I can rustle up another 512GB SSD that I might have stashed somewhere and await further instructions on how to properly do this. The USB Flash Drive is still plugged into the server for Licencing purposes. Cheers, Sparkie

Confirmed that fTPM is enabled on the Mobo Bios. Boot settings confirmed, looks like Hdd boot takes priority over USB boot. Cheers, Sparkie

OK, Thanks for your quick response. Very much appreciated. Looks like I have success on internal boot. Will check the bios of my motherboard to determine boot settings for clarity. So, should anything show up under Main/Boot pool ? I remember watching Ed's video on "The Uncast Show" and he had something listed there but the Heading was slightly different. I wonder if he was running a beta version when he did that video and maybe a slight change in the final release 7.3.0 stable. Mine is empty. See attached image. Now if can get fTPM working. I will double check the setting in the Bios although I am almost 100% certain it is enabled. Here are the diagnostics. Cheers, Sparkie tower-diagnostics-20260516-0957.zip

I just upgraded to Unraid 7.3.0 and setup Internal boot. I set it up as two mirrored volumes with boot + data partitions. Ran into a bunch of problems with failure errors on setting up the internal boot using the onboarding wizard. Did this several times with various degrees of failure but one with a message that errors occurred but probably OK, recommend reboot. Did that and it booted up via flash. I had previously set the boot to the internal boot volume in my bios, but it booted up on the flash drive. Shud down the server and gave up on internal boot and set the bios back to the USB Flash drive instead of the internal boot drive. Rebooted and I was shocked to see the server booting up on the internal hard drives (2 in the pool). Surprised to say the least. Below is what the system shows now. Note that after booting up on internal, brought the array back online and formatted the data volumes as seen below. Server came up and Internal boot was in fact working as shown above. But I don't trust it. Don't see anything under the Boot Pool: See following: As can be seen above the Pool shows 'flash' and HEALTH as "ONLINE" and datasets as 'boot'. So what am I booted up on??? What should I do here? Am I reading this wrong? The Unraid flash device is showing under unassigned devices as shown below: So don't know what to do now. Keep the config as is or revert to the Unraid flash drive. Thoughts? BTW, my motherboard is an ASRock X399 Gaming running a 16 Core Threadripper. It has "AMD fTPM Switch" with comment "Use this to enable or disable AMD CPU fTPM." Enabled this in bios and went to Tools/Registration but no option for "Move License to TPM", just "Manage Licence". Was not going to do this at this time but wanted to see if it was compatible. Does anyone know if Unraid 7.3.0 is compatible with AMD fTPM? Looks like it is not as I think this is attached to the CPU and not the motherboard? Any comments or recommendations would be greatly appreciated. Cheers, Sparkie

@allroy1975 I eventually resolved this but not in a way that will be helpful to you running a 1050 passed thru to a VM in Unraid. I pretty well tried everything with no positive result. Possibly something got corrupted during the power fail I noted previously that started all this. I eventually resolved this by putting together a new computer based upon a B550 MOBO and installed the 1050 along with windows. Multi-monitor support on the 1050 was fully restored and everything is now working OK. Could not devote further time troubleshooting this issue as the VM was used for Digital Audio Workstation functionality connected to a PreSonus StudioLive 32 channel mixer as well as multimedia presentations in a church. Time was not on my side getting the VM fixed. Brute force solution but sometimes that's what it takes LOL.

Was unable to download diagnostics. When I get a chance I will try again next week and attempt to download diagnostics. Regarding browser cache it was the same behaviour on both Linux and Windows and the problem was no longer there when I downgraded back to 6.12.13. But as I noted above I will try to flush cache on both workstations after I upgrade to 6.12.14 again next week. Thanks for your responses. I will report back.

I upgraded from 6.12.13 to 6.12.14. Looks like my unraid server started up fine. Upon launching the WebGui from my Windows, and Linux workstations the WebGui is 'partially broken' at least on my machines. Looking at the Dashboard the PROCESSOR widget shows all the cores, but all the bar graphs are empty. On the MAIN page the Device pages show the parity disks and disks 1-7 but under IDENTIFICATION and the rest of the columns are all empty. Same for Pool Devices. Going to PLUGINS, correctly shows all plugins correctly and all columns are populated correctly BUT clicking on 'Update' the pop-up window is empty and it indicates the update is progressing (three animated dots in the bottom of the window) but no further update. Cannot get to the close button as it does not show. Launching another browser window and going to the plugin page shows the plugin correctly updated. Had to kill the browser window in the first instance. Same behavior on the DOCKER page. Every Docker shows but the update pop-up window is empty. Anyway, successfully performed a downgrade and everything returned to normal in 6.12.13. So for now I will stay away from 6.12.14 as this is my production server. BTW in windows I used Firefox, WebGui broken as noted above. On my Linux workstation, under Chrome exactly the same behavior. This is just for information for what it is worth to document my experience. I will take a pass on 6.12.14 for now.

Reformatted the pool as suggested. All working now.

OK, I will do that and report back. Many thanks, Sparkie

Help is requested. I cannot add or delete docker images. Checking 'Fix Common Problems' it shows I have some errors. 1. Unable to write to cache 2. Unable to write to Docker Image The cache is a pool of two 1Tb nvme drives. Smart status is showing healthy and utilization is 14%. On the surface it seems the cache drives are OK but obviously something is wrong. I have posted diagnostics and included an error file from the cache drive test. Help would be greatly appreciated. Sparkie chapelsvr-diagnostics-20240325-1155.zip cache Errors.zip

I have been getting some machine check events showing up in the Syslog. Below is an extract from that log: Nov 25 17:36:24 Tower kernel: mce: [Hardware Error]: Machine check events logged Nov 25 17:36:24 Tower kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 22: d82000000002080b Nov 25 17:36:24 Tower kernel: mce: [Hardware Error]: TSC 0 MISC d012000200000000 SYND 5a000005 IPID 1002e00000002 Nov 25 17:36:24 Tower kernel: mce: [Hardware Error]: PROCESSOR 2:800f82 TIME 1669410344 SOCKET 0 APIC 0 microcode 800820d Nov 25 17:48:11 Tower root: Fix Common Problems: Error: Machine Check Events detected on your server I have attached diagnostics if this might be needed. Any ideas on what might be causing this? tower-diagnostics-20221125-1825.zip

@ghost82Thanks for the help again. The server at issue is at a remote site and I am managing remotely so the delay in getting back with the current situation. 1. I updated the xml as you suggested ( and spaceinvaderone originally noted ) and can now boot the VM again. Thanks for that. Partial success. 2. I did install windows bare-metal as you suggested with the video card in question and Windows now has multi-monitor (3 monitors) support again. 3. Going back to the VM again and it only has one monitor support, so the bare-metal experiment verifies the Video Card (Gforce 1050 Ti 4MB RAM) is working correctly. 4. In the VM in 3.) above I was working without passing through the vbios. Wanted to keep the variables to the minimum and then add back in if 3-monitor support was working. I will try it again with passed thru bios, Attached below. 5. Regarding diagnostics did not attach as after performing the xml edits you recommended the VM starts OK, but with just one monitor. 6. I was thinking about installing a Linux VM and seeing if that might work with 3-monitor support. I don't know if Linux (say Ubuntu) will auto-detect or revert to a basic resolution if no Nvidia Gforce 1050 drivers are present when Ubuntu starts. Windows will automatically detect the video card being added and load the appropriate drivers. I have checked Nvidia's website and they do have drivers available for Linux. I would setup Linux via the VNC access through the VM, then once setup and working OK then add the 1050 with sound, edit xml and restart and see what happens. Will report when complete. Thanks again... Asus.EditChapel.GTX1050Ti.4096.171212.rom

@ghost82OK, I have done some testing. Tried all combinations as you noted. Same result. I swapped out video card, this time a Asus Phoenix GTX1050Ti with 4Gb RAM instead of the Gigabyte GTX1050 with 2GB RAM. Again same result only one monitor out of three can be enabled at a time. I disconnected the projector, same result only one monitor out of 2 can be enabled at a time. Double checked the template for the VM, everything looks OK (did not check the XML). So I started to suspect maybe the Win10 Image was damaged somehow. So... I created a new Windows 11 VM and fired that up. Set it all up with the Virtual display. Win 11 working fine with all virtio drivers installed. Installed the Teamviewer client for remote access. Went in and selected the Asus Video Card and associated sound card. Updated the template and started the VM. Checking "display settings" I see three monitors (previously reconnected all three) via TeamViewer, working remotely. Accessing via Teamviewer I could login OK. So video via the Asus card was working fine (although only seeing one screen). But I could not verify if all three monitors were in actual fact were displaying. Shutdown the VM after Win11 wanted to do some updates and have not been able to restart the VM ever since. The VM just hangs. Blew away that VM and recreated a new W11 VM again. Virtual display works just fine but selecting the video card and associated sound and the VM just hangs. Have not been able to get video working with the video card ever since, rebooted the server several times, same result, even powered down the server just in case the video needed full power off, no joy. Now I don't know if changes have been made to the XML for VMs with Graphics Card passthrough for Unraid 6.11.1 or 6.10.x (I was running 6.9.x previously). This is the only video card in the Unraid server. In 6.9.x you had to hand-edit the XML to add the multifunction parameter to the video (43.00.00) and edit the slot & function for the sound (43.00.01). Do you know if the necessity to edit the XML has been removed in 6.10.x or 6.11.1 for a passed thru video card with sound? Here is a snippet form the current XML for video and associated sound. Note there is no multi-function parameter included which I had to add previously as per SpaceInvaderOne's video instructions for a Windows 10 VM. I note that his recent video for Windows 11 makes no mention of hand-editing the XML, he just selects the Video Card and assoicated sound, clicks update and starts the VM no problem. Hence my qestion, is this not a problem now? Or is there some work-around 'under the hood' we are not seeing. Here is the XML snippet for Video and associated sound: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/> MY EDIT: VIDEO LINE NO MULTIFUNCTION PARAMETER </source> <alias name='hostdev0'/> <rom file='/mnt/user/domains/Windows 10/Asus.EditChapel.GTX1050Ti.4096.171212.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x1'/> MY EDIT: THIS IS THE SOUND </source> Is the above correct for only one video card in the system and being passed-thru to the VM? Sorry for being long-winded, but any suggestions would be greatly appreciated. At this point just trying to get the VM up and running again on the video card which would be fantastic and then I can go to the site to verify everything. Cheers

Thanks for your response, I will try your recommendations and report back on the results. Thanks again

Looks like I have lost multiple monitor functionality on my Windows 10 VM. I was running version 6.9 of Unraid and all was working perfectly. Two 1080p monitors and a Epson Projector. While I was away it looks like a power failure occurred that lasted over 20 minutes upon which time my UPS shutdown. Upon restart Unraid started up OK but my Win10 VM was no longer functional. Anyway upon logging in to the GUI Unraid flagged that I was running an unsupported version of Unraid and recommended upgrade to latest version which I did. Reboot and everything looked OK. VM still would not start. Then realizing my VirtIO was probably out of date I upgraded to virtio-win-0.1.225-1.iso. I tried restarting the VM, no joy. I edited the VM and updated the Machine Bios: to OVMF TPM (could not get OVMF to work). The Machine parameter is set to: i440fx-7.1 (this is the latest, previously it was 6.1 but not absolutely certain). The video card is passed thru to the VM along with it's sound. Tried rebooting and it worked. Windows 10 started OK, but only had one monitor. I installed the latest Nvidia drivers for the 1050 graphics card and still no joy, only one monitor of the three works. Opened the Nvidia control panel and clicked on multiple monitors and it shows the 3 connected monitors with an option to select the other two monitors besides the working one. Now the problem: When clicking on one of the other monitors I get the following messages: "This GPU supports 1 display". This is not true because I ran it with three monitors previously (the card has a DVI port, an HDMI port and a Display Port). If I click on another monitor and click Apply that monitor works but the other two do not, even though the Nvidia drivers sees all three. BTW I updated all the drivers on the new virtio iso, EXCEPT the Balloon drivers. Could not find how to do that one. I did see somewhere on the forums that you will see under Device Manager and entry for Other devices, but I do not see that. How to update the Balloon drivers? Also I have passed thru the graphics card to the VM with an edited ROM bios with the Header section removed. So I know that is good, it worked before no problems. So to summarize: 1. How to reinstate multiple monitor support? 2. How to update the Balloon drivers from the VirtIO ISO (it is mounted as drive E: in Windows 10.) Any help on this issue would be greatly appreciated. Thanks

OK Thanks, I will proceed with the upgrade using the Parity Swap Procedure. Thanks for all the help. Cheers, Sparkie

Thanks again for the excellent help. Ran the extended SMART test. Diagnostics attached. Unraid reported: Errors occurred - Check SMART report Looks like the drive is needing replacement. On another but related subject: I now have the failed disk and it is being properly emulated. I have two parity disks both 6TB Seagate Ironwolf 7200RPM. My replacement disk for the failed disk is an 8TB WD Red Plus 7200RPM. This will be a problem as the replacement data disk cannot be bigger than the parity drives. SpaceInvader One talked about my situation almost exactly but his scenario had only one parity drive. His procedure involved a parity copy procedure by removing the parity drive replacing it with a larger drive and assigning it to parity then copying the removed parity disk to the new larger parity disk. In my case I have two 6TB parity drives and replacing one of them with the 8TB then copying the removed parity drive to that one. I assume in that case the max size of parity at the end of the parity copy is still 6TB until I get around to replacing the last remaining 6TB parity with an 8TB? With a failed disk in the array will that impact the data rebuild after the parity drive is replaced assuming I can do this. Cheers, Sparkie tower-smart-20220528-1635.zip

Status update: Stopped array, shuddown (power-cycle). Restarted, started array. Disk13 still RED-X but checking data shows everything is still properly emulated. Here are the Diagnostics after restart. Thanks, Sparkie tower-diagnostics-20220528-1553.zip