Issue during Valetudo Installation on Roborock S7: Insufficient Storage and Mounting Error

[chev-ak]

Are you already using Valetudo?

No, but in the process of starting it

Your questions

Hi, I am experiencing an issue during the installation of Valetudo on my Roborock S7 (Production Date: 08.2021).
It seems there is not enough storage space available for the installation on my Roborock S7.

I am following this tutorial exactly: https://valetudo.cloud/pages/installation/roborock.html#fel

I successfully copy the file roborock.vacuum.a1[4_5]_1612_fw.tar.gz with the command:

scp -O -i ~/.ssh/your_keyfile Downloads/roborock.vacuum.a1[4_5]_1612_fw.tar.gz [email protected]:/mnt/data/

to the Roborock, which works fine. Then, as described in the tutorial: ./install.sh

After that, I receive the following error message:

[root@rockrobo data]# ./install.sh
---------------------------------------------------------------------------
 Roborock manual Firmware installer
 Copyright 2020 by Dennis Giese [dgiese at dontvacuum.me]
 Intended to work on s5e, p5, a08, a11
 Version: roborock.vacuum.a1[4|5]
 Use at your own risk
---------------------------------------------------------------------------
We are currently on rootfs1, will installing on rootfs2
check image file size
Checking integrity
./boot.img: OK
./rootfs.img: OK
Start installation ...
Installing Kernel
482+1 records in
482+1 records out
3954688 bytes (4.0 MB) copied, 0.569155 s, 6.9 MB/s
Installing OS
2448+0 records in
2448+0 records out
20054016 bytes (20 MB) copied, 3.35304 s, 6.0 MB/s
Trying to mount system
mount: mounting /dev/nandf on /tmp/system failed: Invalid argument
(!!!) Did not found marker in updated firmware or mount the partition (maybe XZ compressed?). Will try alternative method
23+0 records in
23+0 records out
24117248 bytes (24 MB) copied, 2.18085 s, 11.1 MB/s
Parallel unsquashfs: Using 4 processors
3145 inodes (1569 blocks) to write

[===================================================================================================\                               ] 3615/4714  76%
Write on output file failed because No space left on device

FATAL ERROR: writer: failed to write file /tmp/squashfs-root//usr/lib/arm-linux-gnueabihf/libcurl.so.4.3.0
looks good, proceeding
Setting next boot to B
1+0 records in
1+0 records out
1 byte (1 B) copied, 0.0239953 s, 0.0 kB/s
----------------------------------------------------------------------------------
Done, please reboot and check if the robot boots the new firmware
Repeat installion after rebooting, if everything works
Dont forget to delete the installer files after rebooting
----------------------------------------------------------------------------------

I listed the directories and free space using the command df -h maybe that will help further:

[root@rockrobo ~]# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                   22.8M     22.8M         0 100% /
/dev/root                22.8M     22.8M         0 100% /
devtmpfs                 64.0K         0     64.0K   0% /dev
none                    122.5M     16.0K    122.5M   0% /run
tmpfs                    30.0M    156.0K     29.8M   1% /var
tmpfs                    64.0K         0     64.0K   0% /dev
tmpfs                    60.0M     20.0K     60.0M   0% /tmp
tmpfs                   100.0M      4.2M     95.8M   4% /run/shm
/dev/nandl              149.9M     52.2M     89.9M  37% /mnt/data
/dev/nandb             1003.0K     61.0K    891.0K   6% /mnt/default
/dev/nandk                3.9M      1.6M      2.1M  42% /mnt/reserve
/dev/nandh              768.0K    768.0K         0 100% /mnt/resources/audio_bit
/dev/nandi                2.0M      2.0M         0 100% /mnt/resources/audio_default
/dev/nandj                2.5M      2.5M         0 100% /mnt/resources/audio_custom
[root@rockrobo ~]# 

The installation always fails at 76%.
What does mount: mounting /dev/nandf on /tmp/system failed: Invalid argument mean?
What can I do to get the installation working?

[Hypfer]

I can see that the error message there is confusing and I'm too confused why you're seeing that, however, that should not interfere with the install.

It also did not interfere with the install, because the script continued

looks good, proceeding
Setting next boot to B

Are you sure that the installation failed?

[chev-ak]

I had to abort the installation and disconnect the battery from the board, as I didn’t want to damage the robot.

After your reply here on GitHub, I followed all the steps from your tutorial again.

After running the ./install command, I received the same error message. I ignored it and proceeded with the reboot command. The installation could then continue after the reboot, as you had already suspected. Now Valetudo is running on my Roborock S7. Thanks Hypfer for your Work! :)

---

Maybe a quick tip for Ubuntu users who can use Ubuntu graphically but have trouble with commands in the terminal:
After the first reboot of the Roborock, the SSH connection fails. Here is part of the error message:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is...

You can ignore that problem with ssh-keygen -f '/root/.ssh/known_hosts' -R '192.168.8.1.
After that, the connection can be restored with the command ssh -i ./your-keyfile [email protected].

This worked for me and I was able to continue the installation. Everyone has to decide for themselves, no guarantees. :)

Hypfer mentioned it right at the beginning of the tutorial: If you're inexperienced in linux, hardware, etc., please ask a friend with more experience for help. That would be the best way. :)