Fresh Build, Bitcoind exit code 1 , tor bootstrapping stuck at 95%

My server hardware:
CPU :intel core i3 7020U 64bit 2.3ghz 3mb cache
Ram 16gb
Drive: 2TB M.2

My mini server was running fine, then one day it wasn’t. The blockchain was corrupted, i tried to repair it but it was not working so I did a fresh install. Made it to 65% synced with no OS errors just bitcoin core crashing with an error code 1.

Fresh install again, error code 1 and a whole bunch of other problems after that.
My server is in the DMZ of my router.

Also why does start9 set my time zone to freaken england gmt 0. no matter what i do, it even changes my bios time.

2024-09-18T08:15:22-07:00 2024-09-18T15:15:22.109576Z DEBUG run_main :check : startos::manager::health: Checking health of bitcoind
2024-09-18T08:15:26-07:00 2024-09-18T15:15:26.205149Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 1
2024-09-18T08:15:46-07:00 2024-09-18T15:15:46.874103Z DEBUG run_main :check : startos::manager::health: Checking health of bitcoind
2024-09-18T08:15:50-07:00 2024-09-18T15:15:50.552340Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 1
2024-09-18T08:16:11-07:00 2024-09-18T15:16:11.166445Z DEBUG run_main :check : startos::manager::health: Checking health of bitcoind
2024-09-18T08:16:15-07:00 2024-09-18T15:16:15.668567Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 1
2024-09-18T08:16:26-07:00 2024-09-18T15:16:26.160468Z ERROR startos::net::tor: Tor Daemon Error: Our circuit 0 (id: 10264) 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
2024-09-18T08:16:26-07:00 2024-09-18T15:16:26.160543Z DEBUG startos::net::tor: Error { source:
2024-09-18T08:16:26-07:00 0: Our circuit 0 (id: 10264) died due to an invalid selected path, purpose Hidden service: Uploading HS descriptor. This may be a torrc configuration issue, or a bug.
2024-09-18T08:16:26-07:00 Location:
2024-09-18T08:16:26-07:00 startos/src/net/tor.rs:604
2024-09-18T08:16:26-07:00 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-09-18T08:16:26-07:00 0: startos::net::tor::torctl
2024-09-18T08:16:26-07:00 at startos/src/net/tor.rs:250
2024-09-18T08:16:26-07:00 Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
2024-09-18T08:16:26-07:00 Run with RUST_BACKTRACE=full to include source snippets., kind: Tor, revision: None }
2024-09-18T08:16:28-07:00 2024-09-18T15:16:28.305095Z INFO torctl : startos::net::tor: Tor is started
2024-09-18T08:16:36-07:00 2024-09-18T15:16:36.382933Z DEBUG run_main :check : startos::manager::health: Checking health of bitcoind
2024-09-18T08:16:40-07:00 2024-09-18T15:16:40.361297Z ERROR startos::manager::manager_container: The service bitcoind has crashed with the following exit code: 1
2024-09-18T08:17:00-07:00 2024-09-18T15:17:00.458260Z ERROR startos::net::tor: Tor Daemon Error: Tor stuck bootstrapping at 95%: Restarting tor

You should try to see why the corruption is occurring, this can sometimes be caused by unstable power causing server shutdowns while writing to disk.

Health of your drive or slightly loose connectors might also be a possible suspect.

You can attempt the following action (Which should help):
In the StartOS Bitcoin Core UI go to → Menu → Actions → Reindex Chainstate

In response to your question about the time zone, this is perfectly normal. All StartOS servers are running on the same time and you should not be concerned at all about that.