AES wrote: ↑20 May 2026, 01:48
Thank you for providing such detailed log information and technical analysis. This is very helpful for our investigation. Based on the information you provided, our initial comments are as follows:
1. Regarding the ACPI-related BIOS errors and the leftover VirtualBox rules
We have noted the ACPI-related BIOS error messages as well as the leftover VirtualBox-related rules mentioned in your logs.
The VirtualBox-related rules should indeed not be present in a production release environment. We will arrange to reproduce and verify this issue in our lab environment and clean it up in a future version.
As for the ACPI-related BIOS error messages, we will also perform further validation on the BIOS side to determine whether there are any compatibility issues.
2. Regarding the md array DeviceDisappeared / DegradedArray logs
Regarding the following events you mentioned:
DeviceDisappeared event detected on md device
DegradedArray event detected on md device
These event logs do not necessarily indicate an actual storage array failure or data corruption, nor do they necessarily have a direct impact on normal array operation.
To better assess the actual impact, we would appreciate it if you could help confirm the following after each reboot:
Whether the storage pool is displayed normally
Whether the volume is mounted correctly
Whether all SSDs are properly detected
Whether the stored data remains accessible
Whether SMB / file services are functioning normally
If all of the above are working as expected, these logs are more likely to be state transition events during the boot process rather than signs of an actual array failure.
3. Regarding the Web UI becoming inaccessible after reboot
You mentioned that the Web management interface becomes inaccessible after reboot, but access can be restored by manually running:
systemctl restart nginx
via SSH.
This behavior may indicate that certain services are not completing initialization properly during the boot process. We will further analyze the service startup sequence and dependency relationships based on the logs you provided to determine whether there is room for boot process optimization.
Thank you again for your detailed feedback. We will forward the relevant information to our product team for further analysis and verification.
If convenient, we would also appreciate it if you could continue monitoring whether the storage pool, volumes, and related services remain consistently normal after subsequent reboots. This will help us more accurately determine the scope of the issue.
