fsck.ext4 fails with signal 7

206 views
Skip to first unread message

Karl Fischer

unread,
Sep 27, 2016, 5:11:16 PM9/27/16
to Alt-F
  • Hello
  • i get the followig error everytime i run fsck
  • even manualy or via ssh:

  • Unable to automatically fix md0, mounting Read Only: fsck 1.41.14 (22-Dec-2010)
    /dev/md0 contains a file system with errors, check forced.
    Warning... fsck.ext4 for device /dev/md0 exited with signal 7.
  • Alt-F directory found in md0 but not used, as filesystem is read-only!
Checking md0 finished with status code 8: fsck 1.41.14 (22-Dec-2010)
  • e2fsck 1.41.14 (22-Dec-2010)
    Pass 1: Checking inodes, blocks, and sizes
    Warning... fsck.ext4 for device /dev/md0 exited with signal 7.
  • what can  do ?

João Cardoso

unread,
Sep 28, 2016, 10:21:55 AM9/28/16
to Alt-F


On Tuesday, 27 September 2016 22:11:16 UTC+1, Karl Fischer wrote:
  • Hello
  • i get the followig error everytime i run fsck
  • even manualy or via ssh:

  • Unable to automatically fix md0, mounting Read Only: fsck 1.41.14 (22-Dec-2010)
    /dev/md0 contains a file system with errors, check forced.
    Warning... fsck.ext4 for device /dev/md0 exited with signal 7.

From the e2fsck manual page,  

EXIT CODE
       The  exit  code  returned  by e2fsck is the sum of the following condi‐
       tions:
            0    - No errors
            1    - File system errors corrected
            2    - File system errors corrected, system should
                   be rebooted
            4    - File system errors left uncorrected
            8    - Operational error
            16   - Usage or syntax error
            32   - E2fsck canceled by user request
            128  - Shared library error
 
so it should be errors 4+2+1=7, where 1 and 2 makes no sense together with 4 (other than reboot). So I have no idea.

A bit of context could be useful: how was the RAID created? under which firmware? How long has it working OK? recent/first Alt-F install and boot? does swap exists? W#hat box and rev is it?
Most of the above questions would be answered had you *attached* the System Configuration log, as the forum welcome message says.

In any case you should think in doing a backup, the filesystem is mounted in RO mode to prevent further damages and allow backups to be done.
Reply all
Reply to author
Forward
0 new messages