Vera extroot

I’ll be interested in seeing the results of df -h.

This is a status report on my exrooted VP. I extrooted my test VP on August 28, tested it for a week, then decided it was safe to proceed to the production Vera. That system has been running extrooted on a 128GB SSD without incident since early September of 2018. Here’s the disk map:

Filesystem Size Used Available Use% Mounted on
rootfs 109.4G 107.7M 103.7G 0% /
/dev/root 10.0M 10.0M 0 100% /rom
tmpfs 124.8M 896.0K 123.9M 1% /tmp
/dev/sda2 109.4G 107.7M 103.7G 0% /
tmpfs 512.0K 0 512.0K 0% /dev
/dev/sda1 493.6M 29.6M 427.8M 6% /tmp/log/cmh
/dev/mtdblock10 50.0M 1.4M 48.6M 3% /storage
/dev/mtdblock10 50.0M 1.4M 48.6M 3% /etc/cmh-firmware
/dev/mtdblock10 50.0M 1.4M 48.6M 3% /etc/cmh-backup
/dev/mtdblock9 10.0M 10.0M 0 100% /mios

While it’s difficult to ascribe improvements to stability to extrooting alone, I will say that the system is extremely stable. I only see LUUP reloads when expected. It’s also nice not to have to worry about space for additional plug-ins. For those of you thinking about extrooting, my experience has been positive. @rafele77 has put a lot of effort into this, and I thank him.

I have a USB 120GB SSD. I’m on FW. 1.7.3831. Trying to get extroot running. Tried the script several times.

I thinksomething is wrong, as i end up with only the log drive mounted.

Output from: Storage$: df -h

Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      3.1M      5.5M  36% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M    248.0K    124.5M   0% /tmp
/dev/mtdblock7            8.6M      3.1M      5.5M  36% /overlay
overlayfs:/overlay        8.6M      3.1M      5.5M  36% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/sda1               493.6M    916.0K    456.4M   0% /tmp/log/cmh
/dev/mtdblock10          50.0M     11.4M     38.6M  23% /storage
/dev/mtdblock10          50.0M     11.4M     38.6M  23% /etc/cmh-firmware
/dev/mtdblock10          50.0M     11.4M     38.6M  23% /etc/cmh-backup
/dev/mtdblock9            9.8M      9.8M         0 100% /mios

Is my Fstab corrupted? Content of Fstab file:

config global
	option anon_swap '0'
	option anon_mount '1'
	option auto_swap '1'
	option auto_mount '1'
	option delay_root '5'
	option check_fs '0'

config swap
	option enabled '0'
	option device '/dev/sda2'

config mount
	option enabled '1'
	option target '/tmp/log/cmh'
	option fstype 'ext3'
	option options 'rw,noatime,nodiratime,errors=continue,data=ordered'
	option enabled_fdisk '1'
	option enabled_mkfs '1'
	option enabled_fsck '1'
	option label 'mios'
	option fssize '512'
	option fsck_days '30'
	option fsck_mounts '10'
	option device '/dev/sda1'

config mount
	option enabled '1'
	option target '/'
	option device '/dev/sda2'
	option fstype 'ext4'
	option options 'rw,sync'
	option enabled_fsck '0'

config mount
	option target '/mnt/mmcblk*'
	option enabled '1'

config mount

Could someone post a working Fstab file?

This looks to me like the vera wiped out the sda2 partition and re-edited the fstab. It would do this if you tried to enable USB logging again after extroot was performed. Try extrooting again and make sure to not disable/re-enable USB logging again.

I restored a backup, and started over. Now it works. Thanks for your help.

Filesystem Size Used Available Use% Mounted on rootfs 109.4G 104.7M 103.7G 0% / /dev/root 10.0M 10.0M 0 100% /rom tmpfs 124.8M 272.0K 124.5M 0% /tmp /dev/sda2 109.4G 104.7M 103.7G 0% / tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 493.6M 5.6M 451.7M 1% /tmp/log/cmh /dev/mtdblock10 50.0M 1.6M 48.4M 3% /storage /dev/mtdblock10 50.0M 1.6M 48.4M 3% /etc/cmh-firmware /dev/mtdblock10 50.0M 1.6M 48.4M 3% /etc/cmh-backup /dev/mtdblock9 9.8M 9.8M 0 100% /mios

Great! Thanks for updating status.

Well that seemed painless:

