4036 2013-03-16 09:17:44 +0000 scripts/contrib/mkefidisk.sh hardcodes 'rw' as root mount option 2013-04-05 17:23:43 +0000 1 1 7 Build System, Metadata & Runtime OE-Core deployment unspecified All Multiple RESOLVED FIXED Medium+ normal 1.4 M6 1 koen dvhart --- --- --- oldest_to_newest 30771 0 koen 2013-03-16 09:17:44 +0000 scripts/contrib/mkefidisk.sh hardcodes 'rw' as root mount option, which breaks fsck which expects a 'ro' param to work. 30864 1 dvhart 2013-03-19 18:36:51 +0000 When is fsck breaking? During a boot test? What would you like to see instead? An option to use 'rw', unilateral use of 'ro'? 30865 2 koen 2013-03-19 18:48:07 +0000 you can't run fsck on a rw fs, I'd like to have an option to choose ro or rw, but just replacing rw with ro is fine by me as well 30866 3 dvhart 2013-03-19 18:54:11 +0000 If this is just running it after boot.... why not just remount the fs? $ mount -o remount,ro /dev/sda2 / $ fsck /dev/sda2 This is what I've always done. It seems backwards to change the normal boot method and parameters so a debugging tool can be run without any setup.... 30867 4 koen 2013-03-19 19:00:12 +0000 well, you need to boot with 'ro' if you don't use an initramfs and want the builtin fsck to work, which it doesn't do right now. I realize that oe-core sysv scripts don't have any way to run fsck, but systemd does, and it has worked great for years now on other platforms (e.g. beagle*). I don't see why mkefidisk.sh needs to be special and force rw mode. 30868 5 dvhart 2013-03-19 19:05:13 +0000 OK, that is why asked if it was part of boot or later. I'm fine adding the option to choose which to use. 31622 6 dvhart 2013-04-05 17:23:43 +0000 commit 24cd3ddeb70a3d3f2985ec71c87ae0108f3d2777 Author: Darren Hart <dvhart@linux.intel.com> Date: Tue Mar 19 15:15:03 2013 -0700 mkefidisk: Boot with ro kernel parameter instead of rw