[Bug 1529402] Re: 15.04 Upgrade crash results in powered off server
Robert Hardy
1529402 at bugs.launchpad.net
Sat Dec 26 20:32:14 UTC 2015
Please note the automatic captured data was on the server pre-upgrade
15.04. I did not think ubuntu-bug would run on the corrupted snapshot if
I chrooted so I didn't try.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1529402
Title:
15.04 Upgrade crash results in powered off server
Status in ubuntu-release-upgrader package in Ubuntu:
New
Bug description:
I attempted to upgrade a small home server that serves my parents from 15.04 to 15.10 to remain supported.
The first attempt at this resulted in a crash and power off in roughly the last 20% of the upgrade. The system is a desktop but it does have a good AVR capable UPS protecting it..
Thanks to btrfs I was able to recover and was able to revert my root
to the snapshot before the upgrade and restore the system. I then
attempted to cleanup the mess by removing the @badroot. I found I
could not delete it as btrfs kept insisting an empty directory had
files in it. Running brtfsck --repair from a rescue disk saw nothing
wrong with the file system. Some btrfs developers told me this is
already fixed in 4.3. It was unclear if that was the kernel, btrfs
tools or both. I was eventually forced to wipe and reformat my root
and restore a full tar ball backup I had. That worked and got me up
and running on a root file system free of corruption. I then tried a
do-release-upgrade again, the results of which are this bug report.
I was doing the upgrade over ssh from remote. The upgrade was running
fine until it got to around 85%. The text at the end of the attached
file 20151223ThorFail.txt is the last that appeared on the console.
Shortly after that appeared the system went unreachable and the next
day when I arrived to debug I again found the system powered down with
a corrupt and un-bootable root. My parents had not touched it. From a
rescue USB I moved the borked root file system to @_failed_upgrade and
reverted to the pre-upgrade snapshot. Please note I still have the
borked root file system as a snapshot and the system in the pre-
upgrade state. There should be something useful in that failed
snapshot but I'm not seeing it. What was logged on the console did not
really help me figure why the upgrade was failing. Would someone
please give me some pointers on how I can debug this further? I really
don't want to fully reinstall the server from scratch...
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubuntu-release-upgrader-core 1:15.04.14.3
ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10
Uname: Linux 3.19.0-42-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
CrashDB: ubuntu
Date: Sat Dec 26 14:40:53 2015
InstallationDate: Installed on 2012-12-22 (1099 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to vivid on 2015-12-23 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1529402/+subscriptions
More information about the foundations-bugs
mailing list