# Umbrel Home Bitcoin Node stuck syncing, now stuck on starting **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [August 5, 2024, 12:53am UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676 "2024-08-05T00:53:07Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![jgmontoya](https://avatars.discourse-cdn.com/v4/letter/j/46a35a/32.png) [@jgmontoya](https://community.umbrel.com/u/jgmontoya)\ **Post date:** [August 5, 2024, 12:53am UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/1 "2024-08-05T00:53:07Z")
After I failed to migrate ([How to migrate from a Raspberry Pi Umbrel to Umbrel Home - #38 by jgmontoya](https://community.umbrel.com/t/how-to-migrate-from-a-raspberry-pi-umbrel-to-umbrel-home/12930/38)) I decided to just set up my home as a brand new node. During IBD I noticed it would start syncing normally, then stop and start dropping peers. It would then stay stuck at whatever percent it managed to sync (low single-digit %). I followed this: [Factory Reset (Umbrel Home) - #2 by denny](https://community.umbrel.com/t/factory-reset-umbrel-home/15697/2) to reset my umbrel home. This took me back to version 0.5.x, I updated to 1.2.2 and then tried to install the bitcoin core app again. Now the app is stuck on starting: ![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/2X/6/6185974b58d153a9ff14b15de001da1768b872a6.jpeg) I’ve tried restarting and I’ve also tried removing the app and installing it again. Bitcoin app logs: [umbrel\_bitcoin\_2024-08-04\_20-50.log](https://community.umbrel.com/uploads/short-url/lVHTqh42uj4DRqAVRg1crC62PsB.log) (100.7 KB) ---
**Author:** ![MR.S](https://avatars.discourse-cdn.com/v4/letter/m/cdc98d/32.png) [@MR.S](https://community.umbrel.com/u/MR.S)\ **Post date:** [August 5, 2024, 8:32pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/2 "2024-08-05T20:32:49Z")
Can you post Logs, check to see if it needs reindexing. ---
**Author:** ![jgmontoya](https://avatars.discourse-cdn.com/v4/letter/j/46a35a/32.png) [@jgmontoya](https://community.umbrel.com/u/jgmontoya)\ **Post date:** [August 5, 2024, 11:45pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/3 "2024-08-05T23:45:49Z")
Logs for the bitcoin app are already on the original post. I tried uploading the umbrel logs but had some issues because of the size so here it is (had to add the .txt extension so it would let me upload, but otherwise its directly what I download compressed from my umbrel, just remove the .txt and you’ll be able to uncompress): [umbrel-1722901380592.log.gz.txt](https://community.umbrel.com/uploads/short-url/c7u2BvCeLUXckEENLTrNU5GBrBd.txt) (2.4 MB) ---
**Author:** ![MR.S](https://avatars.discourse-cdn.com/v4/letter/m/cdc98d/32.png) [@MR.S](https://community.umbrel.com/u/MR.S)\ **Post date:** [August 6, 2024, 3:54pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/4 "2024-08-06T15:54:39Z")
I didn’t see what I found in mind. Maybe soeone else can share some insight. Sorry. ---
**Author:** ![babik](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@babik](https://community.umbrel.com/u/babik)\ **Post date:** [August 6, 2024, 10:47pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/5 "2024-08-06T22:47:32Z")
“ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at FlatFilePos” Corrupted block data. You should delete it and start IBD from scratch. Although if you already have synced blockchain data on another (umbrel) device, why not copy it from there? And while at it, you can also copy lightning / lnd dir (or perhaps channel.db alone, which might be more foolproof way, but with few extra steps). Without very basic linux skill you could struggle tho. ---
**Author:** ![jgmontoya](https://avatars.discourse-cdn.com/v4/letter/j/46a35a/32.png) [@jgmontoya](https://community.umbrel.com/u/jgmontoya)\ **Post date:** [August 7, 2024, 1:40pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/6 "2024-08-07T13:40:58Z")
Yes I’ve tried doing it from scratch several times. For some reason it keeps getting corrupted after some time. I don’t really care about copying the LN data over, I’m fine starting from scratch in that regard (and I’ve already closed all of my old channels so it doesn’t matter anyway). I hope this is not some hardware issue, my umbrel home is basically new 😬 ---
**Author:** ![babik](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@babik](https://community.umbrel.com/u/babik)\ **Post date:** [August 8, 2024, 5:47pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/7 "2024-08-08T17:47:48Z")
Hmm, can’t think of other explanation then failing disk then… If u r statistically unlucky enough, I guess it can happen with new disks too… Btw iiuc umbrel home switched from time-tested 2 disks (OS + data) arrangement to 1disk (with extra partitions)… Issues like yours are imo examples of why it was not good design decision. It makes things more complicated, adding unnecessary risks… Umbrel things… 🙄 You can try to run fsck, but not sure if you can even do that properly on the main disk without having the linux booted from different disk (ie usb stick)… Maybe you can, but I’m not planning to buy umbrel home just to try… ---
**Author:** ![octolance](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/octolance/32/7829_2.png) [@octolance](https://community.umbrel.com/u/octolance)\ **Post date:** [August 12, 2024, 5:08pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/8 "2024-08-12T17:08:12Z")
Hey @jgmontoya Just had a look at your logs, and there are tell-tale signs, as @babik suggested, that something might be up with the filesystem or disk that’s causing the Bitcoin Node to not work properly. With that in mind, could you try the following steps and let me know what the results are? 1. Let’s try and rule out a hardware issue by checking the SMART status of the drive. In your umbrelOS terminal can first install the utilities by running: 2. Following that, we can check for any individual sectors / cells on the drive that may have gone “bad” and don’t work anymore. (This can happen, even on new drives and usually its a very small amount, but if the system doesn’t detect and isolate them, it can cause I/O errors to manifest). 3. If the above steps didn’t solve the issue and SMART is saying everything is OK, then it could also just be a corrupted filesystem, you can check it with `fsck` in read-only mode by running: If after all these steps, you’re still experiencing these issues, update us here and let myself or @lukechilds know and we’ll get it sorted for you asap. 🫂 ---
**Author:** ![jgmontoya](https://avatars.discourse-cdn.com/v4/letter/j/46a35a/32.png) [@jgmontoya](https://community.umbrel.com/u/jgmontoya)\ **Post date:** [August 28, 2024, 11:25pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/9 "2024-08-28T23:25:01Z")
Hey! First of all thanks a lot for your response and the detailed instructions, and I’m sorry for the delay in responding, I was unable to do it sooner. 1. From `sudo lsblk` I can see that the disk name is `nvme0n1`. `sudo smartctl -t short /dev/nvme0n1` returned: ```auto smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-23-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org NVMe device successfully opened Use 'smartctl -a' (or '-x') to print SMART (and more) information ``` Then `sudo smartctl -a /dev/nvme0n1`: ```auto smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-23-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: PCIe SSD Serial Number: DE510741042500003431 Firmware Version: EHFM70.2 PCI Vendor/Subsystem ID: 0x1987 IEEE OUI Identifier: 0x6479a7 Controller ID: 0 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 2,048,408,248,320 [2.04 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 6479a7 892a2037fc Local Time is: Wed Aug 28 22:46:55 2024 UTC Firmware Updates (0x12): 1 Slot, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x00df): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 64 Pages Warning Comp. Temp. Threshold: 83 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x08): No_ID_Reuse Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 5.00W - - 0 0 0 0 0 0 1 + 3.00W - - 1 1 1 1 0 0 2 + 1.90W - - 2 2 2 2 0 0 3 - 0.0500W - - 3 3 3 3 5000 2500 4 - 0.0050W - - 4 4 4 4 8000 45000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 1 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 49 Celsius Available Spare: 100% Available Spare Threshold: 5% Percentage Used: 0% Data Units Read: 741,135 [379 GB] Data Units Written: 7,555,896 [3.86 TB] Host Read Commands: 33,528,304 Host Write Commands: 53,151,464 Controller Busy Time: 184 Power Cycles: 18 Power On Hours: 469 Unsafe Shutdowns: 8 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 12 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 49 Celsius Thermal Temp. 1 Transition Count: 942 Thermal Temp. 2 Transition Count: 736 Thermal Temp. 1 Total Time: 12326 Thermal Temp. 2 Total Time: 1138 Error Information (NVMe Log 0x01, 16 of 255 entries) No Errors Logged ``` Given it apparently didn’t found any issues, I did `sudo smartctl -t long /dev/nvme0n1`: ```auto smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-23-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org NVMe device successfully opened Use 'smartctl -a' (or '-x') to print SMART (and more) information ``` Then `sudo smartctl -a /dev/nvme0n1` again: ```auto smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-23-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: PCIe SSD Serial Number: DE510741042500003431 Firmware Version: EHFM70.2 PCI Vendor/Subsystem ID: 0x1987 IEEE OUI Identifier: 0x6479a7 Controller ID: 0 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 2,048,408,248,320 [2.04 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 6479a7 892a2037fc Local Time is: Wed Aug 28 22:52:27 2024 UTC Firmware Updates (0x12): 1 Slot, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x00df): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 64 Pages Warning Comp. Temp. Threshold: 83 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x08): No_ID_Reuse Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 5.00W - - 0 0 0 0 0 0 1 + 3.00W - - 1 1 1 1 0 0 2 + 1.90W - - 2 2 2 2 0 0 3 - 0.0500W - - 3 3 3 3 5000 2500 4 - 0.0050W - - 4 4 4 4 8000 45000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 1 1 - 4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 49 Celsius Available Spare: 100% Available Spare Threshold: 5% Percentage Used: 0% Data Units Read: 741,135 [379 GB] Data Units Written: 7,556,087 [3.86 TB] Host Read Commands: 33,528,308 Host Write Commands: 53,159,202 Controller Busy Time: 184 Power Cycles: 18 Power On Hours: 470 Unsafe Shutdowns: 8 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 12 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 49 Celsius Thermal Temp. 1 Transition Count: 942 Thermal Temp. 2 Transition Count: 736 Thermal Temp. 1 Total Time: 12326 Thermal Temp. 2 Total Time: 1138 Error Information (NVMe Log 0x01, 16 of 255 entries) No Errors Logged ``` 1. `sudo badblocks -b 4096 -c 1024 -s /dev/nvme0n1`: ```auto Checking for bad blocks (read-only test): done ``` 1. I tried the following: `sudo fsck -d -n /dev/nvme0n1p1`: ```auto fsck from util-linux 2.38.1 ``` `sudo fsck -d -n /dev/nvme0n1p2`: ```auto fsck from util-linux 2.38.1 e2fsck 1.47.0 (5-Feb-2023) Warning! /dev/nvme0n1p2 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/nvme0n1p2: clean, 94147/643376 files, 1030997/2576384 blocks ``` `sudo fsck -d -n /dev/nvme0n1p3`: ```auto fsck from util-linux 2.38.1 e2fsck 1.47.0 (5-Feb-2023) /dev/nvme0n1p3: clean, 94026/642112 files, 1029376/2576384 blocks ``` `sudo fsck -d -n /dev/nvme0n1p4`: ```auto fsck from util-linux 2.38.1 e2fsck 1.47.0 (5-Feb-2023) Warning! /dev/nvme0n1p4 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/nvme0n1p4: clean, 199029/494895104 files, 71850818/1979574596 blocks ``` I’m not really sure how to interpret these results, should I try to do the live Linux USB + `fsck -f`? ---
**Author:** ![octolance](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/octolance/32/7829_2.png) [@octolance](https://community.umbrel.com/u/octolance)\ **Post date:** [September 4, 2024, 1:24pm UTC](https://community.umbrel.com/t/umbrel-home-bitcoin-node-stuck-syncing-now-stuck-on-starting/18676/10 "2024-09-04T13:24:44Z")
Hey @jgmontoya Apologies for the delay in getting back to you. Thanks for providing all of this. You did a great job! It looks like everything’s okay with your drive actually. There shouldn’t be any need to run any further filesystem checks. Could you open a support ticket via our live chat or send us a message on [support@umbrel.com](mailto:support@umbrel.com), quoting this problem (you can include the link to this page if you’d like) and also provide the serial number of your Umbrel Home?