Can't enable USB logging

Community Playground General Discussions
1

I have a VeraEdge running 1.7.10 FW and am having some memory leak issues where the VeraEdage is rebooting several times a day . While troubleshooting I disabled USB logging. Now I am trying to re-enable it and getting the following error: “Installing required kernel modules and apps…FAILED”

Things I have tried to resolve the issue:

  1. Factory reset (3 times)
  2. re-formatting the USB
  3. A different USB stick
  4. downgrading the Vera FW

I am now running FW version 1.7.1248 which is the last version I can remember not having issues with but still this problem exists as well as the original memory leak.

Any help would be greatly appreciated.

Thanks,
Andy

2

I am getting that too, I just ordered 3 more diff usb flash drives earlier this week thinking it was just my flash… thanks for the update, at least know is not just me

btw, I am veraedge 7.0.11 (1.7.1419)

3

@ando1, did you every figure out what was causing the frequent reboot (cause of memory leak)? Mike

4

Similair is also discussed here: http://forum.micasaverde.com/index.php/topic,28798.0.html

5

I just finished fighting with this issue after a failed USB stick… on 1.7.12…

The resolution that worked for me was:

  1. Make sure you have “Store logs on USB device” enabled, and that the USB Status shows “Enabled; not mounted”.

  2. use an SSH client to log into your Vera.

  3. edit the fstab config file (/etc/config/fstab)
    change the following entries under “config mount”:

option fstype 'ext3'

to

option fstype 'ext4'
option options 'rw,noatime,nodiratime,errors=continue,data=ordered'

to

option options 'rw,noatime,nodiratime,errors=continue'
  1. reformat the usb stick with an ext4 filesystem
mkfs.ext4 -L "MiOS" -m 0 -O "^has_journal" /dev/sda1
  1. make sure that the JBD2 system is turned off for the USB stick file system
tune2fs -O "^has_journal" /dev/sda1
  1. make sure the file system is synchronized with the OS.
sync
  1. reboot your Vera
reboot

Once you give your Vera 3 or 4 minutes to reboot, you can reload your browser and go to settings/logs and the USB status should show “Enabled”.

6

[quote=“JS007, post:2, topic:188876”]I am getting that too, I just ordered 3 more diff usb flash drives earlier this week thinking it was just my flash… thanks for the update, at least know is not just me

btw, I am veraedge 7.0.11 (1.7.1419)[/quote]

this now works for me on the veraedge with latest beta release Version 7.0.12 (1.7.707/1.7.1509) , so should be fixed on next official release

7

I ended up calling support and they said it was the weather plugin. They uninstalled it and fixed my USB issue by re-installing the USB driver and I haven’t had any issues since. I am using a Monoprice motion sensor outside for temperature reporting now in place of the weather plugin.

8

@cybermage - Interesting. Can you say why it fails with EXT3? Is the EXT3 driver present in

ls -l /lib/modules/$(uname -r)/ext*

or is it that the EXT3 reformat is failing for some reason?

9

The ext3 driver is NOT present… only fat, vfat, msdos, ext4, jfs and xfs file system drivers are present.

The ext4 driver does handle the ext3 (and ext2) filesystem… but the problem appears to be the mke2fs executable (which is linked to the mkfs.ext2, mkfs.ext3 and mkfs.ext4 commands)… It does not appear to reliably handle file system options, and does not create a reliable ext3 filesystem on the USB drive (tested with generic sticks, Lexar sticks and Sandisk sticks).

With he mke2fs command not working properly, it always creates a filesystem with journal support… When the USB stick is mounted (either ext3 or ext4), the journal superblocks on the filesystem are (always) corrupt, and the mount fails.

The tune2fs command does work properly, and will disable the journal. Once the journal is disabled, an ext3 filesystem causes the ext4 driver to throw “incompatibilities” errors, but the filesystem does mount… An native ext4 filesystem does not throw errors, so even if the ext3 filesystem does mount, I prefer to use a filesystem that is not going to cause extra work for the driver.

Having a journaled filesystem is great for cases when you are storing mission-critical data, but is overkill for a filesystem that is used for storing logs, so disabling the filesystems journal support is not a major problem.

10

Thanks for the info and the stock workaround.

[quote=“cybrmage, post:9, topic:188876”]Having a journaled filesystem is great for cases when you are storing mission-critical data, but is overkill for a filesystem that is used for storing logs, so disabling the filesystems journal support is not a major problem.[/quote] and is probably a good idea for the sake of the flash drive’s longevity. EXT4 journalling would more than double the drive writes for this logging.

11

Thanks for the steps, it worked like a charm!! :slight_smile: