![主板和 CPU 升级后安装交换时出错](https://linux22.com/image/1004183/%E4%B8%BB%E6%9D%BF%E5%92%8C%20CPU%20%E5%8D%87%E7%BA%A7%E5%90%8E%E5%AE%89%E8%A3%85%E4%BA%A4%E6%8D%A2%E6%97%B6%E5%87%BA%E9%94%99.png)
几天前,我从 Xeon E5450 换成了 E5-2680v2。除了破坏我的网络设置外,我现在在启动过程中遇到了一些问题,我想解决这些问题。
我将把这篇文章分成几篇文章,以便保持一切井然有序。
现在这篇文章是关于我遇到的两个磁盘问题:1:journalctl -b 有以下消息:
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: random: crng init done
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: scsi 7:0:9:0: Wrong diagnostic page; asked for 7 got 0
>Nov 15 21:39:59 nucleus kernel: ses 7:0:9:0: Attached Enclosure device
>Nov 15 21:39:59 nucleus kernel: raid6: sse2x1 gen() 8785 MB/s
>Nov 15 21:39:59 nucleus kernel: raid6: sse2x1 xor() 7083 MB/s Nov 15 21:39:59 nucleus kernel: raid6: sse2x2 gen() 11168 MB/s
>Nov 15 21:39:59 nucleus kernel: raid6: sse2x2 xor() 7630 MB/s
有趣的是,尽管时间戳表明情况并非如此,但在 ses 7:0:9:0: Attached Enclosure device 这一行之后,接下来的步骤需要半分钟或更长时间才能出现在屏幕上。
我不知道这是否有任何影响,但我觉得值得一提
2:
Nov 15 21:41:28 nucleus systemd[1]: dev-disk-by\x2duuid-99357771\x2d97a4\x2d476b\x2da82e\x2d2bfb8d4dd759.device: Job dev-disk-by\x2duuid-99357771\x2d97a4\x2d476b\x2da82e\x2d2bfb8d4dd759.device/start timed out.
Nov 15 21:41:28 nucleus systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-99357771\x2d97a4\x2d476b\x2da82e\x2d2bfb8d4dd759.device.
Nov 15 21:41:28 nucleus systemd[1]: Dependency failed for /dev/disk/by-uuid/99357771-97a4-476b-a82e-2bfb8d4dd759. Nov 15 21:41:28 nucleus systemd[1]: Dependency failed for Swap. Nov 15 21:41:28 nucleus systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Nov 15 21:41:28 nucleus systemd[1]: dev-disk-by\x2duuid-99357771\x2d97a4\x2d476b\x2da82e\x2d2bfb8d4dd759.swap: Job dev-disk-by\x2duuid-99357771\x2d97a4\x2d476b\x2da82e\x2d2bfb8d4dd759.swap/start failed with result 'dependency'.
Nov 15 21:41:28 nucleus systemd[1]: dev-disk-by\x2duuid-99357771\x2d97a4\x2d476b\x2da82e\x2d2bfb8d4dd759.device: Job dev-disk-by\x2duuid-99357771\x2d97a4\x2d476b\x2da82e\x2d2bfb8d4dd759.devi
由于某种原因,交换分区无法挂载。据我所知,尽管磁盘在新硬件上从 /dev/sda 移到了 /dev/sdb,但 UUID 是正确的。我打算纠正这个问题,但是使用 UUID 我认为这不应该是一个问题,特别是考虑到现在我们讨论的是 /dev/sdb5,而 root 在 /dev/sdb1 上,这似乎运行良好。
手动运行 swapon -a 将毫无问题地挂载交换。
请让我知道我可以提供哪些日志条目以便有人理解这一点。
编辑:smartctl 仅显示一个 CRC 错误,没有其他错误。我认为硬件应该没有问题。
我在谷歌上找到了一篇帖子,其中提到了同样的问题,通过从 fstab 中删除交换或不将其格式化为 Linux 交换来解决。似乎同时使用这两种方法也会尝试安装两次。我已经在 fstab 中注释了该行,并将查看结果。
也感谢您对这篇文章的格式化。