About an 1 hour ago I see that there was a system restart and as Knots tries to come up I get this error in the Knots log:
[error] basic block filter index: best block of the index not found. Please rebuild the index.
2025-06-25T10:28:22+02:00 Error: basic block filter index: best block of the index not found. Please rebuild the index.
2025-06-25T10:28:22+02:00 2025-06-25T08:28:22Z Shutdown: In progress…
I posted this over on Start9’s forum too. Look here for a Start9 and Knots re-indexing the block chain conversation.
Is everyone’s Knots running currently?
There was a “fix” mentioned by one user. Re-index. Would that mean uninstall…reinstall Knots in order to re-sync?
Reindexing is done via Knots > Actions > Reindex Blockchain. I usually see this error when there is a power outage or the server isn’t shut down properly through the System > Shutdown interface.
Yep…must been what happened. It was fast though as it came right back without me noticing. Um. I hope the re-index don’t take days like it says it will…
There is a lot to this and I feel for less experienced people coming into the space and running into problems like this. Mass adoption wont happen very easily if it’s a constant battle with hardware issues.
Here’s an aside. The server was running fine until I fired Public Pool back up and pointed a few miners at it. The server took less than 4 hours to start recycling power. I sat and watched the node and sure enough it would power itself off after about 5 minutes. During this time I was trying to re-index Knots. It would stop constantly…I’d go look at the server and sure enough it had powered down again. This happened at least 20 times in and hour.
So now…thinking back a week ago when the server was acting just like this. Now…come to think of it I had moved 5 miners to Public Pool then as well. This was the exactly same problem that started this whole thing a week ago but I didn’t really make the connection until I thought through the whole process.
My Server One was running at 54C, 25% of 32G of ram being used and 45% storage was used. The specs of the server are a 2TB NVEm and 32G Ram. With that said I don’t think I was taxing the server that hard but maybe I was? I doubt it but it’s a thought.
Installed apps:
Alby
Elecrtrs
Mempool
Core Lightning
LND
Ride the Lightning
Knots
Datum Gateway
Public Pool
So then I wonder if it’s a power supply issue. Power supply failing. Could be? More on that to come as I am in contact with Stuart at Start9 about this.
So…Here is an interesting solution to this topic. I found this at Start9’s forum. The OP’s problem is exactly the same as mine…server just powers down at will.
This is likely a known issue with the BIOS in this model. You can adjust the BIOS to fix. If you can connect a keyboard and monitor to your server and start it up in Kiosk mode. Hit Delete to enter BIOS at startup. Advanced → AMD CBS → CPU Common Options > Core Performance Boost > Disabled. F4 to exit.
I had to re-flash the OS again. The unit just would not stay running yesterday at all as I said and the OS seem to disappear. I went into the BIOS and set the “fix” mentioned over at start9 and as a result the server has been running re-indexing Knots for about 12 hours now. 45% indexed as of this typing. No hiccups. So maybe the BIOS issue was/is culprit?
Any who…I ordered up a Pure Server (4TB, 64G Ram) and should be here Monday. I will have 2 nodes running as I cant afford a single point of failure. I see I just got an email from Stuart this morning so I’ll gleam more later…
If I understand the conclusion, then, performance boost on the Server One can cause the system to restart itself whenever it is under load. I have seen this type of behavior with undervolt faults – a power supply that can’t deliver enough amps is the most common cause (voltage drops below thresholds when it can’t deliver enough power). It also fits with having performance boost enabled and putting the device under load, which is the scenario where it would need to draw the most power.
@Fletcher I’m fixing to find out…my Server One has run flawless since day one. It wasn’t until only recently that I have the problem. I think I can pin point whats making the server work to hard and draw more power. Mining to my own instance of Public Pool on my node and Datum Gateway. A lot of hash going to the internal server.
Anyways…I’ll be finding out when the Pure gets here. First thing I’m going to do is use the Pure power supply on the Server One and load all services and see if the server will shut itself off or recycle. If it does then it’s a server issue…if it doesn’t then it’s the power supply.
Stuart at Start9 talked to me today and said if the power supply on the Server One is bad he’ll get a new one to me. If the server is failing he’ll fix it for me. So win win there. Nice guy.
I did apply the fix to the BIOS though and the server has stayed up 24 hours with out a glitch. Before it would only run for 5 minutes and all I was doing was re-indexing Knots. No other services running.
So I’m looking forward to answers and I have taken steps to have 2 servers, one as a backup, as it imperative for me.
