Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
openwrt-bot opened this issue Jul 30, 2018 · 4 comments
Labels

Comments

@openwrt-bot
Copy link

jwbrack:

Supply the following if possible:

  • Device problem occurs on

    • BCM2710 (Raspberry Pi 3B)
  • Software versions of OpenWrt/LEDE release, packages, etc.

    • LEDE 17.01.05 -> Directly from download page, and from clean build
  • Steps to reproduce

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

jwbrack:

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.

@openwrt-bot
Copy link
Author

127.0.0.1:

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.

@openwrt-bot
Copy link
Author

jwbrack:

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

@openwrt-bot
Copy link
Author

127.0.0.1:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant