Linux Mount Read Only File System Error

El encounter errors while using your distribution favorite tin can be not only a hurting in the chest, but a headache when you have no idea what's going on and why information technology is happening to you.

Although this "Read-simply file system" message has already happened to me several times, causing me to lose my head and, in a higher place all, I ended up having to reinstall my entire system, because when performing some action through the terminal, it displays this message.

The commencement thing we keep to exercise is restart the reckoner, which leads the states to the fact that when we showtime it, the system but does not showtime the graphical server and we receive the famous black screen:

"BusyBox v* multi-call binary   (initramfs)"          

Where many cease up deserting and reinstalling the system.

Merely what we must do is avoid restarting the arrangement, This is the about recommended considering while we are inside, as the bulletin indicates, the arrangement is only in read mode and then we cannot record anything in the system.

Table of Contents

• 1 The trouble
• 2 Solutions

The problem

The first step is to try to place the fault and search the network while nosotros are inside the system, information technology is easier and above all to effort to remember what led u.s.a. to it.

Although the nearly common thing you can find on the net, is that the arrangement protects itselfSince the disk you are using is no longer optimal for storing data.

What information technology turns out is that it just goes into read mode and so information technology just allows united states to admission the information, only without instead it does non let united states of america to make changes within it.

For me, this is unusual, because I have but been with a new deejay for a few weeks and reviewing the SMART data and sectors, information technology is not possible that it is already in bad status.

Since personally I did not agree that my deejay was already in the last, the first matter I decided to exercise is to clean my hardware, for that of some particle that is interfering with its operation.

I started my team again and I got the same result.

Solutions

The next matter I did was alter deejay cablesIn my example SATA, I have known that the classic red cables tend to be damaged very quickly either by high temperatures or by some doubles.

This solution was useful to me.

In another case it is at the software level so we have to do is identify which is the partition that happened to "Read-merely file system".

In the best of cases, if it is a dissimilar division than where your system is located, you lot have the upper hand, since you lot have the facility to be able to mountain and unmount said partitioning without problems.

For this We can apply the terminal and execute the following commands, where nosotros volition start place the partition's mount point and then proceed to remount it with read and write permissions:

sudo fdisk -50          

Once the partition is identified, we remount it, where / sdXx will be the mount betoken, it can be / sdb1 or / sdc, etc.

mount -o remount,rw /dev/sdXx          

Si your organisation partition was the 1 that was protected, applying this command will non piece of work for y'all, so we must utilize the following:

mount -o remount /          

If yous keep getting the same mistake, we tin can cull to run the following:

sudo fsck -Af -M  sudo reboot

What it volition do is bank check file organisation and try to make the corresponding corrections.

Hither we must write down the blocks that are going to unfold u.s. that have errors, in my case I brandish something like this:

Free blocks count wrong for group #190 (102254, counted=102258). Fix? yes Complimentary blocks count wrong for group #629 (1558554, counted=1558555).  Ready? yes Free blocks count wrong for group #1558658     Fix? Yep          

Where we will endeavour to repair them:

sudo fsck -b 102254 /dev/sda1 -y          

In the latter instance, nosotros must access the advanced options of our system from Chow and perform an fsck.

The content of the article adheres to our principles of editorial ideals. To report an fault click hither!.

davenportbiles1978.blogspot.com

Source: https://www.linuxadictos.com/en/solution-to-the-read-only-file-system-error.html