Looking at the log, I was looking for disk 1. Maybe 2 SSDs were recorded in uber.ini when diag, and Raid was grouped in the back. WDT thought that a disk was lost. At this time, after raid is removed, WDT can continue to run
Look at the log to find disk 1. Maybe two SSDs are recorded in uber.ini when diag is in progress, and raid is set in the back. WDT thinks that it has lost a disk. When raid is removed, WDT can continue to run<br>