Knots stalling, updated

[Xrcbgn]

Bitcoin Client Software and Version Number: Bitcoin Knots version v29.1.knots20250903

Operating System: Parrot OS - Linux (Debian)

System Hardware Specs: 32GB RAM , 1TB Harddrive I'm not sure how to find these efficiently with terminal, still a novice linux user.
Description of Problem: I've downloaded the blockchain to 99.81%, it stalled and said "4 mins remaining" for an hour, I left it overnight, turned off the firewall. I was not connected to VPN at the time of download.
On my last machine, my knots software had a similar error where once downloaded, it would say that it needs to re-download the entire blockchain and it would loop like that, I'd download, and error, re-download.
This issue on this machine seems to be different but similar, it's stalled on 98.81%, I force-quit it after 12 hours stalled, re-opened and now it's stuck here. I am a comcast user, and I heard that something fishy was going on with comcast users downloading knots, I do not know the entire story to that, but I heard there was tampering from Core's end they denied.
I really want to use Knots now that I have a machine that can hold the entire blockchain as a full node.  
Screenshot of the problem: https://i.ibb.co/V0fRNS3b/Screenshot-at-2025-10-08-07-14-46.png
Log Files from the Bitcoin Client: It's very large, I cannot paste it, I could link it if needed as a downloadable .log file.
Just let me know.

I apologize if this is a common occurrence in the forum, I'm a semi-new node-runner, and I'm doing my best here to not violate the forums R&G.
Please let me know how I can help you help me.
Thank you.

Xrcbgn

EDIT: I have located the .bitcoin file, which might have been an issue as I had booted up Core and started syncing, but ultimately stopped it, and downloaded knots instead because I wanted to give knots a run to see how it is. I have deleted the old .bitcoin file and an now on track to re-sync with the network. If I have further issues, I may return but I think the main issue was that I had let Core try to begin syncing and then started syncing knots after removing core (but not it's .bitcoin files).
I do apologize for wasting anyone's time that read this.

[retaur]

Are your blocks and chainstate folders still the same?

I remember having a similar issue because a sector went bad that my last blk file was stored on and I had the delete that file and run disk diagnostics so that sector wasn't written to again. If this happens again at the same point, it might be worth trying that too (mine was using core though).

[nc50lc]

I have deleted the old .bitcoin file and an now on track to re-sync with the network.

Where did you originally posted this topic? Because I didn't see it here in the last few weeks.
Anyways, you could've saved a lot of bandwidth (and time) since you don't have to create a new ".bitcoin" data directory to switch between Core and Knots.

Stalled block header sync could just be issue with zero peers which happened to me a couple of times when switching clients using the same datadir.
Refreshing your peers.dat might have fixed it.
If it's caused by other issues, checking the "debug.log" file will surely tell the main issue so we can give the right solution.

Anyways, it's already deleted. I'm just pointing the fact so others who are in the same situation will not do it.