Skip to content
Discussion options

You must be logged in to vote

Yes, that occasionally happens on the NAND-based dreames.
I suspect that there is something not quite right in the storage layer of that custom kernel but I don't know for sure.

The result however is corruption of the ext4 fs on /data, which the robot detects during the daily reboot and then recreates a new fs there.
As valetudo is stored on /data, with that, the binary is gone.

So yeah. You can just put it back like described in the rooting guide
Or you do the easy thing, build a new dustbuilder package with Valetudo prepackaged and install that via ssh.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@chrisduerr
Comment options

Answer selected by chrisduerr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants