This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Error in cannot read /lib/apps/web-index.lua at line I/O error
#1
Hi
This morning I've got that message when I was trying to access my /apps/ folder. What's going on?
Error in cannot read /lib/apps/web-index.lua at line I/O error

Visu works with no problem.

Can I solve it somehow?
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
Reply
#2
(20.11.2017, 11:02)Thomas Wrote: Hi
This morning I've got that message when I was trying to access my /apps/ folder. What's going on?
Error in cannot read /lib/apps/web-index.lua at line I/O error

Visu works with no problem.

Can I solve it somehow?

Hi, when I started to experience similar problems in various scripts, it turns out that my SD card had reached its life limit, so I had to replace it, restore a backup and then the issues gone away...
Reply
#3
Unfortunately I don't have physical access to the device. Is it possible to restart it remotely? Or by KNX bus?
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
Reply
#4
OK, the device has been reset and now it looks OK.
What SD card do I need? Do you have a suggestion?

I see this in my system log:
Nov 20 13:22:33 UHR-VISU kern.notice kernel: [ 9.854655] random: nonblocking pool is initialized
Nov 20 13:22:28 UHR-VISU kern.info kernel: [ 5.667099] fec 2188000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
Nov 20 13:22:28 UHR-VISU user.info sysinit: /lib/genohm-scada/storage/current.db: OK
Nov 20 13:22:27 UHR-VISU kern.info kernel: [ 4.421713] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: nodelalloc
Nov 20 13:22:27 UHR-VISU kern.info kernel: [ 4.421271] EXT4-fs (mmcblk0p3): recovery complete
Nov 20 13:22:26 UHR-VISU user.info sysinit: /dev/mmcblk0p3: ********** WARNING: Filesystem still has errors **********
Nov 20 13:22:26 UHR-VISU user.info sysinit: e2fsck: unable to set superblock flags on /dev/mmcblk0p3
Nov 20 13:22:26 UHR-VISU user.info sysinit: Run journal anyway? yes
Nov 20 13:22:26 UHR-VISU user.info sysinit: Superblock needs_recovery flag is clear, but journal has data.
Nov 20 13:22:25 UHR-VISU user.info sysinit: /dev/mmcblk0p3: recovering journal
Nov 20 13:22:25 UHR-VISU user.info sysinit: e2fsck 1.43.4 (31-Jan-2017)
Nov 20 13:22:25 UHR-VISU kern.info kernel: [ 2.650736] fec 2188000.ethernet eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 1.578946] fec 2188000.ethernet eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.986808] EXT4-fs (mmcblk0p2): re-mounted. Opts: nodelalloc
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.552528] Freeing unused kernel memory: 160K (c03ba000 - c03e2000)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.551947] VFS: Mounted root (ext3 filesystem) readonly on device 179:2.
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.551846] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.550971] EXT4-fs (mmcblk0p2): recovery complete
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.449026] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.448996] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.370497] mmcblk0: p1 p2 p3
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.369178] mmcblk0: mmc0:59b4 USD 3.73 GiB
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.368207] mmc0: new high speed SDHC card at address 59b4
Nov 20 13:22:24 UHR-VISU kern.warn kernel: [ 0.362121] mmc0: host does not support reading read-only switch, assuming write-enable
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.344605] Waiting for root device /dev/mmcblk0p2...
Nov 20 13:22:24 UHR-VISU kern.err kernel: [ 0.344532] Warning: unable to open an initial console.
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.344114] vdd3p0: disabling
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.343401] rtc-pcf85263a 0-0051: setting system clock to 2017-11-20 13:22:23 UTC (1511184143)
Nov 20 13:22:24 UHR-VISU kern.err kernel: [ 0.340020] cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.338701] can: raw protocol (rev 20120528)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.338460] NET: Registered protocol family 29
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.338290] can: controller area network core (rev 20120528 abi 9)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.338225] NET: Registered protocol family 17
Nov 20 13:22:24 UHR-VISU kern.warn kernel: [ 0.322473] 2198000.adc supply vref not found, using dummy regulator
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.306610] mmc0: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.269903] sdhci-esdhc-imx 2194000.usdhc: No vqmmc regulator found
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.269878] sdhci-esdhc-imx 2194000.usdhc: No vmmc regulator found
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.269688] /soc/aips-bus@02100000/usdhc@02194000: voltage-ranges unspecified
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.267951] sdhci-pltfm: SDHCI platform and OF driver helper
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.267936] sdhci: Copyright© Pierre Ossman
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.267912] sdhci: Secure Digital Host Controller Interface driver
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.267353] usbcore: registered new interface driver btusb
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.266469] imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0)
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.264960] i2c /dev entries driver
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.264740] rtc-pcf85263a 0-0051: rtc core: registered rtc-pcf85263a as rtc0
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.260406] hub 2-0:1.0: 1 port detected
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.260297] hub 2-0:1.0: USB hub found
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.259037] usb usb2: SerialNumber: ci_hdrc.1
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.259016] usb usb2: Manufacturer: Linux 4.4.73 ehci_hcd
Nov 20 13:22:24 UHR-VISU kern.info kernel: [ 0.258994] usb usb2: Product: EHCI Host Controller

What's on /dev/mmcblk0p3 ?
Is it OK it's been mounted as ro only and not remounted?
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
Reply
#5
LM team, can you provide me please the actual SD card image for my device for download? I'm afraid these links are obsolete and for different CPUs http://openrb.com/reflash-logicmachine3-...-software/

Thank you
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
Reply
#6
Recovery for power version:
https://dl.openrb.com/recovery-imx6.img.gz
Reply
#7
Thank you
I'm looking for SLC microSD. Does it exist? I can't find any.
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
Reply
#8
(21.11.2017, 13:33)Thomas Wrote: Thank you
I'm looking for SLC microSD. Does it exist? I can't find any.

For example this.
http://uk.rs-online.com/web/p/secure-dig...s/1465583/
Reply
#9
Thank you. I was looking for Samsung or Transcend because these two brands were recommended by LM. Is ATP OK too? Is 4GB enough? I thought LM5LP contains 8GB SD.
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
Reply
#10
Even 1GB is more than enough, but the recovery image is made for 4GB cards if I remember correctly.
Reply


Forum Jump: