OS drive hardware RAID missing?

CombFiltered · Fri Oct 17, 2025 7:22 pm

I updated to 1.7.788.7568, and after a day or two it gave me an error message that the main OS drives in hardware RAID 1 went missing on my bare metal install. It shows as an alert top right on the web interface (Pool state: Missing for sda1), and then in the Storage, Storage pools screen as well. Checking the health on the bare metal showed no issues at all, and the array as healthy. I've been double and triple checking backups, but is there anything I can do here besides restart the VSAN machine and hope for the best? Anything I can check or reset beforehand to hopefully not lose anything? Everything appears to be operating fine besides this error message.

CombFiltered · Sat Oct 18, 2025 1:03 am

Checking for an update now fails, and the updater logs have this:
2025-10-16 21:58:55.328 00005 INFO | [AptOutputValidator]: apt update output:
E: Failed to fetch http://repo.starwind.com/san-and-nas/di ... /InRelease 522 <none> [IP: 104.21.35.130 443]
E: The repository 'http://repo.starwind.com/san-and-nas stable InRelease' is no longer signed.
Error: command apt-get update failed. Return code: 100
2025-10-16 21:58:55.328 00005 INFO | [AptOutputValidator]: Validate [Repo: http://repo.starwind.com/san-and-nas, Template: [EW]:[\s\S]+ {0}]
2025-10-16 21:58:55.328 00005 ERROR | [AptOutputValidator]: apt update is failed for repositories http://repo.starwind.com/san-and-nas

Any chance there's something related here? I see that the version I updated to in order to fix the Proxmox iSCSI booting issues has disappeared from the release notes.

Sat Oct 18, 2025 8:14 am

Hi,

repo is not available, and the build might not be stable (wait for the release).
Sure, you can restart. If the disk is dead, I guess the system will not be responsive. So, feel free to restart.
As a side note, don't run apt-update on StarWind VSAN devices: / might get full and cause unbootable hosts.

CombFiltered · Sun Oct 19, 2025 8:18 pm

I did not intentionally trigger an apt update that I remember, but my drive (185GB) is very nearly full, only 280MB left. Is there a way to clean it up? An apt-get clean did not seem to do anything space-wise.

Mon Oct 20, 2025 3:41 am

I reviewed my notes, and filling /boot is what we need to avoid, as /boot is not that big. You need to see if something is taking it.
Please see what is taking up space. You can try deleting the kernels. Leave only 5.15-113.123, 5.4.0-204.224, and 5.4.0.204.200.

Also, check /mnt. There might be a misplaced image there.