It works! I see my full m.2 disk in the latest version 
1 Like
No success with PowerShell, too. This is what I get:
node-launchpad failed:
Error:
0: ←[91mFailed to parse app data←[0m
yes, the latest launchpad…
one thing that can cause that error is a previous version of the launcher’s config file being there.
Have you run the reset command?
Probably this could be walked-around in Linux and MacOS by symlinks, and quick search revealed that symlinks are also possible on Windows, but I have not tested it.
Not needed, it works now with v0.3.7.
I updated Launchpad to version 0.3.7 and reset but it doesn’t change anything because it’s probably about the memory, which is full:
Will I have to wait for the new feature or could I use the CLI tool to try to change the storage location in the starter?
My guess is that you should try with CLI. I think your SD-card is the primary storage device and the USB-connected SSD is the second drive, correct?
I have such a configuration of the computer that the drive (C:) SSD is used only for the Win system, and the other drive also permanently installed in the computer is the drive (E:) and on it I have a lot of free space, but the starter sees the default basic memory and probably that is why it shows that I have 0GB available space.
I don’t know if I could use the CLI tool to change the location of the starter? Did you do that?
No, I am not using Windows for the node machine.
I would forget about the launchpad for now until there is another update. Focus on the CLI… Good luck!
1 Like
I have another question. Two of my old nodes keep restarting. I can keep killing them with pkill, but they keep coming back. I used safenode-manager to stop, reset and remove all, but these two nodes will not give up…
How do I stop them?
For a fresh start.
sudo killall safenode
sudo systemctl disable --now safenodeX
sudo rm /etc/systemd/system/safenode*
sudo rm -rf /var/safenode-manager
sudo rm -rf /var/log/safenode
sudo systemctl daemon-reload
4 Likes
12 GMT = 13 BST = 14 CET = in 30 minutes?
2 Likes
Thanks! But if I run the first command, I can still see the nodes started again immediately after.
The second command does not work correctly, it says
> sudo systemctl disable --now safenodeX
Failed to disable unit: Unit file safenodeX.service does not exist.
I tried it with the PID too but that does not work. Any recommendations?
no sorry, that normally works for me.
Never mind, I got it now! I had Vdash and the launchpad running. When I closed those, the nodes did not return after killing them. All sorted now! Did your other commands too without any issues.Tnx 
1 Like
Are we starting? Will the nodes be able to pickup a peer automatically?
Well, nodes are up. Now, who’s uploading??
1 Like