The Vera Community forums have moved!

General => General => Topic started by: rafale77 on January 19, 2019, 11:32:42 pm

Title: VeraPlus Flash drive usage
Post by: rafale77 on January 19, 2019, 11:32:42 pm
Out of curiousity, I decided to map the flash drive on my vera plus and suddenly realized how absurd all the drive size problems are at least on the vera plus: There is plenty of room left on the embedded flash drive!!! It is just an incomprehensible decision mios has made to partition the drive in the strangest ways but let me start from the beginning:

- The total NAND Flash in use is only 127.5MB out of the 128MB the Macronix chip has available. This maybe by design for some over-provisioning but I have not seen this on other similar devices.
- There are at least 2 firmware images. Not sure why and how it is used as I doubt given the layout that firmware1 is usable at all. More about the 3rd one below.
- There is a 1MB block called user storage which ironically seems inaccessible so definitely not for the user. Not sure what is in there.
- The MTD9 partition, mounted in the "mios" folder on the vera contains a lot of the mios/vera proprietary file and many functions are linked symbolically into it. What is strange is that the OS reports the partition to be 10MB but the block occupies 16MB. Seems like 6MB wasted there.
- Now the most interesting: There is a 50MB (almost half the size of the flash drive) partition mounted as "storage" which is basically unused. The only thing I have seen there are the logs of past firmware upgrades. These logs are mostly useless except for maybe the very last one... I can't figure out what file system it uses and can't mount it anywhere else but you have a good 49MB wasted right there.
-The last partition of 19.25MB is also inaccessible and is designed by openWRT to have a backup for the firmware. Maybe the devs can tell whether it is being used but I suspect not knowing easily the vera gets bricked and relies on downloading the latest firmware from their servers for repair and recovery.

Now look closely at where all the problems lie: The rootfs data partition is only 8.61MB!!! It is the working partition of the vera which contains the plugins, configurations, user data, all the programs and libraries etc etc... basically the data which should take the most space. It is compressed as it is a squashfs file system and when uncompressed is ~10MB. There is a solution to all the "vera ran out of space" problems. I can offer to provide a script to move all your user files to the storage partition and symbolically link them if people are interested. What drives me nuts is that this tiny partition is intensively overwritten: every few seconds, the vera rotates the user-data.json files. Even though the space occupied are not especially large, The frequency at which it is overwritten causes a lot of wear to the NAND cells in this tiny partition causing it to decay and fail. The hardware it is built on was designed as an embedded device with very little writing and the firmware being essentially acting as a ROM or EEPROM. Luckily the logs are kept in the RAM but the device/plugin status updates are not. The wear leveling embedded in the file system cannot be very effective when the partition is this full. (I am semiconductor engineer in case one wonders).

mios developers, if you read this. Please give some thoughts... I believe you just took the vera edge firmware with some legacy designs which are no longer applicable, modified the LuaUPnP program to add zigbee and called it a day without thinking about using the extra storage space the device offers. I personally have already extrooted my device so I gain nothing from this as I have a solution but in your future firmware iterations, I hope for you to learn from these mistakes.
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 20, 2019, 03:06:17 am
No wonder you have hero status!

C
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 20, 2019, 12:14:01 pm
Nahh, It is just that I have been posting a lot the past few months after deciding to take upon myself to fix the vera.

The conclusion for mios is: The vera plus rootfs partiton could easily be 90 to 100MB and is inexplicably restricted to 8.6MB.
There are completely redundant and unused partitions in the layout and is causing a lot of grief from the last few firmware upgrades.
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 20, 2019, 12:27:28 pm
Nahh, It is just that I have been posting a lot the past few months after deciding to take upon myself to fix the vera.

The conclusion for mios is: The vera plus rootfs partiton could easily be 90 to 100MB and is inexplicably restricted to 8.6MB.
There are completely redundant and unused partitions in the layout and is causing a lot of grief from the last few firmware upgrades.

I wonder if it's causing grief all over!

C
Title: Re: VeraPlus Flash drive usage
Post by: zedrally on January 20, 2019, 05:34:11 pm
I got a spare Edge that I wouldn't mind trying this on....Bring it on.. :)
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 20, 2019, 09:02:52 pm
I bricked my edge sometime ago so I have no way to test on a vera edge.
If you don't mind, could you please send me the output of these two CLI commands:
Code: [Select]
df -h
and
Code: [Select]
dmesg
after a fresh boot/reboot? I will try to map out the flash memory and see how it looks like.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 21, 2019, 03:41:16 am
This is great work !
Hope you can do something about it.
Title: Re: VeraPlus Flash drive usage
Post by: Forzaalfa on January 21, 2019, 03:56:41 am
wow. That constant writing to a small and important partition almost seems like a "planned obsolescence" feature..  :o ;)

couldn't the partitions be resized? reducing one and adding to another? (admittedly, based on almost no knowledge of the FS here. ;) )

I'd love to try a script to fix this nonsense..
Title: Re: VeraPlus Flash drive usage
Post by: blacey on January 21, 2019, 10:38:39 am
I bricked my edge sometime ago so I have no way to test on a vera edge.
If you don't mind, could you please send me the output of these two CLI commands:
Code: [Select]
df -h
and
Code: [Select]
dmesg
after a fresh boot/reboot? I will try to map out the flash memory and see how it looks like.

I have an edge that I use for testing so here you go.

Code: [Select]
[blacey@bbl ~]$ ssh veraedge df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                    9728      4868      4860  50% /
/dev/root                 9472      9472         0 100% /rom
tmpfs                    63344       364     62980   1% /tmp
/dev/mtdblock6            9728      4868      4860  50% /overlay
overlayfs:/overlay        9728      4868      4860  50% /
tmpfs                      512         0       512   0% /dev
/dev/mtdblock10          66304      9564     56740  14% /storage
/dev/mtdblock10          66304      9564     56740  14% /etc/cmh-firmware
/dev/mtdblock10          66304      9564     56740  14% /etc/cmh-backup
/dev/mtdblock9            7936      7936         0 100% /mios

Code: [Select]
[blacey@bbl ~]$ ssh veraedge dmesg
[    0.000000] Linux version 3.10.34 (alecs@builder1204.mios.com) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r39638) ) #16 Tue Jun 23 05:10:41 PDT 2015
[    0.000000] Board has DDR2
[    0.000000] Analog PMU set to hw control
[    0.000000] Digital PMU set to hw control
[    0.000000] SoC Type: Ralink MT7620A ver:2 eco:6
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU revision is: 00019650 (MIPS 24KEc)
[    0.000000] MIPS: machine is Sercomm NA301
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x07ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x07ffffff]
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat 802d6990, node_mem_map 81006480
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32768 pages, LIFO batch:7
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS1,57600 rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=00066820
[    0.000000] Readback ErrCtl register=00066820
[    0.000000] Memory: 126484k/131072k available (2396k kernel code, 4588k reserved, 597k data, 204k init, 0k highmem)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:256
[    0.000000] CPU Clock: 580MHz
[    0.050000] Calibrating delay loop... 385.84 BogoMIPS (lpj=1929216)
[    0.060000] pid_max: default: 32768 minimum: 301
[    0.060000] Mount-cache hash table entries: 512
[    0.070000] pinctrl core: initialized pinctrl subsystem
[    0.080000] NET: Registered protocol family 16
[    0.090000] rt2880-pinmux pinctrl.1: try to register 73 pins ...
[    0.090000] pinctrl core: registered pin 0 (io0) on rt2880-pinmux

