Brain OS Known Issues List

Wallin Solutions AB

Document version: 1.1
Effective Date: June 10, 2026
Last Updated: June 11, 2026

Language. This document is published in English and Swedish; the English version prevails in case of discrepancy.

1. Purpose of This List

1.1 This is the dated, versioned Known Issues List referenced in the End User License Agreement (EULA) (Section 5.2) and the Beta Tester Agreement. It records the known defects, limitations, and deviations of the current beta release of Brain OS.

1.2 Brain OS is pre-release, beta software. The Licensor tests each beta release for its intended purpose before release and records the known state of that release here. This list — not a blanket "the software may contain bugs" statement — is the authoritative record of the known issues of the current release.

1.3 The Software may additionally contain defects that are not yet known or not yet listed. The absence of an issue from this list does not warrant that the Software is free of that issue.

1.4 This list is updated with each beta release. The document version and "Last Updated" date above identify the release this list describes.

2. General Beta Limitations

These limitations apply to every current beta release:

  • Pre-release stability. The Software is under active development. Features may be incomplete or unstable, and may be added, changed, or removed in any update without prior notice.
  • Data loss is possible. As beta software, Brain OS may behave unexpectedly and may cause data loss. Do not store data on Brain OS that you cannot afford to lose without an independent backup held elsewhere.
  • Parity is not a backup. Brain OS parity protects against the hardware failure of a disk. It does not protect against accidental deletion, ransomware, file corruption, fire, or theft, and it cannot restore an earlier version of a file. Keep independent backups and follow the 3-2-1 rule: at least 3 copies of your data, on 2 different media types, with 1 copy off-site.

3. Current Known Issues

The specific known issues for the current beta release are listed below. Each entry notes the affected area and, where one exists, a workaround.

3.1 GPU driver installation

On some hardware the automatic GPU-driver installation can fail — for example, when the system cannot reach the driver server during setup, or a vendor driver tool reports an error. When this happens, Brain OS retries the installation on the next boot, and a manual installation option is available under Settings → GPU. GPU acceleration for apps and the built-in transcoder is unavailable until a driver has been installed successfully.

4. Recently Resolved Issues

Issues found and fixed during recent beta development, newest first. Fixes are rolled into the next beta release.

  • ✅ June 11, 2026 — Storage-array disk identity is now bound to each disk's hardware serial number, not its drive letter. Previously, after a disk was removed or swapped, the system could show — and in specific situations act on — the wrong physical disk when the operating system reassigned drive letters.
  • ✅ June 11, 2026 — A disconnected array disk is now clearly shown as "not connected", the array refuses to start until the disk is reconnected (or the operator explicitly chooses degraded operation), and a reconnected disk is recognized again automatically within seconds.
  • ✅ June 11, 2026 — All destructive disk operations (remove, wipe, preclear, disk copy, rebuild) now verify the target disk's identity immediately before acting, and refuse with a clear message on any mismatch.
  • ✅ June 11, 2026 — Fixed a case where the cache disk could be re-initialized against the wrong disk at boot after drive letters changed; cache disks are now identity-verified before any formatting.
  • ✅ June 11, 2026 — Clear, actionable error messages replace raw system errors when enabling or mounting disks.
  • ✅ June 10, 2026 — App cards now display real CPU and memory usage (some apps previously showed 0 B).
  • ✅ June 10, 2026 — Fixed duplicate app cards and a "Partial" status that could stick after a failed app upgrade; app bookkeeping now self-heals.
  • ✅ June 10, 2026 — The Disks page now shows the parity disk's identity (model and name) inline.
  • ✅ June 9, 2026 — Disk replacement and hot-spare rebuild now always target the correct disk; a case that could begin rebuilding the wrong disk in some configurations was fixed.
  • ✅ June 9, 2026 — Hardened the safeguard against formatting the wrong disk when two disks share the same model.
  • ✅ June 9, 2026 — Ongoing security hardening across the firewall, VPN, app sandboxing, and the API surface.
  • ✅ June 8, 2026 — Apps on the pooled storage array now recover access automatically after the storage layer restarts (previously they could lose access until restarted).
  • ✅ June 8, 2026 — Install progress now reports an app as ready only once its container is genuinely healthy, instead of too early.
  • ✅ June 6, 2026 — Fixed an encrypted-array unlock and passphrase-change issue caused by a key-handling bug.
  • ✅ June 1, 2026 — Significantly faster dashboard loading on systems with many running apps and containers.
  • ✅ May 31, 2026 — App install reliability improvements (request timeouts and cleanup of orphaned containers).
  • ✅ May 30, 2026 — Parity engine improvements: mixed-size dual-parity rebuild and kernel-module hardening.
  • ✅ May 23, 2026 — Fixed the GPU setup step in the first-run setup wizard.

5. Reporting an Issue

If you encounter a defect that is not listed here, please report it — with a description of what happened, the steps to reproduce it, and screenshots where possible — to robban@techflip.se. Your reports help us improve Brain OS and keep this list accurate.

Wallin Solutions AB
Website: https://brainos.wallinsolutions.se