Issues with Knots download, need help

Bitcoin Client Software and Version: Bitcoin Knots version v29.1.knots20250903 Operating System: Parrot OS Linux (Debian) System Specs: 32GB RAM, 1TB Harddrive. Still figuring out how to check this stuff through the terminal, pretty new to Linux. Problem Description: I got the blockchain downloaded to 99.81%, but then it stuck on "4 mins remaining" for over an hour. I left it overnight and even turned off my firewall. I wasn't using a VPN while downloading. On my previous system, I had a similar issue with Knots where it would say it needed to re-download the whole blockchain, and it was a repetitive cycle of download and error. This time it’s different but feels similar since it’s stalled at 98.81%. I tried to force-quit after 12 hours of stalling, reopened, and now it's just stuck. I'm with Comcast and heard some weird stuff was happening with their users and Knots downloads. Not sure about the details, but I think there were some issues from Core's side that got denied. I really want to get Knots working now that I've got a solid setup to run a full node. Image of the issue: https://i.ibb.co/V0fRNS3b/Screenshot-at-2025-10-08-07-14-46.png Log Files: The log file is too big to paste, but I can share it as a downloadable .log file if needed. Just let me know. Sorry if this has been asked before, I'm kinda new to running nodes and trying my best to follow forum rules. Let me know how I can get help here. Thanks!

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).

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.