[opensuse-kernel] no more RW for / by default?
1-cloned a nicely functional 13.1 partition 2-assigned new UUID & partition label, updated Grub menu & fstab on cloned partition 3-booted the clone 4-zypper clean -a 5-replace 13.1 repos with Factory's in /etc/zypp/repos.d/ 6-zypper ref; zypper in zypper libzypp rpm glibc libsolv-tools, udev systemd; zypper -v dup 7-booted the updated clone partition to the newly installed kernel Result: can't do much until manually remounting / rw Booting 13.1's 3.11.6 init mounts / rw. Either I have to add rw to cmdline, or remount / rw before doing much of anything is possible. Is this expected with 3.12.1? Expected of Dracut? Bug? Explicit rw now required for / in fstab? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 11/28/2013 12:11 AM, Felix Miata wrote:
1-cloned a nicely functional 13.1 partition 2-assigned new UUID & partition label, updated Grub menu & fstab on cloned partition 3-booted the clone 4-zypper clean -a 5-replace 13.1 repos with Factory's in /etc/zypp/repos.d/ 6-zypper ref; zypper in zypper libzypp rpm glibc libsolv-tools, udev systemd; zypper -v dup 7-booted the updated clone partition to the newly installed kernel
Result: can't do much until manually remounting / rw
Often, (usually) root is mounted 'ro' by the boot loader -- a protective measure in case your kernel went haywire on boot. Not sure how often that happens these days. Might check your boot line and see if it has a read-only or read-write in the entry for the new kernel. This used to be taken care of in a boot script "boot.rootfsck" - which, of course, has been removed... and the systemd equiv?.. no clue.
Is this expected with 3.12.1? Expected of Dracut? Bug? Explicit rw now required for / in fstab?
Easiest might be for it not to be r/o to begin with (i.e. see about mounting it r/w on boot? Maybe depends on how stable your booting OS's are... hmmm..... maybe keep it r/o for now and ask Christian for the systemd replacement for boot.rootfsck... ;-) (When you come up in 'S' mode root would always be r/o because the "B"(oot) scripts hadn't run yet...) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 28/11/13 05:11, Felix Miata escribió:
1-cloned a nicely functional 13.1 partition 2-assigned new UUID & partition label, updated Grub menu & fstab on cloned partition 3-booted the clone 4-zypper clean -a 5-replace 13.1 repos with Factory's in /etc/zypp/repos.d/ 6-zypper ref; zypper in zypper libzypp rpm glibc libsolv-tools, udev systemd; zypper -v dup 7-booted the updated clone partition to the newly installed kernel
Result: can't do much until manually remounting / rw
Booting 13.1's 3.11.6 init mounts / rw. Either I have to add rw to cmdline, or remount / rw before doing much of anything is possible.
Is this expected with 3.12.1? Expected of Dracut? Bug? Explicit rw now required for / in fstab?
Your root filesystem is likely to have errors.. dracut does NOT mount / ro unless explicitly told to by using --ro-mnt option.. and currently depending on your setup, having the root filesystem listed in fstab or even having a /etc/fstab file at all may not be required. hard to tell without logs, boot with "debug" in the cmdline. -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 2013-12-01 03:17 (GMT-0300) Cristian Rodríguez composed:
Felix Miata composed:
1-cloned a nicely functional 13.1 partition 2-assigned new UUID & partition label, updated Grub menu & fstab on cloned partition 3-booted the clone 4-zypper clean -a 5-replace 13.1 repos with Factory's in /etc/zypp/repos.d/ 6-zypper ref; zypper in zypper libzypp rpm glibc libsolv-tools, udev systemd; zypper -v dup 7-booted the updated clone partition to the newly installed kernel
Result: can't do much until manually remounting / rw
Booting 13.1's 3.11.6 init mounts / rw. Either I have to add rw to cmdline, or remount / rw before doing much of anything is possible.
Is this expected with 3.12.1? Expected of Dracut? Bug? Explicit rw now required for / in fstab?
Your root filesystem is likely to have errors.. dracut does NOT mount / ro unless explicitly told to by using --ro-mnt option.. and currently depending on your setup, having the root filesystem listed in fstab or even having a /etc/fstab file at all may not be required.
hard to tell without logs, boot with "debug" in the cmdline.
Too late now. The problem eventually went away "on its own". I think what happened is I forgot to change the UUID when I changed the volume label before mounting the clone, mounted it, then changed the UUID while still mounted. I later booted it several times both to 13.2 and older installations, and something, likely 12.1 or 13.1, likely fsck'd it automatically it along the way. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (3)
-
Cristian Rodríguez -
Felix Miata -
Linda Walsh