Recover from emergency mode on Centos 7

 CentOS 7 may enter emergency mode if there are issues with the file system or the system fails to boot correctly. To recover from emergency mode, you can follow these steps:


1. **Check the File System**:


   First, you need to check the file system for errors. Run a file system check (fsck) on the root file system:


   ```bash

   fsck /dev/mapper/centos-root

   ```


   Replace `/dev/mapper/centos-root` with the appropriate device for your root file system. You can find this information by running `lsblk` or `df -h`.


2. **Remount the File System**:


   After running `fsck`, remount the file system in read-write mode:


   ```bash

   mount -o remount,rw /

   ```


3. **Check Disk Space**:


   Verify that you have enough disk space. Use `df -h` to check the available disk space on your partitions.


4. **Examine Journal Logs**:


   Check the systemd journal logs to identify any errors:


   ```bash

   journalctl -xb

   ```


   This command will display recent system logs, and you can scroll through them to look for any errors that might have caused the system to enter emergency mode.


5. **Fix the Issue**:


   Based on the error messages and logs you find, take appropriate actions to fix the issues. This might include fixing configuration files, resolving disk space problems, or repairing file system errors.


6. **Reboot the System**:


   Once you have fixed the issues causing the emergency mode, you can try to reboot your system:


   ```bash

   reboot

   ```


   Your system should attempt to boot normally. If you've addressed the underlying problems, it should boot successfully.


If the issue persists or you're unable to fix the problems, consider seeking professional help or consulting your system administrator. Additionally, take necessary backups before making any major changes to your system.

Comments

Post a Comment

Popular posts from this blog

bad character U+002D '-' in my helm template

 In Helm templates, the hyphen character (`-`) can sometimes be treated as a reserved character, particularly when defining values or labels. To include a hyphen character in a Helm template without issues, you can use one of the following approaches: 1. **Quoting the Hyphen:**    You can enclose the hyphen in double quotes, like this:    ```yaml    key: "-"    ```    This way, Helm will interpret the hyphen as a string rather than an operator. 2. **Using Backticks:**    If you need to use the hyphen within a Go template function or inside backticks, you can escape it with a backslash (`\`), like this:    ```yaml    value: `{{ .Values.someField | printf "%s \\-" }}`    ```    The backslash prevents Helm from interpreting the hyphen as a special character. 3. **Variable Assignment:**    Assign the value to a variable and use it. For example:    ```yaml    {{- $hyphen := "-" }}    key: {{ $hyphen }}    ```    This way, you can use the variable `$hyphen` wher
Read more

GitLab pipeline stopped working with invalid yaml error

 When your GitLab pipeline has stopped working with an "invalid YAML" error, it means there's a problem with your `.gitlab-ci.yml` file. This could be due to syntax errors, incorrect indentation, or other issues in your pipeline configuration. Here's how to troubleshoot and resolve this issue: 1. **Check for Syntax Errors**:    Carefully review your `.gitlab-ci.yml` file for any syntax errors. Common issues include missing colons, indentation problems, or mismatched quotation marks. Use a YAML linter or an online YAML validator to identify and correct syntax errors. 2. **Indentation**:    YAML relies heavily on proper indentation. Make sure that all lines within the same block have consistent indentation (typically using spaces, not tabs). Incorrect indentation can cause YAML parsing errors. 3. **Dashes and Lists**:    Ensure that you use the correct syntax for lists (arrays) in YAML by starting each item with a dash (`-`). Be consistent with your use of dashes throug
Read more

How do I add a printer in OpenSUSE which is being shared by a CUPS print server?

 To add a printer in openSUSE that is being shared by a CUPS print server, you can use the following steps: 1. **Ensure CUPS Client is Installed:**    Make sure your openSUSE system has the CUPS client tools installed. You can install them using the following command:    ```bash    sudo zypper install cups-client    ``` 2. **Discover Available Printers:**    Use the `lpinfo` command to discover available printers on your CUPS print server. Replace `cups-server-hostname` with the hostname or IP address of your CUPS server:    ```bash    lpinfo -v -h cups-server-hostname:631    ```    This command should list the printers shared by the CUPS server. 3. **Add a Printer:**    Use the `lpadmin` command to add a printer. Replace `printer-name` with the name of the printer you want to add and `printer-uri` with the URI obtained from the `lpinfo` command:    ```bash    sudo lpadmin -p printer-name -E -v printer-uri    ```    For example:    ```bash    sudo lpadmin -p MyPrinter -E -v socket://cu
Read more