Software wont launch #29033

1. 
   Wolfstorm321 commented at 4:09 pm on December 8, 2023: none

   Is there an existing issue for this?

   • I have searched the existing issues

   Current behaviour

   Version 0.23.0.0 I ran a full node between 2015 and 2020, pruned since 2020. I decided to run a full node recently, as I want to import keys to a new wallet. However, the program wont open while running a full node.

   Started synching yesterday at morning, it synched up to 2018. Closed the program, turned off the computer, went to sleep. Waked up today, turned on the computer, opened the program. Four hours have passed, software is stuck on “verifying blocks, press Q to close” initial screen. I killed the process as it was only at 20% of “verifying”, so I noticed it won’t open for the entire day.

   While pruned, it takes longer to synch, but program opens in a matter of seconds. Why this is happening? I remember it took 30 minutes to open a full node in 2020, and that’s why I switched to pruned. But four hours? How do I avoid the initial “verification”?

   Expected behaviour

   Open the program.

   Steps to reproduce

   Download the blockchain up to 2018, turn if off. Turn it on again.

   Relevant log output

   No response

   How did you obtain Bitcoin Core

   Pre-built binaries

   What version of Bitcoin Core are you using?

   0.23.0

   Operating system and version

   Windows 7

   Machine specifications

   I’m using a EVO 870 SSD, and my processor is a i5 8400, with 32gb of RAM.

2. 
   maflcko commented at 8:56 am on December 9, 2023: member

   Four hours have passed, software is stuck on “verifying blocks, press Q to close” initial screen.

   The software is verifying the blocks that were downloaded previously. This may take a long time, depending on your system. You can look at the tail of the debug log to see the current exact status.

   I killed the process as it was only at 20% of “verifying”, so I noticed it won’t open for the entire day.

   Killing means it’ll likely have discarded the progress. This shouldn’t cause any issues, but it is recommended to shutdown cleanly, so that the program has a chance to save the progress.

3. 
   maflcko commented at 8:56 am on December 9, 2023: member

   You can find the debug.log in your data dir.

   Please be aware that the debug log might contain personally identifying information.

4. maflcko added the label Questions and Help on Dec 9, 2023
5. maflcko added the label Windows on Dec 9, 2023
6. maflcko added the label Resource usage on Dec 9, 2023
7. 
   maflcko commented at 1:49 pm on December 12, 2023: member

   Closing for now, due to lack of more details. Once you find the debug log with more details, feel free to reply below.
8. maflcko closed this on Dec 12, 2023

   ---

9. 
   nikolhaas65 commented at 3:20 pm on March 27, 2024: none

   Encountered similar problem with ubuntu/mantic. bitcoin-qt did not pass initial stage “loading block index” and was killed by OOM (recorded in log). My problem seem to be close to this old issue. #17733#issue-536950393

   • My .bitcoin/blocks directory is stored on external drive, which had some mounting issues due to improper unplugging of drive.
   • Usually, I fix these problems on Windows laptop by “scanning and fixing errors”. It did not work for bitcoin-qt.
   • This time, I additionally switched off “indexing of all files” (set by Windows) for this drive (is in properties). After plugging drive to linux machine bitcoin-qt started to progress further.

   Note aside. Perhaps, there is an issue with drive USB-cable, which I did not replace yet.

Contributors
Wolfstorm321 maflcko nikolhaas65

Labels
Windows Resource usage Questions and Help