My Remarkable stopped to update automatically. It says in the online Remarkable guide that it is because there is not enough space in the root partition of the device. They recommend to ssh to the device and do some cleanup, which I did. The command ‘df -h /‘ returned 98% of the space is used. Then I ran the ‘journalctl—vacuum-size=1’ as recommended. Used space came down to 94%, but still not enough to allow for updates. Beyond that point they recommend to ask for help on the community Discord. So here I am. I could not find any posts on that matter on this forum. Any help about how I can free more space to allow for updates? Thanks
#Freeing space to allow updates
1 messages · Page 1 of 1 (latest)
The guide says it might be because of that, not that it's for sure because of that. 98% would be enough to function properly, it's if it's at 100% usage that you can no longer do any network actions. Next steps are to review the update logs to see what the issue is.
journalctl -eu update-engine will output the update logs and place you at the end of the logs. You can move up/down with the arrow keys and page up/down. When you are done, q or ctrl-c will quit out of the logs view.
Also, freeing up space is only troubleshooting step number 3. I assume you also tried steps 1 and 2?
reMarkable Guide
Is it safe to factory reset my device?, How do I remove all third party software from my device?, Can I downgrade to a different OS version?, How get back to stable after installing the beta?, Can ...
Hi @robust dock , thank you so much for looking into my issue. Yes, I tried steps 1 and 2 in the guide, but it did not help. But it seems that I have a bigger problem now as it seems that the tablet is refusing my ssh connections now. I get these “Connection reset by peer” or “Connection reset by <tablet IP> port 22” errors. I feel that the ssh server inside the tablet is now blocking my connection attempts after I used a wrong login password a few times, although I’m pretty sure I was using the right password. Anyway, I can’t ssh to the tablet anymore and I don’t know how to make it work again.
If you recently updated/downgraded this may be the issue you are encountering: https://remarkable.guide/faqs.html#i-updated-my-os-but-now-i-can-t-ssh-into-my-device-how-do-i-fix-it
You can also try SSHing in over usb instead of wifi or vice versa depending on what you were trying previously.
https://remarkable.guide/guide/access/ssh.html#connecting-via-ssh
I would also recommend getting an SSH key setup to make sure you can get in if the password changes: https://remarkable.guide/guide/access/ssh.html#setting-up-a-ssh-key
Hi @robust dock , I was able to ssh to the tablet. This is the error I see in the update logs:
Unable to get http response code: SSL certificate problem: certificate is not yet valid
Transfer resulted in an error (0), 0 bytes downloaded
Error buffer: SSL certificate problem: certificate is not yet valid
Last update attempt was on March 10.
Sounds like your time is out of sync
Have you restarted the tablet since this issue started?
Yes, I did
What does timedatectl output?
I got this:
reMarkable: ~/ timedatectl
Local time: Sun 2024-03-10 18:24:43 UTC
Universal time: Sun 2024-03-10 18:24:43 UTC
RTC time: Mon 1970-02-16 19:12:21
Time zone: Universal (UTC, +0000)
System clock synchronized: no
NTP service: active
RTC in local TZ: no
I plugged my tablet to my computer via USB as suggested on the web to synchronize time again, and the tablet seems to be updating again. Thanks!!
System clock synchronized: no this would be why it's not able to download an update
I wasn't aware it could sync time via usb. Where was this suggested?