Read-only file system

httpd.service failed to run ‘start’ task: Read-only file system

check root partition by df -h

Filesystem Size Used Avail Use% Mounted on
/dev/md2 906G 74G 787G 9% /

the root partition is /dev/md2

so to mount in read write please type mount -o remount,rw /dev/md2 /

if it gives error

boot system in resue mode

[email protected] ~ # mdadm –examine –scan

ARRAY /dev/md/0 metadata=1.2 UUID=01328cc4:7d0af303:4faf0867:696ea967 name=rescue:0
ARRAY /dev/md/1 metadata=1.2 UUID=28ccd572:f57243f7:edb49a3d:10501de1 name=rescue:1
ARRAY /dev/md/2 metadata=1.2 UUID=55b0ae5f:48f8fea1:d2730dc0:9fd3f725 name=rescue:2

[email protected] ~ # e2fsck -fv /dev/md0


e2fsck 1.44.5 (15-Dec-2018)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks…
e2fsck: Bad magic number in super-block while trying to open /dev/md0

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768

/dev/md0 contains a swap file system


[email protected] ~ # e2fsck -fv /dev/md1


e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

     350 inodes used (0.27%, out of 131072)
      87 non-contiguous files (24.9%)
       1 non-contiguous directory (0.3%)
         # of inodes with ind/dind/tind blocks: 88/18/0
  172589 blocks used (32.95%, out of 523712)
       0 bad blocks
       0 large files

     328 regular files
      12 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
       1 symbolic link (1 fast symbolic link)

0 sockets

     341 files

[email protected] ~ # e2fsck -fv /dev/md2


e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 26738695 was part of the orphaned inode list. FIXED.
Inode 26738696 was part of the orphaned inode list. FIXED.
Inode 26738698 was part of the orphaned inode list. FIXED.

then reboot

Leave a Comment

Your email address will not be published. Required fields are marked *

Hire a server Expert to resolve the issue Now.

Hire a server Expert to resolve the issue Now.

Resolve this issue in just 5$ from https://serverexpert.io

 

You have Successfully Subscribed!

Open chat