Bug#781742: upgrade-reports: armel wheezy->jessie on QNAP: flash-kernel error in dist-upgrade and various glitches but mostly successful
On Sat, 2015-04-04 at 14:13 +0200,
debbug.jessie.upgradereport.nospam.plz@sub.noloop.net wrote:
> On Sat, Apr 04, 2015 at 10:52:35 +0100, Ian Campbell wrote:
> > On Thu, 2015-04-02 at 13:04 +0200, reportbug wrote:
> > > ** error: apt-get dist-upgrade broke during a flash-kernel
> > >
> > > This happened on the two QNAP TS-419P+ devices but not on the QNAP
> > > TS-219P II Turbo device. The "apt-get dist-upgrade" stage aborted in
> > > a flash-kernel trigger that failed, because it seemed to try to flash
> > > the jessie 3.16 kernel before it was properly unpacked. Unfortunately
> > > I don't have the error message
> >
> > Did you upgrade with "apt-get update ; apt-get upgrade ; apt-get
> > dist-upgrade" as recommended by the installation guide or did you follow
> > a different path?
> >
> > I tried an update+upgrade+dist-upgrade from a freshly installed Wheezy
> > system and I didn't see this.
>
> Yep, "update", then "upgrade" (no problems there), then "dist-upgrade" which
> failed, then "apt-get -f install" to keep going, then another "dist-upgrade"
> to wrap it up.
>
> I found I had logged the output of "dpkg -l" on one of the failing
> machines just before the update started, attaching that to this mail.
>
> I also just now discovered a /var/log/apt/term.log that contains the entire
> upgrade process recorded! It does seem to contain the entire terminal
> output, including the interactive diffs and manual root shell sessions ("Z")
> shown during file conflicts (which contain local and perhaps confidential
> information) so I don't feel like attaching the whole log,
Understood.
> but here is
> everything from "Log started" to "Log ended" for the particular dist-upgrade
> run that failed, plus everything from "Log started" to "Log ended" for
> "apt-get -f install" just after that. Not shown are the first upgrade and
> the final dist-ugprade.
Thanks.
I had a go at reproducing this back when you first reported it, without
much luck. Perhaps the dpkg -l will give some clue as to what the
difference is.
> The last lines of the attached log for "dist-upgrade" are:
>
> Preparing to unpack .../module-init-tools_18-3_all.deb ...
> Unpacking module-init-tools (18-3) over (9-3) ...
> Selecting previously unselected package linux-image-3.16.0-4-kirkwood.
> Preparing to unpack .../linux-image-3.16.0-4-kirkwood_3.16.7-ckt7-1_armel.deb ...
> Unpacking linux-image-3.16.0-4-kirkwood (3.16.7-ckt7-1) ...
> Processing triggers for initramfs-tools (0.119) ...
> update-initramfs: Generating /boot/initrd.img-3.2.0-4-kirkwood
> Can't find /boot/vmlinuz-3.16.0-4-kirkwood or /boot/initrd.img-3.16.0-4-kirkwood
Checking and logging those two separately might make sense so we can see
which one failed if this happens again.
And perhaps logging /boot/*$kver* would be a good idea too.
In the absence of being able to repro that might the best we can manage.
> run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
> dpkg: error processing package initramfs-tools (--unpack):
> subprocess installed post-installation script returned error exit status 1
> Processing triggers for install-info (5.2.0.dfsg.1-6) ...
> Errors were encountered while processing:
> initramfs-tools
Reply to: