File system disappears on the Omega1 until reboot



  • Hi,

    Does anybody else get the file system randomly disappear on the Omega1? I have the root running on a usb through a hub. I First thought it was a loos connection but this has happened in exactly the same way on two completely different devices. here is the error I get:

    BusyBox v1.23.2 (2016-07-08 19:27:03 UTC) built-in shell (ash)
    
    cat: read error: Input/output error
    [14908.630000] EXT4-fs error (device sda): ext4_find_entry:1289: inode #131140:                                    comm ash: reading directory lblock 0
    [14908.640000] EXT4-fs error (device sda): ext4_find_entry:1289: inode #130308:                                    comm ash: reading directory lblock 0
    [14908.650000] EXT4-fs error (device sda): ext4_find_entry:1289: inode #131140:                                    comm ash: reading directory lblock 0
    [14908.660000] EXT4-fs error (device sda): ext4_find_entry:1289: inode #131140:                                    comm ash: reading directory lblock 0
    [14908.670000] EXT4-fs error (device sda): ext4_find_entry:1289: inode #130308:                                    comm ash: reading directory lblock 0
    root@Omega-1E48:/#
    root@Omega-1E48:/#
    

    any ls after that returns a blank prompt. Also if I ftp into the device, it appears to be blank.

    I would like to get to the bottom of the cause and also write a script that would detect this and rectify it if it happens. Currently I reboot and this fixes the problem. Any ideas on how to rectify without a reboot?

    Thanks.



  • For a detection of the problem, maybe you can create a script that tests for the existence of a specific file on your USB fs, and reboot the Omega if need be. This script can run on a regular basis using cron.

    I'm not familiar with OpenWRT, but maybe there's a less drastic solution like unmount and remount the USB fs instead of rebooting? Is this something that you tried in your investigation about this problem?


Log in to reply
 

Looks like your connection to Onion Community was lost, please wait while we try to reconnect.