STARTOS node unresponsive, after reboot bitcoin won't sync (error 135) and TOR freezes at 95%

[timroller88]

OS logs below, you can see when I click START on bitcoin and the problem starts looping over and over!

025-12-03T23:28:17+00:00 2025-12-03T23:28:17.468099Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:28:32+00:00 2025-12-03T23:28:32.519610Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:28:47+00:00 2025-12-03T23:28:47.571852Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:29:02+00:00 2025-12-03T23:29:02.618189Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:29:17+00:00 2025-12-03T23:29:17.663405Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:29:32+00:00 2025-12-03T23:29:32.708517Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:29:47+00:00 2025-12-03T23:29:47.766428Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:30:02+00:00 2025-12-03T23:30:02.849316Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:30:17+00:00 2025-12-03T23:30:17.896275Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:30:32+00:00 2025-12-03T23:30:32.945641Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:30:48+00:00 2025-12-03T23:30:48.032639Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:31:03+00:00 2025-12-03T23:31:03.083164Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:31:18+00:00 2025-12-03T23:31:18.162856Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:31:33+00:00 2025-12-03T23:31:33.219756Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:31:48+00:00 2025-12-03T23:31:48.264552Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:32:03+00:00 2025-12-03T23:32:03.308467Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:32:18+00:00 2025-12-03T23:32:18.362396Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:32:28+00:00 2025-12-03T23:32:28.772943Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135
2025-12-03T23:32:33+00:00 2025-12-03T23:32:33.431497Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:32:46+00:00 2025-12-03T23:32:46.640493Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135
2025-12-03T23:32:48+00:00 2025-12-03T23:32:48.474905Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:33:03+00:00 2025-12-03T23:33:03.556039Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:33:04+00:00 2025-12-03T23:33:04.381577Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135
2025-12-03T23:33:06+00:00 2025-12-03T23:33:06.504806Z ERROR startos::net::tor: Tor Daemon Error: Our circuit 0 (id: 2315) died due to an invalid selected path, purpose Hidden service: Uploading HS descriptor. This may be a torrc configuration issue, or a bug.: Restarting tor
2025-12-03T23:33:06+00:00 2025-12-03T23:33:06.504869Z DEBUG startos::net::tor: Error { source:
2025-12-03T23:33:06+00:00 0: Our circuit 0 (id: 2315) died due to an invalid selected path, purpose Hidden service: Uploading HS descriptor. This may be a torrc configuration issue, or a bug.
2025-12-03T23:33:06+00:00 Location:
2025-12-03T23:33:06+00:00 startos/src/net/tor.rs:604
2025-12-03T23:33:06+00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2025-12-03T23:33:06+00:00 0: startos::net::tor::torctl
2025-12-03T23:33:06+00:00 at startos/src/net/tor.rs:250
2025-12-03T23:33:06+00:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2025-12-03T23:33:06+00:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Tor, revision: None }
2025-12-03T23:33:08+00:00 2025-12-03T23:33:08.605267Z INFO torctl: startos::net::tor: Tor is started
2025-12-03T23:33:18+00:00 2025-12-03T23:33:18.598315Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:33:22+00:00 2025-12-03T23:33:22.310234Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135
2025-12-03T23:33:33+00:00 2025-12-03T23:33:33.655771Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:33:40+00:00 2025-12-03T23:33:40.186620Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135
2025-12-03T23:33:40+00:00 2025-12-03T23:33:40.978288Z ERROR startos::net::tor: Tor Daemon Error: Tor stuck bootstrapping at 95%: Restarting tor
2025-12-03T23:33:40+00:00 2025-12-03T23:33:40.978358Z DEBUG startos::net::tor: Error { source:
2025-12-03T23:33:40+00:00 0: Tor stuck bootstrapping at 95%
2025-12-03T23:33:40+00:00 Location:
2025-12-03T23:33:40+00:00 startos/src/net/tor.rs:354
2025-12-03T23:33:40+00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2025-12-03T23:33:40+00:00 0: startos::net::tor::torctl
2025-12-03T23:33:40+00:00 at startos/src/net/tor.rs:250
2025-12-03T23:33:40+00:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2025-12-03T23:33:40+00:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Tor, revision: None }
2025-12-03T23:33:43+00:00 2025-12-03T23:33:43.079891Z INFO torctl: startos::net::tor: Tor is started
2025-12-03T23:33:48+00:00 2025-12-03T23:33:48.732171Z DEBUG run_main:check: startos::manager::health: Checking health of nostr
2025-12-03T23:33:58+00:00 2025-12-03T23:33:58.244747Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135

2025-12-03T23:34:03+00:00 2025-12-03T23:34:03.813169Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

2025-12-03T23:34:15+00:00 2025-12-03T23:34:15.153755Z ERROR startos::net::tor: Tor Daemon Error: Tor stuck bootstrapping at 95%: Restarting tor
2025-12-03T23:34:15+00:00 2025-12-03T23:34:15.153793Z DEBUG startos::net::tor: Error { source:
2025-12-03T23:34:15+00:00 0: Tor stuck bootstrapping at 95%
2025-12-03T23:34:15+00:00 Location:
2025-12-03T23:34:15+00:00 startos/src/net/tor.rs:354
2025-12-03T23:34:15+00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2025-12-03T23:34:15+00:00 0: startos::net::tor::torctl
2025-12-03T23:34:15+00:00 at startos/src/net/tor.rs:250
2025-12-03T23:34:15+00:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2025-12-03T23:34:15+00:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Tor, revision: None }

2025-12-03T23:34:15+00:00 2025-12-03T23:34:15.871297Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135

2025-12-03T23:34:17+00:00 2025-12-03T23:34:17.264962Z INFO torctl: startos::net::tor: Tor is started

2025-12-03T23:34:18+00:00 2025-12-03T23:34:18.890875Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

2025-12-03T23:34:33+00:00 2025-12-03T23:34:33.486938Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135
2025-12-03T23:34:33+00:00 2025-12-03T23:34:33.970340Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

2025-12-03T23:34:48+00:00 2025-12-03T23:34:48.326436Z ERROR startos::net::tor: Tor Daemon Error: Tor stuck bootstrapping at 95%: Restarting tor
2025-12-03T23:34:48+00:00 2025-12-03T23:34:48.326480Z DEBUG startos::net::tor: Error { source:
2025-12-03T23:34:48+00:00 0: Tor stuck bootstrapping at 95%
2025-12-03T23:34:48+00:00 Location:
2025-12-03T23:34:48+00:00 startos/src/net/tor.rs:354
2025-12-03T23:34:48+00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2025-12-03T23:34:48+00:00 0: startos::net::tor::torctl
2025-12-03T23:34:48+00:00 at startos/src/net/tor.rs:250
2025-12-03T23:34:48+00:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2025-12-03T23:34:48+00:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Tor, revision: None }

2025-12-03T23:34:49+00:00 2025-12-03T23:34:49.051723Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

2025-12-03T23:34:50+00:00 2025-12-03T23:34:50.387424Z INFO torctl: startos::net::tor: Tor is started

2025-12-03T23:34:51+00:00 2025-12-03T23:34:51.153862Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135

2025-12-03T23:35:04+00:00 2025-12-03T23:35:04.184651Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

2025-12-03T23:35:08+00:00 2025-12-03T23:35:08.893799Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135

2025-12-03T23:35:19+00:00 2025-12-03T23:35:19.248091Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

2025-12-03T23:35:22+00:00 2025-12-03T23:35:22.458043Z ERROR startos::net::tor: Tor Daemon Error: Tor stuck bootstrapping at 95%: Restarting tor
2025-12-03T23:35:22+00:00 2025-12-03T23:35:22.458107Z DEBUG startos::net::tor: Error { source:
2025-12-03T23:35:22+00:00 0: Tor stuck bootstrapping at 95%
2025-12-03T23:35:22+00:00 Location:
2025-12-03T23:35:22+00:00 startos/src/net/tor.rs:354
2025-12-03T23:35:22+00:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2025-12-03T23:35:22+00:00 0: startos::net::tor::torctl
2025-12-03T23:35:22+00:00 at startos/src/net/tor.rs:250
2025-12-03T23:35:22+00:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2025-12-03T23:35:22+00:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Tor, revision: None }

2025-12-03T23:35:24+00:00 2025-12-03T23:35:24.563354Z INFO torctl: startos::net::tor: Tor is started