... reduced noise ... to satisfy 2K character limit.

[    0.090000] pinctrl core: registered pin 72 (io72) on rt2880-pinmux
[    0.090000] pinctrl core: add 5 pinmux maps
[    0.090000] rt2880-pinmux pinctrl.1: found group selector 0 for i2c
[    0.090000] rt2880-pinmux pinctrl.1: found group selector 10 for rgmii2
[    0.090000] rt2880-pinmux pinctrl.1: found group selector 2 for spi
[    0.090000] rt2880-pinmux pinctrl.1: found group selector 12 for ephy
[    0.090000] rt2880-pinmux pinctrl.1: found group selector 1 for uartf
[    0.090000] rt2880-pinmux pinctrl.1: request pin 1 (io1) for pinctrl.1
[    0.090000] rt2880-pinmux pinctrl.1: request pin 2 (io2) for pinctrl.1
[    0.090000] rt2880-pinmux pinctrl.1: request pin 60 (io60) for pinctrl.1

... reduced noise ... to satisfy 2K character limit.

[    0.090000] rt2880-pinmux pinctrl.1: request pin 14 (io14) for pinctrl.1
[    0.090000] rt2880-pinmux pinctrl.1: failed to lookup the sleep state
[    0.100000] bio: create slab <bio-0> at 0
[    0.110000] rt2880_gpio 10000600.gpio: registering 24 gpios
[    0.120000] rt2880_gpio 10000600.gpio: registering 24 irq handlers
[    0.130000] rt2880_gpio 10000638.gpio: registering 16 gpios
[    0.140000] rt2880_gpio 10000638.gpio: registering 16 irq handlers
[    0.150000] rt2880_gpio 10000660.gpio: registering 32 gpios
[    0.160000] rt2880_gpio 10000660.gpio: registering 32 irq handlers
[    0.170000] Switching to clocksource MIPS
[    0.180000] NET: Registered protocol family 2
[    0.190000] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[    0.200000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.210000] TCP: Hash tables configured (established 1024 bind 1024)
[    0.230000] TCP: reno registered
[    0.230000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.240000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.260000] NET: Registered protocol family 1
[    0.270000] PCI: CLS 0 bytes, default 32
[    0.270000] rt-timer 10000100.timer: maximum frequncy is 2441Hz
[    0.280000] alarmtimer alarmtimer: no of_node; not parsing pinctrl DT
[    0.290000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.310000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.330000] msgmni has been set to 247
[    0.330000] io scheduler noop registered
[    0.340000] io scheduler deadline registered (default)
[    0.350000] gpio-export gpio_export.7: 0 gpio(s) exported
[    0.360000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.380000] serial8250 serial8250: no of_node; not parsing pinctrl DT
[    0.380000] 10000500.uart: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
[    0.390000] pinctrl core: add 1 pinmux maps
[    0.390000] rt2880-pinmux pinctrl.1: found group selector 3 for uartlite
[    0.390000] rt2880-pinmux pinctrl.1: request pin 15 (io15) for 10000c00.uartlite
[    0.390000] rt2880-pinmux pinctrl.1: request pin 16 (io16) for 10000c00.uartlite
[    0.390000] 10000c00.uartlite: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
[    0.410000] console [ttyS1] enabled, bootconsole disabled
[    0.430000] !!! nand page size = 2048, addr len=4
[    0.440000] mtk_nand_probe: alloc 1368, at 8789a000 , btt(8789b0c0, 100), ranfc_mtd:8789b1c0
[    0.460000] 9 ofpart partitions found on MTD device ra_nfc
[    0.470000] Creating 9 MTD partitions on "ra_nfc":
[    0.480000] 0x000000000000-0x000000020000 : "u-boot"
[    0.490000] 0x000000200000-0x000000240000 : "factory"
[    0.500000] 0x000000208000-0x00000021ffba : "config_default"
[    0.510000] 0x000000240000-0x000000640000 : "Config"
[    0.530000] 0x000000640000-0x000001a40000 : "firmware"
[    0.540000] 0x000000780000-0x000001a40000 : "rootfs"
[    0.550000] mtd: device 5 (rootfs) set to be root filesystem
[    0.570000] mtd: partition "rootfs_data" created automatically, ofs=0x10c0000, len=0x980000
[    0.580000] 0x0000010c0000-0x000001a40000 : "rootfs_data"
[    0.590000] 0x000001a40000-0x000002e40000 : "firmware2"
[    0.610000] 0x000002e40000-0x000002f40000 : "user_storage"
[    0.620000] 0x000002f40000-0x000003f40000 : "mios"
[    0.640000] 0x000003f40000-0x000008000000 : "storage"
[    0.670000] pinctrl core: add 1 pinmux maps
[    0.670000] pinctrl core: add 1 pinmux maps
[    0.670000] rt2880-pinmux pinctrl.1: found group selector 6 for rgmii1
[    0.670000] rt2880-pinmux pinctrl.1: found group selector 5 for mdio
[    0.670000] rt2880-pinmux pinctrl.1: request pin 24 (io24) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 25 (io25) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 26 (io26) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 27 (io27) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 28 (io28) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 29 (io29) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 30 (io30) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 31 (io31) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 32 (io32) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 33 (io33) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 34 (io34) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 35 (io35) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 22 (io22) for 10100000.ethernet
[    0.670000] rt2880-pinmux pinctrl.1: request pin 23 (io23) for 10100000.ethernet
[    0.670000] ralink_soc_eth 10100000.ethernet: Enabling TSO
[    0.680000] (unregistered net_device): port 0 link up (100Mbps/Full duplex)
[    0.690000] libphy: mdio: probed
[    0.700000] ralink_soc_eth 10100000.ethernet: connected port 4 to PHY at mdio-bus:04 [uid=03a2940d, driver=Generic PHY]
[    0.720000] ralink_soc_eth 10100000.ethernet: connected port 5 to PHY at mdio-bus:05 [uid=00000000, driver=Generic PHY]
[    0.740000] ralink_soc_eth 10100000.ethernet: loaded mt7530 driver
[    0.760000] eth0: done loading
[    0.760000] rt3xxx-usbphy ubsphy.3: loaded
[    0.770000] rt2880_wdt 10000120.watchdog: Initialized
[    0.780000] TCP: cubic registered
[    0.790000] NET: Registered protocol family 17
[    0.800000] 8021q: 802.1Q VLAN Support v1.8
[    0.920000] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[    0.940000] Freeing unused kernel memory: 204K (802ed000 - 80320000)
[    3.730000] usbcore: registered new interface driver usbfs
[    3.740000] usbcore: registered new interface driver hub
[    3.750000] usbcore: registered new device driver usb
[    3.810000] JFS: nTxBlock = 989, nTxLock = 7918
[    3.920000] SGI XFS with security attributes, large block/inode numbers, no debug enabled
[    3.950000] rt2880-pinmux pinctrl.1: request pin 11 (io11) for pio:11
[    3.950000] rt2880-pinmux pinctrl.1: request pin 12 (io12) for pio:12
[    3.950000] rt2880-pinmux pinctrl.1: request pin 14 (io14) for pio:14
[    3.960000] SCSI subsystem initialized
[    3.970000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.980000] ehci-platform: EHCI generic platform driver
[    4.190000] rt3xxx-usbphy ubsphy.3: remote usb device wakeup disabled
[    4.210000] rt3xxx-usbphy ubsphy.3: UTMI 16bit 30MHz
[    4.220000] ehci-platform 101c0000.ehci: EHCI Host Controller
[    4.230000] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus number 1
[    4.240000] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
[    4.280000] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
[    4.290000] usb usb1: no of_node; not parsing pinctrl DT
[    4.290000] hub 1-0:1.0: no of_node; not parsing pinctrl DT
[    4.290000] hub 1-0:1.0: USB hub found
[    4.300000] hub 1-0:1.0: 1 port detected
[    4.310000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.320000] ohci-platform 101c1000.ohci: Generic Platform OHCI Controller
[    4.330000] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
[    4.350000] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
[    4.420000] usb usb2: no of_node; not parsing pinctrl DT
[    4.420000] hub 2-0:1.0: no of_node; not parsing pinctrl DT
[    4.420000] hub 2-0:1.0: USB hub found
[    4.430000] hub 2-0:1.0: 1 port detected
[    4.440000] leds-gpio gpio-leds.6: pins are not configured from the driver
[    4.460000] rt2880-pinmux pinctrl.1: request pin 67 (io67) for pio:67
[    4.460000] rt2880-pinmux pinctrl.1: request pin 40 (io40) for pio:40
[    4.460000] rt2880-pinmux pinctrl.1: request pin 68 (io68) for pio:68
[    4.460000] rt2880-pinmux pinctrl.1: request pin 69 (io69) for pio:69
[    4.460000] usbcore: registered new interface driver usb-storage
[    4.620000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[    4.780000] usb 1-1: no of_node; not parsing pinctrl DT
[    4.780000] usb-storage 1-1:1.0: no of_node; not parsing pinctrl DT
[    4.780000] usb-storage 1-1:1.0: USB Mass Storage device detected
[    4.790000] scsi0 : usb-storage 1-1:1.0
[    5.850000] scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer Fit       1.27 PQ: 0 ANSI: 6
[    5.870000] sd 0:0:0:0: no of_node; not parsing pinctrl DT
[    5.870000] sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[    5.880000] sd 0:0:0:0: [sda] Write Protect is off
[    5.890000] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[    5.900000] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    5.930000]  sda: sda1 sda2
[    5.950000] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    6.250000] jffs2: notice: (383) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 32 of xref (0 dead, 23 orphan) found.
[   14.970000] loop: module loaded
[   15.200000] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   15.240000] u32 classifier
[   15.250000]     input device check on
[   15.260000]     Actions configured
[   15.280000] Mirror/redirect action on
[   15.300000] fuse init (API version 7.22)
[   15.330000] usbcore: registered new interface driver cdc_acm
[   15.340000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[   15.370000] Loading modules backported from Linux version master-2014-01-23-0-g62c147d
[   15.380000] Backport generated by backports.git backports-20140124-0-g1256d3e
[   15.430000] nf_conntrack version 0.5.0 (1979 buckets, 7916 max)
[   15.620000] Netfilter messages via NETLINK v0.30.
[   15.640000] usbcore: registered new interface driver ums-alauda
[   15.660000] usbcore: registered new interface driver ums-cypress
[   15.680000] usbcore: registered new interface driver ums-datafab
[   15.690000] usbcore: registered new interface driver ums-freecom
[   15.700000] usbcore: registered new interface driver ums-isd200
[   15.720000] usbcore: registered new interface driver ums-jumpshot
[   15.730000] usbcore: registered new interface driver ums-karma
[   15.760000] usbcore: registered new interface driver ums-sddr09
[   15.770000] usbcore: registered new interface driver ums-sddr55
[   15.780000] usbcore: registered new interface driver ums-usbat
[   15.800000] usbcore: registered new interface driver usbserial
[   15.810000] usbcore: registered new interface driver usbserial_generic
[   15.830000] usbserial: USB Serial support registered for generic
[   15.890000] xt_time: kernel timezone is -0000
[   15.900000] usbcore: registered new interface driver belkin_sa
[   15.910000] usbserial: USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
[   15.960000] cfg80211: Calling CRDA to update world regulatory domain
[   15.970000] usbcore: registered new interface driver cp210x
[   15.990000] cfg80211: World regulatory domain updated:
[   16.000000] cfg80211:  DFS Master region: unset
[   16.000000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   16.020000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   16.040000] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   16.050000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   16.070000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[   16.080000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[   16.100000] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
[   16.120000] usbserial: USB Serial support registered for cp210x
[   16.140000] usbcore: registered new interface driver ftdi_sio
[   16.160000] usbserial: USB Serial support registered for FTDI USB Serial Device
[   16.180000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   16.200000] usbcore: registered new interface driver keyspan
[   16.220000] usbserial: USB Serial support registered for Keyspan - (without firmware)
[   16.230000] usbserial: USB Serial support registered for Keyspan 1 port adapter
[   16.250000] usbserial: USB Serial support registered for Keyspan 2 port adapter
[   16.260000] usbserial: USB Serial support registered for Keyspan 4 port adapter
[   16.310000] usbcore: registered new interface driver mct_u232
[   16.320000] usbserial: USB Serial support registered for MCT U232
[   16.340000] ctnetlink v0.93: registering with nfnetlink.
[   16.360000] usbcore: registered new interface driver pl2303
[   16.370000] usbserial: USB Serial support registered for pl2303
[   16.380000] PPP generic driver version 2.4.2
[   16.390000] NET: Registered protocol family 24
[   16.420000] usbcore: registered new interface driver sierra
[   16.430000] usbserial: USB Serial support registered for Sierra USB modem
[   16.450000] usbcore: registered new interface driver option
[   16.460000] usbserial: USB Serial support registered for GSM modem (1-port)
[   19.160000] jffs2: notice: (1495) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   23.230000] device eth0.1 entered promiscuous mode
[   23.240000] device eth0 entered promiscuous mode
[   23.260000] br-lan: port 1(eth0.1) entered forwarding state
[   23.270000] br-lan: port 1(eth0.1) entered forwarding state
[   25.270000] br-lan: port 1(eth0.1) entered forwarding state
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 21, 2019, 01:12:31 pm
Thank you blacey.
See the layout of the Edge in the attached screenshot.
It is much better than the one for the vera plus.
- First there is one less wasted partition: backup.
- The rootfs data is also a little bigger. 9.5MB instead of the odd 8.6MB.
- The plus maintained the same firmware block size as the edge but accommodates a little larger kernel which apparently caused the engineers to have to resize the rootfs data and screwed it up
- The storage partition is 64.75MB vs 50MB on the plus.
- Notice also how much bigger the config partition is on the edge (4MB) when the plus only has 512kB. Same comment for the factory ones. I suspect these are imposed by the custom bootloader provided by Sercomm.

That being said, it is still over half of your drive space which is essentially unused by vera and they run out of space trying to cram all of their data into the 9.5MB partition.
I will provide the script shortly
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 21, 2019, 01:53:33 pm
Here is the script. It will work on the vera edge/plus/secure.
Load it on your vera and run ./savespace.sh
There is no need to reboot the vera.

Also added the script to revert the changes

Edit: Please use the newest version of the script in post #44
Title: Re: VeraPlus Flash drive usage
Post by: Talisker on January 21, 2019, 02:34:56 pm
Hi rafale77.  Could you please explain what the savepace.sh file does when run?  My limited understanding is that it moves the partition to provide more space for vera configuration.  Also if you could give a little more info. about where to load the file and where to run the ./savespace.sh command I would appreciate it. 
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 21, 2019, 03:12:11 pm
Hi rafale77.  Could you please explain what the savepace.sh file does when run?  My limited understanding is that it moves the partition to provide more space for vera configuration.  Also if you could give a little more info. about where to load the file and where to run the ./savespace.sh command I would appreciate it. 

It moves a bunch of user files which get overwritten frequently or occupy space into the storage partition and creates a symbolic link to it from their original location. It makes it transparent to the vera.
You can load the script on your vera in many ways. You can load it on a USB stick and stick it into the vera and mount the USB drive, You can SCP the file onto it. Are you familiar with SSH? If prefer not to do this from the UI because I kill the luup engine and restart it in the process.
It can run from anywhere on the vera, the location of the file doesn't matter.

Essentially all of your plugins will be moved to the storage partition and it should free up the working partition of the vera. You should have also significantly more space now for your plugins.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 22, 2019, 08:41:08 am
As far as I remember the vera will delete a USB and use it for logging if you mount it. ! ?
Do you write the command (./savespace.sh) in "test luop". ?
Can you dismount the usb aftewards or does vera use it ?
The "revert" file is that for going back to normal use ?

A lot of stupid Q's, sorry...better safe than sorry.
Regards !
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 22, 2019, 09:20:43 am
I suspect it will only erase it if you tell it to use if for logs....

Rafael's script is elegantly simple:
Installs a couple of packages
Formats the SD disc
Mounts it
Creates the directory structure
Does some funky tar work to move the file structure, then alters the file system table to mount the new structure on boot

I'd be pretty happy that powering off, unplugging the drive and rebooting will put you right back to where you were before you started.

C
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 22, 2019, 09:24:16 am
Of course that was the exroot file! Doh!
The save space stops the engine
Makes a new folder out of cmh
Moves some files from cmh to the new folder
Symlinks the new location to the old
Restarts the engine
It uses absolute paths so could be run (as far as I can tell) from anywhere.

Revert does pretty much the exact reverse

C
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 22, 2019, 09:44:35 am
Thanks Catman
I know little of scp and ssh.
That is why I asked about installing from a usb especially.
In pracis.
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 22, 2019, 12:33:01 pm
Thank you for the enthusiastic responses Catman!

Yes his responses are correct. The script is pretty simple and just moves files and links around and the revert does the opposite.

The vera mounts the USB log partition on its own. It doesn't erases it unless you do it from the UI by unchecking and rechecking the USB log function.
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 22, 2019, 12:37:24 pm
No problem.  Firm believer that it's not really reasonable to complain if I'm not going to engage with potential solutions :)

