Linux Readonly Filesystem Error
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the linux going in read only workings and policies of this site About Us Learn more about Stack
How To Change Read Only File System In Linux
Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags
Ubuntu Read Only File System Usb
Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it
Read Only File System Error Android
works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to fix “sudo: unable to open … Read-only file system”? up vote 54 down vote favorite 14 The title might not be as descriptive as I would like it to be but couldn't come up with a better one. My read only file system android server's file system went into Read-only. And I don't understand why it does so and how to solve it. I can SSH into the server and when trying to start apache2 for example I get the following : username@srv1:~$ sudo service apache2 start [sudo] password for username: sudo: unable to open /var/lib/sudo/username/1: Read-only file system * Starting web server apache2 (30)Read-only file system: apache2: could not open error log file /var/log/apache2/error.log. Unable to open logs Action 'start' failed. The Apache error log may have more information. When I try restarting the server I get : username@srv1:~$ sudo shutdown -r now [sudo] password for username: sudo: unable to open /var/lib/sudo/username/1: Read-only file system Once I restart it manually it just start up without any warning or message saying something is wrong. I hope somebody could point me into the right direction to resolve this issue. filesystem restart read-only share|improve this question edited Feb 11 '14 at 13:47 Pro Backup 1,4672726 asked Oct 7 '12 at 15:41 John 4131411 I recommend to @John to change the answer to the last poste
here for a quick overview of the site Help Center Detailed answers to any questions you touch cannot touch read only file system might have Meta Discuss the workings and policies of this site cannot remount block device /dev/sda1 read-write, is write-protected About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting centos read only file system ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users http://askubuntu.com/questions/197459/how-to-fix-sudo-unable-to-open-read-only-file-system of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top read only root filesystem up vote 11 down vote favorite 4 Somehow my Debian went to http://unix.stackexchange.com/questions/145882/read-only-root-filesystem read only in root file system. I have no idea how this could have happened. For example when I am in /root folder and type command nano and after that press Tab to list possible file in that folder I get the message: root@debian:~# nano -bash: cannot create temp file for here-document: Read-only file system The same for the cd command when I type cd /home and press Tab to list paths I have this: root@debian:~# cd /home -bash: cannot create temp file for here-document: Read-only file system I also have problems with software like apt and others. Can't even apt-get update. I have a lot of errors like this: Err http ://ftp.de.debian.org wheezy-updates/main Sources 406 Not Acceptable W: Not using locking for read only lock file /var/lib/apt/lists/lock W: Failed to fetch http ://ftp.de.debian.org/debian/dists/wheezy/Release rename failed, Read-only file system (/var/lib/apt/lists/ftp.de.debian.org_debian_dists_wheezy_Release -> /var/lib/apt/lists/ftp.de.debian.org_debian_dists_wheezy_Release). W: Failed to fetch http ://security.debian.org/dists/wheezy/updates/main/source/Sources 404 Not Found W: Failed to fetch http ://security.debian.org/dists/wheezy/updates/main/binary-amd64/Packages 404 Not Found W: Failed to fetch http ://ftp.de.debian.org/debian/dists/wheez
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://unix.stackexchange.com/questions/174323/read-only-file-system-error-while-accessing-the-files-on-ubuntu the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux https://ubuntuforums.org/showthread.php?t=1968575 Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join read only them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Read-only file system error while accessing the files on Ubuntu up vote 2 down vote favorite 1 I have a Ubuntu machine. I am connected to it remotely and read only file getting the following errer: mkdir: cannot create directory `/testFolder': Read-only file system LIKE WINDOWS, REBOOTING the machine solved this error. Can someone explain this behaviour to me. I am bit surprised. ubuntu filesystems readonly share|improve this question edited Dec 15 '14 at 11:22 John WH Smith 6,41712343 asked Dec 15 '14 at 11:01 Tariq 111112 This question is impossible to answer sensibly without knowing what file system it is about you're trying to create your testFolder on. Consider that also NTFS partitions can be accessed from a Linux-type system... –syntaxerror Dec 15 '14 at 19:42 add a comment| 1 Answer 1 active oldest votes up vote 6 down vote A filesystem goes into read-only mode when it has consistency issues. It is a way to prevent possible data corruption. Your next would be to take a backup of all important data from this drive since this could also mean that the hard-drive could be on its way out. When you rebooted the machine, the / partition got mounted back in the regular rw mode from t
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support New to Ubuntu [SOLVED] Read Only File System Error Ubuntu 11.10 Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 2 of 2 Thread: Read Only File System Error Ubuntu 11.10 Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode April 29th, 2012 #1 Jugurtha View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Dec 2010 Location Algiers, Algeria. Beans 7 DistroUbuntu 10.10 Maverick Meerkat Read Only File System Error Ubuntu 11.10 Hello everyone, This is a solved issue, and this thread is just to record how it was .. I think it was after an update. I tried to compile a C program, and I had this error. Everything I did, basically triggered this error. I've looked different fora, I searched a lot.. and each solution proposed involved changing something that would trigger this error. (Goes the same for changing permissions, etc) Tinkering with Code: fstab , would trigger this error. sudo command would trigger it, etc... So, I tried to boot in recovery mode and chose "drop root" and I basically got the same error. Then, from the grub menu .. I tried "Previous Linux versions" and chose the oldest release in recovery mode .. Then drop root.. Then : Code: fsck -As The rest is basically just hitting "Y" to let it "repair" the file system. Then rebooting and voilą The rest is just updating and upgrading: Code: sudo apt-get update Code: sudo apt-get upgrade Maybe cleaning , etc..