Can no longer remove rootfs verification

[DennisLfromGA]

I recently got an update and am using:

    Google Chrome: Version 91.0.4472.81 (Official Build) beta (64-bit)

    Platform: 13904.41.0 (Official Build) beta-channel eve

   Channel: beta-channel

    Firmware Version: Google_Eve.9584.201.0

    ARC Enabled: true

    ARC: 7360525

    Enterprise Enrolled: false

    Developer Mode: true

I usually remove rootfs verification to add some config scripts to /etc/init, but I can no longer do that.

I have run the following as root and gotten 'success' messages -

• /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions  [CURRENT KERNEL PARTITION]

But after rebooting I cannot remount / as read-write; I have also used the '--force' option and have even run it on both kernel partitions just in case.

I have also run the following as root to no avail -

• /usr/libexec/debugd/helpers/dev_features_rootfs_verification
  

Is removing rootfs verification no longer possible or am I doing something wrong?

Thanx in advance for any help,

~DennyL

[dragon788]

The docs appear to show a slightly different syntax now.

https://chromium.googlesource.com/chromiumos/docs/+/master/developer_mode.md#disable-verity

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss
---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

[DennisLfromGA]

Thanx drag...@

I looked at the doc you linked above and ran the command without specifying the active kernel partition.

That gave me an error and told me the disk (/dev/mmcblk0) was NOT MODIFIED.

It suggested to 'only change the partition I booted with' so I did that, see below:

After rebooting rootfs verification was still NOT removed, see below:

So I'm still back at square one.

I think the docs need to be updated with a command that works or let us know that removing rootfs verification is no longer supported/possible.

At least that's my experience, I'm not sure if this is happening to anyone else tho.

[dragon788]

The last time I ran into this I was brave/foolish and ran it against both partitions with the `--force` parameter, it seems to worked fine with no major issues that I've seen.

[DennisLfromGA]

Yup, I even tried that first, as mentioned in my first post above, that didn't work either. :-(

[dragon788]

I'll try transitioning my Eve to Developer mode and see if it works on Stable, and then switch to Beta and give it a try and see if I see the same errors. I did notice when I powerwashed back to Stable from the Dev channel I have the new dark mode for the Developer mode transition and warnings which is VERY nice, I hope more devices get that soon.

[DennisLfromGA]

drag...@,

Please don't do all that on my account unless you are just that curious. I'm not even sure others are hitting this issue.

I would love to hear back from a CrOS dev but so far, that hasn't happened.

Thanx for your help.

[dragon788]

Not a problem, my Eve has been feeling neglected since I got my Arcada(s) and started using them far more heavily since I don't have to worry about the writes to the NVME because they can be replaced pretty easily where on the Chomebook Pixel and Pixelbook once that dies they are pretty much dead (especially on the latter where there isn't a microSD slot to boot from either).
I am a bit curious, previously I had run into a scenario where the "static packages" for `dev_install` were missing/broken for certain releases so I ended up having to reset my system with a previous version of the recovery image where those files were present and then upgrade to a newer ChromeOS after I had what I needed, and part of that process required making the rootfs r/w so knowing whether that door is closed or closing now will be good.

[dragon788]

I didn't have any issues making the rootfs r/w on the Stable channel 91.0.4471.81 aka 13904.41.0 stable-channel eve.

I then did a Powerwash before I transitioned to Beta with `sudo update_engine_client --channel=beta-channel` and `sudo update_engine_client --update` and `sudo update_engine_client --reboot` after connecting to the wireless in the initial setup screen.

I then did `sudo su -` and `/usr/share/vboot/bin/make_dev_ssd.sh --remove-rootfs-verfication --partition 2` and `--partition 4` and rebooted and it allowed me to `mount -o rw,remount /` after a reboot.

[Denny Lockhart]

Okay, Thanx very much for the testing and all of your effort, I really appreciate it.

Guess I'll have to try and figure out what might be wrong with my setup.

[DennisLfromGA]

drag...@,

I just got the 92 beta update, version 13982.7.0 / 92.0.4515.36 and the script works, it remove rootfs verification so I'm good to go again.

I don't know what was wrong before but thankfully an update seems to have fixed it.

Thanx for your help I really appreciate it.

[Mike Frysinger]

weird.  i don't think we've made any changes to these scripts.  but if it's working for you again, should be good enough :/.

-mike

[DennisLfromGA]

Yes, it was weird but evidently something I may have done.

That happened to me once before and an update corrected it then too; wish I knew what I'm doing to prevent it from working but it's definitely good now.

Thanx for your input everyone.

[dragon788]

I did notice that after I unlocked the rootfs for both partitions and only remounted rw once and maybe attempting a dev_install that when I tried to Powerwash after switching to the beta channel it ended up breaking and I had to do a full recovery from USB. I've seen this once or twice before, but I haven't figured out the exact sequence of events that makes a Powerwash break the system.