The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

cpanel wont start Read-only file system

Discussion in 'General Discussion' started by lucaribeirorj, Jun 19, 2015.

  1. lucaribeirorj

    lucaribeirorj Registered

    Joined:
    Jun 19, 2015
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brazil
    cPanel Access Level:
    Root Administrator
    hello, my cpanel is not starting, the following message appears.

    root@srv1 [/]# /etc/init.d/cpanel start

    Starting cpanel:


    *** /usr/local/cpanel/etc/init/startup ERROR: ***

    Refusing to start because log directory /usr/local/cpanel/logs is not writable!

    The specific error was: Read-only file system at /usr/local/cpanel/Cpanel/LogCheck.pm line 29.


    Please rectify this problem and then try again.
     
  2. 24x7ss

    24x7ss Well-Known Member

    Joined:
    Sep 30, 2014
    Messages:
    271
    Likes Received:
    16
    Trophy Points:
    18
    Location:
    India
    cPanel Access Level:
    Root Administrator
    Twitter:
    As per the mentioned error it seems that your server is in read only mode because of that cpanel is unable to write logs file. Just simple try creating file on server it will give "Read Only File System Error".

    In this case check which disk partition is in read only mode and try to run fsck on that. If single partition is there then first boot the server in single user mode and then run fsck on that partition this will fix your issue.

    fsck -Cy /dev/sdaX
     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    648
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Please consult with your system administrator or data center to help determine why the /usr partition is in read-only mode. It's possible the filesystem is corrupted, or there are hardware issues that need to be resolved. Please use caution if proceeding with the instructions in the previous post. You risk further issues if FSCK fails to complete successfully.

    Thank you.
     
Loading...

Share This Page