New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 760007 link

Starred by 144 users

Comments by non-members will not trigger notification emails to users who starred this issue.

device losing enrollment - Lenovo and PixelBook devices

Project Member Reported by marcore@chromium.org, Aug 29 2017

Issue description

I'm opening a new bug because the HW is different from https://bugs.chromium.org/p/chromium/issues/detail?id=738895

Chrome Version: 59.0.3071.134, 60.0.3112.112
OS: ChromeOS
HW: Lenovo N22 REKS C25-E4E-U5A-Q6E

- How many devices are affected?
So far they have reported more than 50

What steps will reproduce the problem?
(1) enroll device
(2) Leave Chromebook charging on a cart during the night
(3) Turn the device on

What is the expected result?
device keeps enrollment
What happens instead?
Devices goes straight to enrollment screen (looks like device was wiped)

debug logs: https://drive.google.com/open?id=0B01ZVp8vDQocckJ1VHFzVDg5RDA

in the logs I see:
ui/ui.20170822-192054:[1016:1016:0822/192059.441158:ERROR:device_cloud_policy_store_chromeos.cc(238)] Device policy read on enrolled device yields no DM token! Status: 4.
as written in https://bugs.chromium.org/p/chromium/issues/detail?id=738895#c6
Value 4 means:
STORE_INVALID_POLICY,    // Invalid settings blob (proto parse failed).

messages.1
2017-08-22T08:18:32.624821-04:00 INFO kernel: [    0.992990] mmc0: BKOPS_EN bit is not set
2017-08-22T08:18:32.624822-04:00 INFO kernel: [    1.009039] mmc0: new HS200 MMC card at address 0001
2017-08-22T08:18:32.624824-04:00 INFO kernel: [    1.009657] mmcblk0: mmc0:0001 AGND3R 14.5 GiB 
2017-08-22T08:18:32.624826-04:00 INFO kernel: [    1.009751] mmcblk0boot0: mmc0:0001 AGND3R partition 1 4.00 MiB
2017-08-22T08:18:32.624833-04:00 INFO kernel: [    1.009832] mmcblk0boot1: mmc0:0001 AGND3R partition 2 4.00 MiB
2017-08-22T08:18:32.624836-04:00 INFO kernel: [    1.009921] mmcblk0rpmb: mmc0:0001 AGND3R partition 3 4.00 MiB
2017-08-22T08:18:32.624838-04:00 INFO kernel: [    1.013375]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
...
2017-08-22T08:18:32.625772-04:00 CRIT kernel: [    2.564271] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:757: group 6, block bitmap and bg descriptor inconsistent: 24036 vs 24090 free clusters
2017-08-22T08:18:32.625774-04:00 CRIT kernel: [    2.564501] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:757: group 0, block bitmap and bg descriptor inconsistent: 18985 vs 18984 free clusters
...
2017-08-22T08:18:37.249574-04:00 WARNING cryptohomed[1041]: Could not load the device policy file.
2017-08-22T08:18:37.872329-04:00 ERR session_manager[959]: [ERROR:session_manager_impl.cc(576)] Failed to retrieve policy data.
2017-08-22T08:18:37.953048-04:00 CRIT kernel: [    7.985788] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:757: group 10, block bitmap and bg descriptor inconsistent: 25580 vs 25579 free clusters
2017-08-22T08:18:37.953078-04:00 CRIT kernel: [    7.986365] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:757: group 14, block bitmap and bg descriptor inconsistent: 23675 vs 23780 free clusters
2017-08-22T08:18:37.873942-04:00 ERR session_manager[959]: message repeated 2 times: [ [ERROR:session_manager_impl.cc(576)] Failed to retrieve policy data.]
2017-08-22T08:18:38.212705-04:00 INFO cryptohomed[1041]: Attestation: Valid attestation data exists.
2017-08-22T08:18:38.239117-04:00 INFO cryptohomed[1041]: Cannot read boot lockbox files.

 
Showing comments 135 - 234 of 234 Older
We are having this issue with our Levovo N22 devices. 5 of the devices with issues are on Chrome OS: 53, 60, 51, 58, 60, 59
-We are now pushing a new Chrome OS build, 9592.94.0 to devices that have upgraded to 9460.61.0 or newer.

-Devices on 9460.60.0 or older will not receive this build at this time, they'll stay on 9460.60.0 which is not showing this issue.

-We believe the new build will minimize unenrollment occurrences. We are still working hard to understand and solve the root cause (filesystem corruption).

-If you see devices unenrolling on 9592.94.0, please grab logs and attach them here.

https://support.google.com/chrome/a/answer/3293821?hl=en
We are having a much more severe version of this issue.  Our devices are stuck in a reboot loop when connected to wifi after upgrading to 59.

Anyone else having boot problems?
#133: SUS power fail means the DRAM lose power in SUSpend state and should not be relied upon, which is expected when we shutdown.

#127, #130: the leak is due to imageloader, which normally release the 3 mounts for encstateful (encstateful, /var and /home), but only 2 on my systems.
With cl:668108, on a working systems:
[    5.274457] imageloader clone mount 3                                                                
[    5.280166] imageloader clone mount 4                                                                
[    5.284369] imageloader clone mount 5                                                                
[    5.304725] imageloader deactivate 6                                                                 
[    5.311713] imageloader deactivate 5                                                                 
[    5.318650] imageloader deactivate 4 
then at shutdown:
[   31.255749] mount-encrypted deactivate 3
[   31.266740] mount-encrypted deactivate 2
[   31.275739] mount-encrypted deactivate 1
[   31.280144] mount-encrypted deactivate locked 1

