Reflash not helping

OK, will do. The SD card was new before last reflash 0.4.15 two days ago
Will try again with v.16
Thanks

Unfortunately reflashing 0.4.16 didn’t work, here’s the latest debug script:
https://0bin.net/paste/TFqzKzMB#o4WZQmEcff+qNIrHn6th2kS4YDhUGqY5HUhUXpMSVnT

Mar 15 22:39:17 umbrel external storage mounter[481]: fallocate: fallocate failed: No space left on device
Mar 15 22:39:17 umbrel systemd[1]: umbrel-external-storage.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 22:39:17 umbrel systemd[1]: umbrel-external-storage.service: Failed with result ‘exit-code’.
Mar 15 22:39:17 umbrel systemd[1]: Failed to start External Storage Mounter.

External storage SD card update service logs

– Logs begin at Tue 2022-03-15 22:39:07 UTC, end at Tue 2022-03-15 22:40:59 UTC. –
Mar 15 22:39:17 umbrel systemd[1]: Dependency failed for External Storage SDcard Updater.
Mar 15 22:39:17 umbrel systemd[1]: umbrel-external-storage-sdcard-update.service: Job umbrel-external-storage-sdcard-update.service/start failed with result ‘dependency’.

I think the answer is there: something wrong with that mSD card.

Logs simply say many times SSD disk is full, but people don´t care logs… :man_shrugging:

so a 64GB mSD should solve the problem?

Look’s like the current one is corrupted or full or for whatever reason is not working as it should. If you have another (32GB is enough, 64GB maybe better) one try with a fresh umbrel install and follow the steps to restore your node.

2 Likes

It’s always good to have a spare mSD ready to replace. Those little fuckers broke very easy.

1 Like

I can´t stop laughing. People don´t know what is a SSD… :laughing:

1 Like

is too much text man… people get bored to read or sometimes don’t know to read. Just asking here they think will resolve all at once magically… :rofl: :rofl: :rofl:

Reflashed a brand new 64gb mSD but no joy.
Seems to rule out the faulty SD card.
Would it be the SSD?

You think it’s a full SSD? It is 1TB.
I thought it was only storing the blockchain, a bit over half that size

Logs are clear about this, please read logs.
Use a Raspbian SD in RaspPi, install VNC Viewer in your PC and enable it in RaspPi, then look the contents of SSD in file explorer.
You can also install Gparted in the Raspbian SD, to view partitions state on SSD.

1 Like

@Catoshi

Filesystem information
----------------------
Filesystem Size Used Avail Use% Mounted on

/dev/root 29G 3.1G 25G 12% /
/dev/sda1 916G 916G 0 100% /home/umbrel/umbrel <<<< Answer

The answer is yes. Your SSD is FULL and has 0 bytes available. That looks like the logs got out of control and filled up the entire SSD.

1 Like

Thanks. Looks like I’ll be studying this a bit deeper. You said PC, same for Mac?

Thanks for pointing me at the line, I see it clearly when you show it to me like that

For Mac you can also install a EXT4 file reader soft, and plug SSD direct to it.

1 Like

I have absolutely no idea what I am doing :exploding_head:

This is the info I could find so far-

/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4
1: Linux Filesystem ⁨⁩ 1.0 TB disk4s1

Would it be best to wipe the SSD and start again?

If you don’t have opened channels, no problem. If you have channels, before deleting data, copy to another disk the files channel.backup and channels.db of SSD, so you can restore the channels after reinstall.

1 Like

Gracias Lobo

Can I just delete the logs?
From what I’ve read below I need to use EXT4 file reader.
I’ve managed to pull up info of the SSD using MACfuse, but no idea how to actually get in and delete the logs.

I get the following error msg:
Error: ext4fuse has been disabled because it requires closed-source macFUSE!

Therefore it doesn’t recognise the cmd line:
sudo ext4fuse /dev/disk4s1 ~/tmp/ext4_support_PARTITION -o allow_other

Maybe it would be better to upgrade to 2TB SSD? (can’t really justify the expense right now)