[lede-17.01.5-x86-64-combined-ext4.img] An error occurred after saved config

for example

vi /etc/config/network
:wq
reboot

then:

vi /etc/config/network

All characters become countless ‘^@^@’

^@^@ is vi's representation of null-bytes, which hints at possible filesystem corruption. Do you see any filesystem related errors in dmesg ?

cp /etc/config/network /etc/config/network.origin
vi /etc/config/network
:wq

before rebooting

vi /etc/config/network

All look normal.
There is no error about filesystem by ‘dmesg’ .

after rebooting

vi /etc/config/network.original

It's null, nothing.

first boot:

[    3.185484] EXT4-fs error (device sda2): ext4_has_uninit_itable:2883: comm mount_root: Inode table for bg 0 marked as needing zeroing
[    3.189962] EXT4-fs (sda2): Remounting filesystem read-only
[    3.191588] EXT4-fs (sda2): re-mounted. Opts: (null)
[    3.263868] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)

After modification,and reboot:

[    3.247238] EXT4-fs (sda2): warning: mounting unchecked fs, running e2fsck is recommended
[    3.261925] EXT4-fs error (device sda2): ext4_has_uninit_itable:2883: comm mount_root: Inode table for bg 0 marked as needing zeroing
[    3.284013] EXT4-fs (sda2): Remounting filesystem read-only
[    3.286388] EXT4-fs (sda2): re-mounted. Opts: (null)
[    3.340538] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)

@ jow

Bug fixes have been merged by https://github.com/openwrt/openwrt/commit/0a2c984222d03d940c52c3675849dd6398b34e64

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.