I simply chose the kernel with recovery mode option and pressed e to modify the boot parameter from ro to rw. I'm not sure if it will solve your problem though, good luck. Thanks, Colleen He means this way to change the kernel parameters when booting (https://help.ubuntu.com/community/Grub2#Editing Menus During Boot). The kernel the executes the 'init' process and during this the fstab is read and the filesystem is remounted read-write. http://ibuildsystem.com/ubuntu-cannot/ubuntu-cannot-unmount-usb.php
This looks perfectly sensible when switching between different RW modes, whereas when switching from RO to RW (that means: with a "cold" journal, that might have been replayed but definitely NOT It always worked for me. Even if its not my main data volume, I like the idea of the whole OS running with the best integrity. Offline Pages: 1 Index »Newbie Corner »"Cannot change data mode on remount" Board footer Jump to Newbie Corner Installation Kernel & Hardware Applications & Desktop Environments Laptop Issues Networking, Server, and http://www.linuxquestions.org/questions/linux-general-1/data%3Dwriteback-in-fstab-mounts-root-partition-as-read-only-916031/
I understand that this means that the "data=" option does not match between the mounting and remounting. Thanks, Colleen miegielApril 13th, 2010, 01:55 AMCan you explain this in a little more detail, I am having a similar problem (mine is specifically with RAID 0 I believe) and have The kernel doesn't allow changing data=writeback during runtime, that's why it refuses this.
And one more: I saw some references that you could set the root mount mode at the grub cmdline, at least in earlier Ubuntu releases Your grub kernel line would read Opts: (null) [ 17.557900] EXT4-fs (nand2): Cannot change data mode on remount [ 17.604119] EXT4-fs (nand2): Cannot change data mode on remount As the official cubieboard 2 download Should we use > that switch from systemd-remount-fs? Journal_data_writeback do: mke2fs -t ext4 -O ^has_journal /dev/sdaX (root) 3.
In the unlikely event this is a different issue to what's been originally reported, I'd be happy to open a separate one (I would have opened it against anaconda, but then Ext4 Data=writeback Change the default filesystem mount options in the filesystem itself. See the man page for 'mount' for more info. http://superuser.com/questions/1075028/root-fs-read-only-remounting-gives-cannot-change-data-mode-on-remount-when-no So, in order to avoid journalling completely, you have decided to change from one journalling mode to another journalling mode.
Post a reply 5 posts by asaz989 » Sat Aug 03, 2013 11:37 pm After one reboot, my Pi has started mounting its root filesystem (an ext4 flash card partition) Are you new to LinuxQuestions.org? Data=writeback Bad Option Comment 16 Lukáš Czerner 2015-11-11 04:43:56 EST From my point of view the best solution would be to mount it with the right options in the first place, however if you Ext4 Commit All fixed! :p WylieEApril 12th, 2010, 08:49 PMHi there, I found out a solution to the Read Only issue.
It booted right up with my new fstab options. check over here Right? How do I deal with my current employer not respecting my decision to leave? How can I claim compensation? Ext4 Data=journal
Code: # tune2fs /dev/sda2 -o journal_data_writeback . xyepblraOctober 21st, 2009, 04:35 PMFinally I found the thread my help request it would be proper to post to. Because you are specifying the data=journal option the remount fails and the root filesystem is left read-only. http://ibuildsystem.com/ubuntu-cannot/ubuntu-cannot-resolve.php Then the fs will be auto mounted with data=journal by the kernel and won't conflict with the fstab.Disclaimer: I haven't tested this.
Why? Ext4 Disable Journaling If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later We've got a file system which is already mounted and the user space requested remount with the options that's it's not supported for remount.
Next to "Filesystem Features" - if 'has_journal' does not appear, then journalling has been turned off Please let me know if anything here is incorrect or missing and I will update There doesn't seem to be anything wrong with the filesystem (I've put it into a laptop to run fsck with no problems) and it works perfectly fine if I say "mount Just run data=writeback,commit=600 (edit: should have been more explicit - only data=journal journals your data. Ext4 Performance Tuning Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us.
LinuxQuestions.org > Forums > Linux Forums > Linux - General [SOLVED] "data=writeback" in fstab mounts root partition as "read-only" User Name Remember Me? How can I change it back?84How do I remount a filesystem as read/write?10Ubuntu goes into read-only mode randomly0What to do after ubuntu remounts my filesystem in read/write mode?2How do I fix Assuming you have a 2nd running machine with ubuntu, you can make a live USB (instead of a live CD) with System > Administration > USB Startup Disk Creator and the weblink Thank you for reporting this bug and we are sorry it could not be fixed.
Arch Linux HomePackagesForumsWikiBugsAURDownload Index Rules Search Register Login You are not logged in. Thanks. Not the answer you're looking for? Might be a solution, but also slows down the boot process.
Taking "data=writeback" off the / partition but leaving it in for /boot and /home partitions and everything mounts just fine. If the kernel command line options (in this case ro equivalent to rootflags=ro) clashes with a remount to the fstab options it is not the job of dracut or systemd to Alternatively, I can choose the recovery option prior to booting and boot into that, but the file system is still mounted as read only. However -o rmount,rw,data=writeback gives the same error.
I mistyped an option in fstab for the / directory (very bad, I know). So with a Macbook, that shouldn't matter since I believe that they are USB driven (don't quote me on that, it has been a while since I have used my old Here's my old fstab:
/dev/mapper/vg1-root / ext4 defaults,errors=remount-ro 0 1
I changed it to:
/dev/mapper/vg1-root / ext4 rw,data=journal,journal_checksum 0 1
Well… upon reboot, I got I know its slower, but I prefer data integrity over speed on this system.
Password Linux - General This Linux forum is for general Linux questions and discussion. If you experience problems, please add a comment to this bug. And the same fstab is used (the script just changes the mmc string to nand2) As my intention is to have the system safe after unexpected power failures I'm good If you are unable to reopen this bug, please file a new report against the current release.