我强制关闭了我的 Ubuntu 笔记本电脑，现在 Ubuntu 无法启动。我尝试重新安装 Ubuntu，但无法格式化硬盘。
这是我收到的错误。
单击“忽略”约 10 次后，将显示这两个分区。
我无法使用 Gparted 删除分区。我是 ubuntu 新手，所以不知道该怎么办？
通过实时 USB 运行以下命令。
ubuntu@ubuntu:~$ sudo badblocks -nsv /dev/sda
/dev/sda is apparently in use by the system; it's not safe to run badblocks!
另一个可能对调试有用的输出：
ubuntu@ubuntu:~$ sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: WDC PC SN520 SDAPMUW-256G-1001
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 536144C8-7CBB-4497-A20D-C6D39DD7EABE
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 500117503 499066880 238G Linux filesystem
更多数据：
ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/loop0: 1.98 GiB, 2103640064 bytes, 4108672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 29.9 MiB, 31334400 bytes, 61200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 54.98 MiB, 57626624 bytes, 112552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 255.58 MiB, 267980800 bytes, 523400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 62.9 MiB, 65105920 bytes, 127160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 49.8 MiB, 52203520 bytes, 101960 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/nvme0n1: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: WDC PC SN520 SDAPMUW-256G-1001
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 536144C8-7CBB-4497-A20D-C6D39DD7EABE
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 500117503 499066880 238G Linux filesystem
Disk /dev/sda: 114.62 GiB, 123060879360 bytes, 240353280 sectors
Disk model: Ultra USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x56f48570
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 0 5439487 5439488 2.6G 0 Empty
/dev/sda2 5017392 5025327 7936 3.9M ef EFI (FAT-12/16/32)
/dev/sda3 5439488 240353279 234913792 112G 83 Linux
ubuntu@ubuntu:~$ sudo fsck -f /dev/nvme0n1p2
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext2: Input/output error while trying to open /dev/nvme0n1p2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
ubuntu@ubuntu:~$
更多细节：
ubuntu@ubuntu:~$ sudo fsck -f /dev/sda3
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda3 is mounted.
e2fsck: Cannot continue, aborting.
更多细节：
ubuntu@ubuntu:~$ sudo e2fsck -f -b 32768 /dev/nvme0n1p2
e2fsck 1.45.5 (07-Jan-2020)
Error reading block 30965760 (Input/output error). Ignore error<y>? yes
Force rewrite<y>? yes
Superblock has an invalid journal (inode 8).
Clear<y>? yes
*** journal has been deleted ***
Superblock has_journal flag is clear, but a journal is present.
Clear<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data. Clear<y>? yes
Error reading block 6291570 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 6291597 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 6291718 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 6291719 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 1576532 was part of the orphaned inode list. FIXED.
Inode 1576538 was part of the orphaned inode list. FIXED.
Error reading block 6815909 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 7864841 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 12058950 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 12058951 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253160 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253161 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253162 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253163 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253164 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253165 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253166 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253167 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253168 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253169 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253170 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253171 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253172 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253173 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253174 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 16253175 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 24117297 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 24117658 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 27263127 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Inode 6820975 was part of the orphaned inode list. FIXED.
Inode 7869489 was part of the orphaned inode list. FIXED.
Error reading block 31982810 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 33554476 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 33554478 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 34603382 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 34603493 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 35651726 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 35651955 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 37224639 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 38273066 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 38273078 (Input/output error) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 39845934 (Input/output error) while getting next inode from scan. Ignore error<y>?
.... 上述命令不断重复..
我在 Gparted 中看到的两个分区的状态。
答案1
在启动 NVMe 时，您无法对其进行操作。
让我们检查您的文件系统，看看是否可以修复它。
- 以“试用 Ubuntu”模式启动 Ubuntu Live DVD/USB
terminal按Ctrl+ Alt+打开窗口T- 输入sudo fdisk -l识别“Linux 文件系统”的 /dev/sdXX 设备名称- 输入
sudo fsck -f /dev/nvme0n1p2，替换sdXX为您之前找到的数字 fsck如果有错误则重复命令- 类型
reboot
更新＃1：
请将笔记本电脑退回至购买地点，进行保修更换。