Filesystem Size Used Available Use% Mounted on
rootfs 8.6M 6.5M 2.1M 75% /
/dev/root 10.0M 10.0M 0 100% /rom
tmpfs 124.8M 300.0K 124.5M 0% /tmp
/dev/mtdblock7 8.6M 6.5M 2.1M 75% /overlay
overlayfs:/overlay 8.6M 6.5M 2.1M 75% /
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock10 50.0M 1.5M 48.5M 3% /storage
/dev/mtdblock10 50.0M 1.5M 48.5M 3% /etc/cmh-firmware
/dev/mtdblock10 50.0M 1.5M 48.5M 3% /etc/cmh-backup
/dev/sda1 487.8M 2.5M 455.8M 1% /tmp/log/cmh
/dev/mtdblock9 10.0M 10.0M 0 100% /mios

Vs

Filesystem Size Used Available Use% Mounted on
rootfs 54.4G 99.2M 51.5G 0% /
/dev/root 10.0M 10.0M 0 100% /rom
tmpfs 124.8M 308.0K 124.4M 0% /tmp
/dev/sda2 54.4G 99.2M 51.5G 0% /
tmpfs 512.0K 0 512.0K 0% /dev
/dev/sda1 487.8M 2.7M 455.5M 1% /tmp/log/cmh
/dev/mtdblock10 50.0M 1.5M 48.5M 3% /storage
/dev/mtdblock10 50.0M 1.5M 48.5M 3% /etc/cmh-firmware
/dev/mtdblock10 50.0M 1.5M 48.5M 3% /etc/cmh-backup
/dev/mtdblock9 10.0M 10.0M 0 100% /mios

Time for some decent plugins perhaps

Cheers, sir!

C

I finally received some USB adapters. I was thinking I would try using a compact flash together with my Veralite since I have some at work that are not used for anything.

@rafale77 let me know your thought on using compact flash and then when you find some time you could look in to the “Script” for Veralite.

Hi Tomas,

Compact flash is not much better than USB. Although it has a controller, unlike SD card, it does not really have garbage collection and wear leveling which makes it failure prone if you write on it a lot.
As for extrooting the vera lite, let me look into it. I maybe able to get you a script to test.

Isn’t CF a bit on the slow side as well? I’m guessing that these devices are not exactly IO bound but…

C

[quote=“Catman, post:70, topic:199691”]Isn’t CF a bit on the slow side as well? I’m guessing that these devices are not exactly IO bound but…

C[/quote]
They are slower and you’d probably notice under some circumstances. Honestly, using a real SSD with wear leveling and garbage collection is the way to go. I’ve been extrooted with a high-quality 128GB (what I had on-hand) SSD since September of 2018 and the system has performed flawlessly. The cost of a small SSD is not high.

[quote=“HSD99, post:71, topic:199691”][quote=“Catman, post:70, topic:199691”]Isn’t CF a bit on the slow side as well? I’m guessing that these devices are not exactly IO bound but…

C[/quote]
They are slower and you’d probably notice under some circumstances. Honestly, using a real SSD with wear leveling and garbage collection is the way to go. I’ve been extrooted with a high-quality 128GB (what I had on-hand) SSD since September of 2018 and the system has performed flawlessly. The cost of a small SSD is not high.[/quote]

I think I paid about ?13 for a 60G…

C

Adding a Transcend SATA-2 SSD 32GB (TS32GSSD630) to my Veralite today.

@rafale77 If you can find some time to prepare a script I’m ready to test.

All set:

/etc/cmh/wan_failover:
-rw-r–r-- 1 root root 44 Oct 3 2016 check_internet.hosts
df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 4.5M 4.5M 0 100% /rom
tmpfs 30.5M 360.0K 30.2M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock7 11.0M 4.1M 6.9M 37% /overlay
overlayfs:/overlay 11.0M 4.1M 6.9M 37% /
/dev/sda1 495.8M 10.7M 459.5M 2% /tmp/log/cmh
/dev/mtdblock8 6.4M 6.4M 0 100% /mios

@korttoma, I am out for another week. I will try to get you something after I get back.

@korttoma. So I looked around and have not been able to find the packages necessary to run extroot on a veralite. It requires a backfire version built on an ancient kernel for the Ralink RT3883 CPU or at least a ramips architecture which I have not been able to locate. Sorry but for now, this is not doable on a veralite.

It is ok rafale77, thanks for the effort. The extroot thing is not that important for me on the veralite anyway since it has just a few devices on it. I just like to try things out on the veralite first before I do anything on my main VeraPlus.

rafale77, is this repo of any use Index of /snapshots/trunk/ramips/rt3883/

I’m definitely interested in adding some memory to a veralite as the onboard memory is failing.

[quote=“Buxton, post:78, topic:199691”]rafale77, is this repo of any use Index of /snapshots/trunk/ramips/rt3883/

I’m definitely interested in adding some memory to a veralite as the onboard memory is failing.[/quote]

Unfortunately this is the lede snapshot which is 6 generations of openWRT newer than what the veralite runs. It is build with a different kernel and c compiler so it will not work…

Does it have to be an SSD or can use large USB stick ok?