Closed OhSoGood closed 2 years ago
This is probably better suited for the discussion part since it's not a bug report. I would close this issue and post your question there instead. https://github.com/Hypfer/Valetudo/discussions
Done. Thanks for the tip. Link to the discussion: https://github.com/Hypfer/Valetudo/discussions/1432
Hi,
I have an old version running on my Roborock V1 (Valetudo 0.4 if I'm not wrong). I've created and downloaded a new firmware image from Dustbuilder, and I cannot upload it to my vacuum. Any write on /mnt/data or any subfolders, even a simple file creation, leads to "No space left on device".
Can anybody help me? Should I install the image the old way, with mirobo? Or can I use / to upload the image (I think / is volatile and and its content won't exist after a reboot, will it?).
Thank you!
My /etc/fstab:
A df -h:
cat /proc/cmdline:
rootwait boot_fs=a console=ttyS0,115200 root=/dev/mmcblk0p8 rootfstype=ext4 loglevel=7 partitions=boot-res@mmcblk0p2:env@mmcblk0p5:app@mmcblk0p6:recovery@mmcblk0p7:system_a@mmcblk0p8:system_b@mmcblk0p9:Download@mmcblk0p10:reserve@mmcblk0p11:UDISK@mmcblk0p1 boot_reason=0x0 location=prc boot_ver=2011.09-rc1-dirty