New Member
Posts: 28
Registered: ‎06-30-2014
Kudos: 2

Interesting boot/reboot issues after upgrading to v2.0.0

So I updated to v2.0.0 today on my EdgeRouter Lite (ERLite-3), and run into some issues.

 

First the router never came online after the update. After almost half an hour it still wasn't responding. I decided to power cycle the unit and 10 minutes later still nothing. I hooked up the console cable and power cycled it again expecting to see an error somewhere, but it booted this time. I rebooted it successfully three times while logging the console output, and then it started having issues again.

 

I clicked reboot in the web UI, and the serial output in code block no 2 down below happened. As can be seen I tried the reset command but that did not work. Power cycling the unit again however did.

 

There is some weirdness going on during boot though with services starting and stopping multiple times in a row, as can be seen in code block no 1 below.

 

The first time I hooked up to the console I got a bunch of SquashFS errors, failing to read blocks and such. That has not happened again.

 

Is the internal USB flashdrive giving up again? Or are these issues with the upgrade? I had no problems before the upgrade, but that's no guarantee that the flashdrive is good.

 

At this point it seems to boot fine if I power cycle, but I can't reboot from software.

 

Code block no 1

         Stopping System Logging Service...
[  OK  ] Stopped System Logging Service.
         Starting System Logging Service...
[  OK  ] Started System Logging Service.
         Starting Network Time Service...
[  OK  ] Started Network Time Service.
         Stopping System Logging Service...
[  OK  ] Stopped System Logging Service.
         Starting System Logging Service...
[  OK  ] Started System Logging Service.

...


[ ***  ] A start job is running for UBNT Routing Daemons (1min 50s / no limit)
         Stopping Network Time Service...
[  OK  ] Stopped Network Time Service.
         Starting Network Time Service...
[  OK  ] Started Network Time Service.
         Stopping Network Time Service...
[  OK  ] Stopped Network Time Service.
         Starting Network Time Service...
[  OK  ] Started Network Time Service.

...

[K[ ***  ] A start job is running for UBNT Routing Daemons (2min 2s / no limit)
         Stopping System Logging Service...
[  OK  ] Stopped System Logging Service.
         Starting System Logging Service...
[  OK  ] Started System Logging Service.
         Starting GUI Telnet Daemon...
[  OK  ] Started GUI Telnet Daemon.
         Starting Lighttpd Daemon...
[  OK  ] Started Lighttpd Daemon.
         Starting EdgeOS DHCP Server...
[  OK  ] Started EdgeOS DHCP Server.
         Starting dnsmasq - A lightweight DHCP and caching DNS server...
[  OK  ] Started dnsmasq - A lightweight DHCP and caching DNS server.
         Stopping dnsmasq - A lightweight DHCP and caching DNS server...
[  OK  ] Stopped dnsmasq - A lightweight DHCP and caching DNS server.
         Starting dnsmasq - A lightweight DHCP and caching DNS server...
[  OK  ] Started dnsmasq - A lightweight DHCP and caching DNS server.
         Starting Simple Network Management Protocol (SNMP) Daemon....
[  OK  ] Started Simple Network Management Protocol (SNMP) Daemon..

 

 

Code block no 2

[  OK  ] Stopped EdgeOS IMI manager.
         Stopping UBNT daemon...
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
blk_update_request: I/O error, dev sda, sector 1871168
Aborting journal on device sda2-8.
JBD2: Error -5 detected when updating journal superblock for sda2-8.
[  OK  ] Stopped UBNT daemon.
[  OK  ] Stopped target Network (Pre).
EXT4-fs error (device sda2): ext4_find_entry:1469: inode #76349: comm scsi_id: reading directory lblock 0
         Stopping Netplug Services...
[  OK  ] Stopped Netplug Services.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed UUID daemon activation socket.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Stopped target Encrypted Volumes.
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
[  OK  ] Stopped Dispatch Password Requests to Console Directory Watch.
[  OK  ] Stopped target Swap.
         Stopping Load/Save Random Seed...
         Stopping Update UTMP about System Boot/Shutdown...EXT4-fs error (device sda2): ext4_journal_check_start:56: Detected aborted journal

EXT4-fs (sda2): Remounting filesystem read-only
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
         Unmounting /tmp...
         Unmounting /lib/init/rw...
         Unmounting /root.dev...
         Unmounting /opt/vyatta/config/tmp/n…bdaa5518af24357959b67f45294e5c7...
         Unmounting /run/shm...
[  OK  ] Stopped Flush Journal to Persistent Storage.
         Unmounting /var/log...
[  OK  ] Unmounted /tmp.
[  OK  ] Unmounted /lib/init/rw.
[FAILED] Failed unmounting /root.dev.
[  OK  ] Unmounted /opt/vyatta/config/tmp/ne…_2bdaa5518af24357959b67f45294e5c7.
[  OK  ] Unmounted /run/shm.
[  OK  ] Unmounted /var/log.
         Unmounting /opt/vyatta/config...
[  OK  ] Unmounted /opt/vyatta/config.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
watchdog: watchdog0: watchdog did not stop!
EXT4-fs error (device sda2): ext4_remount:4918: Abort forced by user
EXT4-fs error (device sda2): ext4_remount:4918: Abort forced by user
EXT4-fs error (device sda2): ext4_find_entry:1469: inode #76321: comm systemd-shutdow: reading directory lblock 0
EXT4-fs error (device sda2): ext4_remount:4918: Abort forced by user
EXT4-fs error (device sda2): ext4_remount:4918: Abort forced by user
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/64, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
usb 1-1: device descriptor read/8, error -145
usb usb1-port1: unable to enumerate USB device
reboot: Restarting system

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000


U-Boot 1.1.1 (UBNT Build Version: e102_002_20738) (Oct 26 2018 - 09:19:29)

BIST check passed.
UBNT_E100 r1:2, r2:14, f:4/71, serial #: DC9FDB80354F
MPR 13-00000-00
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB
Clearing DRAM....... done
ERROR: Unable to allocate linux reserved memory (addr: 0x100000, size: 0x8000000).
Flash:  4 MB
Net:   octeth0, octeth1, octeth2

USB:   (port 0) scanning bus for devices... #### ERROR: USB control polling timed out!
#### ERROR: Unable to close pipe handle (control): 0

      USB device not responding, giving up (status=80000000)
1 USB Devices found
       scanning bus for storage devices...
No device found. Not initialized?
leds_init 206
 0 
** Partition 1 not valid on device 0 **

** Unable to use usb 0:1 for fatload **
reading 

** Unable to read  
argv[2]: coremask=0x3
argv[3]: root=/dev/sda2
argv[4]: rootdelay=15
argv[5]: rw
argv[6]: rootsqimg=squashfs.img
argv[7]: rootsqwdir=w
argv[8]: mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom)
## No elf image at address 0x07d00000
Octeon ubnt_e100# reset


Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000


U-Boot 1.1.1 (UBNT Build Version: e102_002_20738) (Oct 26 2018 - 09:19:29)

BIST check passed.
UBNT_E100 r1:2, r2:14, f:4/71, serial #: DC9FDB80354F
MPR 13-00000-00
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB
Clearing DRAM....... done
ERROR: Unable to allocate linux reserved memory (addr: 0x100000, size: 0x8000000).
Flash:  4 MB
Net:   octeth0, octeth1, octeth2

USB:   (port 0) scanning bus for devices... #### ERROR: USB control polling timed out!
#### ERROR: Unable to close pipe handle (control): 0

      USB device not responding, giving up (status=80000000)
1 USB Devices found
       scanning bus for storage devices...
No device found. Not initialized?
leds_init 206
 0 
** Partition 1 not valid on device 0 **

** Unable to use usb 0:1 for fatload **
reading 

** Unable to read  
argv[2]: coremask=0x3
argv[3]: root=/dev/sda2
argv[4]: rootdelay=15
argv[5]: rw
argv[6]: rootsqimg=squashfs.img
argv[7]: rootsqwdir=w
argv[8]: mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom)
## No elf image at address 0x07d00000
Octeon ubnt_e100# reset


Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000
New Member
Posts: 28
Registered: ‎06-30-2014
Kudos: 2

Re: Interesting boot/reboot issues after upgrading to v2.0.0

No one?

Established Member
Posts: 969
Registered: ‎02-12-2013
Kudos: 251
Solutions: 90

Re: Interesting boot/reboot issues after upgrading to v2.0.0

@Erik5678
It looks like the internal USB key is dead or corrupted. I'm not sure if there's a newer method for ER-Lite, but this thread has worked for many others:
https://community.ubnt.com/t5/EdgeMAX/EdgeMax-rescue-kit-now-you-can-reinstall-EdgeOS-from-scratch/t...
New Member
Posts: 28
Registered: ‎06-30-2014
Kudos: 2

Re: Interesting boot/reboot issues after upgrading to v2.0.0

Thank you. I have changed it out once before and I will probably do it again to be on the safe side. It could just be a corrupt file system, but if I'm going to go though the trouble of fixing that I may as well change the USB drive as well.

Highlighted
New Member
Posts: 28
Registered: ‎06-30-2014
Kudos: 2

Re: Interesting boot/reboot issues after upgrading to v2.0.0

Just a follow up:

Replacing the USB drive was successfull. I'm now up and running again without these problems.