C
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 22, 2019, 04:38:43 pm
Was just reading this thread:

http://forum.micasaverde.com/index.php?topic=62422.0

and I am a bit flabbergasted that the vera plus and the vera edge both have a second firmware partition and yet it appears that it is either completely unused and wasted space or that we have no way to switch to it as even support seems to say that when the first partition is corrupted, the vera is toast. Maybe Sorin or someone from support could give us some insight as to why we have so many backup firmware partitions (seems like 2 for the vera plus) and how can we switch to booting from it. I actually think that it is a great feature to have a failsafe firmware partition from which you can copy everything over or you can switch to when there is a problem. It is pretty common in embedded devices to prevent bricking but not sure how the MTK based veras are handling it.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 23, 2019, 04:30:49 am
Rafale, catman
You are both most helpful !

I DO understand what the files are doing.
I an just TOO STUPID to DO it.

1. I put in the usb.
2. I write "./savespace.sh" in "test luop"
3. How do I check it is done ?

Sorry !
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 23, 2019, 04:45:24 am
Rafale, catman
You are both most helpful !

I DO understand what the files are doing.
I an just TOO STUPID to DO it.

1. I put in the usb.
2. I write "./savespace.sh" in "test luop"
3. How do I check it is done ?

Sorry !

Not stupid, I suspect, probably more 'un-skilled' or 'in-experienced' :)

I don't think that it will work from the Test Lua (see I'm hardly an expert) Rafael can surely explain if I'm wrong or how he expects this to be done.
Do you know how to SSH into your Vera? That is how *I* would do it, but that's because it's what I'm used to.  I can give you step by step instructions but would need to ask a load of questions and probably get some pre work sorted for you.

*Probably* best to wait for Rafael to respond and we can go from there.

C
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 23, 2019, 05:00:11 am
No. I dont know how to use ssh or scp as erlyer mentioned.
(Apart from vera support help some years ago.)
And with vera3 I ruined 2 or 3 usb sticks using "datamine".
So I would very much like some step by step "how to".
Thanks for understanding.

I am on a vera plus now,
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 23, 2019, 05:52:31 am
No. I dont know how to use ssh or scp as erlyer mentioned.
(Apart from vera support help some years ago.)
And with vera3 I ruined 2 or 3 usb sticks using "datamine".
So I would very much like some step by step "how to".
Thanks for understanding.

I am on a vera plus now,

I'm going to see if Rafael can explain a simpler way that I will, but if not will help.

C
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 23, 2019, 06:15:08 am
Thanks a lot.
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 23, 2019, 10:48:42 am
Hi svaleb,

see this for ssh
http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
likewise for scp you can use wincp for windows
https://winscp.net/eng/index.php
or Rbrowser for mac
http://www.rbrowser.com

This is how you get access to the vera to run commands. Alternatively you can always dump the file through the app/develop app/luup files page and then an Os command in lua code but you won't see what is happening and whether it succeeds of fail so I would not recommend doing it that way;
Title: Re: VeraPlus Flash drive usage
Post by: wilme2 on January 23, 2019, 10:51:44 am
Here is the script. It will work on the vera edge/plus/secure.
Load it on your vera and run ./savespace.sh
There is no need to reboot the vera.

Also added the script to revert the changes

I am very interested.  I will copy the scripts to my VeraSecure - but I think I want want to hear some success stories before I execute.
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 23, 2019, 12:46:34 pm
Hi svaleb,

see this for ssh
http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
likewise for scp you can use wincp for windows
https://winscp.net/eng/index.php
or Rbrowser for mac
http://www.rbrowser.com

This is how you get access to the vera to run commands. Alternatively you can always dump the file through the app/develop app/luup files page and then an Os command in lua code but you won't see what is happening and whether it succeeds of fail so I would not recommend doing it that way;

Pretty much what I thought.  If you need more help I can tag team :)

C
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 23, 2019, 07:48:54 pm
Hi svaleb,

see this for ssh
http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
likewise for scp you can use wincp for windows
https://winscp.net/eng/index.php
or Rbrowser for mac
http://www.rbrowser.com

This is how you get access to the vera to run commands. Alternatively you can always dump the file through the app/develop app/luup files page and then an Os command in lua code but you won't see what is happening and whether it succeeds of fail so I would not recommend doing it that way;

