General :: Root File System Is Mounted Read-only On Boot On Gentoo?
Sep 27, 2010
I am using Gentoo Linux and for a while now, the root file system is mounted read-only on booting. For obvious reasons, this is quite annoying as most services do not start up correctly (I do not use a separate file system for /var). After the system is up, I have to log in, remount the root file system read-write, fix /etc/mtab, mount all other file systems in from /etc/fstab and then start up all the missing daemons. I know that there are ways to make a system run properly with a read-only file system, but I would rather restore the old behaviour of a writable root file system.
The strange thing is that after running mount / -o remount,rw, the file system is mounted in writable mode without any errors. I suspected some problem with fsck, but now I have disabled automatic file system checks on the partition (tune2fs -c0 -i0).When I run dmesg, only these lines mention the partition at all, although I am not sure if not something gets lost because /var/log is not writable:
EXT3-fs (sda5): mounted filesystem with writeback data mode</code>
EXT3-fs (sda5): using internal journal
The line in /etc/fstab looks like this:
I have a 9.04 64bit Ubuntu server that I use for a home file server and for downloading duties, every few days the root filesystem gets remounted as read only, usually requiring a reboot and fsck to get everything running again. The box is tucked away in the roof space to keep the noise down so it's a bit of a pain to keep pulling it out to get console access.troubleshoot what might be causing this?/ is on a raid 1 array on 2 8GB usb sticks last few lines of DMESG EXT3-fs error (device md3): ext3_journal_start_sb: Detected aborted journal
Code: [632280.290419] journal_bmap: journal block not found at offset 23180 on md3 [632280.290470] Aborting journal on device md3.
For my project, it's absolutely necessary to have a read-only root partition system. I have a writable /opt/project partition.But, I also need to start x server. startx This tries to write to some temporary files and fails as / is readonly. Is there any how-to on how to move this temporary files to the writable portions of the file system.
I have an ntfs partition that I wish to access as a normal user(non-root). For this I did the following. As root I created a folder /windows and did a chmod 777 -R on /windows. Then I added the following line to /etc/fstab
Now, the partition is mounted alright but the problem is that when any other user (non-root) creates a files in /windows (say by executing touch newfile) the newly created file has the owner and group set as root. The non-root user can create the file and he can also delete the file, however, he cannot change the permissions of the file and also the owner:group is always set as root:root. How do I get across this problem, i.e. how do I mount a partition, so that a non-root user can also change the permissions and ownerships of the files he creates.
Remember back in the days of MS-DOS, a file could have 4 different attributes: archive, read-only, hidden, system. As you know, MS-DOS didn't have any user rights or privileges. Files had no owner. If you were at the command line, you could do whatever you wanted, you could change or delete any files you wanted to... so long as they weren't read-only. Under MS-DOS, if you had a read-only file and tried to delete it, you would get an error saying "Cannot delete read-only file". There was a simple remedy to this, just turn off the read-onlyness:
attrib -r hello.txt
The point I'm trying to make here is that even though you had full permissions over the file, you still had to turn off its read-onlyness before you could make a change. Well I'm trying to do something similar in Linux. Under Linux, the root user has full permissions over every file. But I need to make a particular file read-only so that not even the root user can alter it. I have a few programs on my computer that need to be run as root because they do some low-level networking (raw sockets and the like), and these programs alter my "/etc/resolv.conf" file. Well I need to find a way of making my "/etc/resolv.conf" file READ-ONLY, even for the root user. It doesn't seem as though the Linux filesystem provides a means of doing this, reason being that the root user will always be able to alter any file it wants to. I was thinking though... there's some way I could turn my "/etc/resolv.conf" file into a virtual file of some sort, like maybe I could use some sort of mount program to mount the file as read-only... ?
I downloaded Gentoo and burnt it on CD.I did boot the livecd and the system passed starting stage and it recognised my hardware. After that, there islivecd login prompt, and obviously I tried to use root and no password but it says login incorrect. This is what I did:
Code: livecd login: root Password: [hit enter here]
I was installing "wine" last night and since I knew it was going to take a while I closed the lid of the laptop and turned it upside down on the floor. (I always turn the laptop upside down when not using it otherwise might overheat)When I woke up this morning roughly 8 hours after I went to sleep the machine was turned off.Using the "last -x | grep shutdown | head -1" it stated that it went down at roughly 6 hours from when I went to sleep.The program I was installing got finished installing but I never set up an auto-shutdown program or anything of the sort.If this isn't a problem with linux then its a problem with my bios. If its a problem with my bios I will just have to live with it because my bios is locked. /var/log/messages says this:
Code: alexslaptop logger: ACPI event unhandled: battery BAT1 00000080 00000001 alexslaptop shutdown: shutting down for system halt
I bought a new SD card which I intend to put some MP3s on - except that I can't write to it because it tells me the destination is Read Only. No-probs thinks I: I'll just reformat it.
"Error creating file system: helper exited with exit code 1: cannot open /dev/mmcblk0p1: Read-only file system"
Various chmod commands all result in Read-only file system. I tried umount then mount commands, but it couldn't find it to mount once I'd unmounted it using the same /media/ file path (I assume it's the only one).
My Redhat Enterprise Linux 4 with 6x partitions (/, /boot,/home, /usr, /var, /tmp) of 6.0 GB IDE Hardisk was working quite fine. I decided to create LVM on /home and /var partitions but due to some errors occured and I delete the /home partitions. That's why partition table altered. I then delete 4,5,and 6th partitions (/home, /var, /tmp) partitions and now try to create one by one but following error is coming:-
The Super block could not be read or do not describe a clear ext2 file system. E2fsck b 8193 <device> I have tried following commands,but could not successful:- e2fsck -p /dev/hda7 (where hda7 was created but afterthat it was deleted) e2fsck -a /dev/hda7
I made a modification to the /etc/fstab using Ubuntu 10.04 and now it wont boot correctly. I can get the cli but when I enter /etc/fstab and make an edit it says" changing permission of /etc/fstab: read only file system" This is what I get when the system boots:
so if I choose manual I get to the cli and whenever I attempt to edit the file I get the above error. I used another machine and attempted to mount the drive but I get the same error I added notaime option to my fstab by accident so if I choose manual I get to the cli and whenever I attempt to edit the file I get the above error. I used another machine and attempted to mount the drive but I get the same error. I tried
and I get
How can I mount the partition so that I can edit it?
I work for a company that makes portable devices running Linux and I was recently asked to make the underlying file system read-only for "security" purposes. Since the distribution is based on LinuxFromScratch, I know that very little writing happens at run time. So, even if the device runs on a usb flash device, I doubt that putting the root file system RO will be that beneficial. I am actually more concerned about a process actually breaking because it cannot open a file in RW mode than a process going rogue and filling the root file system with log files, etc. I'd really like to ear what kind of advantages disadvantages there really is with read-only file-systems.
I have a computer in the university and I have root access to this pc. Iam trying to install Cblas library on it. But it gives me a starnge error /usr/local/atlas is read only file system. I tried doing mount -l and it gave me that appserver1:/export/d1/Linux/doe on /usr/local type nfs4 (ro,sec=.......) I think what it means that the main server directory is mounted to /usr/local and it is read only. So, how can I fix this problem to separate the two and make my /usr/local separate
Does anyone know why files in my /tmp directory are not able to rm even using root login? not only that, I can't even chmod or do anything to files in /tmp directory... it always saying "read only file system" warning
I am working on a light version of linux for no particular reason other than to see how small I could make it. I was wondering if INIT was necessary, or if I could perform all of the INIT-related tasks (fsck, unmounting, etc) by hand/bash scripts?
I do not need multi-user functionality (Or much of anything for that matter). I started off with a Gentoo base 2.0.2 Install with kernel 2.6.38.
What are the possible problem when Windows access the file from Ubuntu got Read Only even though have a full permission to read, write and execute the file? Ubuntu to Ubuntu accessing the file there is no problem only Windows got a problem.
Every time I mount one partition manually as read write it works fine for a couple of minutes before reverting to read only. It still appears as read-write when I list the mounted directories but won't let me write to it. I have tried unmounting and remounting it, but after a few minutes it always ends up as read-only again.
$ mount /dev/sda3 on /scratch type ext3 (rw) $ mkdir /scratch/file
Have just assembled a new computer and thought I would install the 64 bit version of openSUSE 11.2 in a "Windows free zone". After a hiccup or two I have managed to get a system of sorts running but on trying to copy files from my old computer(via a memory stick) it tells me that Vfat is an unknown file system.On my old computer I am running 32 bit openSUSE 11.2 as a dual boot system with Windows XP and have no problems moving files between the two different file systems.Is it possible to get a 64 bit file system to read 32 bit file system drives and if so how do I do it?
I am using Slackware 13 x86_4. I have it set so that when I close my lid, it suspends to RAM. When I open my lid, it asks for password, but after I enter it, it freezes. I force KDE down by Ctrl+Alt+Backspace then read the errors. It says:
xauth: error in locking authority file /home/ridwan/.Xauthority rm: cannot remove '/home/ridwan/.serverauth.3457': Read-only file system
When I try to startx again, it says
/usr/bin/startx: line 158: cannot create temp file for here document: Read-only file system /usr/bin/startx: line 174: cannot create temp file for here document: Read-only file system /usr/bin/startx: line 174: cannot create temp file for here document: Read-only file system
It forces me to power off the laptop by holding down the power button. When I try ctrl+alt+delete, I get an error saying "can't execute from /sbin/shutdown/"
I administer a remote server via SSH that runs CentOS 5.5. I have been unsuccessful in all my attempts to write to two different external USB hard drives with a single ext3 partition when logged in as root.
When attempting to create a "test" directory I get one of two messages:
Both drives *appear* to have filesystem issues. When I run an fsck on either drive, I get:
Keep in mind this is a newly-formatted, empty drive.
Not putting stock in the odds that I've had two hard drives (different sizes and brands) with the exact same hardware problem, I'm going to assume this is a software issue, although maybe it isn't. Hence, my post in "Linux - General". I've heard talk elsewhere of controller (chipset) issues coming into play. Is this valid?
Okay, here's the information you'll need to make a diagnosis....
Here's the output of a "df -h" command:
Here's the contents of my /etc/fstab:
Here's the output of "cat /etc/mtab":
Here's the output of a mount command:
Here's the output of fdisk on the device in question:
The number of cylinders for this disk is set to 48641.
There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
I've got someone with access to the box if necessary. But it might take days to implement solutions since this isn't his full-time job. Remote solutions are, therefore, preferable.
I want to simply mount an ext4 file-system onto a normal mount point in Ubuntu (/media/whereever), as read-writable for the current logged-in user, i.e. me.
I don't want to add anything into /etc/fstab, I just want to do it now, manually. I need super-user privileges to mount a device, but then only root can read-write that mount. I've tried various of the mount options, added it into fstab, but with no luck.
I bought a Western Digital 1TB external hard drive to use with a Gentoo build. It connected beautifully, mounted visibly but despite being mounted read/write any attempt to write to it produced the error "read-only file system". I chased a number of red herrings before I found that the drive comes with an NTFS filesystem and NTFS support in my kernel was set to read-only, which I think was a default setting. Simple fix was to install a different file system - as it was a new drive there was no old data to lose.