在强制关闭 Ubuntu 20.04 几次后，我在从 256GB M.2 SATA SSD（sdb）启动时收到 busybox 提示。从另一台 HDD（sda）启动时，尝试修复 SSD 时显示以下错误：
Error while repairing filesystem
Error repairing filesystem on /dev/sdb5: Process reported exit code 12: e2fsck 1.45.5 (07-Jan-2020)
e2fsck: unable to set superblock flags on /dev/sdb5 (udisks-error-quark, 0)
该SSD上有两个请求，分别是Root（sdb1）和Home（sdb5）。
我可以挂载 Root 并进行浏览，但无法挂载主页。
我目前采取的步骤-
# sudo fsck -f /dev/sdb
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
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>
Found a dos partition table in /dev/sdb
尝试用以下方法替换替代超级块e2fsck -b 32768 <device>
这些都不起作用。
使用备份对 Root 进行了（部分）备份，我还没有尝试格式化和恢复。
可以修复这个 SSD 吗？具体问题是什么？
编辑：
~ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
<removed snaps and loops>
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 114.5G 0 part /
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 124G 0 part /home
└─sda6 8:6 0 227.3G 0 part /run/timeshift/backup
sdb 8:16 0 238.5G 0 disk
├─sdb1 8:17 0 93.3G 0 part
├─sdb2 8:18 0 1K 0 part
└─sdb5 8:21 0 145.2G 0 part
~ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: OSC M.2 256GB
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: 0x9c55915b
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 195710975 195708928 93.3G 83 Linux
/dev/sdb2 195710976 500117503 304406528 145.2G 5 Extended
/dev/sdb5 195715072 500117503 304402432 145.2G 83 Linux
编辑1：
~ sudo fsck -f /dev/sdb1
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sdb1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
fsck.ext4: unable to set superblock flags on /dev/sdb1
/dev/sdb1: ********** WARNING: Filesystem still has errors **********
➜ ~ sudo fsck -f /dev/sdb5
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Input/output error while trying to open /dev/sdb5
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>
谢谢