Starting a NODE

[aoluain]

Major head scratching going on ATM, Starting right off with the most basic setup.
--snip--
So more questions to be asked . . .

I'm not sure whether you just share your experience or also asking help. So i'll just mention few things,
1. To format drive, set it's mount point and permission, i usually just use GUI application (such as GNOME disk utility). See https://askubuntu.com/a/1407682.
2. Based on PDF you shared a week ago, your Chromebook have 64GB or 128GB storage. It should be more than enough to download and store application you need.

Thanks ABC - its a bit of both really [I realise what I am experiencing ATM is Linux related and not
Bitcoin related so I dont really want this thread to turn into "hey guys how do I save in the fstab editor?"
because there would be soooo many questions.]

1. Drive is formatted to ext4 and partitioned

Its the mounting I cant seem to do.

2. I'm trying to set the drive up so that both Fulcrum and BitcoinCore download directly to it.
from what I read from one of the links above Fulcrum is about 110gb, I would rather have that
on the external drive.

the instructions I am using are as follows:

AI Overview

To automatically download to an external SSD on Debian, you must first auto-mount the SSD,
then configure the system to use the SSD as the download directory for your applications. For example,
for your web browser, you'd go into its settings and change the download location from your internal drive
to a folder on the mounted SSD. For other applications, you may need to set a new download directory
within their individual settings.

Here are the general steps to achieve this:

1. Identify the SSD and your desired mount point:
Open the Disks utility or use the lsblk command in the terminal to identify your external SSD and its partition.
Decide where you want it to be mounted, such as /mnt/my_external_drive.

2. Create a mount point folder (if it doesn't exist):
Open a terminal and enter sudo mkdir /mnt/my_external_drive to create the directory, replacing my_external_drive with your chosen folder name.

3. Set up automatic mounting using systemd-mount or fstab:
For systemd-mount: You can use systemd-mount to create a temporary mount point that will also mount on startup, which is simpler than manually editing fstab.
For fstab (more permanent):
Open the fstab file with a text editor: sudo nano /etc/fstab.
Add a line like this, replacing the placeholders with your SSD's information: UUID=YOUR_SSD_UUID /mnt/my_external_drive ext4 defaults,nofail 0 2. (You can find your SSD's UUID using lsblk -f in the terminal.)
Save and exit the editor.

4. Configure your applications:
Open your browser's settings: and change the default download location to your new SSD folder.
Open settings for other applications: like torrent clients or file managers and do the same.

5. Verify the setup:
Restart your computer: to confirm the SSD mounts automatically.

Try downloading a file: to ensure it saves to the external SSD.

It looks really straight forward - but for myself who is not familiar with code or Linux I find I am
in way over my head.

I find I have to "research" every little instruction and I dont know what I am doing really.

I.E "Open the fstab file with a text editor: sudo nano /etc/fstab" - yea thats fine, when I open
it there is no other text there so I dont know if I should be just adding a line of code to that blank
window or if I need to take another step to place the code at the end of existing code -
so I have to do more research to this effect and I'm not getting it and its very slow.

I.E "Save and exit the editor." - a simple action like Save means I need to research how to do that
because its not an option in the fstab window - lol

I'm guessing what I am trying to do is maybe a 5 minute set of tasks for someone familiar
with Linux, I'm a good 10 hours into this now - which is a bit worrying
_{I can imagine some of you are saying i need to abandon this especially if i am struggling on the first rung of the ladder!}

Thanks for the GNOME disk utility link, I'll check it out
I wont post any more until I figure it out  . . . so we can move on to the Bitcoin related install . . .

[aoluain]

. . . I'm back _{without much of an update}

apologies I'm still stuck on the Debian issues but I thought I better "show my face" here with
somewhat of an update at least to say I am still working on it!


My issue now is that Debian has stopped launching ^FFS
I open terminal and the Debian launch is hanging on:

Code:

[======|        ] Starting the Linux container

and after a number of minutes a notice comes up:

Code:

Launching vmshell failed: Error starting crostini for terminal: 58 (START_CONTAINER_TIMED_OUT)

I have posted the issue on the Debian forum and the first reply is suggesting I need to reinstall
Debian ^{i think} - that does not sound well to me.

Anyway, thats the update for now . . .

[MarangoZ]

Hi All, After 8 years a Bitcoiner I have decided to jump into running a NODE, its something
which has been on my radar for a while now but I think I am ready to make the move.
[I'm probably making it sound like a life changing experience - maybe it is...

Anyway, I have been doing a little research but I thought I would consult the Guru's here
before I actually make a start.

Questions:

Hardware: What do I need [miniumm]? I have read that the way to go is a Raspberry Pi and an SSD but what else to I need?
Node: What type of node do I run [Full, Pruned or Light]?

Info:
I just checked my internet connection and currently the speeds are:
Down 23Mbps / Up 0.85Mbps

Thanks in advance!

great step to take  here you can read my experience and the hardware im using
Running My First Bitcoin Node – My Experience & Setup Guide

[aoluain]

Thanks for the link MarangoZ. Now I am beginning to wish I had maybe used a VPS as
suggested earlier in the thread!


So after messing around with the suggestions from a google search I think I am going to
have to start afresh with this which is ultra frustrating. The pressing questions I have are,

When will this error happen again?
How often will this happen?
If/when it happens again, how is it going to affect the running of the node?


Here is the search result from Google

https://www.google.com/search?q=debian+on+chromebook+cannot+start+the+linux+container&sca_esv=c280e7663ee8d6fe&ei=VcjTaIiBMsaBhbIPk6ySyQQ&ved=0ahUKEwjI__3cmPGPAxXGQEEAHROWJEkQ4dUDCBA&uact=5&oq=debian+on+chromebook+cannot+start+the+linux+container&gs_lp=Egxnd3Mtd2l6LXNlcnAiNWRlYmlhbiBvbiBjaHJvbWVib29rIGNhbm5vdCBzdGFydCB0aGUgbGludXggY29udGFpbmVyMgUQABjvBTIFEAAY7wUyCBAAGIAEGKIEMggQABiABBiiBEj1HVC7BFjZFXABeAGQAQCYAcABoAHWCaoBAzkuM7gBA8gBAPgBAZgCDaACqArCAgoQABiwAxjWBBhHwgIKECEYoAEYwwQYCsICCBAhGKABGMMEmAMAiAYBkAYIkgcDOC41oAfyMbIHAzcuNbgHoQrCBwcxLjguMi4yyAcp&sclient=gws-wiz-serp

Method 1: Restart the Linux Container
This is the simplest method and often resolves temporary issues.
1.Right-click on the Terminal app icon in your Chromebook's shelf.
2.Select "Shut down Linux" from the context menu.
3.Once the container has shut down, launch any Linux application (like Terminal) from the launcher to restart it.

Method 2: Manually Start from Crosh
If the simple restart doesn't work, try starting the VM and container manually to get more information.
1.Press Ctrl+Alt+T to open the crosh terminal.
2.Type vmc start termina and press Enter to start the virtual machine.
3.If you get an error, note it down and report it to Google using Alt+Shift+i.
4.If no error, type exit to exit the crosh prompt.
5.Type vmc container termina penguin and press Enter to start the container.
6.If you get an error, report it using Alt+Shift+i.

Method 3: Deactivate and Reactivate Linux
If the previous steps fail, you can try deactivating and then re-enabling the Linux development environment for a fresh start.
Go to Settings > Linux development environment.
Select "Turn off" or "Deactivate" to remove your Linux environment and data.
Once deactivated, you can go back to Settings > About Chrome OS > Linux development environment and select "Set up" to reinstall it.

and here is the result of Method 2 above, a problem with penguin.

Code:

Welcome to crosh, the ChromeOS developer shell.

If you got here by mistake, don't panic!  Just close this tab and carry on.

Type 'help' for a list of commands.

If you want to customize the look/behavior, you can use the options page.
Load it by using the Ctrl-Shift-P keyboard shortcut.

crosh> vmc start termina
(termina) chronos@localhost ~ $ 
(termina) chronos@localhost ~ $ exit
logout
crosh> vmc container termina penguin
ERROR vsh: [../../../../../tmp/portage/chromeos-base/vm_host_tools-0.0.2-r3468/work/vm_host_tools-0.0.2/
vm_tools/vsh/vsh.cc:173] Failed to launch vshd for termina:penguin: requested container does not exist: penguin
crosh> 

[ABCbits]

Thanks for the link MarangoZ. Now I am beginning to wish I had maybe used a VPS as
suggested earlier in the thread!

VPS may be better choice if you can trust the VPS provider and willing to work with VPS package you buy. But FYI, VPS specification used by @MarangoZ is inferior compared with your Chromebook.

So after messing around with the suggestions from a google search I think I am going to
have to start afresh with this which is ultra frustrating. The pressing questions I have are,

When will this error happen again?
How often will this happen?
If/when it happens again, how is it going to affect the running of the node?

I don't know what exactly you did, but i almost never break Debian (or other linux distro) on my device. Although i have use linux for many years.

Here is the search result from Google

https://www.google.com/search?q=debian+on+chromebook+cannot+start+the+linux+container&sca_esv=c280e7663ee8d6fe&ei=VcjTaIiBMsaBhbIPk6ySyQQ&ved=0ahUKEwjI__3cmPGPAxXGQEEAHROWJEkQ4dUDCBA&uact=5&oq=debian+on+chromebook+cannot+start+the+linux+container&gs_lp=Egxnd3Mtd2l6LXNlcnAiNWRlYmlhbiBvbiBjaHJvbWVib29rIGNhbm5vdCBzdGFydCB0aGUgbGludXggY29udGFpbmVyMgUQABjvBTIFEAAY7wUyCBAAGIAEGKIEMggQABiABBiiBEj1HVC7BFjZFXABeAGQAQCYAcABoAHWCaoBAzkuM7gBA8gBAPgBAZgCDaACqArCAgoQABiwAxjWBBhHwgIKECEYoAEYwwQYCsICCBAhGKABGMMEmAMAiAYBkAYIkgcDOC41oAfyMbIHAzcuNbgHoQrCBwcxLjguMi4yyAcp&sclient=gws-wiz-serp

--snip--

I see you use guide created by google "AI overview". I rarely use AI/chatbot when i need to mess with linux on my device and wouldn't recommend it to other people.