Pretty much what I thought.  If you need more help I can tag team :)

C

Your help is very much appreciated. Love the enthusiasm!  :D
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 24, 2019, 07:03:45 am
I have os-command in ALTUI.
So maybe I just need the right commands after setting the usb into vera ! (?)
This is what I have now:

Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      7.8M    824.0K  91% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M      6.0M    118.8M   5% /tmp
/dev/mtdblock7            8.6M      7.8M    824.0K  91% /overlay
overlayfs:/overlay        8.6M      7.8M    824.0K  91% /
tmpfs                   512.0K         0    512.0K   0% /dev
/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
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 24, 2019, 10:56:58 am
I have os-command in ALTUI.
So maybe I just need the right commands after setting the usb into vera ! (?)
This is what I have now:

Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      7.8M    824.0K  91% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M      6.0M    118.8M   5% /tmp
/dev/mtdblock7            8.6M      7.8M    824.0K  91% /overlay
overlayfs:/overlay        8.6M      7.8M    824.0K  91% /
tmpfs                   512.0K         0    512.0K   0% /dev
/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

How big is your USB stick?

C
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 24, 2019, 12:28:02 pm
@svaleb: Your overlay is 91%... It is close to disaster. Also your USB logging is not enabled.
You may not need a USB drive though it would help to first move your logging there.
I would recommend to first insert a USB stick on the vera and enable USB logging in the vera's settings/log page.

I just realized the OS command is likely not going to work since the vera wants to compress it when you use the build-in upload mechanism. Sorry, you will need to learn to SSH to get into the vera.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 24, 2019, 01:59:36 pm
Hmm, serious.
I used usb logging on my vera 3 some years ago, never thought it would be necessary on the plus as I dont use datamine.
Thought the plus was big enough for the few things I have.
I wil try to mount a usb for logging and get back to you.

Thanks both of you.
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 24, 2019, 02:29:24 pm
It is kind of the point of my post to begin with and the mod I am proposing: The vera plus is not making use of the extra storage space offered by the hardware. It is strangely restrincting itself to use 8.6MB of what could be 90MB
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 24, 2019, 03:27:03 pm
Yes I am aware of it. (that is why I am interested), but I was not aware I was in the "danger zone".
I have downloaded SCP but it is outside of my terminologi, I dont understand a word.

You mentioned the files could be coppyed into luop files and given a run command, Is this a possibillity ?

IF I knew the Command.

Edit
Just noticed that support, at some point, has checked all these :
Show polling activity
Show individual jobs
Verbose logging
Lock Log Levels (not recommended)
Archive old logs on MiOS (recommended)

Will uncheck verbose and log levels, would it help ?
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 24, 2019, 04:00:29 pm
probably will for the logs.
copying the script into the luup files will not work because moving files this way into the vera will compress them into an lzo format and prevent it from executing.

As for SCP and SSH, maybe let me get you some basics.

Just like many "embedded" devices ranging from your car ECU, to your router, wifi AP, network switch etc, the vera hub is technically a computer. Unlike your PC, it is not designed to interact with the users directly through a screen and keyboard (and mouse). It is designed to be headless, ie boot, load it's operating system and run its code on its own. It is technically not really designed for the user to change anything on it. In order to be programmed though they usually have an access open to the outside world so you can actually talk to it through an interface. For the vera, this interface and protocol is the secure shell aka SSH and it communicates through the TCP/IP ethernet port. Other devices use different interfaces and protocols.
The SSH interface on the vera is run by a program called dropbear which basically opens that communication port and acts as a server.
SSH will allow you to log in to the vera and access its operating system through its CLI (command line interface) which is a program called busybox.
Both of these programs are very common and standard for the operating system called OpenWRT which is a linux distribution originally designed for home wireless routers and open sourced.
Dropbear just happens to also support SCP which is a file transfer protocol allowing us to move files from one computer to another through the ethernet port.

Now with this in mind, the SCP client program (the one you installed on your mac or pc) asks you what host you want to connect to: That will be your vera IP address. You will need the login: it will be "root", and password: It is printed on the label at the bottom of your vera. You may need to make sure that the protocol used is correct: SCP. Once logged in, you can move the files you want into any place on the vera.
With these, you should be able to login to your unit using the SCP protocol but you cannot execute programs on the vera with SCP. For this you will need to access the CLI which will require SSH.

The login name and password are the same as above. You can then go to the folder where you copied the file in question and execute it. The screen will look exactly as if you had a monitor and a keyboard hooked to the vera as a computer. The commands are all standard linux commands. Hope that at least this takes you one step further.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 24, 2019, 04:42:07 pm
Again, Thanks a lot !
I will try.
Maybe I will contact Catman If I get stuck.
Regards
Title: Re: VeraPlus Flash drive usage
Post by: zedrally on January 24, 2019, 06:45:42 pm
^^^ That login gets me every time. As I infrequently SSH into anything I made it a habit of labelling the login used on the back of the unit. Granted, it's easy if you are forever logging into Vera, but if you only do it every few months you tend to get a Seniors moment....
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 25, 2019, 05:16:13 am
Again, Thanks a lot !
I will try.
Maybe I will contact Catman If I get stuck.
Regards

Feel free

C
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 25, 2019, 07:20:21 am
Rafale you brought me some great steps further
@Catman
I DID come a little further.
With SCP I put the file in "lib" I have had acces with PUTTY...
From there what next ?
I do not know the commands to find and execute the file.

Edit
I am able to reach it in ALTUI OScommand, it must be possible to execute it from there.
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 25, 2019, 11:22:27 am
Code: [Select]
cd /lib
cd is for "change directory" should get you to the lib folder.
Then run ./savespace.sh
You can verify the content of the folder by entering
Code: [Select]
ls
Make sure to not run the savespace.sh script twice.
Title: Re: VeraPlus Flash drive usage
Post by: Forzaalfa on January 25, 2019, 11:34:40 am
I just uploaded to /etc/ using winscp, then used ssh(putty), and "root"/pw.

went to the /etc/ and typed ./savespace.sh

reply: "Permission Denied".

what now?

Code: [Select]
root@MiOS_50103006:/etc# ls
TZ                     functions_firmware.sh  opkg.conf
TZ-full                functions_leds.sh      passwd
alerts                 functions_usbdrive.sh  ppp
banner                 gcom                   preinit
bluetooth              group                  profile
chatscripts            host_ip                protocols
cmd                    hosts                  rc.button
cmh                    hotplug-preinit.json   rc.common
cmh-backup             hotplug.d              rc.d
cmh-firmware           hotplug.json           rc.local
cmh-lu                 init.d                 resolv.conf
cmh-ludl               inittab                revertspace.sh
cmh-ra                 iproute2               savespace.sh
cmh-static             ld.so.cache            ser2net.conf
cmh-zbfw               ld.so.conf             services
cmh-zwfw               lighttpd               shadow
cmh.factory.default    lighttpd.conf          shells
config                 lighttpd.users         ssl
crontabs               logrotate.conf         sysctl.conf
dbus-1                 logrotate.d            sysupgrade.conf
device_info            mios                   uci-defaults
diag.sh                mios_backup.info       udhcpc.user
dnsmasq.conf           mios_backup.info.old   ule
dropbear               modules-boot.d         usb-mode.json
e2fsck.conf            modules.d              wireless
ethers                 mtab                   zwave
firewall.user          openwrt_build          zwave-aes
fstab                  openwrt_release
functions_3g.sh        openwrt_version
root@MiOS_50103006:/etc# ./savespace.sh
-ash: ./savespace.sh: Permission denied
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 25, 2019, 11:38:55 am
ohh the executionability did not move with the file.

