Author

Topic: Bitcoin Core Reindexing After Windows 10 Crash (Read 1956 times)

legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
August 02, 2015, 02:09:47 PM
#8
Unfortunately, it really is dependent upon the hardware running it as well.  Reindexing requires everything to be verified to ensure it wasn't corrupted, and fixed if it was.  With ~50G of data to parse, it's going to take a while, regardless of which OS you're using.  Of course, using an OS that can manage these tasks better would help (hint, it isn't anything MS is producing), but even so, you're hamstringing yourself if you're running some old dual core box with minimal RAM (not sure that you are, this was just an example).

spot on. I use 8 gb ram 250 gb ssd and an intel i5 2500t  still takes 13 or 14 hours.





if I do it on my i7 4790 cpu, 16gb ram, samsung 1tb ssd ,it still takes 7 hours.--- no one want to use this quality machine for an offline wallet




I have a 50 down 15 up internet connections hard wired.
newbie
Activity: 15
Merit: 0
Unfortunately, it really is dependent upon the hardware running it as well.  Reindexing requires everything to be verified to ensure it wasn't corrupted, and fixed if it was.  With ~50G of data to parse, it's going to take a while, regardless of which OS you're using.  Of course, using an OS that can manage these tasks better would help (hint, it isn't anything MS is producing), but even so, you're hamstringing yourself if you're running some old dual core box with minimal RAM (not sure that you are, this was just an example).

You're pretty much correct on the equipment. The computer is an inexpensive Toshiba Satellite C855D, dual core with 8GB of RAM. Like I said before this is only an inconvenience, not a problem, as I am running a Bitcoin Core Node 24/7 and at present it has about 37 connections.

I think the best thing I should do with this LT is to bring up Bitcoin Core, let it update and then shut it down while I do other things, until such time I am more confident of not running into another crash with this new upgrade to Win 10. I appreciate all the help I've been getting. Computing has come a long way since my first Altair and then with my Zorba CPM machine.

Again, thanks to all the folks on this forum for their timely comments and support for this bitcoin newbie. An oldie but goodie.[/size]
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Unfortunately, it really is dependent upon the hardware running it as well.  Reindexing requires everything to be verified to ensure it wasn't corrupted, and fixed if it was.  With ~50G of data to parse, it's going to take a while, regardless of which OS you're using.  Of course, using an OS that can manage these tasks better would help (hint, it isn't anything MS is producing), but even so, you're hamstringing yourself if you're running some old dual core box with minimal RAM (not sure that you are, this was just an example).
newbie
Activity: 15
Merit: 0
I'd been beta testing Win 10 since October 2014 and had a Blue Screen wipeout on one laptop that was unrecoverable and I had to reinstall Windows 7 on that machine. Three days ago I upgraded to Windows 10 and what happens, but I get another Blue Screen crash. It's a good thing I've canceled all other Reservations for Win 10.

Now, it concerns me about letting Bitcoin Core run the entire time I am on the laptop. I would not want Win 10 to crash again while Bitcoin Core is running. The crash was Saturday evening and here it is Sunday afternoon and Bitcoin is still reindexing at 1 year and 7 weeks left. This is not a satisfactory condition and it looks like this is a definite weak link in running the Bitcoin Core program. Something really needs to be done about this kind of situation, but I'm just not sure what could be done. It looks like I may have to look for a different Bitcoin Wallet that doesn't require me to wait several days to see the return of my bitcoin.

Thanks for the comments and recommendations.
staff
Activity: 3458
Merit: 6793
Just writing some code
Two days ago I upgraded Windows 8.1 to Windows 10. This evening Windows 10 Blue Screen Crashed. Bitcoin Core came up okay when the computer came back, but it started Reindexing 6+ years of blocks. Is this normal and is there anyway to prevent this in the future? Is there something I should do differently? I am running a Bitcoin Core Node on another machine so I'm not in danger of losing anything but am concerned.
This is normal behavior. Whenever the computer crashes, you will most likely have to reindex the database since it isn't closed properly. To prevent this, try to make sure that your computer doesn't crash. You won't be losing any Bitcoin from this.
staff
Activity: 3500
Merit: 6152
Two days ago I upgraded Windows 8.1 to Windows 10. This evening Windows 10 Blue Screen Crashed. Bitcoin Core came up okay when the computer came back, but it started Reindexing 6+ years of blocks. Is this normal and is there anyway to prevent this in the future? Is there something I should do differently? I am running a Bitcoin Core Node on another machine so I'm not in danger of losing anything but am concerned.

There is nothing to worry about ,  I get Database corrupted message all the time with Bitcoin Core which pisses me off and made me change to Electrum (or making me ... since I'am upgrading to Windows 10 right now ) Since the blockchain is downloaded already , you just need to wait reindexing and you should be fine and good to go and you won't lose anything .
legendary
Activity: 4536
Merit: 3188
Vile Vixen and Miss Bitcointalk 2021-2023
It is normal if the block index got corrupted. This can be prevented by the operating system using a journaling file system, which it seems Microsoft still hasn't gotten right. There's really nothing you can do about it other than to use a less unreliable operating system.
newbie
Activity: 15
Merit: 0
Two days ago I upgraded Windows 8.1 to Windows 10. This evening Windows 10 Blue Screen Crashed. Bitcoin Core came up okay when the computer came back, but it started Reindexing 6+ years of blocks. Is this normal and is there anyway to prevent this in the future? Is there something I should do differently? I am running a Bitcoin Core Node on another machine so I'm not in danger of losing anything but am concerned.
Jump to: