OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Critical
  • Priority Very Low
  • Reported Version lede-17.01
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Jonathon Brack - 30.07.2018

FS#1712 - LEDE 17.01.05 on BCM2710 (Raspberry Pi 3) defaults configuration on reboot

Supply the following if possible:
- Device problem occurs on

  1. BCM2710 (Raspberry Pi 3B)

- Software versions of OpenWrt/LEDE release, packages, etc.

  1. LEDE 17.01.05 → Directly from download page, and from clean build

- Steps to reproduce

  1. Perform initial flash of software.
  2. Boot device up and confirm interfaces work correctly, and DHCP is server properly from eth0
  3. Confirm that configuration for /etc/dhcp and /etc/network looks correct
  4. Reboot device (either via LuCI or console reboot)
  5. Upon start, confirm that dhcp config is empty, network config is defaulted (missing wlan0, etc).
  6. Confirm that interfaces do not work correctly, GUI is no longer navigable even with a static IP fixed on PC.

Jonathon Brack commented on 30.07.2018 18:59

From a quick glance, as compared to 17.01.04, it seems that squashfs is enabled by default now (although I tried a build with it disabled with no luck). It was my understanding that the overlayfs required to make squashfs work properly was not fully integrated and working for the Raspberry Pi 3b (at least way back on 17.01.01). Confirmed that "/overlay" and ".rom" are both completely empty both before and after any hand modifications, for both initial boot, and subsequent boots.

David Xie commented on 07.08.2018 15:51

Try using the ext4 image, since you're able to plug into another Linux computer and check the filesystem. Additionally, MicroSD card on RPi is not being recognize as a MTD device, it has a MBR (msdos) partition scheme.

Jonathon Brack commented on 09.08.2018 15:53

The firmware image from the Stable Releases is EXT4. Additionally, the image I built locally is EXT4. I'm loading both images via "dd if=<SOME_IMAGE> of=/dev/sdb bs=2M conv=fsync" on a SD card without any native partitions (all deleted prior with fdisk).

I can boot the device, and have access to the serial terminal. Main differences I see between 17.01.4 and 17.01.5 in bootup are below. It seems that v17.01.5 is getting re-mounted as read-only, which would explain the issues that I am seeing (changes are cached and not written through to the SD card). This is absolutely repeatable (attempted 5+ times now comparing v17.01.4 to v17.01.5).

LEDE v17.01.4
[ 4.654896] mount_root: mounting /dev/root
[ 4.656451] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 4.656590] mount_root: loading kmods from internal overlay

LEDE v17.01.5
[ 4.550542] mount_root: mounting /dev/root
[ 4.561791] EXT4-fs error (device mmcblk0p2): ext4_has_uninit_itable:2883: comm mount_root: Inode table for bg 0 marked as needing zeroing
[ 4.580761] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[ 4.592648] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 4.604003] mount_root: loading kmods from internal overlay

David Xie commented on 08.02.2019 18:28

The filesystem is corrupt and you need to check this ext4 filesystem on another Linux computer.


Available keyboard shortcuts


Task Details

Task Editing