Before executing the file, you need to make it executable:

Code: [Select]
chmod +x savespace.sh
Title: Re: VeraPlus Flash drive usage
Post by: Forzaalfa on January 25, 2019, 01:42:53 pm
Thats better! :D

Code: [Select]
root@MiOS_50103006:/lib# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      6.9M      1.8M  80% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M      2.1M    122.6M   2% /tmp
/dev/mtdblock7            8.6M      6.9M      1.8M  80% /overlay
overlayfs:/overlay        8.6M      6.9M      1.8M  80% /
tmpfs                   512.0K         0    512.0K   0% /dev
/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
root@MiOS_50103006:/lib# ./savespace.sh
stopping luup engine
OKmoving cmh files to /storage
create symlinks
starting luup engine
root@MiOS_50103006:/lib# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      2.8M      5.8M  32% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M      2.5M    122.2M   2% /tmp
/dev/mtdblock7            8.6M      2.8M      5.8M  32% /overlay
overlayfs:/overlay        8.6M      2.8M      5.8M  32% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock10          50.0M      5.5M     44.5M  11% /storage
/dev/mtdblock10          50.0M      5.5M     44.5M  11% /etc/cmh-firmware
/dev/mtdblock10          50.0M      5.5M     44.5M  11% /etc/cmh-backup
/dev/mtdblock9           10.0M     10.0M         0 100% /mios
root@MiOS_50103006:/lib#

Thanks, Rafale! I presume all new installs go to the new location? :)
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 25, 2019, 01:44:02 pm
Yes it will!

By the way, a firmware upgrade will normally revert this script. You can reapply it and then recover from backup to get all your plugins back.

Note: Do not attempt to revert if you already have more data than the original partitition can hold: You should be able to see if from the free space available on /dev/mtdblock7 Vs what you have used in /dev/mtdblock10 minus 1.5M. Given the fact that I doubt there will be any new firmware for our unit for some time, I am not too worried about anyone having to revert but if there is, I will figure out something to help with the migration.
PS: I had a sudden paranoid epiphany and decided to add a few things to the scripts to prevent people from running it twice and risk disabling the vera. Please use the latest version attached. You do not need to do anything if you already applied it. Just use this instead moving forward.
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 25, 2019, 10:01:45 pm
Out of curiosity, I downloaded a couple of firmware upgrade files from mios and mounted them to see what is in there. Turns out they only contain an image of the rootfs-data partition which is ~10MB so I don't believe mios/vera repartitions the drive or upgrade the kernel or boot loader on our units. It doesn't seem to be capable of doing it. It limits what vera can do in the upgrades to just changing the zwave/zigbee firmware and the LuaUPnP program and the cmh proprietary code.
Also been trying to switch from one firmware image to the other or maybe to the backup and have not been successful, having tried various combinations of buttons during the boot up. I suspect the second firmware partition and the backup partition are just empty. Sorin? Cristina? any input? This seems to be, I am sorry to say, a very poorly thought through flash memory arrangement. I am really puzzled... Why give us a 128MB flash chip to use only about 30MB of it?
Title: Re: VeraPlus Flash drive usage
Post by: Buxton on January 25, 2019, 10:09:50 pm
Quote
Why give us a 128MB flash chip to use only about 30MB of it

Indeed.  I'd love to be able to safely re-size my partitions on my veralite, as hitting the limit of the rootfs-data partition seems to be the most common way people brick their machines.  I won't even get near an upgrade anymore for fear of bringing down the whole box.  Failing a repartition, offloading to an SSD is a possibility if anyone can get that to work with veralites.....  That would future proof the radio to some degree.
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 25, 2019, 10:22:43 pm
Quote
Why give us a 128MB flash chip to use only about 30MB of it

Indeed.  I'd love to be able to safely re-size my partitions on my veralite, as hitting the limit of the rootfs-data partition seems to be the most common way people brick their machines.  I won't even get near an upgrade anymore for fear of bringing down the whole box.  Failing a repartition, offloading to an SSD is a possibility if anyone can get that to work with veralites.....  That would future proof the radio to some degree.


I have an old veralite, maybe when I have time, I may try to extroot it... DId you try the script I posted on the extrooted thread? I updated it recently to force the mounting of the USB drive earlier.
Title: Re: VeraPlus Flash drive usage
Post by: Buxton on January 26, 2019, 05:44:42 pm
No I didn't try it per this message http://forum.micasaverde.com/index.php/topic,103140.msg414660.html#msg414660 .  "because Vera has removed all of the sources other than their own from /etc/opkg.conf."
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 26, 2019, 05:56:57 pm
My script overcomes this.... the comment is unrelated to the script provided. My script does not use Vera's sources.

I never actually paid attention to this comment from Rigpapa, not sure how I missed this and should have responded with a clarification. Thank you.
His comment is incorrect in the sense that vera never removed any source repository. What they did was to remove the standard packages from their own repository and only left the vera specific ones. My script changes the source altogether.
Title: Re: VeraPlus Flash drive usage
Post by: Buxton on January 26, 2019, 06:52:52 pm
OK.  I have a backup vera that I can test on.  I need to get an SSD and cable and then should be good to go.  If you do a similar test, I'd be interested in your results as you have some fundamental insights into the vera platform.  Thx
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 26, 2019, 07:05:59 pm
My production vera has been running on an external SSD for several months now. I have "fine-tuned" the script over time on a backup unit... There has been a lot of SSDs on sale lately. Prices are dropping. Extrooting has even been my safety net for a lot of my tests when I developed the mods to upgrade the vera packages and make mios server independent. I bricked the vera several times and the recovery was  just to unplug the SSD, boot the vera on the original partition, plug the SSD back and run the extroot script again. I still highly recommend extrooting whenever possible rather than this patch I posted on this thread.

I may need to create a vera light version of it though since the version of the repo may not work.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 28, 2019, 04:53:49 am
Code: [Select]
cd /lib
cd is for "change directory" should get you to the lib folder.
Then run ./savespace.sh
You can verify the content of the folder by entering
Code: [Select]
ls
Make sure to not run the savespace.sh script twice.

Yes, I just dont know how to "run" it...the command string to run.
Something "chmod?." ??

Should I change to the new files before I try again?
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 28, 2019, 12:10:12 pm
Code: [Select]
cd /lib
cd is for "change directory" should get you to the lib folder.
Then run ./savespace.sh
You can verify the content of the folder by entering
Code: [Select]
ls
Make sure to not run the savespace.sh script twice.

Yes, I just dont know how to "run" it...the command string to run.
Something "chmod?." ??

Should I change to the new files before I try again?

