upgrade from 20.04 to 22.04 failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
do-release-upgrade seems to have failed on grub-efi, wondering if it choked on my config; attached logs as per error message.
System was left in bootable, runnable state, but a zpool was blown away.
------
system pools and one pool on NVMe were ok:
sribe@sribe000:~$ sudo zpool status
pool: bpool
state: ONLINE
scan: scrub repaired 0B in 0 days 00:00:01 with 0 errors on Sun May 8 00:24:02 2022
config:
NAME STATE READ WRITE CKSUM
bpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-
ata-
errors: No known data errors
pool: pg_pool
state: ONLINE
scan: scrub repaired 0B in 0 days 00:00:15 with 0 errors on Sun May 8 00:24:16 2022
config:
NAME STATE READ WRITE CKSUM
pg_pool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
nvme-
nvme-
errors: No known data errors
pool: rpool
state: ONLINE
scan: scrub repaired 0B in 0 days 00:00:11 with 0 errors on Sun May 8 00:24:13 2022
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-
ata-
errors: No known data errors
------
but an archive pool on HDD is fubar:
sribe@sribe000:~$ sudo zpool import
pool: zp_repo
id: 117191089997894
state: FAULTED
status: The pool metadata is corrupted.
action: The pool cannot be imported due to damaged devices or data.
The pool may be active on another system, but can be imported using
the '-f' flag.
see: http://
config:
zp_repo FAULTED corrupted data
logs
mirror-1 ONLINE
nvme-
nvme-
------
the pool is not active on another system and import with -f fails
Fortunately, reverting to a snapshot of the system before the failed upgrade brought the zpool back. I have a pretty customized ZFS setup, including tweaks to /usr/share/
affects: | ubuntu → ubuntu-release-upgrader (Ubuntu) |
tags: | added: focal |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1974598/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]