OMV stops responding

    • OMV 4.x
    • OMV stops responding

      I have been running OMV for over a year now but recently it would become unresponsive after a few weeks. I can ping the server but I can't ssh or access the GUI. I am running it via a USB drive and it might be the drive is going bad. What logs can I look at to confirm it? The issue is resolved after a reboot.
    • I actually found this in the syslog:

      Source Code

      1. Jun 1 19:48:47 omvserver kernel: [2496518.932681] EXT4-fs warning (device sde1): dx_probe:746: inode #14: lblock 0: comm dockerd: error -5 reading directory block
      2. Jun 1 19:48:48 omvserver kernel: [2496519.178396] EXT4-fs error: 67 callbacks suppressed
      3. Jun 1 19:48:48 omvserver kernel: [2496519.178398] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #522255: comm smbd: reading directory lblock 0
      4. Jun 1 19:48:48 omvserver kernel: [2496519.178432] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      5. Jun 1 19:48:48 omvserver kernel: [2496519.178442] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      6. Jun 1 19:48:48 omvserver kernel: [2496519.178522] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      7. Jun 1 19:48:48 omvserver kernel: [2496519.178546] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      8. Jun 1 19:48:48 omvserver kernel: [2496519.178550] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      9. Jun 1 19:48:48 omvserver kernel: [2496519.178554] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      10. Jun 1 19:48:48 omvserver kernel: [2496519.178558] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      11. Jun 1 19:48:48 omvserver kernel: [2496519.178561] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      12. Jun 1 19:48:48 omvserver kernel: [2496519.178565] EXT4-fs error (device sde1): ext4_find_entry:1439: inode #225: comm smbd: reading directory lblock 0
      Display All
      This is repeated a lot of times before I restarted the server and are gone since the restart. sde is my root drive which is a USB drive.
    • utamav wrote:

      I actually found this in the syslog
      The messages deal with just 3 different inodes so you need to do an fsck and see if the issues are resolved. You can do a touch /forcefsck followed by a reboot, follow the advice when searching the web for 'fsck rootfs debian' or use a second box with Linux where you mount the USB stick (the latter approaches allow for reading error messages and decide what to do in case of fatal errors).
    • Thanks for the input. fsck didn't show any errors but this has happened to me twice recently after running fine for over a year. So I went ahead and created a Clonezilla backup.

      One question: My Clonezilla backup for a 32GB drive was only 2GB. Is that normal? I used clone to local drive.
    • utamav wrote:

      warhawk8080 wrote:

      You don't have swapspace on your USB do you?
      Check to see if the openmediavault-flashmemory plugin is used
      I do have openmediavault-flashmemory plugin. I presume it's good to have it if using OMV on a flash drive.
      It is if you configure it correctly and run the command it tells you when you first install it.I personally use a cheap SSD they are usually more reliable and robust then a USB