Vera extroot

I think that they should package it all into a RasPi…

1 Like

This would not work. The vera is not arm based.
Heads up. The beta 7.30 firmware is indeed blocking extroot. The main reason behind it appears to me that the numerous workarounds to better utilize the onboard flash is neutralizing the ability for the kernel to pivot the root file system. As a workaround, I am actually going to create a firmware upgrade script which will upgrade you to the beta firmware while still extrooted. So the best way to go around this is to downgrade to 7.29, extroot with the previous extroot script and then run this new script I am working on to upgrade to 7.30 beta. This will take a little longer than I thought as it is a bit more complicated but in a way will make your vera upgrade process much more similar to what I am doing with my emulator. You will therefore not use the UI firmware upgrade feature which runs a different script.

Wonderful work.

What about those on Exroot, that have not updated at all yet? I assume we can still use the script you are creating?



Yes it should work. Unfortunately I am struggling with the downgrade at the moment so people who want to keep extroot, please do not upgrade to the beta quite yet. Once upgraded, the new storage partitioning can’t be reverted at the moment.

I think I found a solution… It will not be a full extroot but will serve to move all of the frequently written and overwritten user files to be run and loaded from the ssd.
See the attached script below. This assumes that you upgraded your vera to 7.30 beta, plugged in your SSD and already set up USB logging. Upload the .sh file, make it executable (chmod +x and execute the script ./ (1.0 KB)

OK tracked down the original thread and script, thanks.


Please find enclosed two new scripts for the vera plus for those who are extrooted on 7.29.

  1. A new enhanced extroot script for 7.29
  2. Once extrooted, (no need to run it again if you already are extrooted), run the upgrade script. It will upgrade your external drive to the new 7.30 firmware build 4833 without the kernel mods!
    Note that your network settings will be reset to DHCP (I have not had the time to go fix that) so you may get a new IP address.

The magic of this upgrade is that unplugging the USB drive and rebooting will take you back to 7.29. :scream:

Reminder of why you would want to upgrade: Zwave Network On Vera Explained

Update: Successfully created the same functionality for the vera edge. For the vera secure, you could try the veraplus version. (1.5 KB) (2.4 KB)


so we have to go back to 7.29 first correct?

You have to have never upgraded. The downgrade fails to downgrade the kernel and will not allow you to pivot. As noted, it assumes that you are on 7.29

ok ill reflash this weekend, safe to say this is exactly how future firmware should be implemented. a stable firmware and extrooted overlay / firmware update so if things go wrong. we just unplug the hard drive and go back to the stable version. Excellent job. Support should really look to implement extroot into the firmware for massive systems

1 Like

Next up: I will give a shot to making it work on the vera edge. I think I found a way to workaround the memory limitation.


Agree…They would save alot of supporttime with a native exroot = earn money…

Oooh, I’m tempted. But rather scared!


Well the edge also appears to have gotten some kernel changes preventing extroot from working… This is frustrating. I may need to downgrade the kernel again to start from 7.29 and then follow the same process of first extrooting on 7.29 and then upgrade only the drive to 7.30. Stay tuned…



wget: not an http or ftp url:

mounting squashfs

mount: mounting mt7621_Luup_ui7-1.7.4833-en-mios.squashfs on /mnt/tmpfw failed: No such file or directory

copying firmware files over to USB drive

cp: can’t stat ‘/mnt/tmpfw/*’: No such file or directory

umount: can’t umount /mnt/tmpfw: Invalid argument

rm: /mnt/tmpfw: is a directory

rm: can’t remove ‘mt7621_Luup_ui7-1.7.4833-en-mios.squashfs’: No such file or directory

Reboot? n


Hope I’m not screwed now :slight_smile:

I’ll hold off rebooting.



No it did nothing. It looks like I uploaded the wrong file. Let me send you another one.

Sorry about this. Please delete the previous file and try this one. I indeed uploaded the wrong file.

Never a need to apologise! I was only teasing that I thought I was scuppered :wink:

PS are you updating the link or attaching new? It seems unchanged? Thanks again!


and we can recover it if it bricks :sweat_smile:

1 Like

Yep, I just did a forced downgrade of the kernel to try extrooting the edge. Somehow this time, it did not pop the vera4lite error when upgrading to 7.0.29… weird.

Success! Same script for the vera edge now available!

As a reminder, the process is as follows:
Start from 7.0.29 before ever upgrading to 7.0.30. You may need to run a chmod +x *.sh after uploading the files on your vera either through sftp or scp. Then:

  1. extroot using the extroot script
  2. then upgrade to 7.0.30 using the upgrade script.
root@MiOS_4500XXXX:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                   58.1G     85.2M     55.0G   0% /
/dev/root                 9.5M      9.5M         0 100% /rom/rom
tmpfs                    61.9M    400.0K     61.5M   1% /tmp
/dev/mtdblock6            9.4M      3.8M      5.6M  41% /rom/overlay
overlayfs:/overlay        9.4M      3.8M      5.6M  41% /rom
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock10          64.8M      9.3M     55.4M  14% /rom/storage
/dev/mtdblock10          64.8M      9.3M     55.4M  14% /rom/etc/cmh-firmware
/dev/mtdblock10          64.8M      9.3M     55.4M  14% /rom/etc/cmh-backup
/dev/sda1               487.8M      2.8M    459.5M   1% /tmp/log/cmh
/dev/mtdblock9            7.5M      7.5M         0 100% /rom/mios
/dev/sda2                58.1G     85.2M     55.0G   0% /overlay
overlayfs:/overlay       58.1G     85.2M     55.0G   0% /
1 Like

That was a tad scary

I think your scriptm needs cp -r as opposed to just cp?
Anyway ran each step manually, appeared to have a fully bricked router. (only power and wifi LEDs even after USB unplugged)

Tried to do a reset, did nothing. One more hadr boot with the USB in and it’s come back up, I assume with the new FW in place. PHEW

Looooong boot time though


Yeah I noticed that I posted a version of the script which was not the one I tested. This last one should be all good now. There is also no chance for it to brick your vera… it only edits the fstab from your main drive which defaults back to the original onboard root if it fails.

1 Like

Best Home Automation shopping experience. Shop at getvera!

© 2021 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules