On 8/29/20 7:34 AM, TimC wrote:
Hi Dusty
Is this a likely culprit?
```
-- Reboot --
Aug 28 20:56:24 localhost.localdomain systemd[1]: Finished OSTree Finalize Staged
Deployment.
Aug 28 21:07:23 localhost.localdomain systemd[1]: Stopping OSTree Finalize Staged
Deployment...
Aug 28 21:07:23 localhost.localdomain ostree[14561]: Finalizing staged deployment
Aug 28 21:07:32 localhost.localdomain ostree[14561]: Copying /etc changes: 10 modified, 0
removed, 34 added
Aug 28 21:07:32 localhost.localdomain ostree[14561]: Copying /etc changes: 10 modified, 0
removed, 34 added
Aug 28 21:08:30 localhost.localdomain ostree[14561]: **
Aug 28 21:08:30 localhost.localdomain ostree[14561]:
OSTree:ERROR:src/libostree/ostree-sysroot-deploy.c:1775:install_deployment_kernel:
assertion failed (kernel_layout->bootcsum == bootcsum):
("02ec07fa832b4485887f6dbac19d0311e3>
Aug 28 21:08:30 localhost.localdomain ostree[14561]: Bail out!
OSTree:ERROR:src/libostree/ostree-sysroot-deploy.c:1775:install_deployment_kernel:
assertion failed (kernel_layout->bootcsum == bootcsum):
("02ec07fa832b4485887f6dba>
Aug 28 21:08:30 localhost.localdomain systemd[1]: ostree-finalize-staged.service: Control
process exited, code=dumped, status=6/ABRT
Aug 28 21:08:30 localhost.localdomain systemd[1]: ostree-finalize-staged.service: Failed
with result 'core-dump'.
Aug 28 21:08:30 localhost.localdomain systemd[1]: Stopped OSTree Finalize Staged
Deployment.
Aug 28 21:08:30 localhost.localdomain systemd[1]: ostree-finalize-staged.service:
Consumed 8.211s CPU time.
```
I would say so. It's either a bug or the things you did to modify the system
(mentioned below) caused some
corruption maybe.
Note that this is from yesterday’s fail. When I tried again today, I only get this
(before reboot):
```
-- Reboot --
Aug 29 11:12:12 localhost.localdomain systemd[1]: Finished OSTree Finalize Staged
Deployment.
```
When I run `sudo ostree admin finalize-staged`, it fails, thus:
```
sudo ostree admin finalize-staged
Copying /etc changes: 10 modified, 0 removed, 34 added
**
OSTree:ERROR:src/libostree/ostree-sysroot-deploy.c:1775:install_deployment_kernel:
assertion failed (kernel_layout->bootcsum == bootcsum):
("02ec07fa832b4485887f6dbac19d0311e3039855cc6ebd57aefaafa4a3997d1e" ==
"fc8629fdb6f5355dd5359350296b619216cbc32e19887511caf75ee9d6aafbad")
Bail out!
OSTree:ERROR:src/libostree/ostree-sysroot-deploy.c:1775:install_deployment_kernel:
assertion failed (kernel_layout->bootcsum == bootcsum):
("02ec07fa832b4485887f6dbac19d0311e3039855cc6ebd57aefaafa4a3997d1e" ==
"fc8629fdb6f5355dd5359350296b619216cbc32e19887511caf75ee9d6aafbad")
Aborted
```
I’d guess that’s a fail originating somehow in my trying to increase the image and
filesystem in the download as my first attempts to layer packages just ran out of space.
The approach worked with Fedora-IoT 29 and was based on decompressing, appending 0’s to
the end of the file and then resizing the filesystem.
I'm not sure if that is OK or not. I haven't used IoT much, but I do know the
rpm-ostree ecosystem a bit. Somebody else might
be able to answer better than I.
Would it make sense to confirm the cause by layering a single package onto the original
download, if that’s useful? I think that I will need some mechanism to increase the image
size, tho’ or I won’t be able to get many tools onto the pi.
That would be good information.
>
> Tim