1. Yes, please use the new file. It is a much safer and will prevent you from making mistakes.
2. You need to SSH into the box. If you use windows, try using a program called putty (https://www.putty.org), login to the vera using the same credentials as before and navigate to the file you just uploaded using winscp. Actually winscp normally allows you to login with putty as well.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 30, 2019, 07:02:44 am
Succes (I hope)
This is what I got now :
Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      2.6M      6.1M  30% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M      3.6M    121.2M   3% /tmp
/dev/mtdblock7            8.6M      2.6M      6.1M  30% /overlay
overlayfs:/overlay        8.6M      2.6M      6.1M  30% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock10          50.0M      6.7M     43.3M  13% /storage
/dev/mtdblock10          50.0M      6.7M     43.3M  13% /etc/cmh-firmware
/dev/mtdblock10          50.0M      6.7M     43.3M  13% /etc/cmh-backup
/dev/mtdblock9           10.0M     10.0M         0 100% /mios

I said something like : "could not remow storidge/etc no such directory".

What does that mean ?

Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 30, 2019, 08:17:23 am
It is normal. It was an extra step to remove a folder in case it already existed.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 30, 2019, 08:37:16 am
Thanks !
I can see it made a lot of difference.
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 31, 2019, 05:18:30 am
Rafale I think this is great work !
A lot of others would need this to avoid problems.
I had no knowledge of how to do it.
You and Catman brought me through. Thanks !
In this tread it is, almost, there "how to".
I will try to collect it here so people as "stupid" as me can find most of it in one place.
Please correct me if I make errors in this.

"How to"

Useful links.

see this for ssh
http://wiki.micasaverde.com/index.php/Logon_Vera_SSH
likewise for scp you can use wincp for windows
https://winscp.net/eng/index.php
or Rbrowser for mac
http://www.rbrowser.com

https://ubuntudanmark.dk/filer/fwunixref.pdf

Download WINSCP
Hostname is your Vera IP
Port 22
Username: root
Password : the one on the bottom of your Vera
File protocol : SCP
Then login
Find your file and drag it into a directory ( in my case I chose "lib")
You find the Vera files on the right side by double clicking on the broken arrow at the top of the files.
Close

Next

Go to WINSCP
This time you chose PUTTY (in the bottom by the arrow at "login").
You start with your password and "enter"
You write : cd /XXX (instead of XXX you write the library where you have your file. In my case "cd /lib". Enter
Write :?ls? to open the directory and find the file "savespace" so you can see it is there. Enter
To make the file executable you write "chmod +x savespace.sh". Enter.
To run the file write : "./savespace.sh". Enter
You wil be asked if you are sure you want to run this file. Press "Enter" and you will get further instructions such as  Write : "yes", "no" or how to leave the session.
Write :"yes"
It will be confirmed that the file is running and LUA will restart.
In my case it said  something like "cannot remowe storidge/etc no such directory", Rafale has told me it is normal.
You are now finished.

If you have ALTUI you can check it there (os command) Free space.

READ reply #44 and get the most recent files (25 of Jan. 2019)
 
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 31, 2019, 07:09:31 am
That's a really useful piece of text, Svaleb. Well done!
I definitely feel that Rafale led you further, but most importantly, you're up and running

C
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 31, 2019, 08:33:19 am
I hope it is ok.
And that you did not find something wrong.
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 31, 2019, 08:53:12 am
I hope it is ok.
And that you did not find something wrong.

I think you've done a great job!
If you want be to be picky Macs actually have ssh and scp built into the operating system, and you can access them from the terminal program.
Also, to prevent future confusion I think your quotation marks around commands and key presses have been converted to '?'. That may be the local settings on my system here, though.
As I say, well done! :)

C
Title: Re: VeraPlus Flash drive usage
Post by: svaleb on January 31, 2019, 04:02:45 pm
About the Mac.
It  a quote. Rafale did not know wether I used Mac or Win.
Have changed ? to ". I dont know why it sometimes change.
Thanks.
Title: Re: VeraPlus Flash drive usage
Post by: rigpapa on January 31, 2019, 04:13:19 pm
About the Mac.
It  a quote. Rafale did not know wether I used Mac or Win.
Have changed ? to ". I dont know why it sometimes change.
Thanks.

Some text editors will automatically change the straight quote " to a "curly" quote, to make the text more aesthetically pleasing. That may be a good typographic choice but it really screws up code, and often doesn't "paste" well into other facilities, like these forums. These editors often have a setting you can turn off to stop this automatic replacement (sometimes called "smart quotes" or similar).
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on January 31, 2019, 04:38:55 pm
Sorry guys, rigpapa is correct. Whenever I post from my phone or ipad, it seems to convert all my ' and " into ?... editor compatibility problems.
Title: Re: VeraPlus Flash drive usage
Post by: Catman on January 31, 2019, 04:59:32 pm
Sorry guys, rigpapa is correct. Whenever I post from my phone or ipad, it seems to convert all my ' and " into ?... editor compatibility problems.

Figures. I can see it, but it might cause headaches for a newbie (as it were)

C
Title: Re: VeraPlus Flash drive usage
Post by: korttoma on February 08, 2019, 02:45:51 am
Am I supposed to add an external drive to the USB port that the script will make use of or does the script only change how the Vera internal flash drive is used?
Can the script be used on a Veralite? Has anyone tried?

Sorry for the n00b questions...
Title: Re: VeraPlus Flash drive usage
Post by: Catman on February 08, 2019, 04:19:00 am
Am I supposed to add an external drive to the USB port that the script will make use of or does the script only change how the Vera internal flash drive is used?
Can the script be used on a Veralite? Has anyone tried?

Sorry for the n00b questions...

I can be corrected but this script is to change the way in which the internal flash drive is used.

C
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on February 08, 2019, 06:46:22 am
Am I supposed to add an external drive to the USB port that the script will make use of or does the script only change how the Vera internal flash drive is used?
Can the script be used on a Veralite? Has anyone tried?

Sorry for the n00b questions...

If the idea is to use an external drive, look at the extroot thread. This thread is about using the existing storage on the vera. I don't have the flash map of the veralite at the moment so for now I would not recommend this.
Title: Re: VeraPlus Flash drive usage
Post by: korttoma on February 08, 2019, 02:46:14 pm
If the idea is to use an external drive, look at the extroot thread. This thread is about using the existing storage on the vera. I don't have the flash map of the veralite at the moment so for now I would not recommend this.

I will check the extroot thread.

About the flash map for Veralite, would this help?

Code: [Select]
df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 4608      4608         0 100% /rom
tmpfs                    31240       552     30688   2% /tmp
tmpfs                      512         0       512   0% /dev
/dev/mtdblock7           11264      4140      7124  37% /overlay
overlayfs:/overlay       11264      4140      7124  37% /
/dev/mtdblock8            6528      6528         0 100% /mios

Code: [Select]
dmesg
Linux version 2.6.37.1 (builder@builder.micasaverde.com) (gcc version 4.3.3 (GCC) ) #2 Fri Feb 22 04:07:32 PST 2013
prom: fw_arg0=00000001, fw_arg1=83f46fb0, fw_arg2=03f473b0, fw_arg3=00000000
env[0]: memsize=64
env[1]: initrd_start=0x00000000
env[2]: initrd_size=0x0
env[3]: flash_start=0x00000000
env[4]: flash_size=0x2000000
env[0]: memsize=64
env[1]: initrd_start=0x00000000
env[2]: initrd_size=0x0
env[3]: flash_start=0x00000000
env[4]: flash_size=0x2000000
CPU revision is: 0001974c (MIPS 74Kc)
Ralink RT3883   ver:1 eco:5 running at 500.00 MHz
Determined physical RAM map:
 memory: 04000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
  Normal   0x00000000 -> 0x00004000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00004000
On node 0 totalpages: 16384
free_area_init_node: node 0, pgdat 80249270, node_mem_map 81000000
  Normal zone: 128 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 16256 pages, LIFO batch:3
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line:  console=ttyS1,57600 board=VERALITE rootfstype=squashfs,jffs2
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Writing ErrCtl register=00000000
Readback ErrCtl register=00000000
Memory: 62324k/65536k available (1890k kernel code, 3212k reserved, 451k data, 156k init, 0k highmem)
SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:48
console [ttyS1] enabled
Calibrating delay loop... 249.85 BogoMIPS (lpj=1249280)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
NET: Registered protocol family 16
MIPS: machine is MiCasaVerde VeraLite
bio: create slab <bio-0> at 0
Switching to clocksource MIPS
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
JFFS2 version 2.2 (NAND) (ZLIB) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
msgmni has been set to 121
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
serial8250: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
ra_nand_probe: alloc 7f8, at 83841000 , btt(838415f8, 200), mtd:83841000
Creating 10 MTD partitions on "ramips-nand":
0x000000000000-0x000000080000 : "u-boot"
0x000000080000-0x0000000a0000 : "config"
0x0000000a0000-0x0000000b0000 : "factory"
0x0000000b0000-0x0000000d0000 : "config_default"
0x0000000d0000-0x0000000f0000 : "user_storage"
0x0000000f0000-0x0000004f0000 : "kernel"
0x0000004f0000-0x000000cf0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
0x000000cf0000-0x0000017f0000 : "rootfs_data"
ra_nand_block_checkbad: offs:1158000 tag: BAD
0x0000017f0000-0x000001ff0000 : "mios"
0x000001ff0000-0x000002000000 : "pid"
ramips_mdio: probed
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
VFS: Mounted root (squashfs filesystem) readonly on device 31:6.
Freeing unused kernel memory: 156k freed
input: gpio-buttons as /devices/platform/gpio-buttons/input/input0
Button Hotplug driver version 0.4.4
Registered led device: veralite:red:error
Registered led device: veralite:orange:zwave
Registered led device: veralite:yellow:lan
Registered led device: veralite:blue:power
eth0: link up (100Mbps/Full duplex)
ra_nand_block_checkbad: offs:1158000 tag: BAD
JFFS2 notice: (373) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (0 unchecked, 0 orphan) and 7 of xref (0 dead, 0 orphan) found.
diag: Detected 'MiCasaVerde VeraLite'
eth0: link down
eth0: link up (100Mbps/Full duplex)
Compat-wireless backport release: compat-wireless-2011-05-23
Backport based on wireless-testing.git master-2011-05-27
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver rt2800usb
loop: module loaded
PPP generic driver version 2.4.2
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 24
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
rt3883-ehci rt3883-ehci: Ralink RT3883 built-in EHCI controller
rt3883-ehci rt3883-ehci: new USB bus registered, assigned bus number 1
rt3883-ehci rt3883-ehci: irq 26, io mem 0x101c0000
rt3883-ehci rt3883-ehci: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
nf_conntrack version 0.5.0 (976 buckets, 3904 max)
xt_time: kernel timezone is -0000
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
rt3883-ohci rt3883-ohci: Ralink RT3883 built-in OHCI controller
rt3883-ohci rt3883-ohci: new USB bus registered, assigned bus number 2
rt3883-ohci rt3883-ohci: irq 26, io mem 0x101c1000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-1: new high speed USB device using rt3883-ehci and address 2
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
Initializing USB Mass Storage driver...
scsi0 : usb-storage 1-1:1.0
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
usbcore: registered new interface driver belkin
belkin_sa: v1.3:USB Belkin Serial converter driver
USB Serial support registered for cp210x
usbcore: registered new interface driver cp210x
cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
USB Serial support registered for Keyspan - (without firmware)
USB Serial support registered for Keyspan 1 port adapter
USB Serial support registered for Keyspan 2 port adapter
USB Serial support registered for Keyspan 4 port adapter
usbcore: registered new interface driver keyspan
keyspan: v1.1.5:Keyspan USB to Serial Converter Driver
USB Serial support registered for MCT U232
usbcore: registered new interface driver mct_u232
mct_u232: z2.1:Magic Control Technology USB-RS232 converter driver
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer           1.01 PQ: 0 ANSI: 2
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
ramips-wdt: timeout value 60 must be 0 < timeout < 25
Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on February 08, 2019, 05:21:13 pm
It does! Thank you. I have not gotten to go dust off the vera lite in my storage so this is useful. Unfortunately though you do not have an extra storage partition on the vera lite where you could offload some of the files. If I remember correctly, the veralite only has 64mb of storage and 11mb is available. I don?t know if people see the irony here but the available partition for the vera is going down as we go to newer models: 11mb for the lite, 10mb for the edge, 8.6mb for the plus... while mios has been selling us on larger nand flash, less and less is actually available for use so at each upgrade, we are actually downgrading the storage...sigh
Title: Re: VeraPlus Flash drive usage
Post by: korttoma on February 09, 2019, 01:30:39 am
Ok, seems the extroot is then the only option for Veralite, I will join the discussion in the other thread.
Just thought that I would test it on my Veralite first but, now I need to work up the confidence to apply this savespace script on my main VeraPlus instead  :D
Title: Re: VeraPlus Flash drive usage
Post by: Tarkus on February 09, 2019, 11:09:30 am
Worked for me on my plus. Do you recommend a revert before any firmware upgrades?

Code: [Select]
Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      7.3M      1.3M  84% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M    740.0K    124.0M   1% /tmp
/dev/mtdblock7            8.6M      7.3M      1.3M  84% /overlay
overlayfs:/overlay        8.6M      7.3M      1.3M  84% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock10          50.0M     11.5M     38.5M  23% /storage
/dev/mtdblock10          50.0M     11.5M     38.5M  23% /etc/cmh-firmware
/dev/mtdblock10          50.0M     11.5M     38.5M  23% /etc/cmh-backup
/dev/mtdblock9           10.0M     10.0M         0 100% /mios


Filesystem                Size      Used Available Use% Mounted on
rootfs                    8.6M      2.6M      6.0M  31% /
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   124.8M      1.6M    123.2M   1% /tmp
/dev/mtdblock7            8.6M      2.6M      6.0M  31% /overlay
overlayfs:/overlay        8.6M      2.6M      6.0M  31% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock10          50.0M     16.2M     33.8M  32% /storage
/dev/mtdblock10          50.0M     16.2M     33.8M  32% /etc/cmh-firmware
/dev/mtdblock10          50.0M     16.2M     33.8M  32% /etc/cmh-backup
/dev/mtdblock9           10.0M     10.0M         0 100% /mios

Title: Re: VeraPlus Flash drive usage
Post by: rafale77 on February 09, 2019, 11:32:24 am
I willl have to see how the next firmware installs but for current firmware, I do not recommend to revert anymore since the firmware I have seen are only a rootfs and mios partition overwrites.