root@OpenWrt:~# mtd erase 0:ethphyfw1
Could not open mtd device: 0
Could not open mtd device: 0
root@OpenWrt:/tmp# mtd -n write AQR-G4_v5.4.C-AQR_CIG_WF-1945_0x0_ID44778_VER1630.cld 0:ethphyfw1
Could not open mtd device: 0
Can't open device for writing!
@sppmaster
I end up with the above, would you know why?
Nope, sorry I can't tell why? I've followed @robimarko's advice.
And seeing below looked scary.
I've proposed it for safety because if someone doesn't notice the mistake that was eventually made they would be really unpleasantly surprised with no bootable router.
Maybe this 0: is somehow the culprit. Just my speculation, though.
Also, the front leds are not working, I saw a commit related to leds, the config needs to be changed? Didn't do a reset when I uploaded the latest build.
The front LEDs work in my case but I've discovered a new issue:
Ports 1 -4 become unusable if the router is started up without hooking up a LAN cable to any of the ports. Clients connected to these ports after the router is fully started up do not get IPs assigned. The ports become fully functional again after a reboot. 10g-1 and 10g-2 ports are not affected, clients connected to these ports get IPs assigned without any issues.
With the LAN cable disconnected and router rebooted, Lan ports 1 - 4 still unusable in my case. A LAN cable must be plugged into LAN ports 1-4 at startup in order to get these ports working after startup.
@robimarko updated to today OpenWrt SNAPSHOT, r28669-17dc0797d0
but seem that changes are not persistent, tried second sysupgrade without keeping the changes and also firstboot but seems that changes are not persistent anymore
[ 27.899646] loop0: detected capacity change from 0 to 1048576
[ 27.945833] loop0: detected capacity change from 1048576 to 1017600
[ 27.947246] mount_root: overlay filesystem in /dev/loop0 has not been formatted yet
[ 27.953912] mount_root: no usable overlay filesystem found, using tmpfs overlay
[ 27.959198] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
saw some changes about sysupgrade but this shouldn't affect saving changes, no ?
also added f2fs tools and at that moment I could not recover anymore, the tmpfs could not be mounted anymore and was forced to recover via serial tftpboot, loaded the latest nss build that seems to work as it should.
not sure if I'm missing something in the oficial image
I've updated yesterday and today using latest snapshots keeping the config settings. No issues keeping the settings.
This is my log.
[ 26.869364] loop0: detected capacity change from 0 to 1048576
[ 26.924421] loop0: detected capacity change from 1048576 to 1007616
[ 26.937152] mount_root: overlay filesystem in /dev/loop0 has not been formatted yet
[ 27.394328] F2FS-fs (loop0): Found nat_bits in checkpoint
[ 27.399849] F2FS-fs (loop0): Mounted with checkpoint version = 50006c37
[ 27.454507] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 27.500450] scsi host0: uas
[ 27.721050] block: attempting to load /tmp/overlay/upper/etc/config/fstab
[ 27.721206] block: unable to load configuration (fstab: Entry not found)
[ 27.726920] block: attempting to load /tmp/overlay/etc/config/fstab
[ 27.733710] block: unable to load configuration (fstab: Entry not found)
[ 27.739833] block: attempting to load /etc/config/fstab
[ 27.746729] block: unable to load configuration (fstab: Entry not found)
[ 27.751518] block: no usable configuration
[ 27.758645] block: attempting to load /etc/config/fstab
[ 27.762395] block: unable to load configuration (fstab: Entry not found)
[ 27.767509] block: no usable configuration
[ 27.775174] mount_root: overlay filesystem has not been fully initialized yet
[ 27.778641] mount_root: switching to f2fs overlay
[ 27.790275] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
