"Read-only file system" after some working time.

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post please read how to get help
User avatar
unixlover0
Level 1
Level 1
Posts: 13
Joined: Thu Sep 13, 2012 1:52 pm

"Read-only file system" after some working time.

Postby unixlover0 » Mon Feb 04, 2013 2:35 pm

Hello, forum mates!
I'm very grateful for your previous help, but after some time of using Mint 13 x32 Cinnamon, I have a very strange error, with a writing permission even on a Home directory! Maybe this started after an electricity problem (my PC turned off unsafelly and fast).
Bellow some errors.
First error (on recovery mode):

Code: Select all

"Unexpected inconsystency; run fsck manually"


Code: Select all

In recovery mode I have next message (but only if I use 'clean', 'dpkg', 'fsck', 'grub' and 'network' option:
"Continuing will remount your / filesystem in read/write mode and mount any other filesystem defined in /etc/fstab.
Do you want to continue?
<Yes> <No>"


When I try "Clean" on "Recovery mode":

Code: Select all

mountall: fsck / [14] terminated with status 4
mountall: Filesystem has errors: /
mountall: Skipping mounting / since Plymouth is not available fsck from  util-linux 2.20.1 /dev/sda8filesystem contains errors... fsck


If I run any Linux/Unix command:

Code: Select all

$ <anycommand>
<anycommand>: cannot (...) : Read-only file system

(this often happens after running StuntRally from Desura).

If I try to create any file/document or a new folder:

Code: Select all

Error while creating file Untitled Documnet.
There was an error creating the directory in  /home/user_name/Desktop
>Show more details
Error opening file '/homeplayer/Desktop/Untitled Document': Read only file system
<Cancel> <Skip>


Some times after Reboot:

Code: Select all

The disk ... /tmp not ready or present
F to atempt to fix or S to skip

(or /)

Code: Select all

$ sudo fsck -Ap
/dev/sda8: recovering journal
/dev/sda8: Clearing orphaned inode

Also after every log in I'm waiting about a minute on black screen before I see my Desktop. I think the boot its slower now.
Maybe those errors appeared after I used Ctrl+Alt+Del or after power off.

I don't know what more I can add to my error description. Please help me and tell me what can I do to fix that. If you need more description or command answers or log, please ask me.

User avatar
viking777
Level 14
Level 14
Posts: 5137
Joined: Mon Dec 01, 2008 11:21 am

Re: "Read-only file system" after some working time.

Postby viking777 » Tue Feb 05, 2013 11:51 am

That doesn't sound good.

You will need to use a second distro if you have one, or a live cd/recovery cd if you don't, to run the command

Code: Select all

sudo fsck -fp /dev/sd??


Where ?? is the drive letter of your mint partition eg. /dev/sda1. If you have a separate home partition run the same command on that.

This will force a file system check and repair any errors. You have to do it from a second distro or live cd because partitions cannot be mounted when they are being checked.
Fujitsu Lifebook AH532. Intel i5 processor, 6Gb ram, Intel HD3000 graphics, Intel Audio/wifi. Realtek RTL8111/8168B Ethernet.Lubuntu 13.10,Ubuntu12.10 (Unity), Mint16 (Cinnamon), Manjaro (Xfce).

User avatar
unixlover0
Level 1
Level 1
Posts: 13
Joined: Thu Sep 13, 2012 1:52 pm

Re: "Read-only file system" after some working time.

Postby unixlover0 » Tue Feb 05, 2013 2:41 pm

Hello viking777!
I tried (from a Live USB):

Code: Select all

$ sudo fsck -fp /dev/sda8

fsck from util-linux 2.20.1
/dev/sda8: Inodes that were part of a corrupted orphan linked list found. 

/dev/sda8: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
   (i.e., without -a or -p options)

Then I tried without -p option:

Code: Select all

$ sudo fsck -f /dev/sda8
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes

Inode 794788 was part of the orphaned inode list.  FIXED.
Inode 794824 was part of the orphaned inode list.  FIXED.
Inode 795015 was part of the orphaned inode list.  FIXED.
Inode 795084 was part of the orphaned inode list.  FIXED.
Inode 795127 was part of the orphaned inode list.  FIXED.
Inode 795169 was part of the orphaned inode list.  FIXED.
Inode 796419 was part of the orphaned inode list.  FIXED.
Inode 820282 was part of the orphaned inode list.  FIXED.
Inode 841233 was part of the orphaned inode list.  FIXED.
Inode 841235 was part of the orphaned inode list.  FIXED.
Inode 842569 was part of the orphaned inode list.  FIXED.
Inode 843724 was part of the orphaned inode list.  FIXED.
Inode 843726 was part of the orphaned inode list.  FIXED.
Inode 843733 was part of the orphaned inode list.  FIXED.
Inode 843753 was part of the orphaned inode list.  FIXED.
Inode 843771 was part of the orphaned inode list.  FIXED.
Inode 844724 was part of the orphaned inode list.  FIXED.
Inode 844726 was part of the orphaned inode list.  FIXED.
Inode 844744 was part of the orphaned inode list.  FIXED.
Inode 844761 was part of the orphaned inode list.  FIXED.
Deleted inode 2883616 has zero dtime.  Fix<y>?
Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes

Inode 2883665 was part of the orphaned inode list.  FIXED.
Inode 2883672 was part of the orphaned inode list.  FIXED.
Inode 2883675 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -5722350 -(6616796--6616798) -(6770062--6770067) -(6770082--6770083) -(6788652--6788653) -(6789639--6789641) -(6789675--6789680) -(6921035--6921037) -(6921068--6921074) -(6921077--6921086) -(6921148--6921159) -(6934648--6934653) -(7005713--7005715) -(8160793--8160794) -(9611264--9613311) -(9615360--9617288)
Fix<y>?
Free blocks count wrong for group #174 (3891, counted=3892).
Fix<y>?
Free blocks count wrong for group #201 (1229, counted=1232).
Fix<y>?
Free blocks count wrong for group #206 (5783, counted=5791).
Fix<y>?
Free blocks count wrong for group #207 (7224, counted=7235).
Fix<y>?
...

/dev/sda8: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda8: 450627/3301376 files (0.3% non-contiguous), 11291548/13183488 blocks

Is now my operating system and/or file system fixed or not? What should I do next?
Thanks in advance!
==
After reboot, I launched Steam Ubuntu version and were playing "Tiny and Big: Grandpa's Leftovers". After some time, the game begin stopping and then it stopped and the HDD led turned off. After few seconds HDD led turned on (but it wasn't blinking, like normally) and the game still freezed. I think FSCK didn't helped at all :(

User avatar
viking777
Level 14
Level 14
Posts: 5137
Joined: Mon Dec 01, 2008 11:21 am

Re: "Read-only file system" after some working time.

Postby viking777 » Wed Feb 06, 2013 6:06 am

If it only happens when you are using Steam then that is probably to do with Steam, not Mint. Just use your machine without running Steam for a while, if that is OK then it is probably Steam that is causing the problem.

You can always run fsck again from your live usb, if it reports no further errors then the file system is fixed, at least as far as fsck is concerned (and it doesn't usually get things wrong). If it reports further errors then either the power outage you suffered has caused permanent damage to your hard drive or your machine is overheating under load. Those are my two guesses anyway.

If it is a disk problem you should open the 'disks' program from the menu, select the correct disk, then click on the cog icon on the top right of the gui. This will open a 'Smart Data' window with the latest 'Smart Attributes' listing many properties of the drive including temperature. Any faults listed there? You can start a new self-test from that window as well to get up to the minute information.
Fujitsu Lifebook AH532. Intel i5 processor, 6Gb ram, Intel HD3000 graphics, Intel Audio/wifi. Realtek RTL8111/8168B Ethernet.Lubuntu 13.10,Ubuntu12.10 (Unity), Mint16 (Cinnamon), Manjaro (Xfce).

User avatar
catweazel
Level 7
Level 7
Posts: 1668
Joined: Fri Oct 12, 2012 9:44 pm

Re: "Read-only file system" after some working time.

Postby catweazel » Wed Feb 06, 2013 6:48 am

viking777 wrote:If it only happens when you are using Steam


It's either a kernel bug or a drive firmware problem, and nothing to do with Steam.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354
Mint Testing Team & Mint Donor #3606

User avatar
unixlover0
Level 1
Level 1
Posts: 13
Joined: Thu Sep 13, 2012 1:52 pm

Re: "Read-only file system" after some working time.

Postby unixlover0 » Sat Feb 09, 2013 3:28 pm

Hello guys!
Thank you very much for your answers and sorry for my answer delay.

I tested more how is happening. So, when I where playing the Ubuntu version of Steam - Tiny and Big, read- only error were happening. Also, if I was playing on Desura Stuntrally 1.8. Others games from Steam (Serious Sam 3) and Desura (CoreBreach, Helena The 3rd and Vrtigo) were not causing this annoying error. I will keep testing which software is causing that.
I have tested my hdd for bad blocks and S.M.A.R.T. test by using a program called Victoria. There is all OK with my disk. Also I used the program called "Disk Utility" (Menu>Accessories>Disk Utility). SMART test was good too - "Disk is healthy", temperature is good on Windows and Mint (about 31* C/88* F), only if I'm playing a modern "hard" graphics game the temperature is about 37* C and the game begins to freez.
I tried $ sudo fsck -As and $ sudo fsck -fp (I guess), but not worked. So, I have run GParted, and selected my problem partition after next error. I selected from Menu, Check option of my /dev/sda8 - it used a command

Code: Select all

e2fsck -f -y -v /dev/sda8

Code: Select all

File system check on "54 GB Filesystem" (Partition 8 of Partition 2 of ATA ST3500418AS) completed
File system is clean.
<Close>

I checked for bad blocks (all is OK):

Code: Select all

$  sudo badblocks -v /dev/sda8
Checking blocks 0 to 52733951
Checking for bad blocks (read-only test):   0.00% done, 0:00 elapsed. (0/0/0 errdone                                                 
Pass completed, 0 bad blocks found. (0/0/0 errors)


But if I launch again any "problematic" software, this read permission error repeats again. If I not fix it, after next boot on screen appear a message saying something about "there are errors on '/' press F to fix, S to skip M for manual fixing". When I press F, it beggin to fix and appear other error saying "there is no /tmp folder" or something...
I don't want to reinstall this system.
Also I read that information about kernel bugs (thanks @TehGhodTrole). I have 3.2.0-35 and 3.2.0-23 kernels and both have now this problem, but only if I run some games (not all), maybe other soft is causing this too, but I didn't found it yet. I leave my PC on for 24 hours or more downloading from internet, but no error for now. So, I don't know, what is the problem?

User avatar
unixlover0
Level 1
Level 1
Posts: 13
Joined: Thu Sep 13, 2012 1:52 pm

Re: "Read-only file system" after some working time.

Postby unixlover0 » Sun Feb 10, 2013 3:47 pm

If I'm not wrong, a kernel upgrade (3.2.0-35-generic to 3.2.0-37-generic). I need to test more, because now CS Source from Steam Ubuntu, is not dropping a game to Desktop with a "read-only" fs error, now it is hanging (freezing) on black screen with a console cursor and a red light (not blinking) on hdd LED.


Return to “Other topics”

Who is online

Users browsing this forum: No registered users and 2 guests