some notes
This commit is contained in:
parent
f1b30050eb
commit
46b18feee8
2 changed files with 57 additions and 0 deletions
32
how_to_add_data_disk.md
Normal file
32
how_to_add_data_disk.md
Normal file
|
|
@ -0,0 +1,32 @@
|
||||||
|
# Add data disk
|
||||||
|
|
||||||
|
I'm trying to add a 1TB SSD drive to banky, connected to the mainboard,
|
||||||
|
to use it as a data disk.
|
||||||
|
|
||||||
|
I used `fdisk -l` to list the connected disks. The SSD already appeared
|
||||||
|
there.
|
||||||
|
|
||||||
|
I then partitioned this disk with `fdisk /dev/sda/` (/dev/sda was the
|
||||||
|
given name for the disk. The exact name for your case can be checked by
|
||||||
|
running `fdisk -l`). The command for partitioning is `n`.
|
||||||
|
|
||||||
|
Now it's time for formatting. After some reading, apparently the right
|
||||||
|
choice for a linux data disk would to use `ext4`. But bear in mind this
|
||||||
|
is not compatible with windows and macos. If you have a disk that would
|
||||||
|
like to use across different OS systems, you can pick `fat32`.
|
||||||
|
|
||||||
|
To format, pick the partition (you can find it with `lsblk`) and use the
|
||||||
|
mkfs command.
|
||||||
|
|
||||||
|
Well that was the theory, because it didn't work for me. I ended up using
|
||||||
|
Debian's GUI disk tool. Two clicks and done.
|
||||||
|
|
||||||
|
Finally, the disk needs to be mounted. To do so on every boot, you need
|
||||||
|
to add a line like this one to `/etc/fstab`.
|
||||||
|
|
||||||
|
```
|
||||||
|
UUID=66d23b74-677d-4122-8e67-4bc88ea03b18 /media/data_disk/ auto rw,user,auto 0 0
|
||||||
|
```
|
||||||
|
|
||||||
|
Where the UUID should be one for the disk (you can find it out with `blkid`
|
||||||
|
or some other of the disk utilities) and the path should exist.
|
||||||
25
notes_on_bitcoin_core_install.md
Normal file
25
notes_on_bitcoin_core_install.md
Normal file
|
|
@ -0,0 +1,25 @@
|
||||||
|
# Bitcoin core install
|
||||||
|
|
||||||
|
Just a few notes to refresh my mind if needed.
|
||||||
|
|
||||||
|
I've gone to the bitcoin.org page and downloaded the Linux version
|
||||||
|
for bitcoin core 22.0. I followed the instructions there and installing
|
||||||
|
was super easy and quick.
|
||||||
|
|
||||||
|
My next issue is setting up the config of the daemon so that it stores
|
||||||
|
the blockchain in the SSD disk I've set up for that, instead of in my
|
||||||
|
small main drive.
|
||||||
|
|
||||||
|
After some tinkering, I find how. The default dir where core stores data
|
||||||
|
is ~/.bitcoin. When I started the daemon, it started creating all sorts of
|
||||||
|
stuff there, including the copy of the blockchain. I completely erased the
|
||||||
|
folder, and created a new folder in my target SSD. Then, I used Jameson
|
||||||
|
Lopp's bitcoin core config file generator tool to tweak some settings,
|
||||||
|
including the data dir for all data. I placed the conf file in
|
||||||
|
~/.bitcoin/bitcoin.conf and started the bitcoin daemon. Then, the daemon
|
||||||
|
started writing into the dir in the SSD I pointed it to through the config
|
||||||
|
file. Great success!
|
||||||
|
|
||||||
|
Now the blockchain is actively being downloaded. The process is easy to
|
||||||
|
monitor: there is a blocks folder, and each block gets a different file
|
||||||
|
within it. So a simple ls allows watching the process live.
|
||||||
Loading…
Add table
Add a link
Reference in a new issue