SYS_PANIC [Linux filesystem becoming read-only]

fabrysfabrys
edited April 2023 in Problems Now Fixed

Good morning.

Can anyone tell me what this alert means that I've never seen before?

Or rather should something be done?

It appears when I go to Admin - Log


Sat Apr 15 16:29:36 1d:10:35:29.049 0... [02] L PWD admin admin ALLOWED: from 192.**
Sat Apr 15 16:29:36 1d:10:35:29.332 0...        SYS_PANIC: "_cfg_write_file fopen" Read-only file system (init/cfg.cpp, line 1306) Read-only file system
Sat Apr 15 16:29:37 1d:10:35:30.461 0...        cfg_write_file exit_status=0xff
Sat Apr 15 16:29:37 1d:10:35:30.498 0...        SYS_PANIC: "_cfg_write_file fopen" Read-only file system (init/cfg.cpp, line 1306) Read-only file system
Sat Apr 15 16:29:38 1d:10:35:31.609 0...        cfg_write_file exit_status=0xff
Sat Apr 15 16:29:38 1d:10:35:31.646 0...        SYS_PANIC: "_cfg_write_file fopen" Read-only file system (init/cfg.cpp, line 1306) Read-only file system
Sat Apr 15 16:29:40 1d:10:35:32.766 0...        cfg_write_file exit_status=0xff
Sat Apr 15 16:29:40 1d:10:35:32.808 0...        SYS_PANIC: "_cfg_write_file fopen" Read-only file system (init/cfg.cpp, line 1306) Read-only file system
Sat Apr 15 16:29:41 1d:10:35:33.940 0...        cfg_write_file exit_status=0xff
Sat Apr 15 16:29:41 1d:10:35:33.974 0...        SYS_PANIC: "_cfg_write_file fopen" Read-only file system (init/cfg.cpp, line 1306) Read-only file system
Sat Apr 15 16:29:42 1d:10:35:35.117 0...        cfg_write_file exit_status=0xff
Sat Apr 15 16:29:42 1d:10:35:35.155 0...        SYS_PANIC: "_cfg_write_file fopen" Read-only file system (init/cfg.cpp, line 1306) Read-only file system
Sat Apr 15 16:29:43 1d:10:35:36.266 0...        cfg_write_file exit_status=0xff


Installed version: v1.595, built Apr 13 2023 23:57:19

Git clone damaged!

Comments

  • jksjks

    Ugh. This is not good. When Linux detects severe damage to the filesystem it puts it in read-only mode to prevent the damage from potentially spreading. But the real question is why is your Kiwi trying to write its configuration file every few seconds? That's not normal and may eventually lead to wear problems with the eMMC filesystem memory chip over a very long period of time. How old is this Kiwi? Does it ever experience any power failures?

    First, go to the console tab and click the yellow disk free button. Is the use% column at 100%?

    Try rebooting Linux (not just restarting the Kiwi server). Use the blue Beagle Reboot button on the admin control tab. Do you still get the messages?

    If so then about all you can do is restore from a backup sd card. You do have a backup don't you? If not then you'll have to start all over again and will lose all of your configuration settings.

    These days it means downloading a Kiwi Debian 10 image onto an sd card and re-flashing from that. See the kiwisdr.com home page for instructions. The sd card supplied in the original Kiwi box will no longer work for re-flashing due to changes by debian.org You must use a newer Kiwi Debian 10 image.

    But after all that it is possible you will still have the problem if there has been actual hardware damage. In that case you'll have to replace the BeagleBone with a BBGreen or BBBlack.

  • fabrysfabrys

    the kiwi is a couple of years old but I changed the BBGreen card last year, when it was completely unprogrammed and it no longer started, since then I have put it under power with an uninterruptible power supply ups


    CONSOLE: open connection
root@kiwisdr:~/Beagle_SDR_GPS# df .
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1  3.5G  1.5G  1.8G  46% /

    I waited to restart the KIWI from scratch not without having read what that error meant in general and I had understood that the KIWI had stalled now after your communications I restarted from scratch and everything seems to work as it should, I also tried to do the test update and it responds as it should.

    Installed version: v1.595, built Apr 13 2023 23:57:19

    Running most current version


    so I hope it was a one-time event that doesn't repeat itself.

    Thanks for the info.

  • jksjks

    Yes, it is possible that this was some strange one-time event that caused Linux to take the drastic "read-only" action.

Sign In or Register to comment.