System automatically turning into read-only mode

dashingdon · 2017-07-05 12:33:29

Long time user of CB and then BL. This new issue is driving me crazy as I can not find any explaination. Hope someone can explain the issue and possible solution.

After I boot the os , for some unknown period of time os works fine and then suddenly goes into the read only mode. Every command starts throwing input/output error and then hard reboot is the only option. I have tested all hardware including SSD hard drive and everything is fine. I am trying to avoid re-installation if I can. same laptop was running CB and BL before with no issues. This all started after the latest update which included kernel.

So far, I have already updated SSD firmware and laptop bios to the latest version.

Insallation details.

Distributor ID:	BunsenLabs
Description:	BunsenLabs GNU/Linux 8.7 (Hydrogen)
Release:	8.7
Codename:	bunsen-hydrogen

Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux

Thanks in advance for the help.

-dash

Here is an example error message after sudo apt-get update

E: Couldn't create temporary file to work with /var/lib/apt/lists/httpredir.debian.org_debian_dists_jessie_Release - mkstemp (30: Read-only file system)

Last edited by dashingdon (2017-07-05 15:20:09)

Steve · 2017-07-05 13:07:24

Arch linux has a detailed wiki on ssd.
https://wiki.archlinux.org/index.php/Solid_State_Drives

Debian as well.
https://wiki.debian.org/SSDOptimization

I plan to use ssd one day so i hope you solve this issue. Just posted some links in the hope they may help, i cant say i know what the error is that you have though.

iMBeCil · 2017-07-05 14:55:56

dashingdon wrote:

Here is an example error message after sudo apt-get update
E: Couldn't create temporary file to work with /var/lib/apt/lists/httpredir.debian.org_debian_dists_jessie_Release - mkstemp (30: Read-only file system)

Please, post output of following commands:

$ df -h
$ lsblk

(I suspect, you are running out of space on your disks.)

Last edited by iMBeCil (2017-07-05 14:56:05)

dashingdon · 2017-07-05 15:03:19

iMBeCil wrote:

Please, post output of following commands:
$ df -h
$ lsblk
(I suspect, you are running out of space on your disks.)

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       451G  147G  281G  35% /
udev             10M     0   10M   0% /dev
tmpfs           3.1G  9.2M  3.1G   1% /run
tmpfs           7.8G   11M  7.7G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
tmpfs           1.6G  4.0K  1.6G   1% /run/user/108
tmpfs           1.6G  8.0K  1.6G   1% /run/user/1000

$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   477G  0 disk 
├─sda1   8:1    0 457.6G  0 part /
├─sda2   8:2    0     1K  0 part 
└─sda5   8:5    0  19.3G  0 part [SWAP]
sdb      8:16   0 465.8G  0 disk 
└─sdb1   8:17   0 465.8G  0 part 
sdc      8:32   1   3.9G  0 disk 
├─sdc1   8:33   1   855M  0 part 
└─sdc2   8:34   1   704K  0 part

Could it be related to power management ? I am observing this behavior after I connect the power. As long as I am on battery , computer behaves normal.

---Mod edit: Please use [ code ] tags for terminal output ---

Last edited by damo (2017-07-05 15:17:06)

damo · 2017-07-05 15:18:59

Do you have the same problem if you boot to the old kernel (choose from the submenu in the grub boot screen)?

dashingdon · 2017-07-05 15:23:20

damo wrote:

Do you have the same problem if you boot to the old kernel (choose from the submenu in the grub boot screen)?

I did not see the old kernel to boot with. When I reboot it next time, I will try again. For now ,I have disabled all power management functions and connected to the power. I will update my findings as soon as possible.

Thanks for the help.

-dash

dashingdon · 2017-07-05 16:01:23

Steve wrote:

I plan to use ssd one day so i hope you solve this issue. Just posted some links in the hope they may help, i cant say i know what the error is that you have though.

Thanks Steve. I have been using SSD for quite a while without any issues.Overall performance is great with SSD. Go for it when you can.

