Cloning a emmc drive to a nvme drive question

[Patrick Izumi]

Hi, not having much success in getting my question answered in the ChromiumOS group.

Does anybody know why if I a clone an emmc drive to a nvme drive and then boot to the nvme drive it wont update chrome os?

Any way to forcibly update chrome os?

[Luigi Semenzato]

You may want to add a little more detail on what you did.  Like, are you running Chrome OS Flex?  Or are you running in developer mode?  Etc.

[Luigi Semenzato]

A chromebook in developer mode will not auto-update, because the update might interfere with your changes (if any), and vice versa.

You could try a manual update with the command "update_engine_client --update", but I am not familiar with that system and I don't know if it will work, sorry.  (I suspect it will not, because it's not a feature that many people would find useful.)

And that's pretty much all the help I can give!

On Tue, Sep 5, 2023 at 5:25 PM Patrick Izumi <usu...@gmail.com> wrote:

Hi,

  Running ChromeOS in developer mode.

Are you able to help with my issue of not being able to update ChromeOS when I am using a nvme drive which is plugged into wifi port of Lenovo ideapad 3 chromebook with an adapter?

Any more info I can provide, let me know if you can help thanks in advance.

[Patrick Izumi]

Hi,

  Running ChromeOS in developer mode.

Are you able to help with my issue of not being able to update ChromeOS when I am using a nvme drive which is plugged into wifi port of Lenovo ideapad 3 chromebook with an adapter?

Any more info I can provide, let me know if you can help thanks in advance.

On Tuesday, September 5, 2023 at 9:19:06 AM UTC-7 Luigi Semenzato wrote:

[Patrick Izumi]

Hi, not trying to auto update, issue with manual update is that it states it is updating, gets to 100%, then asks me to restart, which i do, then once i check the version after that it is still the same one, it failed to update.

I tried that command but unfortunately it failed too.

If you can help more, or know somebody that can assist in this issue, thanks again.

[dragon788]

If you removed the rootfs protection then there isn't a way to update your device. If you didn't remove that there may be an issue with the device uuids in /etc/fstab, but to fix it you'd have to remove the rootfs protection thereby negating your ability to update.

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

[Patrick Izumi]

Hi, I didn't remove rootfs protection as far as I know, actually I don't know how to do that.

I did however disable firmware write protection to update the firmware using :

MrChromebox.tech 

Does that disable rootfs protection?

I reverted back to chrome os stock firmware though

[Denny Lockhart]

Sorry, the two replies below do not relate to the OPs issue but I think they're important to mention/clarify. 

Luigi Semenzato said:

> A chromebook in developer mode will not auto-update, because the update might interfere with your changes (if any), and vice versa.

That has not been my experience on consumer devices, not test images.
I have had every Chromebook I've owned since the Cr-48 in Developer mode and have never had an issue with getting updates - unless I tweak the /etc/lsb-release file.

dragon788 said:

> If you removed the rootfs protection then there isn't a way to update your device.

Again, that has not been my experience on consumer devices, not test images.
I usually remove rootfs verification on the active boot pair and am still able to get updates - unless I tweak the /etc/lsb-release file.

From what I've heard from others, their experience is the same as mine.

~DennyL

[Luigi Semenzato]

Thank you for the correction.  Our own documentation suggests that it does not :/

https://www.chromium.org/chromium-os/chromiumos-design-docs/developer-mode/

[dragon788]

Yeah I was also going off the documentation. I haven't had to disable rootFS verification in quite a while so I don't have any experience with the current actual behavior.

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