2025-12-03T23:35:26+00:00 2025-12-03T23:35:26.576866Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135

2025-12-03T23:35:34+00:00 2025-12-03T23:35:34.323855Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

2025-12-03T23:35:44+00:00 2025-12-03T23:35:44.251872Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 135

2025-12-03T23:35:49+00:00 2025-12-03T23:35:49.371507Z DEBUG run_main:check: startos::manager::health: Checking health of nostr

[Alvaro]

If your server’s tor connection is not bootstrapping all the way to 100% and remaining stable, you can reset the connection by going to:

System->Manage->Experimental Features->Reset Tor

Try to do this without selecting “Wipe State” first.

You can then check in the Tor logs if the connection is bootstrapping all the way up to 100% and remaining stable. If not, then try again and select “Wipe State”.

[StuPleb]

I notice a 135 exit code on Bitcoin, it’s probably Bitcoin crashing Tor, rather than Tor crashing Bitcoin.

Bitcoin logs (Services → Bitcoin → Logs) would be useful, but I suspect you’d find also a hardware related error in the Kernel logs (System → Kernel Logs).

[timroller88]

Thanks - should have said that I tried this already though, both types and still throws the same error when starting BTC core

[timroller88]

thanks, I think that’s right since the recurring issue with disconnect and reconnecting to TOR only happens when I START the bitcoin core app

Kernel logs loop:

