我想修复损坏的逻辑卷和分区。SSD最初由Proxmox操作系统使用。然而,我试图通过Ubuntu (安全图形)从Live中恢复它。
首先,我尝试直接运行fsck来破坏逻辑卷。但是,我发现修复超级块会导致分区级别上的另一个错误。
$ sudo fsck -b 32768 /dev/dm-11
...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mapper/pve-data_meta1
...
$ journalctl | grep error
...
Apr 03 05:43:30 ubuntu kernel: blk_update_request: critical medium error, dev nvme0n1, sector 1902965000 op 0x0:(READ) flags 0x80700
Apr 03 05:43:30 ubuntu kernel: Buffer I/O error on dev dm-11, logical block 42, async page read在看到这个错误日志之后,我开始尝试修复nvme0n1。然而,警告说它正在使用中。
$ sudo fsck -n /dev/nvme0n1
...
Warning! /dev/nvme0n1 is in use.
ext2fs_open2: Superblock invalid, trying backup blocks...
ext2fs_open2: Bad magi number in super-block while trying to open /dev/nvme0n1
...
$ sudo fsck -b 32768 /dev/nvme0n1
...
/dev/nvme0n1 is in use.
e2fsck: Cannot continue, aborting.umount /dev/nvme0n1,但它返回umount: /dev/nvem0n1: not mounted.mount /dev/nvme0n1 /mnt,mount: /mnt: /dev/nvme0n1 already mounted or mount point busy说。sudo systemctl stop systemd-udevd,但不工作。sudo swapoff -a,但不工作。lsof /dev/nvme0、lsof /dev/nvme0n1和lsof /dev/dm-11,什么都不返回。sudo e2fsck -f -b 32768 /dev/nvme0n1,但不工作。欢迎任何意见或意见。请给我一些提示来解决这个问题。
发布于 2023-05-24 12:20:57
在我的例子中,这个设备是由正在运行的Docker使用的。在我停下来之后,一切都很好
sudo systemctl stop dockerhttps://askubuntu.com/questions/1400645
复制相似问题