After the update (from 162 beta), booting resulted in a kernel panic. Relevant lines:
Run /init as init process
/bin/sh: symbol lookup error: /lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
…etc. The machine is a 64-bit Atom. I had to reinstall everything, but imaged the system, so I have access to all logs.
In the update log, there are a massive amount (2203 lines!) of
/usr/lib/dracut/modules.d/90kernel-modules/module-setup.sh: line 17: warning: command substitution: ignored null byte in input
thank you very much for your post! Glad to receive some testing feedback.
I had to reinstall everything, but imaged the system, so I have access to all logs.
That’s a professional way of doing this. Great!
Could you please post or attach (probably works better) the update log here? The upgrade went smooth on my machine, so I am curious what went wrong in your case.
If you are on testing or next this is normal. (pakfire always reinstall the current version to make sure that you have all changes that maybee added after you has installed the version)
FWIW, I did an upgrade to CU 163 on a test box and it seems to have worked okay other than the WUI never came back – after starting the upgrade from the WUI. Waiting and watching the console till things quiesced, I rebooted. It seems okay but I have done minimal testing as this box is downstream behind an edger outer hanging off my blue zone – damn little traffic there.
That said, it seems functional
/boot was 128 MB. It’s not filled now, at least.
This system has always been on testing, and was once installed as CU136 if I am to believe the upgrade logs.
