I tried 1.14.[0,1,2] and 1.13.0
They all failed at the same point 
At this point, I’m considering reinstalling the OS.
Edit: I’ve opened a new topic to discuss this issue.
@alessandro Just to inform you that I’ve been able to build the missing file by creating a swap partition on my SSD.
4GB of RAM is not enough to build Cardano-node.
2 Likes
Nice, yeah building takes a lot of RAM. I had no problems with the 8GB version. Worked flawless.
1 Like
Agree. I went through the same with a 4Gb RP4 and it always complained on memory. With the 8Gb RP4 it worked first time.
2 Likes
What would you recommend for the 250GB SSD? I was doing a quick search and saw that the Samsung 950 Pro NVME works well for the RPi4 but it’s a bit too pricy for me, would cheaper alternatives work? Also I don’t have any SSD cable adapters, what would be a good one to get as new? Thanks.
Will this SSD and this adapter last on the RPi4 running 24/7?
1 Like
I think it doesn’t matter which SSD you buy. I have the SanDisk Plus SSD.
The Eluteng Sata Adapter should work without problems. I have Sabrent and it works too, but I needed add quirks.
1 Like
Thanks a ton! For the advice and for the guide. From what I see online, quirks is on the software side and not an accessory/hardmod, is that correct?
yes, it’s just a small software modification. This tutorial helped me:
1 Like
Any recommendations for cooling? Regular heat sinks? Cooling cases? Fans?
I’m using an aluminium case. Actually the case had two cooling fans on it, but they were too loud hahaha, so I removed them and I’m just using the case for passive cooling. That’s more than enough, because CPU usage is just about at 5-6% with two running nodes.
1 Like
Wow, never thought it was that light on cpu usage. Was expecting somwhere from 10-20%. The RPi 3 I used for multimedia was almost always at 80% cpu usage. Props to the devs at IOG. Gonna try the aluminium case. May add a fan during summer heatwaves. Thanks as always.
The building and syncing process will take a lot of cpu and ram. But as soon as the node is running normally, the cpu and ram usage is very low. The Pi can handle this easily.
do not buy Nvme. the enclosed cases are not compatible with raspberry. ive tried them all from amazon. i end up with a 500gb SSD. anyway there is no need for nvme . you will not feel the difference
1 Like
Great man. Will this work for the ROCkPI too?
Maybe yes, if you get Ubuntu 20.04 LTS on the Rock Pi, the guide should work out of the box.
I’m new to Raspberry Pi, but I’m thinking about getting one to try and run my pool (thanks for the tutorial btw). I’m concerned about the IP though. I know you can change the local IP address on your Raspberry Pi to a static one. For the relay node, do you use the local IP address of your Raspberry Pi or do you use your router’s public IP address? I’m unsure about this because I only have experience running a pool with a free trial from a cloud server which offers you a static IP, so I know I need to use that static IP so my core node and relay node are connected to the blockchain and among themselves. But I have no idea how that’ll work with a Raspberry Pi. Sorry if this question is dumb or whatever, I have zero experience with Pi’s and changing IP addresses. Thanks
1 Like
Hey, the problem is actually not Pi specific. It’s generally a problem if you want to run a pool from home.
But it’s definitely solvable. If you run the relay node in the same network as the core node I would surely use the local IP to connect to it.
So the local IP as you said can be made static. It should be an option in the router settings.
The public IP is necessary so that other nodes can connect to your relay. Maybe your ISP allows you to get a public static IP. If not you can also connect a dynamic domain name. I have a FritzBox and I have an option there to connect a domain. Although my IP address might change, the domain always points to the router.
2 Likes
What if I want to have more than one relay? The hostname/domain will be the same for both, but what differentiates them will be their ports, right? So it’ll be something like:
R1: IP - domain.ddnsserver.xyz (hostname/domain) ||| port - AAAA
R2: IP - domain.ddnsserver.xyz (hostname/domain) ||| port - BBBB
Core: IP - local static IP ||| port CCCC
1 Like
Exactly it’s just the port, that differentiates between the relays. You need to forward the ports in the router settings and then you can access them from outside with the domain/public ip.
1 Like