Horizon_Brave · 2017-07-05 16:56:31

I believe you could also try booting from a live CD and see if you still get the same read write errors.

Can you not open up files or programs during this state? What do the permissions of random files look like when you enter this state?

DeepDayze · 2017-07-05 20:19:11

What about the general health of the device?

dashingdon · 2017-07-06 05:17:08

Horizon_Brave wrote:

I believe you could also try booting from a live CD and see if you still get the same read write errors.
Can you not open up files or programs during this state? What do the permissions of random files look like when you enter this state?

When I reach to that state , every action results into input/output error. Only way I can recover from it is to hard reboot. I used live boot to run fsck on sda but did not test the behavior. Thanks for the pointer.

DeepDayze wrote:

What about the general health of the device?

Overall device health is good. I ran every possible hardware test and all came negative. OS had no issues in the past.

Update : It seems like

 SSD + New Kernel : 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) + Suspend / Hibernate in power management

is possible root cause.Since I disabled power management functions 12+ hours ago , I did not observe the read-only system issue. Power management settings worked fine prior to the update.

I will continue to monitor and update my observations. At this point, os is working as expected with power management functions disabled. Thanks all who offered the help.

-dash

Last edited by dashingdon (2017-07-06 05:18:33)

damo · 2017-07-06 05:43:08

So did you try booting the previous kernel like I suggested?

dashingdon · 2017-07-06 05:57:42

damo wrote:

So did you try booting the previous kernel like I suggested?

I dont see the option. It shows two options with 3.16.0-4-amd64 and recovery mode. No other kernel version is available to boot with. Is there a way to attach picture here?

http://picpaste.com/IMG_20170706_112358-UHOloA87.jpg

Last edited by dashingdon (2017-07-06 06:35:59)

Head_on_a_Stick · 2017-07-06 06:51:47

This may be worth an upstream bug report if it can be reproduced in pure Debian, the Stack Clash fixes could have broken several things.

Head_on_a_Stick · 2017-07-06 07:10:49

You can boot from /vmlinuz.old to check if the old kernel works.

Add this snippet to the end of /etc/grub.d/40_custom (do not overwrite the file):

menuentry 'Old kernel' {
    set root=(hd0,1)
    linux /vmlinuz.old root=/dev/sda1 ro
    initrd /initrd.img.old
}

Then run `sudo update-grub` to generate the new entry.

martix · 2017-07-06 11:11:31

An other option might be: In the boot folder check the vmlinuz files for older versions. In grub.cfg change the appropriate version numbers for the vmlinuz and initrd lines (make sure to have a grub.cfg backup or simply change back the numbers afterwards).

As for pictures: Check the site scrot.moe and copy&paste the links for thumbnails.

#1 2017-07-05 12:33:29

System automatically turning into read-only mode

#2 2017-07-05 13:07:24

Re: System automatically turning into read-only mode

#3 2017-07-05 14:55:56

Re: System automatically turning into read-only mode

#4 2017-07-05 15:03:19

Re: System automatically turning into read-only mode

#5 2017-07-05 15:18:59

Re: System automatically turning into read-only mode

#6 2017-07-05 15:23:20

Re: System automatically turning into read-only mode

#7 2017-07-05 16:01:23

Re: System automatically turning into read-only mode

#8 2017-07-05 16:56:31

Re: System automatically turning into read-only mode

#9 2017-07-05 20:19:11

Re: System automatically turning into read-only mode

#10 2017-07-06 05:17:08

Re: System automatically turning into read-only mode

#11 2017-07-06 05:43:08

Re: System automatically turning into read-only mode

#12 2017-07-06 05:57:42

Re: System automatically turning into read-only mode

#13 2017-07-06 06:51:47

Re: System automatically turning into read-only mode

#14 2017-07-06 07:10:49

Re: System automatically turning into read-only mode

#15 2017-07-06 11:11:31

Re: System automatically turning into read-only mode

Board footer