Reconnected at 2025-12-04T22:27:59+00:00
2025-12-04T22:27:58+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:27:58+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:27:58+00:00 ata1.00: configured for UDMA/133
2025-12-04T22:27:58+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:27:58+00:00 sd 0:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2025-12-04T22:27:58+00:00 sd 0:0:0:0: [sda] tag#24 Sense Key : Medium Error [current]
2025-12-04T22:27:58+00:00 sd 0:0:0:0: [sda] tag#24 Add. Sense: Unrecovered read error - auto reallocate failed
2025-12-04T22:27:58+00:00 sd 0:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 06 f2 c2 62 00 00 08 00
2025-12-04T22:27:58+00:00 I/O error, dev sda, sector 116572776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-12-04T22:27:58+00:00 BTRFS error (device dm-3): bdev /dev/mapper/EMBASSY_ZA2MNATZGZH3XOKTYR2VU35VRJZFWUPXOJRV3FY7SVARUQLCRRTQ_package-data errs: wr 0, rd 73475, flush 0, corrupt 0, gen 0
2025-12-04T22:27:58+00:00 ata1: EH complete
2025-12-04T22:27:59+00:00 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
2025-12-04T22:27:59+00:00 ata1.00: irq_stat 0x40000001
2025-12-04T22:27:59+00:00 ata1.00: failed command: READ DMA
2025-12-04T22:27:59+00:00 ata1.00: cmd c8/00:08:62:c2:f2/00:00:00:00:00/e6 tag 23 dma 4096 in
res 51/40:00:68:c2:f2/00:00:00:00:00/e6 Emask 0x9 (media error)
2025-12-04T22:27:59+00:00 ata1.00: status: { DRDY ERR }
2025-12-04T22:27:59+00:00 ata1.00: error: { UNC }
2025-12-04T22:27:59+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:27:59+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:27:59+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:27:59+00:00 ata1.00: configured for UDMA/133
2025-12-04T22:27:59+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#23 Sense Key : Medium Error [current]
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#23 Add. Sense: Unrecovered read error - auto reallocate failed
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 06 f2 c2 62 00 00 08 00
2025-12-04T22:27:59+00:00 I/O error, dev sda, sector 116572776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-12-04T22:27:59+00:00 BTRFS error (device dm-3): bdev /dev/mapper/EMBASSY_ZA2MNATZGZH3XOKTYR2VU35VRJZFWUPXOJRV3FY7SVARUQLCRRTQ_package-data errs: wr 0, rd 73476, flush 0, corrupt 0, gen 0
2025-12-04T22:27:59+00:00 ata1: EH complete
2025-12-04T22:27:59+00:00 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
2025-12-04T22:27:59+00:00 ata1.00: irq_stat 0x40000001
2025-12-04T22:27:59+00:00 ata1.00: failed command: READ DMA
2025-12-04T22:27:59+00:00 ata1.00: cmd c8/00:08:62:c2:f2/00:00:00:00:00/e6 tag 22 dma 4096 in
res 51/40:00:68:c2:f2/00:00:00:00:00/e6 Emask 0x9 (media error)
2025-12-04T22:27:59+00:00 ata1.00: status: { DRDY ERR }
2025-12-04T22:27:59+00:00 ata1.00: error: { UNC }
2025-12-04T22:27:59+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:27:59+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:27:59+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:27:59+00:00 ata1.00: configured for UDMA/133
2025-12-04T22:27:59+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#22 Sense Key : Medium Error [current]
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#22 Add. Sense: Unrecovered read error - auto reallocate failed
2025-12-04T22:27:59+00:00 sd 0:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 06 f2 c2 62 00 00 08 00
2025-12-04T22:27:59+00:00 I/O error, dev sda, sector 116572776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-12-04T22:27:59+00:00 BTRFS error (device dm-3): bdev /dev/mapper/EMBASSY_ZA2MNATZGZH3XOKTYR2VU35VRJZFWUPXOJRV3FY7SVARUQLCRRTQ_package-data errs: wr 0, rd 73477, flush 0, corrupt 0, gen 0
2025-12-04T22:27:59+00:00 ata1: EH complete
2025-12-04T22:27:59+00:00 br-start9: port 2(veth1) entered disabled state
2025-12-04T22:27:59+00:00 device veth1 left promiscuous mode
2025-12-04T22:27:59+00:00 br-start9: port 2(veth1) entered disabled state
2025-12-04T22:28:15+00:00 br-start9: port 2(veth1) entered blocking state
2025-12-04T22:28:15+00:00 br-start9: port 2(veth1) entered disabled state
2025-12-04T22:28:15+00:00 device veth1 entered promiscuous mode
2025-12-04T22:28:15+00:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2025-12-04T22:28:15+00:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2025-12-04T22:28:15+00:00 br-start9: port 2(veth1) entered blocking state
2025-12-04T22:28:15+00:00 br-start9: port 2(veth1) entered forwarding state
2025-12-04T22:28:16+00:00 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40000 action 0x0
2025-12-04T22:28:16+00:00 ata1.00: irq_stat 0x40000001
2025-12-04T22:28:16+00:00 ata1: SError: { CommWake }
2025-12-04T22:28:16+00:00 ata1.00: failed command: READ DMA
2025-12-04T22:28:16+00:00 ata1.00: cmd c8/00:08:62:c2:f2/00:00:00:00:00/e6 tag 19 dma 4096 in
res 51/40:00:68:c2:f2/00:00:00:00:00/e6 Emask 0x9 (media error)
2025-12-04T22:28:16+00:00 ata1.00: status: { DRDY ERR }
2025-12-04T22:28:16+00:00 ata1.00: error: { UNC }
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: configured for UDMA/133
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#19 Sense Key : Medium Error [current]
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#19 Add. Sense: Unrecovered read error - auto reallocate failed
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#19 CDB: Read(10) 28 00 06 f2 c2 62 00 00 08 00
2025-12-04T22:28:16+00:00 I/O error, dev sda, sector 116572776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-12-04T22:28:16+00:00 BTRFS error (device dm-3): bdev /dev/mapper/EMBASSY_ZA2MNATZGZH3XOKTYR2VU35VRJZFWUPXOJRV3FY7SVARUQLCRRTQ_package-data errs: wr 0, rd 73478, flush 0, corrupt 0, gen 0
2025-12-04T22:28:16+00:00 ata1: EH complete
2025-12-04T22:28:16+00:00 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
2025-12-04T22:28:16+00:00 ata1.00: irq_stat 0x40000001
2025-12-04T22:28:16+00:00 ata1.00: failed command: READ DMA
2025-12-04T22:28:16+00:00 ata1.00: cmd c8/00:08:62:c2:f2/00:00:00:00:00/e6 tag 30 dma 4096 in
res 51/40:00:68:c2:f2/00:00:00:00:00/e6 Emask 0x9 (media error)
2025-12-04T22:28:16+00:00 ata1.00: status: { DRDY ERR }
2025-12-04T22:28:16+00:00 ata1.00: error: { UNC }
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: configured for UDMA/133
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#30 Sense Key : Medium Error [current]
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#30 Add. Sense: Unrecovered read error - auto reallocate failed
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#30 CDB: Read(10) 28 00 06 f2 c2 62 00 00 08 00
2025-12-04T22:28:16+00:00 I/O error, dev sda, sector 116572776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-12-04T22:28:16+00:00 BTRFS error (device dm-3): bdev /dev/mapper/EMBASSY_ZA2MNATZGZH3XOKTYR2VU35VRJZFWUPXOJRV3FY7SVARUQLCRRTQ_package-data errs: wr 0, rd 73479, flush 0, corrupt 0, gen 0
2025-12-04T22:28:16+00:00 ata1: EH complete
2025-12-04T22:28:16+00:00 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
2025-12-04T22:28:16+00:00 ata1.00: irq_stat 0x40000001
2025-12-04T22:28:16+00:00 ata1.00: failed command: READ DMA
2025-12-04T22:28:16+00:00 ata1.00: cmd c8/00:08:62:c2:f2/00:00:00:00:00/e6 tag 8 dma 4096 in
res 51/40:00:68:c2:f2/00:00:00:00:00/e6 Emask 0x9 (media error)
2025-12-04T22:28:16+00:00 ata1.00: status: { DRDY ERR }
2025-12-04T22:28:16+00:00 ata1.00: error: { UNC }
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: configured for UDMA/133
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#8 Sense Key : Medium Error [current]
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#8 Add. Sense: Unrecovered read error - auto reallocate failed
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 06 f2 c2 62 00 00 08 00
2025-12-04T22:28:16+00:00 I/O error, dev sda, sector 116572776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-12-04T22:28:16+00:00 BTRFS error (device dm-3): bdev /dev/mapper/EMBASSY_ZA2MNATZGZH3XOKTYR2VU35VRJZFWUPXOJRV3FY7SVARUQLCRRTQ_package-data errs: wr 0, rd 73480, flush 0, corrupt 0, gen 0
2025-12-04T22:28:16+00:00 ata1: EH complete
2025-12-04T22:28:16+00:00 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
2025-12-04T22:28:16+00:00 ata1.00: irq_stat 0x40000001
2025-12-04T22:28:16+00:00 ata1.00: failed command: READ DMA
2025-12-04T22:28:16+00:00 ata1.00: cmd c8/00:08:62:c2:f2/00:00:00:00:00/e6 tag 27 dma 4096 in
res 51/40:00:68:c2:f2/00:00:00:00:00/e6 Emask 0x9 (media error)
2025-12-04T22:28:16+00:00 ata1.00: status: { DRDY ERR }
2025-12-04T22:28:16+00:00 ata1.00: error: { UNC }
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: supports DRM functions and may not be fully accessible
2025-12-04T22:28:16+00:00 ata1.00: configured for UDMA/133
2025-12-04T22:28:16+00:00 ahci 0000:00:17.0: port does not support device sleep
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#27 Sense Key : Medium Error [current]
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#27 Add. Sense: Unrecovered read error - auto reallocate failed
2025-12-04T22:28:16+00:00 sd 0:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 06 f2 c2 62 00 00 08 00
2025-12-04T22:28:16+00:00 I/O error, dev sda, sector 116572776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-12-04T22:28:16+00:00 BTRFS error (device dm-3): bdev /dev/mapper/EMBASSY_ZA2MNATZGZH3XOKTYR2VU35VRJZFWUPXOJRV3FY7SVARUQLCRRTQ_package-data errs: wr 0, rd 73481, flush 0, corrupt 0, gen 0
2025-12-04T22:28:16+00:00 ata1: EH complete
2025-12-04T22:28:17+00:00 br-start9: port 2(veth1) entered disabled state
2025-12-04T22:28:17+00:00 device veth1 left promiscuous mode
2025-12-04T22:28:17+00:00 br-start9: port 2(veth1) entered disabled state
Disconnected at 2025-12-04T22:28:18+00:00

[StuPleb]

I expected as much… there are repeated drive errors related to the physical health of the drive itself. It probably needs to be replaced.