raspiblitz: rsync: write failed on "/mnt/hdd/bitcoin/blocks/blk01103.dat": Read-only file system
Hi, I’m syncing bitcoin blockchain on a rpi 4, I’m using raspiblitz 1.4, I downloaded and validated the blockchain on my laptop and I choose the option to copy from laptop to raspiblitz, this works fine, after I run rsync the shell is copying for hours and it works until the last file, but after it finish I received this error
chainstate/144462.ldb
703.48K 100% 4.97MB/s 0:00:00 (xfr#6056, to-chk=10/6069)
chainstate/144463.ldb
2.17M 100% 5.42MB/s 0:00:00 (xfr#6057, to-chk=9/6069)
chainstate/144464.ldb
1.81M 100% 2.92MB/s 0:00:00 (xfr#6058, to-chk=8/6069)
chainstate/144465.log
4.97M 100% 4.24MB/s 0:00:01 (xfr#6059, to-chk=7/6069)
chainstate/144466.ldb
16.42M 100% 7.30MB/s 0:00:02 (xfr#6060, to-chk=6/6069)
chainstate/144467.log
130 100% 0.86kB/s 0:00:00 (xfr#6061, to-chk=5/6069)
chainstate/144468.ldb
0 100% 0.00kB/s 0:00:00 (xfr#6062, to-chk=4/6069)
chainstate/144469.ldb
5.16M 100% 6.96MB/s 0:00:00 (xfr#6063, to-chk=3/6069)
chainstate/CURRENT
16 100% 0.02kB/s 0:00:00 (xfr#6064, to-chk=2/6069)
chainstate/LOCK
0 100% 0.00kB/s 0:00:00 (xfr#6065, to-chk=1/6069)
chainstate/MANIFEST-142284
rsync: write failed on "/mnt/hdd/bitcoin/blocks/blk01103.dat": Read-only file system (30)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]
If I just wanted to run again rsync I get this message
grunch@wepa:/media/grunch/bitcoin/blockchain $ sudo rsync -avhW --progress ./chainstate ./blocks bitcoin@192.168.0.87:/mnt/hdd/bitcoin
ssh: connect to host 192.168.0.87 port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]
I checked the rsync output and all files were copied but I can’t ssh back, then I reboot the rpi and now I can ssh in but it shows me a message telling me that the blockchain data is corrupted and ask me to delete and try again.
I deleted it and tried again and I had the same issue.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 22 (1 by maintainers)
Commits related to this issue
- #1095 adding recommendation to use exact hardware models — committed to raspiblitz/raspiblitz by deleted user 4 years ago
Update.
I bought a new SSD enclosure that was recommended on the hardware list (UGREEN) and did a fresh install. Worked great and was able to sync the blockchain in a little over 2 days. The first external SSD case I had was the issue and was not compatible. Lesson that many newbies learn - get known compatible hardware. The SSD itself does not seem to be an issue and seems to be compatible.
Compatible SSD enclosure = UGREEN 50743, USB 3.1 SATA 2.5 inch SSD enclosure https://www.amazon.com/gp/product/B07D2BHVBD/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
NOT compatible SSD enclosure = ORICO transparent USB 3.0 SATA 2.5 inch SSD enclosure https://www.newegg.com/orico-2139u3-bk-enclosure/p/0VN-0003-000Z5?Item=9SIA1DS4VX9128
Also note that I was having a variety of issues during the install and I think they were all related to my SSD cutting out due to the SSD enclosure compatibility. I kept trying to research and fix what I thought were multiple issues that I came across but I think the root cause was that SSD enclosure. I haven’t had a single issue since I swapped it out.
Can confirm, I also had an SSD case that was not compatible (it was with my HDD but after 1 week still not synced I switched to SSD). First I thought the SSD was the problem but after reading here and getting the UGREEN USB 3.0 case it works flawlessly. Immediatly noticed the difference in speed as well.
@sedknieper what a different an SSD case makes. Got my SSH back and now downloading the blockchain again. Thanks for the help!!
I added a notice to the README to remind people to best use the exact hardware models from the shopping list to prevent such problems.
great, I’ll buy it and let you know if it works in this issue before close it