Hey @Brian_Fay,
Thanks for the follow up and timestamp!
From a fresh diagnostic report, we can see the SSD was plugged in around 07:04 local time and was seen by the system. At 13:44 local, a manual backup to the SSD was triggered. It initialized successfully, created the NEW BACKUPS for ROON folder, and began computing files to back up — then crashed at 13:47:16 with this error:
Warn: [broker/backups] unexpected error doing backup on FileBrowser.Entry:
8TB-Cx10-1, Micron CT8000X10SSD9 : /NEW BACKUPS for ROON/RoonBackups:
Sooloos.SynchronizationContextThreadException: In Broker:Media
---> System.OutOfMemoryException: Exception of type
'System.OutOfMemoryException' was thrown.
at LevelDb.KeySpace.GetEnumerator()
at Sooloos.Broker.TinySooidDb.Vacuum()
at Sooloos.Broker.Database.Validate()
at Sooloos.Broker.BackupCompute.ComputeBackupFiles()
Immediately after this, the logs confirm the worst:
Warn: [broker] validation failed: System.OutOfMemoryException
Error: [broker/database] corruption detected
Warn: [broker] detected corrupt database, notifying client
Warn: [broker] detected corrupt database, halting broker threads
The backup failure triggered a database corruption event and crashed the Roon broker. The memory stats leading up to this show the process was consuming a staggering amount of RAM — climbing from 194MB to 9,524MB physical in under 5 minutes before hitting the wall.
Later on, the service came back up. The SSD was still mounted and visible. The system then ran a restore operation from the old BearStation/music share at 02:53 UTC (22:53 local), which succeeded. This was Roon recovering the database from the prior backup on BearStation.
We then see a handful of successful manual backups. From there, Mar 31, 01:00 (local) — Scheduled auto-backup to SSD → SUCCESS Only 148 incremental files, completed in ~5 minutes. Clean.
Mar 31, 03:00 (local) — Scheduled backup to BearStation → FAILED (NotAvailable) The BearStation music share was still unreachable (consistent with the kernel logs showing constant LOGON_FAILURE).
Mar 31, 04:00 (local) — Backup to BearStation backups_new share → SUCCESS This one did mount and complete — so BearStation itself isn’t dead, but the music share specifically has the credential/access problem.
With that, we also reviewed the Nucleus system log, and saw 99%+ of all log content was a single repeating error:
CIFS: Attempting to mount //BearStation.local/music
CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
I would investigate the BearStation credentials, re-enter the SMB username/password in Roon’s storage settings. The continuous LOGON_FAILURE suggests something changed (password rotation, NAS update, guest access disabled)
In addition to this, the SSD backup appears to now be healthy, no action needed there. The first attempt failed due to OOM; subsequent runs worked fine.
- Monitor memory usage — if the library continues to grow, this OOM condition could recur. Consider whether the Nucleus Titan has enough RAM for the database size.
Although it looks like you have ~25k tracks and ~15GB of RAM, which should be plenty.
We’ll be monitoring for your reply, thank you Brian! 