While on my systems, I have:
[    5.198967] imageloader clone mount 3
[    5.198996] imageloader clone mount 4
[    5.199007] imageloader clone mount 5
[    5.205333] platform vpd: Driver vpd requests probe deferral
[    5.206496] platform vpd: Driver vpd requests probe deferral
[    5.224986] platform vpd: Driver vpd requests probe deferral
[    5.253329] device-mapper: verity: Argument 0: 'payload=/dev/loop6'
[    5.253347] device-mapper: verity: Argument 1: 'hashtree=/dev/loop6'
[    5.253358] device-mapper: verity: Argument 2: 'hashstart=29784'
[    5.253369] device-mapper: verity: Argument 3: 'alg=sha256'
[    5.253380] device-mapper: verity: Argument 4: 'root_hexdigest=c36ba182e0a1a533dd079ea00bbb9289d0300ae5e8ab2d03feeb25be6a4e29c0'
[    5.253397] device-mapper: verity: Argument 5: 'salt=90b9b5d4b7fda62e70011df97b403095330ae3dbe9f03501e726d79879c01439'
[    5.253413] device-mapper: verity: Argument 6: 'error_behavior=eio'
[    5.305022] imageloader deactivate 6
[    5.305040] imageloader deactivate 5

Then at shutdown:
[  120.242911] mount-encrypted deactivate 4
[  120.248912] mount-encrypted deactivate 3
[  120.254905] mount-encrypted deactivate 2
We are not at refcount 1, so umount does not complete.


re #138 - I see the same thing on my Caroline

I dumped the stack there at deactivate and it looks like this:

[    2.196633] deactivate_super: ffff880075e26800 s->s_id = dm-1 s_active = 5 comm = imageloader
[    2.196642] CPU: 3 PID: 564 Comm: imageloader Tainted: G        W      3.18.0 #78
[    2.196649] Hardware name: Google Caroline/Caroline, BIOS Google_Caroline.7820.263.0 01/26/2017
[    2.196658]  0000000000000000 00000000e39e1f3a ffff88017595fe28 ffffffff8c6a1140
[    2.196670]  0000000000000000 ffff880075e26800 ffff88017595fe48 ffffffff8c155226
[    2.196681]  ffff880176142280 ffffffff8ce71720 ffff88017595fe68 ffffffff8c16bd35
[    2.196693] Call Trace:
[    2.196698]  [<ffffffff8c6a1140>] dump_stack+0x4e/0x71
[    2.196705]  [<ffffffff8c155226>] deactivate_super+0x60/0x96
[    2.196712]  [<ffffffff8c16bd35>] cleanup_mnt+0x59/0x78
[    2.196719]  [<ffffffff8c16bd94>] __cleanup_mnt+0x12/0x14
[    2.196726]  [<ffffffff8c07bf78>] task_work_run+0x7e/0xab
[    2.196734]  [<ffffffff8c065268>] do_exit+0x43b/0x964
[    2.196745]  [<ffffffff8c0e0386>] ? seccomp_phase1+0x48/0x95
[    2.196760]  [<ffffffff8c066657>] do_group_exit+0x43/0xb1
[    2.196776]  [<ffffffff8c0666d9>] SyS_exit_group+0x14/0x14
[    2.196785]  [<ffffffff8c6a651c>] system_call_fastpath+0x1c/0x21

so what is happening there is that when the task exits we run through some tasks in the task_work_run() function.  Tasks are added to the list of tasks by task_work_add() and one of the users of task_work_add() is mntput_no_expire() which is adding the "__cleanup_mnt" callbacks.

So it seems like somewhere we're missing a call to mntput() somewhere in the kernel, which might be a little hard to track down quickly.  

This is all on kernel 3.18, so I think we should verify whether same thing is happening on the other kernels or not.

Comment 140 by dun...@usd367.org, Sep 15 2017

I'm also having the same issue, but with our Acer chromebooks. I'm not sure exactly which log file you guys are looking at, but here's some logs from one of mine.

https://drive.google.com/file/d/0B8a8QPPAhXpSOFhUNkI1d3llNGc/view?usp=sharing

Comment 141 by dun...@usd367.org, Sep 15 2017

Here's another dump from one of my acer chromebooks.

https://drive.google.com/file/d/0B8a8QPPAhXpSb3YzeU5DaHhvVVk/view?usp=sharing

Comment 142 Deleted

We are also seeing this on hp chromebook 11 ee g5.

So far about 100+ chromebooks have had this problem. 

Comment 144 by jsmy...@ccpcs.org, Sep 15 2017

What will trigger devices to take the new build?

Jeremy Smythe


Director of Information Technology

Capital City Public Charter School

www.ccpcs.org ☎ (202)-808-9755 <//(202)-808-9755>

On September 14, 2017 at 4:21:03 PM, jayh… via monorail (
monorail+v2.1523987270@chromium.org) wrote:

Comment 145 Deleted

