Ubuntu 系统大版本升级指南:sudo do-release-upgrade 实践记录

我不道啊的头像
我不道啊
标签:
Ubuntu 升级教程do-release-upgradeUbuntu Hash 校验和不符系统大版本升级

在 Ubuntu 系统中使用 sudo do-release-upgrade 升级到新版本时,可能会遇到软件包锁定、网络校验错误等问题。本文记录一次完整升级过程,并提供优化方法和注意事项。

升级前准备

如果升级到非 LTS 版本,需要运行该命令更改 Prompt 为 normal

复制
展开
~ sudo nano /etc/update-manager/release-upgrades

# Default behavior for the release upgrader.

[DEFAULT]
# Default prompting and upgrade behavior, valid options:
#
#  never  - Never check for, or allow upgrading to, a new release.
#  normal - Check to see if a new release is available.  If more than one new
#           release is found, the release upgrader will attempt to upgrade to
#           the supported release that immediately succeeds the
#           currently-running release.
#  lts    - Check to see if a new LTS release is available.  The upgrader
#           will attempt to upgrade to the first LTS release available after
#           the currently-running one.  Note that if this option is used and
#           the currently-running release is not itself an LTS release the
#           upgrader will assume prompt was meant to be normal.

# 这里,升级到 LTS 版本,这里可以不用动,非 LTS 则需要改为 normal
Prompt=normal

在执行 do-release-upgrade 前,确保系统已安装所有可用更新:

复制
展开
~  sudo do-release-upgrade
正在检查新版 Ubuntu
请在升级前安装您的发行版所有可用更新。
~  
复制
展开
sudo apt-mark unhold "*"           # 解除所有被锁定的软件包
sudo apt update && sudo apt upgrade -y

说明:解除锁定可以避免升级过程中出现版本冲突,保证系统包为最新状态。

常见问题:Hash 校验和不符

升级过程中可能出现如下错误:

复制
展开
错误 https://mirrors.cloud.tencent.com/ubuntu plucky-updates/restricted amd64 Components                                           
  Hash 校验和不符
Hashes of expected file:
 - Filesize:212 [weak]
 - SHA256:87df20faa3c957ab6928e62f6d46e6b55cab298e31055d610406b8257b0b50be
 - SHA1:d807a646aa6aa0d90ab71b77a1f1bf297d547718 [weak]
 - MD5Sum:fe603e783a8ab4c6af9692c62e8d038d [weak]
Hashes of received file:
 - SHA256:8d01c055a4f11f61e143a38cc33038e3206563ee60884034879058c1c1d9574c
 - SHA1:f7f48a759a3fcc629445830409454b467ff1c9fe [weak]
 - MD5Sum:4addb445ffc5944f5c0b0d345c021bcc [weak]
 - Filesize:212 [weak]
Last modification reported: Mon, 17 Nov 2025 15:22:29 +0000
Release file created at: Tue, 18 Nov 2025 02:47:08 +0000

99% [执行中]                                                                                                                      99% [执行中]                                                                                                                      已下载 126 kB,耗时 0秒 (0 B/s)                                                                                                         

升级时出错 

升级过程中出错。这通常是一些网络问题,请检查您的网络连接后再试 

E:无法下载 
https://mirrors.cloud.tencent.com/ubuntu/dists/plucky-updates/restricted/dep11/Components-amd64.yml.xz 
Hash 校验和不符 
Hashes of expected file: 
- Filesize:212 [weak] 
- 
SHA256:87df20faa3c957ab6928e62f6d46e6b55cab298e31055d610406b8257b0b50be 
- SHA1:d807a646aa6aa0d90ab71b77a1f1bf297d547718 [weak] 
- MD5Sum:fe603e783a8ab4c6af9692c62e8d038d [weak] 
Hashes of received file: 
- 
SHA256:8d01c055a4f11f61e143a38cc33038e3206563ee60884034879058c1c1d9574c 
- SHA1:f7f48a759a3fcc629445830409454b467ff1c9fe [weak] 
- MD5Sum:4addb445ffc5944f5c0b0d345c021bcc [weak] 
- Filesize:212 [weak] 
Last modification reported: Mon, 17 Nov 2025 15:22:29 +0000 
Release file created at: Tue, 18 Nov 2025 02:47:08 +0000 
, E:部分索引文件下载失败。如果忽略它们,那将转而使用旧的索引文件。 


正在恢复原始系统状态

中止
正在读取软件包列表... 完成     
正在分析软件包的依赖关系树... 完成 
正在读取状态信息... 完成  

具体表现为:

  • Expected SHA256、SHA1、MD5 与下载文件不一致
  • 升级中止并提示 “升级过程中出错”

原因:

  1. 第三方镜像源同步延迟
  2. 网络不稳定导致文件下载异常

解决方案

  1. 切换为官方软件源,避免第三方源同步延迟:
复制
展开
# /etc/apt/sources.list 示例
Types: deb
URIs: http://archive.ubuntu.com/ubuntu
Suites: plucky plucky-updates plucky-security plucky-backports
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

# Types: deb
# URIs: http://security.ubuntu.com/ubuntu/
# Suites: noble-security
# Components: main restricted universe multiverse
# Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
  1. 更新系统软件包
复制
展开
sudo apt update && sudo apt upgrade -y
  1. 确保网络通畅,避免下载中断或文件损坏。

  2. 再次运行升级命令:

复制
展开
sudo do-release-upgrade

注意事项

  • 升级前确保当前版本所有软件包更新到最新状态
  • 使用官方源可降低升级失败风险
  • 网络稳定性直接影响升级文件的校验和
  • 第三方源或镜像可能存在同步延迟,导致升级失败

作者:https://blog.xn--rpv331d.com/我不道啊

链接:https://blog.xn--rpv331d.com/我不道啊/blog/130

转载请保留文章出处...

No data
No data