We are experiencing this as well.  We have ASUS C202's.  950 units, I have had probably 10 the last 2 weeks.
Blocking: 763887
We are seeing this too. We have HP 11 G5 EE and we are starting to see couple of them unenrolling. 
We have more than 30000 Chromebooks and starting to see the number of unenrolled Chromeboosk creeping up. Even though we have force enrollment on, they are still coming up as though they were not enrolled. 

Comment 150 by e...@g.mvusd.net, Sep 15 2017

Regarding Comment 136,
I have Dell 3180, and the latest version is 9460.60.0 (ChromeOS v59( and we ARE having issues with it automatically unenrolling!
confirmed that if I disable imageloader (by renaming /etc/init/imageloader.conf) I am now able to get clean shutdowns for encstateful and stateful

so something in the way imageloader is running is causing the kernel to leak a reference to encstateful
re #151 -- I tried the same mitigation on kevin (4.4) kernel  but I'm still seeing unclean shutdowns of encstateful -- so there may be multiple causes for unclean shutdown, still investigating
Uploaded cl/670041: with this CL, we remove PepperFlashPlayer mount point before unmount encstateful: therefore, we are able to umount cleanly, preventing recovery at reboot.

This ensures we reboot with clean filesystems, reducing the risk of corruption at reboot. We still have to fully understand why ext4 crypto introduction prevents unmounted filesystems to be cleanup properly at reboot sometimes, but the proposed fix should reduce the rate of unenrollement.
Project Member

Comment 154 by bugdroid1@chromium.org, Sep 16 2017

Labels: merge-merged-release-R60-9592.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/4bc568d96a6fa3dbc0a188f1d7e1c4a304bd8ea1

commit 4bc568d96a6fa3dbc0a188f1d7e1c4a304bd8ea1
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Sat Sep 16 15:19:41 2017

Add script to unloaded loaded images

Add script to unload PepperFlashPlayer, its device mapper and loop devices.
It ensurses we can unmount encstateful and stateful properly.

BUG= chromium:760007 
CQ-DEPEND=CL:669704
TEST=On cyan, check that dm-1 and mmcblk0p1 are mounted without repairs.

Change-Id: I3f065890968d59484acc74e3aed0ea8e307d752b
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/669910
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>

[add] https://crrev.com/4bc568d96a6fa3dbc0a188f1d7e1c4a304bd8ea1/imageloader-shutdown.conf
[modify] https://crrev.com/4bc568d96a6fa3dbc0a188f1d7e1c4a304bd8ea1/imageloader.conf

This went to the wrong bug:

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/c68db285a46d62f2eeef4e1f677018e0a4ffee1b

commit c68db285a46d62f2eeef4e1f677018e0a4ffee1b
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Sat Sep 16 15:20:02 2017

image-loader: Add shutdown conf file

Add conf file to undo what has been done at load time.
In particular, be sure that PepperFlashPlayer resources are freed.

BUG=  chromium:76007  
CQ-DEPEND=CL:669705
TEST=On cyan, check that dm-1 and mmcblk0p1 are mounted without repairs.

Change-Id: Ib7b883255ca71aea80b31785a2b8454f75189299
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/669869
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>

[modify] https://crrev.com/c68db285a46d62f2eeef4e1f677018e0a4ffee1b/chromeos-base/imageloader/imageloader-9999.ebuild
Project Member

Comment 156 by bugdroid1@chromium.org, Sep 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/c549b5e1b3cf7ddde35d6961f784e3720b3d7f78

commit c549b5e1b3cf7ddde35d6961f784e3720b3d7f78
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Sat Sep 16 19:15:04 2017

Add script to unloaded loaded images

Add script to unload PepperFlashPlayer, its device mapper and loop devices.
It ensurses we can unmount encstateful and stateful properly.

BUG= chromium:760007 
CQ-DEPEND=CL:669704
TEST=On cyan, check that dm-1 and mmcblk0p1 are mounted without repairs.

Change-Id: I3f065890968d59484acc74e3aed0ea8e307d752b
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/669705
Commit-Ready: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[add] https://crrev.com/c549b5e1b3cf7ddde35d6961f784e3720b3d7f78/imageloader-shutdown.conf
[modify] https://crrev.com/c549b5e1b3cf7ddde35d6961f784e3720b3d7f78/imageloader.conf

Project Member

Comment 157 by bugdroid1@chromium.org, Sep 18 2017

Labels: merge-merged-release-R61-9765.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/7f84bd47d48bac90d5d39c4ec98a9ae9ed7f5869

commit 7f84bd47d48bac90d5d39c4ec98a9ae9ed7f5869
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Mon Sep 18 03:00:06 2017

image-loader: Add shutdown conf file

Add conf file to undo what has been done at load time.
In particular, be sure that PepperFlashPlayer resources are freed.

BUG= chromium:760007 
CQ-DEPEND=CL:669705
TEST=On cyan, check that dm-1 and mmcblk0p1 are mounted without repairs.

Change-Id: Ib7b883255ca71aea80b31785a2b8454f75189299
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/669868

[modify] https://crrev.com/7f84bd47d48bac90d5d39c4ec98a9ae9ed7f5869/chromeos-base/imageloader/imageloader-9999.ebuild

Project Member

Comment 158 by bugdroid1@chromium.org, Sep 18 2017

Labels: merge-merged-release-R62-9901.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/72183321a8edbbe55e732fcfb2c0706a69069828

commit 72183321a8edbbe55e732fcfb2c0706a69069828
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Mon Sep 18 03:01:49 2017

image-loader: Add shutdown conf file

Add conf file to undo what has been done at load time.
In particular, be sure that PepperFlashPlayer resources are freed.

BUG= chromium:760007 
CQ-DEPEND=CL:669705
TEST=On cyan, check that dm-1 and mmcblk0p1 are mounted without repairs.

Change-Id: Ib7b883255ca71aea80b31785a2b8454f75189299
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/669867

[modify] https://crrev.com/72183321a8edbbe55e732fcfb2c0706a69069828/chromeos-base/imageloader/imageloader-9999.ebuild

Project Member

Comment 159 by bugdroid1@chromium.org, Sep 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/391ef9c3d99c8d4313e468d3ebcf3f3bba573796

commit 391ef9c3d99c8d4313e468d3ebcf3f3bba573796
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Mon Sep 18 03:01:49 2017

Add script to unloaded loaded images

Add script to unload PepperFlashPlayer, its device mapper and loop devices.
It ensurses we can unmount encstateful and stateful properly.

BUG= chromium:760007 
CQ-DEPEND=CL:669704
TEST=On cyan, check that dm-1 and mmcblk0p1 are mounted without repairs.

Change-Id: I3f065890968d59484acc74e3aed0ea8e307d752b
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/669909

[add] https://crrev.com/391ef9c3d99c8d4313e468d3ebcf3f3bba573796/imageloader-shutdown.conf
[modify] https://crrev.com/391ef9c3d99c8d4313e468d3ebcf3f3bba573796/imageloader.conf

Project Member

Comment 160 by bugdroid1@chromium.org, Sep 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/ef3ece24f05ab504c9ce62a4b32cf35d4ee8b2df

commit ef3ece24f05ab504c9ce62a4b32cf35d4ee8b2df
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Mon Sep 18 03:01:52 2017

Add script to unloaded loaded images

Add script to unload PepperFlashPlayer, its device mapper and loop devices.
It ensurses we can unmount encstateful and stateful properly.

BUG= chromium:760007 
CQ-DEPEND=CL:669704
TEST=On cyan, check that dm-1 and mmcblk0p1 are mounted without repairs.

Change-Id: I3f065890968d59484acc74e3aed0ea8e307d752b
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/669908

[add] https://crrev.com/ef3ece24f05ab504c9ce62a4b32cf35d4ee8b2df/imageloader-shutdown.conf
[modify] https://crrev.com/ef3ece24f05ab504c9ce62a4b32cf35d4ee8b2df/imageloader.conf

Labels: M-62
Cc: ken...@chromium.org
 Issue 765340  has been merged into this issue.
Cc: -dskaram@chromium.org
I'm having the same issue here but with Acer C740's. If I reboot the Chromebook a few times i can reproduce the issue. I have to re enroll at least 1-5 a day.
I have acer c740 and the same issue.  Many each day are brought back on the welcome screen with the wifi disconnected.  We push wifi to the device via Google Admin...

Attaching 2 logs....
HS Cart B 18.tgz
1.7 MB Download
HS Cart B 25.tgz
1.5 MB Download
Blockedon: 766347
We are seeing this on Lenovo N42 touch also and upon re-enroll it shows update available. Will post logs later.

Comment 168 by jsmy...@ccpcs.org, Sep 19 2017

Is there any update to this issue?  This has become a major issue for our school. 
Project Member

Comment 169 by bugdroid1@chromium.org, Sep 19 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/16d735ce501cbfbfdb50998d1f048455716d11f1

commit 16d735ce501cbfbfdb50998d1f048455716d11f1
Author: Thiemo Nagel <tnagel@chromium.org>
Date: Tue Sep 19 14:11:06 2017

init: Add sync to chromeos_shutdown

Sync before unmounting in chromeos_shutdown to guard against present and
(potential) future unmount failures.

(This is intentionally placed before writing boot stats because the sync
time is legitimately part of shutdown and should be covered by the
stats. Due to the change in coverage, this CL will look like a
regression though it likely isn't one as the subsequent umount will be
sped up by approximately the amount of time that sync takes.)

BUG= chromium:760007 
TEST=manual: reboot works

Change-Id: Ic5e577f3facfd3f1b12862b211248c387fb65210
Reviewed-on: https://chromium-review.googlesource.com/671244
Commit-Ready: Thiemo Nagel <tnagel@chromium.org>
Tested-by: Thiemo Nagel <tnagel@chromium.org>
Reviewed-by: Gwendal Grignou <gwendal@google.com>

[modify] https://crrev.com/16d735ce501cbfbfdb50998d1f048455716d11f1/init/chromeos_shutdown

We're now pushing 9592.96.0 / 60.0.3112.114 (Chrome build is same as .94 was) with a potential fix for the unenrollment issue.

We'd love to get feedback on 9592.96.0, if you see a device in the field that starts showing the unenrollment issue *after* upgrading to .96, please submit logs here.

We are holding off on pushing this new build to devices on older Chrome OS releases that do not have this issue. Once we further validate that it is solving the issue we'll push to all devices.
jayhlee, if we have devices pinned to 58 in the admin console that are currently sitting on some version of 59 or 60, will they upgrade to 9592.96.0 or do we need to move them to unpinned?
@jsmith: they'll need to be unpinned to get the update.

Comment 173 by jsmy...@ccpcs.org, Sep 19 2017

Has anyone seen 60.0.3112.114 get un=enrolled?
How do you know if they are pinned and how do you go about unpinning them?

By Pinned, they mean that Updates are being prevented.  You would change the setting Restrict Updates in Device Settings to Unrestricted.
60.0.3112.114 has indeed been affected as well, there has however been a firmware update to 60.0.3112.114 that can be seen if you look under Detailed build information. You can see the changes before and after a manual update. 

Comment 177 by jsmy...@ccpcs.org, Sep 20 2017

Not seen any issue with 9592.96.0 yet. Checking each machine as we re-enroll and they are all on a lower version. 
> Checking each machine as we re-enroll and they are all on a lower version.

Thank you for doing that!
Seeing devices with 59.0.3071.91 updating to 60.0.3112.114. Is the older OS no longer pinned or were we supposed to do that manually? 

Also seeing devices hang on white screen on boot after being on 60.0.3112.114. Been told by support that this could be because of remnants of data corruption (assume related to initial issue) and to wipe device to fix. Wiping device when initial issue presents will be our procedure going forward in hopes of avoiding white screen issue after un-enroll/re-enroll. 
We are updating 59.0.3071.91 because over time our metrics showed that this version likely is affected by the bug (contrary to what I wrote in comment #66). In that situation, updating to 60.0.3112.114/9592.96.0 which has a potential fix seems better than sticking around on a known-broken version. (58 and older are still blocked from updating, though.)
Yes, I am testing the update, just re-enrolled 7 Chromebooks with the issue and updated them...now we wait and see

Thanks for clarifying tnagel! 
tnagel@ any further updates on this issue? Have we validate the complete fix? can we close this issue?
I just implemented the fix yesterday, can we give it until Friday before we
jump and close it?
We'll hold the public bug open until we get full confirmation issue is resolved. Thanks.
This is the latest log from a device I work with.
debug-logs_20170921-145140.tgz
1.7 MB Download

Comment 187 by jsmy...@ccpcs.org, Sep 22 2017

How is the 9592.96.0 working for everyone? I have not seen any issues yet. Would love to hear from other users. 

We should not close this ticket until there is 100% certainty this issue is resolved. This has been a major headache for a lot of people. I am happy that it might be fixed but still upset it ever happened.  
jayhlee@ can you please clarify who and what you are looking for confirmation on?
@Ketaki: please see my email
jsmythe: thanks for the logs, looks like that device is on Chrome OS 59 and trying to update to the latest Chrome OS 60 that I mentioned in:

https://bugs.chromium.org/p/chromium/issues/detail?id=760007#c170

until the device is updated and re-enrolled, the issue is likely to continue.
It seems this bug has been corrected via the 9592.96.0 /60.0.3112.114 push.
Enrollment seems to be holding for us.
It seems like updating to 60.0.3112.114/9592.96.0 has been working for us, the ones that are still affected are on 9592.94
Cc: dskaram@chromium.org
Issue 767923 has been merged into this issue.
likewise here. It seems to holding with 9592.96.0

thank you for the quick turnaround 
Project Member

Comment 195 by bugdroid1@chromium.org, Sep 26 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/ab5f056ff6a21a77fb0a19e4b61572f0eb8ee8a5

commit ab5f056ff6a21a77fb0a19e4b61572f0eb8ee8a5
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Tue Sep 26 23:14:08 2017

chromeos-init: Add UMA FS error stats

Move send-kernel-errors to its own script,
Reenable unit test and add test for send-kernel-errors.

BUG= chromium:760007 
TEST=Unit test, check on ultima the script runs without error.

Change-Id: I0651e6e580153191ea7b1beffabd599794fc5ca9
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/682355
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/ab5f056ff6a21a77fb0a19e4b61572f0eb8ee8a5/chromeos-base/chromeos-init/chromeos-init-9999.ebuild

Project Member

Comment 196 by bugdroid1@chromium.org, Sep 26 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/66d7eb52f04781db90792aca2cc73a6e7de0f462

commit 66d7eb52f04781db90792aca2cc73a6e7de0f462
Author: Gwendal Grignou <gwendal@chromium.org>
Date: Tue Sep 26 23:14:08 2017

init: Add UMA FS error stats

Move send-kernel-error code from .conf file.
Add unit tests.
Report to UMA when stateful/encrypted stateful have some errors.

BUG= chromium:760007 
CQ-DEPEND=CL:682355
TEST=Unit test, check on gnawty

Change-Id: Ibbc0c25a5d4baa06624cd638e63dc289a37c48c4
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/682596
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[add] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/tests/gather_battery_errors_2.golden
[add] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/tests/test_dmesg_1
[add] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/tests/test_dmesg_2
[modify] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/upstart/send-kernel-errors.conf
[add] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/tests/test_dumpe2fs_1
[add] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/chromeos-send-kernel-errors
[add] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/tests/send-kernel-errors-test.sh
[add] https://crrev.com/66d7eb52f04781db90792aca2cc73a6e7de0f462/init/tests/gather_fs_error_1.golden

Have been seeing the Public Session enrollment reset issue on Samsung Chromebook Plus models. I believe we have seen this issue while running 60.0.3112.114 but I have to verify with my team. 
Project Member

Comment 198 by bugdroid1@chromium.org, Sep 27 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/3fc50e258087e49054e0f97bd6c66998673beeac

commit 3fc50e258087e49054e0f97bd6c66998673beeac
Author: Thiemo Nagel <tnagel@chromium.org>
Date: Wed Sep 27 19:57:58 2017

init: Add another sync call to chromeos_shutdown

Add a sync below bootstat in order to have a maximally clean filesystem
before unmount in the hope of minimizing the potential for corruption.
Also clarify the comment as to why sync is needed.

BUG= chromium:760007 
TEST=none

Change-Id: I8c8873e56eeac2f0a3475217f7b3410fe1ef4173
Reviewed-on: https://chromium-review.googlesource.com/675688
Commit-Ready: Thiemo Nagel <tnagel@chromium.org>
Tested-by: Thiemo Nagel <tnagel@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/3fc50e258087e49054e0f97bd6c66998673beeac/init/chromeos_shutdown

Project Member

Comment 199 by bugdroid1@chromium.org, Sep 28 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/7076091b18ab7d8b14722d224b456409b89070bb

commit 7076091b18ab7d8b14722d224b456409b89070bb
Author: Allen Webb <allenwebb@google.com>
Date: Thu Sep 28 18:18:50 2017

platform_ImageLoader: Added tests for --unmount_all and --unmount.

BUG= chromium:760007 
CQ-DEPEND=CL:677792
TEST=test_that -b amd64-generic <ip:port> platform_ImageLoaderServer

Change-Id: Ic0547aa60a7c3d69bc29a73c0cb698583d366ac4
Reviewed-on: https://chromium-review.googlesource.com/682339
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>

[modify] https://crrev.com/7076091b18ab7d8b14722d224b456409b89070bb/client/site_tests/platform_ImageLoader/platform_ImageLoader.py

Comment 201 by jsmy...@ccpcs.org, Sep 29 2017

Any reported issues with the .114 build?
Project Member

Comment 202 by bugdroid1@chromium.org, Sep 29 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/f4e8671e0ce791c7cc6ad570dfe03d695382fa30

commit f4e8671e0ce791c7cc6ad570dfe03d695382fa30
Author: Allen Webb <allenwebb@google.com>
Date: Fri Sep 29 21:35:33 2017

imageloader: Execute unmount_all flag on stopped ui.

BUG= chromium:760007 
CQ-DEPEND=CL:677792
TEST=test_that -b amd64-generic <ip:port> platform_ImageLoaderServer

Change-Id: I0ec96c441b238ce3b9f3a5df220e60a2b9e1e814
Reviewed-on: https://chromium-review.googlesource.com/690438
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>

[modify] https://crrev.com/f4e8671e0ce791c7cc6ad570dfe03d695382fa30/imageloader-shutdown.conf

Project Member

Comment 203 by bugdroid1@chromium.org, Sep 30 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/c745a92832f1f13ffaf32329306eb9c98a21a359

commit c745a92832f1f13ffaf32329306eb9c98a21a359
Author: Mike Frysinger <vapier@chromium.org>
Date: Sat Sep 30 03:16:29 2017

imageloader: add libdevmapper dep

BUG= chromium:770386 
BUG= chromium:760007 
TEST=precq passes

Change-Id: I7d0d208b03db5430f1c7a6f7485d78e4fc853c34
Reviewed-on: https://chromium-review.googlesource.com/693224
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Nicolas Norvez <norvez@chromium.org>
Reviewed-by: Allen Webb <allenwebb@google.com>

[modify] https://crrev.com/c745a92832f1f13ffaf32329306eb9c98a21a359/chromeos-base/imageloader/imageloader-9999.ebuild

So far 60.0.3112.114 looks good; all unenrollment issues we've had have been with older versions.
Status: Fixed (was: Started)
Project Member

Comment 206 by bugdroid1@chromium.org, Oct 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/e43d8af075ffad0a1a7c690e21f5db7d13cba6c3

commit e43d8af075ffad0a1a7c690e21f5db7d13cba6c3
Author: Mike Frysinger <vapier@chromium.org>
Date: Fri Oct 06 23:53:41 2017

imageloader: add libdevmapper dep

BUG= chromium:770386 
BUG= chromium:760007 
BUG= chromium:772132 
TEST=precq passes

Change-Id: I7d0d208b03db5430f1c7a6f7485d78e4fc853c34
Reviewed-on: https://chromium-review.googlesource.com/693224
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Nicolas Norvez <norvez@chromium.org>
Reviewed-by: Allen Webb <allenwebb@google.com>
(cherry picked from commit c745a92832f1f13ffaf32329306eb9c98a21a359)
Reviewed-on: https://chromium-review.googlesource.com/701574
Trybot-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Commit-Queue: Allen Webb <allenwebb@google.com>

[modify] https://crrev.com/e43d8af075ffad0a1a7c690e21f5db7d13cba6c3/chromeos-base/imageloader/imageloader-9999.ebuild

Project Member

Comment 207 by bugdroid1@chromium.org, Oct 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/06c56d3140a4bb5be69a23a274d0475400b69b1d

commit 06c56d3140a4bb5be69a23a274d0475400b69b1d
Author: Allen Webb <allenwebb@google.com>
Date: Fri Oct 06 23:53:45 2017

platform_ImageLoader: Added tests for --unmount_all and --unmount.

BUG= chromium:760007 
BUG= chromium:772132 
CQ-DEPEND=CL:701594
TEST=test_that -b amd64-generic <ip:port> platform_ImageLoaderServer

Change-Id: Ic0547aa60a7c3d69bc29a73c0cb698583d366ac4
Reviewed-on: https://chromium-review.googlesource.com/682339
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
(cherry picked from commit 7076091b18ab7d8b14722d224b456409b89070bb)
Reviewed-on: https://chromium-review.googlesource.com/690815
Trybot-Ready: Allen Webb <allenwebb@google.com>
Commit-Queue: Allen Webb <allenwebb@google.com>

[modify] https://crrev.com/06c56d3140a4bb5be69a23a274d0475400b69b1d/client/site_tests/platform_ImageLoader/platform_ImageLoader.py

Project Member

Comment 208 by bugdroid1@chromium.org, Oct 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/69850078c6ab9bd3e46dc2312aa89e883adfb0dc

commit 69850078c6ab9bd3e46dc2312aa89e883adfb0dc
Author: Allen Webb <allenwebb@google.com>
Date: Fri Oct 06 23:53:52 2017

imageloader: Added an unmount_all flag.

BUG= chromium:760007 
BUG= chromium:772132 
CQ-DEPEND=CL:690815
CQ-DEPEND=CL:701574
TEST=test_that -b amd64-generic <ip:port> platform_ImageLoaderServer

Change-Id: I1739d36c086c1a124d2c4c79ed2ec05b1fdd2987
Reviewed-on: https://chromium-review.googlesource.com/677792
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
(cherry picked from commit c1a83d303c0643d8d089d501a29a583268d3f43a)
Reviewed-on: https://chromium-review.googlesource.com/701594
Trybot-Ready: Allen Webb <allenwebb@google.com>
Reviewed-by: Allen Webb <allenwebb@google.com>
Commit-Queue: Allen Webb <allenwebb@google.com>

[modify] https://crrev.com/69850078c6ab9bd3e46dc2312aa89e883adfb0dc/imageloader.gyp
[add] https://crrev.com/69850078c6ab9bd3e46dc2312aa89e883adfb0dc/verity_mounter_impl.h
[add] https://crrev.com/69850078c6ab9bd3e46dc2312aa89e883adfb0dc/verity_mounter_impl.cc
[modify] https://crrev.com/69850078c6ab9bd3e46dc2312aa89e883adfb0dc/verity_mounter.h
[add] https://crrev.com/69850078c6ab9bd3e46dc2312aa89e883adfb0dc/verity_mounter_unittest.cc
[modify] https://crrev.com/69850078c6ab9bd3e46dc2312aa89e883adfb0dc/verity_mounter.cc
[modify] https://crrev.com/69850078c6ab9bd3e46dc2312aa89e883adfb0dc/imageloader_main.cc

Project Member

Comment 209 by bugdroid1@chromium.org, Oct 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/08941abfd7fe79eb54f51f71e6fae87a3c9c619f

commit 08941abfd7fe79eb54f51f71e6fae87a3c9c619f
Author: Allen Webb <allenwebb@google.com>
Date: Fri Oct 06 23:53:55 2017

imageloader: Execute unmount_all flag on stopped ui.

BUG= chromium:760007 
BUG= chromium:772132 
CQ-DEPEND=CL:701594
TEST=test_that -b amd64-generic <ip:port> platform_ImageLoaderServer

Change-Id: I0ec96c441b238ce3b9f3a5df220e60a2b9e1e814
Reviewed-on: https://chromium-review.googlesource.com/690438
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
(cherry picked from commit f4e8671e0ce791c7cc6ad570dfe03d695382fa30)
Reviewed-on: https://chromium-review.googlesource.com/701595
Trybot-Ready: Allen Webb <allenwebb@google.com>
Reviewed-by: Allen Webb <allenwebb@google.com>
Commit-Queue: Allen Webb <allenwebb@google.com>

[modify] https://crrev.com/08941abfd7fe79eb54f51f71e6fae87a3c9c619f/imageloader-shutdown.conf

Issue 765910 has been merged into this issue.
Blockedon: 773474
Project Member

Comment 212 by bugdroid1@chromium.org, Oct 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/1e51d8b63530b571c20edc37c0e336637d1f9e00

commit 1e51d8b63530b571c20edc37c0e336637d1f9e00
Author: Allen Webb <allenwebb@google.com>
Date: Fri Oct 13 16:41:10 2017

imageloader: Fix to error logging for --unmount_all.

BUG= chromium:760007 
TEST=test_that -b amd64-generic <ip:port> platform_ImageLoaderServer

Change-Id: Idf22cd6f52c00ce93a511c3ba54e9b9ea190e682
Reviewed-on: https://chromium-review.googlesource.com/713637
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>

[modify] https://crrev.com/1e51d8b63530b571c20edc37c0e336637d1f9e00/imageloader_main.cc

Project Member

Comment 213 by bugdroid1@chromium.org, Oct 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/imageloader/+/27ca312bb82df59772edfa6b037d661569679f03

commit 27ca312bb82df59772edfa6b037d661569679f03
Author: Allen Webb <allenwebb@google.com>
Date: Fri Oct 13 17:54:53 2017

imageloader: Fix to error logging for --unmount_all.

BUG= chromium:760007 
BUG= chromium:773924 
TEST=test_that -b amd64-generic <ip:port> platform_ImageLoaderServer

Change-Id: Idf22cd6f52c00ce93a511c3ba54e9b9ea190e682
Reviewed-on: https://chromium-review.googlesource.com/713637
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
(cherry picked from commit 1e51d8b63530b571c20edc37c0e336637d1f9e00)
Reviewed-on: https://chromium-review.googlesource.com/718992
Commit-Queue: Greg Kerr <kerrnel@chromium.org>
Trybot-Ready: Greg Kerr <kerrnel@chromium.org>

[modify] https://crrev.com/27ca312bb82df59772edfa6b037d661569679f03/imageloader_main.cc

Status: Verified (was: Fixed)
Verified no issue with M64.0.3282.192 10176.80.0 stable glimmer by repeatedly rebooting and shut off power during normal operation, starting up and powering down sequences.  I believe this issue has long been fixed as we have not observed any device losing enrollment issue during our testings for the past months.
Status: Assigned (was: Verified)
Summary: device losing enrollment - Lenovo and PixelBook devices (was: device losing enrollment - Lenovo devices)
I have seen the same thing on my PixelBook. Just filed a feedback report
visit_id=1-636561358123172505-2890521879

The funny thing is that after re-enrolling and going through the re-adding of a (the same) user all my data was preserved. Version: M64
Status: Verified (was: Assigned)
I don't believe there's any evidence this is the same issue as this closed bug.

Your issue may be related to  crbug.com/810716  but let's keep this one closed unless we find the verified fixed issue here has somehow returned from the dead.
Haven't looked at the feedback from #215 yet. But if the user data is preserved after re-creating the user, that means the stateful partition was not cleared, and it's only Chrome that lost state. In this case, re-creating the same user will give access to the already existing user directory.  Issue 810716  is different - we lose stateful there due to non-communicating TPM.

It's possible that Chrome is losing state due to the filesystem corruption. Not clear if related to this specific issue.
Are people starting to see this issue again?  I have started to have devices drop off our network and need re-enrolled again which is identical to the symptoms we experienced with this.  So far it has only been 10-15 but that too is has this one started and before long all 2000ish had unenrolled.
-Thanks Nick
It happened again.
visit_id=1-636572826189694351-3714448021
Status: Assigned (was: Verified)
Reproduction:

Leave eve running, don't close the lid. Wait until it goes into suspend mode. Try to wake it up. ...

I have seen several oddities in this case.
Re #215, #217, #220: I actually was wrong. If the tpm was not cleared, it is possible to see out-of-box UI, but after logging in again with the previously existing user see that user's data. So, it's possible that encrypted stateful was lost while everything else was preserved. I wouldn't tie Pixelbook issues to  issue 810716 , though - the security module is different on those devices. Also, the root cause is likely different from this one, especially seeing the repro steps tied to suspend. Let's open a separate bug for that.
Can you do this? 
Update: I am now every time going through the OOBE. Sometimes it asks for enterprise enrollment, sometimes it forgets the users and let me re-add them, ...
Not sure if you want this to investigate further, but using this system is somewhat annoying as is. I am tempted to remove all users and re-add them myself.. well ... if that is even possible at this time. 
Cc: skuhne@chromium.org
Status: Verified (was: Assigned)
Re #222: Sure. Turns out we have a bug for it already: b/74457045. Let's continue there. Seems to be quite specific to the device that shows this behavior, and happens after each suspend, so the root cause must be different. Re-closing this bug.
This issue has begun appearing on our school district devices.  We are running lenovo yoga 11e Chromebooks OS v.63.  They are losing WiFi information and booting to set up screen forcing re-enrollment after connecting to WiFi.  Is there a solution that we should try?  Thank you for assistance.
Have seen this enterprise unenrollment issue on ASUS Chromeboxes -- have any updates made that would improve the situation? 
Enterprise unenrollment issues for some models are tracked in  issue 810716 .
The fixes for those are made in 67.
We have experienced this issue on Lenovo Chromebook 13  with OS version 69.0.3497.95, 100+ devices effected so far.
We can provide log file is required.
Please let me know the next step.
noz.safa, the issue at hand has been resolved a long time ago. Even though you may experience similar symptoms, it's likely due to a different cause. Therefore, could you please file a separate bug?
We are experiencing the same problem on Samsung and Dell Chromebooks.  Has there been a new bug opened for re-occurrence mentioned in comment 228 of this issue?  I couldn't find one with a simple search.  I would like to add my info to an existing incident but if there isn't one I will open a new one.

Comment 231 Deleted

I have a user experiencing devices losing enrollment for Dell Chromebook 13 3380. This issue has began recently. If there is no other bug open at the moment we will proceed to investigate a open a new bug if needed. Does anyone know of other recent bugs for losing enrollment?
#232, an enrollement issue on that machine is being tracked at crbug.com/878595

We are having the same issues with Dell Chromebooks 3120s, and 3180s. It seems related to chromebooks that doesn't get used daily.
Showing comments 135 - 234 of 234 Older

Sign in to add a comment