主页 / ubuntu / 问题

问题[ssd](ubuntu)

Martin Hope
Worn-out_home-tech
Asked: 2024-11-05 11:11:49 +0800 CST
  • 7

从 24.04 升级到 24.10 后，当我将便携式三星 T7（Ext4）插入 USB 端口时，它不再自动挂载。

当我插入它时，驱动器的名称会出现在 files/nautilus 中，但弹出符号不会出现，程序无法访问它。当我单击驱动器名称时，它将安装。

但是，如果我插入一个拇指驱动器（Fat32），它就会完美地自动挂载。

我应该如何尝试修复此问题？

编辑：我还尝试了“磁盘”并覆盖了正常会话设置，并为驱动器打开了“启动时自动挂载”，但这不起作用。

ssd
Martin Hope
Alex
Asked: 2024-08-17 22:18:40 +0800 CST
  • 6

在我主 SSD 上复制一个大文件后不久，IO PSI 值上升到 90% 以上，系统变得非常迟钝。大约需要一分钟才能恢复正常。

我还注意到在执行诸如此类的操作时会出现冻结问题docker pull，但现在能够重现我认为是同一问题rsync。

当测试文件位于第二个SSD时，问题似乎不会发生。

可重现的示例：

受到这篇文章的启发，我每秒将负载和 IO PSI 记录到 CSV 文件中。

在第一个终端会话中我运行

rm monitor.csv; t=0; while true; do t=$(($t+1)); echo $s,$(cat /proc/loadavg | cut -d ' ' -f1),$(grep some  /proc/pressure/cpu  | cut -d' ' -f2 | cut -d= -f2),$(grep some /proc/pressure/io | cut -d' ' -f2 | cut -d= -f2),$(grep full /proc/pressure/io | cut -d' ' -f2 | cut -d= -f2) >> monitor.csv; sleep 1; done

我在主 SSD 上复制了一个 3.3 GB 的测试文件：

rm test.zip ; echo "start rsync" >> monitor.csv ; rsync original.zip test.zip ; echo "end rsync" >> monitor.csv

现在 monitor.csv 如下所示：

1,0.64,0.18,0.00,0.00
2,0.67,0.14,0.00,0.00
3,0.67,0.14,0.00,0.00
4,0.67,0.12,0.00,0.00
start rsync
5,0.67,0.12,0.00,0.00
6,0.67,0.09,0.00,0.00
7,0.70,0.09,0.00,0.00
8,0.70,0.08,0.00,0.00
end rsync
9,0.70,0.08,0.00,0.00
10,0.70,0.42,6.15,5.79
11,0.70,0.42,6.15,5.79
12,0.80,0.35,16.99,15.97
13,0.80,0.35,16.99,15.97
14,0.80,0.28,30.94,29.38
15,0.80,0.28,30.94,29.38
16,1.14,0.23,43.09,41.27
17,1.14,0.23,51.59,49.73
18,1.14,0.19,51.59,49.73
19,1.14,0.19,51.59,49.73
20,1.14,0.33,58.00,55.40
21,2.57,0.27,62.89,60.22
22,2.57,0.27,62.89,60.22
23,2.57,0.22,67.80,65.25
24,2.57,0.22,67.80,65.25
25,2.57,0.18,72.37,69.73
26,3.57,0.18,72.37,69.73
27,3.57,0.15,75.38,72.68
28,3.57,0.15,75.38,72.68
29,3.57,0.12,79.48,76.90
30,3.57,0.12,79.48,76.90
31,4.56,0.10,83.01,80.36
32,4.56,0.10,83.01,80.36
33,4.56,0.08,84.46,81.38
34,4.56,0.08,84.46,81.38
35,4.56,0.06,86.37,83.12
36,5.24,0.06,86.37,83.12
37,5.24,0.05,86.66,83.10
38,5.24,0.05,86.66,83.10
39,5.24,0.04,87.09,82.90
40,5.24,0.04,87.09,82.90
41,5.94,0.03,84.71,80.02
42,5.94,0.03,84.71,80.02
43,5.94,0.02,84.77,79.65
44,5.94,0.02,84.77,79.65
45,5.94,0.02,86.26,80.08
46,6.91,0.02,86.26,80.08
47,6.91,0.01,86.93,80.42
48,6.91,0.01,86.93,80.42
49,6.91,0.01,86.04,79.80
50,6.91,0.01,86.04,79.80
51,7.95,0.01,85.67,79.29
52,7.95,0.01,85.67,79.29
53,7.95,0.01,86.45,79.78
54,7.95,0.01,86.45,79.78
55,7.95,0.00,86.73,79.82
56,8.12,0.00,86.73,79.82
57,8.12,0.18,80.08,73.69
58,8.12,0.18,80.08,73.69
59,8.12,0.33,65.57,60.34
60,7.55,0.33,65.57,60.34
61,7.55,0.27,54.05,49.77
62,7.55,0.27,54.05,49.77
63,7.55,0.22,44.26,40.76
64,7.55,0.18,36.24,33.37
65,7.02,0.18,36.24,33.37
66,7.02,0.18,36.24,33.37
67,7.02,0.14,29.67,27.32
68,7.02,0.12,24.30,22.37
69,7.02,0.12,24.30,22.37
70,6.46,0.10,19.89,18.32
71,6.46,0.10,19.89,18.32
72,6.46,0.08,16.29,15.00
73,6.46,0.08,16.29,15.00
74,6.46,0.06,13.34,12.28
75,5.94,0.06,13.34,12.28
76,5.94,0.05,10.92,10.06
77,5.94,0.05,10.92,10.06
78,5.94,0.04,8.94,8.23
79,5.94,0.04,8.94,8.23
80,5.55,0.03,7.32,6.74
81,5.55,0.03,7.32,6.74
82,5.55,0.02,5.99,5.52
83,5.55,0.02,5.99,5.52
84,5.55,0.02,4.91,4.52
85,5.10,0.02,4.91,4.52
86,5.10,0.01,4.02,3.70
87,5.10,0.01,4.02,3.70
88,5.10,0.01,3.29,3.03
89,5.10,0.01,3.29,3.03

图表：

图表

  • 复制文件仅需约 5 秒
  • 此后 PSI 会变得非常高，一分钟后恢复正常
  • 在此期间，系统 GUI 变得非常迟钝

复制过程结束后，顶部还会闪烁一个警告：

位于红色 NVM/crypt 顶部

对位于第二个 SSD 上的文件进行相同的操作会花费更长的时间，但系统不会冻结，并且 IO PSI 值也不会出现如此严重的峰值：

1,2.42,0.00,0.01,0.01
2,2.42,0.00,0.01,0.01
3,2.42,0.00,0.01,0.00
4,2.23,0.00,0.01,0.00
start rsync
5,2.23,0.00,0.00,0.00
6,2.23,0.00,0.00,0.00
7,2.23,0.00,1.27,1.09
8,2.23,0.00,1.27,1.09
9,2.13,0.00,2.85,2.70
10,2.13,0.00,2.85,2.70
11,2.13,0.18,3.42,3.30
12,2.13,0.18,3.42,3.30
13,2.13,0.14,4.25,4.15
14,2.04,0.14,4.25,4.15
15,2.04,0.12,5.11,5.03
16,2.04,0.12,5.11,5.03
17,2.04,3.72,9.44,7.02
end rsync
18,2.04,3.72,9.44,7.02
19,1.88,3.04,8.63,6.65
20,1.88,3.04,8.63,6.65
21,1.88,2.49,7.07,5.44
22,1.88,2.49,7.07,5.44
23,1.73,2.04,5.79,4.46
24,1.73,2.04,5.79,4.46
25,1.73,1.67,4.74,3.65
26,1.73,1.67,4.74,3.65
27,1.73,1.36,3.88,2.99
28,1.59,1.36,3.88,2.99
29,1.59,1.12,3.17,2.44
30,1.59,1.12,3.17,2.44

系统详细信息

  • 联想 E14

  • Ubuntu 22.04

  • Gnome 和 Wayland

  • 带有 Radeon 显卡的 AMD Ryzen 7 4700U CPU

  • 内置 2 个 NVME SSD，均具有加密文件系统

    • 主 SSD：（mvme0）
      • 型号：KBG40ZNT512G 东芝内存
      • 固件版本：0109AELA（似乎是最新版本）
    • 辅助 SSD：（nvme1）
      • 型号：CT500P3SSD8

  • 两个设备上的调度程序相同：

$ cat /sys/block/nvme0n1/queue/scheduler 
[none] mq-deadline 
$ cat /sys/block/nvme1n1/queue/scheduler 
[none] mq-deadline

理论/问题：

  • 主 SSD 是不是坏了？
  • 这与系统中 PCI-E 通道数量有限有关吗？

尝试过

  • 我尝试了内核 6.8.0-40-generic（我的系统上的标准）以及 6.5.0-45 - 但在这方面表现相同。

EDIT1（根据@ubfan1的评论）

  • Trim 似乎在第二台设备上运行得更多（没有问题）。在主设备上它运行得不那么频繁 - 这是好事还是坏事？
$ journalctl |grep "fstrim\["|grep nvme0
Jul 01 08:32:31 example fstrim[27758]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Jul 01 08:32:31 example fstrim[27758]: /boot: 1.2 GiB (1269686272 bytes) trimmed on /dev/nvme0n1p2
Jul 08 09:53:27 example fstrim[50828]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Jul 08 09:53:27 example fstrim[50828]: /boot: 1.2 GiB (1269567488 bytes) trimmed on /dev/nvme0n1p2
Jul 15 09:43:17 example fstrim[46889]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Jul 15 09:43:17 example fstrim[46889]: /boot: 1.2 GiB (1269567488 bytes) trimmed on /dev/nvme0n1p2
Jul 22 12:33:55 example fstrim[14093]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Jul 22 12:33:55 example fstrim[14093]: /boot: 1.2 GiB (1267404800 bytes) trimmed on /dev/nvme0n1p2
Jul 29 10:15:54 example fstrim[63916]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Jul 29 10:15:54 example fstrim[63916]: /boot: 1.2 GiB (1267404800 bytes) trimmed on /dev/nvme0n1p2
Aug 05 09:37:39 example fstrim[46612]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Aug 05 09:37:39 example fstrim[46612]: /boot: 1.2 GiB (1269469184 bytes) trimmed on /dev/nvme0n1p2

  • 两个设备都是内置的，不通过 USB 连接

  • 智能控制

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.8.0-40-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       KBG40ZNT512G TOSHIBA MEMORY
Serial Number:                      30TPxxxxxxx
Firmware Version:                   0109AELA
PCI Vendor/Subsystem ID:            0x1e0f
IEEE OUI Identifier:                0x8ce38e
Total NVM Capacity:                 512.110.190.592 [512 GB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512.110.190.592 [512 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            8ce38e 0400911b0e
Local Time is:                      Tue Aug 20 08:58:37 2024 CEST
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x001f):   Security Format Frmw_DL NS_Mngmt Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     86 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     3.50W       -        -    0  0  0  0        1       1
 1 +     2.60W       -        -    1  1  1  1        1       1
 2 +     1.80W       -        -    2  2  2  2        1       1
 3 -   0.0500W       -        -    4  4  4  4      800    1200
 4 -   0.0050W       -        -    4  4  4  4     3000   32000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         3
 1 -    4096       0         1

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        29 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    12%
Data Units Read:                    41.196.433 [21,0 TB]
Data Units Written:                 54.357.811 [27,8 TB]
Host Read Commands:                 792.033.014
Host Write Commands:                1.093.950.301
Controller Busy Time:               10.506
Power Cycles:                       3.308
Power On Hours:                     6.391
Unsafe Shutdowns:                   4
Media and Data Integrity Errors:    0
Error Information Log Entries:      44
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               29 Celsius

Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
ssd
Martin Hope
sotirov
Asked: 2023-11-17 20:21:27 +0800 CST
  • 13

在我的主笔记本电脑上运行 Ubuntu 22.04。我使用4TB 十铨 MP34 NVMe作为我的主驱动器。文件系统是ext4.

昨天（11 月 16 日），在下载一些大文件（大约 300 个文件，总共 600GB）时，突然我的笔记本电脑开始出现异常。一切都变得非常慢，我的系统崩溃了。我能够使用可启动 USB 和fsck. 然而，笔记本电脑的速度仍然很慢，并且 NVMe SSD 变得非常热，大约 75 摄氏度（通常低于 35 度）。磁盘只有大约 35% 已满。我在磁盘上运行基准测试，速度不一致并且非常慢。经过几分钟的工作后，磁盘进入只读模式。

最初，我认为存在一些硬件问题。我打开笔记本电脑并用异丙醇清洁触点。我换了另一个NVMe，笔记本电脑工作正常。我重新安装了最初的 NVMe，笔记本电脑又变得非常慢。在某个时候，我决定运行sudo fstrim -av，大约需要 5-6 分钟（经过修剪2.9TB），之后笔记本电脑开始像新的一样工作。我已经使用它超过 5 天了，没有任何问题。我做了一些压力测试和基准测试，一切正常。

我在 11 月 16 日编写的手册的输出sudo fstrim -av：

/boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
/: 2.9 TiB (3138692276224 bytes) trimmed on /dev/nvme0n1p2

看起来fstrim.service工作正常：

cat /var/log/syslog | grep -a fstrim

Nov 13 01:43:37 dev fstrim[98095]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Nov 13 01:43:37 dev fstrim[98095]: /: 2.9 TiB (3140636598272 bytes) trimmed on /dev/nvme0n1p2
Nov 13 01:43:37 dev systemd[1]: fstrim.service: Deactivated successfully.

最后的 TRIM 看起来更正常：

cat /var/log/syslog | grep -a fstrim
Nov 20 01:26:54 dev fstrim[109477]: /boot/efi: 504.9 MiB (529436672 bytes) trimmed on /dev/nvme0n1p1
Nov 20 01:26:54 dev fstrim[109477]: /: 31.5 GiB (33783455744 bytes) trimmed on /dev/nvme0n1p2
Nov 20 01:26:54 dev systemd[1]: fstrim.service: Deactivated successfully.

NVMe 非常新且状况良好：

sudo smartctl -a /dev/nvme0

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.2.0-36-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       TEAM TM8FP4004T
Serial Number:                      xxxxxxxxxxxxxxxxxxxxx
Firmware Version:                   VB421D65
PCI Vendor/Subsystem ID:            0x10ec
IEEE OUI Identifier:                0x00e04c
Controller ID:                      1
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4,096,805,658,624 [4.09 TB]
Namespace 1 Formatted LBA Size:     512
Local Time is:                      Fri Nov 17 12:57:17 2023 EET
Firmware Updates (0x02):            1 Slot
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0014):     DS_Mngmt Sav/Sel_Feat
Log Page Attributes (0x02):         Cmd_Eff_Lg
Maximum Data Transfer Size:         32 Pages
Warning  Comp. Temp. Threshold:     100 Celsius
Critical Comp. Temp. Threshold:     110 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.00W       -        -    0  0  0  0   230000   50000
 1 +     4.00W       -        -    1  1  1  1     4000   50000
 2 +     3.00W       -        -    2  2  2  2     4000  250000
 3 -     0.50W       -        -    3  3  3  3     4000    8000
 4 -   0.0090W       -        -    4  4  4  4     8000   30000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        35 Celsius
Available Spare:                    100%
Available Spare Threshold:          32%
Percentage Used:                    0%
Data Units Read:                    4,447,105 [2.27 TB]
Data Units Written:                 8,885,998 [4.54 TB]
Host Read Commands:                 48,182,921
Host Write Commands:                112,476,615
Controller Busy Time:               0
Power Cycles:                       34
Power On Hours:                     2,423
Unsafe Shutdowns:                   11
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 8 of 8 entries)
No Errors Logged

输出journalctl | grep "fstrim.*/:"：

Jul 03 00:21:43 dev fstrim[27756]: /: 3.6 TiB (4009258434560 bytes) trimmed on /dev/nvme0n1p2
Jul 10 00:54:49 dev fstrim[1244594]: /: 3.6 TiB (4001406066688 bytes) trimmed on /dev/nvme0n1p2
Jul 17 00:32:58 dev fstrim[4040993]: /: 54.6 GiB (58677125120 bytes) trimmed on /dev/nvme0n1p2
Jul 24 00:29:14 dev fstrim[1600660]: /: 138.8 GiB (149000179712 bytes) trimmed on /dev/nvme0n1p2
Jul 31 00:35:13 dev fstrim[620323]: /: 135.8 GiB (145785393152 bytes) trimmed on /dev/nvme0n1p2
Aug 07 00:13:04 dev fstrim[35853]: /: 2.9 TiB (3226885373952 bytes) trimmed on /dev/nvme0n1p2
Aug 14 00:29:27 dev fstrim[125210]: /: 2.9 TiB (3230223196160 bytes) trimmed on /dev/nvme0n1p2
Aug 21 01:32:45 dev fstrim[332311]: /: 56.8 GiB (61013270528 bytes) trimmed on /dev/nvme0n1p2
Aug 28 00:11:05 dev fstrim[586592]: /: 90.3 GiB (96974286848 bytes) trimmed on /dev/nvme0n1p2
Sep 04 01:28:47 dev fstrim[16608]: /: 3 TiB (3257704198144 bytes) trimmed on /dev/nvme0n1p2
Sep 11 00:22:26 dev fstrim[21637]: /: 2.9 TiB (3238865485824 bytes) trimmed on /dev/nvme0n1p2
Sep 18 01:14:48 dev fstrim[126317]: /: 2.9 TiB (3240947859456 bytes) trimmed on /dev/nvme0n1p2
Sep 25 00:22:54 dev fstrim[410142]: /: 36.2 GiB (38895230976 bytes) trimmed on /dev/nvme0n1p2
Oct 02 00:31:31 dev fstrim[90432]: /: 3 TiB (3249296408576 bytes) trimmed on /dev/nvme0n1p2
Oct 09 00:48:51 dev fstrim[319128]: /: 54.2 GiB (58184278016 bytes) trimmed on /dev/nvme0n1p2
Oct 16 01:11:15 dev fstrim[29502]: /: 2.8 TiB (3103039946752 bytes) trimmed on /dev/nvme0n1p2
Oct 23 00:31:40 dev fstrim[85578]: /: 2.9 TiB (3152333541376 bytes) trimmed on /dev/nvme0n1p2
Oct 30 01:16:53 dev fstrim[212523]: /: 2.9 TiB (3140076969984 bytes) trimmed on /dev/nvme0n1p2
Nov 06 01:11:08 dev fstrim[38462]: /: 2.9 TiB (3138336178176 bytes) trimmed on /dev/nvme0n1p2
Nov 13 01:43:37 dev fstrim[98095]: /: 2.9 TiB (3140636598272 bytes) trimmed on /dev/nvme0n1p2
Nov 20 01:26:54 dev fstrim[109477]: /: 31.5 GiB (33783455744 bytes) trimmed on /dev/nvme0n1p2

虽然是一个老问题，但这与上面的数字有关： 运行 fstrim 后修剪的大量数据。我不经常重新启动笔记本电脑，几周的正常运行时间对我来说是正常的。

我使用SSD已经很多年了，这是我第一次遇到这样的问题。这也是我第一次必须fstrim手动执行。所以，我有点疑惑。是什么导致了这种行为？正常吗？有没有办法知道我的 NVMe SSD 是否需要 TRIM？

ssd
Martin Hope
Otto Julio
Asked: 2022-06-16 06:26:14 +0800 CST
  • 0

我面临System freezes on disk I/O报告的类似（可能是相同的问题） 。Fedora 36 的第一个版本也出现了这个问题。

当我启动一个对磁盘 I/O 要求更高的进程时，所有应用程序都会冻结，磁盘的光会在几秒钟甚至几分钟内保持恒定的全亮度。简单的任务，例如复制 [200 MB 目录] 或解压缩文件（使用图形界面或终端），足以触发问题。即使在恢复模式下使用 shell 也会发生这种情况。

我尝试了磁盘 I/O 的可用调度选项、mq-deadline（默认）和无。

我的配置：

  • Ubuntu 22.04（内核 5.15.0-37-generic）
  • i7 9700k
  • 16 GB 内存
  • RTX 2070
  • SSD 金士顿 A400
$ free -h
               total        used        free      shared  buff/cache   available
Mem:            15Gi       1,6Gi        11Gi        88Mi       2,2Gi        13Gi
Swap:          2,0Gi          0B       2,0Gi

# smartctl -a /dev/sda
...
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   000    Old_age   Always       -       100
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       6174
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1145
148 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
149 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
167 Write_Protect_Mode      0x0000   100   100   000    Old_age   Offline      -       0
168 SATA_Phy_Error_Count    0x0012   100   100   000    Old_age   Always       -       3
169 Bad_Block_Rate          0x0000   100   100   000    Old_age   Offline      -       0
170 Bad_Blk_Ct_Erl/Lat      0x0000   100   100   010    Old_age   Offline      -       0/0
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
173 MaxAvgErase_Ct          0x0000   100   100   000    Old_age   Offline      -       0
181 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
182 Erase_Fail_Count        0x0000   100   100   000    Old_age   Offline      -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
192 Unsafe_Shutdown_Count   0x0012   100   100   000    Old_age   Always       -       201
194 Temperature_Celsius     0x0022   037   073   000    Old_age   Always       -       37 (Min/Max 26/73)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
199 SATA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
218 CRC_Error_Count         0x0032   100   100   000    Old_age   Always       -       3
231 SSD_Life_Left           0x0000   095   095   000    Old_age   Offline      -       95
233 Flash_Writes_GiB        0x0032   100   100   000    Old_age   Always       -       7968
241 Lifetime_Writes_GiB     0x0032   100   100   000    Old_age   Always       -       4379
242 Lifetime_Reads_GiB      0x0032   100   100   000    Old_age   Always       -       2333
244 Average_Erase_Count     0x0000   100   100   000    Old_age   Offline      -       53
245 Max_Erase_Count         0x0000   100   100   000    Old_age   Offline      -       153
246 Total_Erase_Count       0x0000   100   100   000    Old_age   Offline      -       37087
...

# gdisk /dev/sda
...
Model: KINGSTON SA400S3
Sector size (logical/physical): 512/512 bytes
...
Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         2000895   976.0 MiB   EF00  
   2         2000896         6000639   1.9 GiB     8300  
   3         6000640       937701375   444.3 GiB   8300
...

编辑：

$ df -h
Filesystem              Size  Used Avail Use% Mounted on
tmpfs                   1,6G  3,6M  1,6G   1% /run
/dev/mapper/sda3_crypt  437G  297G  118G  72% /
tmpfs                   7,8G  127M  7,7G   2% /dev/shm
tmpfs                   5,0M  4,0K  5,0M   1% /run/lock
/dev/sda2               1,9G  244M  1,5G  14% /boot
/dev/sda1               975M   33M  942M   4% /boot/efi
tmpfs                   1,6G  2,4M  1,6G   1% /run/user/1000
ssd
Martin Hope
Marco
Asked: 2022-05-27 23:33:34 +0800 CST
  • 3

我知道有一些方法可以使用 Ubuntu 工具安全擦除整个 SSD，但我的用例只是擦除 SSD 的一个分区，因为我想卖掉我的旧笔记本并且需要确保 SSD 的恢复分区不是删除，以便买家有可能重新安装笔记本电脑（出厂设置和操作系统）。

这可以通过 Ubuntu 工具实现吗？如果不是，那么 Gparted 可能是仅擦除分区的第二好的选择吗？（笔记本上没有存储超敏感数据）

ssd
Martin Hope
MrConorAE
Asked: 2022-02-20 19:20:27 +0800 CST
  • 1

我的联想 Thinkpad X1 Yoga (20JD) 与三星 970 EVO Plus 一直随机冻结，最终显示黑屏并显示 journalctl 和其他错误。我必须按住电源按钮才能将其关闭。如果有帮助，我正在双启动 Windows 10 和 Ubuntu 21.10。

这是它显示的一些错误（没有特别的顺序，它们都滚动得太快了，我看不太清楚）

systemd-journald[297]: Failed to write entry (22 items, 757 bytes), ignoring: Read-only file system
EXT4-fs error: (device nvme0n1p6): __ext4_find_entry:1611: inode #1835133: comm gmain: reading directory lblock 0

dmesg 中还有一个错误，在一切停止工作之前就出现了，我不记得确切的文本，但它类似于resetting nvme controller.

我已经看过关于此的其他帖子。我试过了：

  • 禁用 fstrim - 没有变化
  • 使用较旧的内核版本 - 没有变化
  • 运行 fsck - 没有错误
  • 添加nvme_core.default_ps_max_latency_us=5500到我的启动参数 - 没有变化
  • 更新我的 SSD 固件 - 没有可用的新版本
  • 更新我的 BIOS - 没有可用的新版本

冻结似乎不是我采取任何行动的直接结果 - 有时会在启动后 30 秒内发生，有时根本不会发生。通常最早的标志以图标开始，我的光标变为空白方块，然后是命令（例如pwd）返回bash: pwd: I/O error。最终，我的背景会消失，然后 GNOME/Wayland/其他重要的东西会崩溃，它会进入文本模式并开始显示上述错误。做 I/O 密集型的事情似乎不会触发它。

任何帮助将不胜感激，因为这是我做功课的主要机器。

提前致谢！

ssd
Martin Hope
Leon
Asked: 2022-01-03 20:42:30 +0800 CST
  • 0

我将 2 个 NVMe SSD（Samsung 980 Pro）添加到我的 PC 作为 postgresql 的表空间，而操作系统像以前一样从另一个 SATA SSD（Samsung 860 EVO）启动。

这 2 个 nvme m.2 SSD 具有读取 6GB/s 和写入 600MB/s 的基本性能，这是我在 Gnome-Disks 中获得的。

我通过mdadm将这两个nvme做了一个软RAID，然后再次测试。

写入速度达到预期的1.3GB/s，但读取速度仍然是6GB/s。

我想知道为什么阅读性能没有改变？

谢谢！

CPU：AMD-5900X

主板：华硕Pro WS X570-ACE

芯片组：AMD-X570

操作系统：Kubuntu-20.04.2

ssd
Martin Hope
Axel Lieber
Asked: 2021-10-14 20:40:45 +0800 CST
  • 0

在我的旧 Macbook Air（目前包括 Ubuntu）上尝试不同操作系统的过程中，我设法在我的 SSD 上累积了总共 13 个分区。我怎样才能清理这个烂摊子，基本上让SSD回到原始状态？需要明确的是 - 我想彻底擦除它，摆脱它上面的所有东西，包括所有这些分区。丢失上面的任何数据都没有问题。不过，我确实想继续使用这台机器，并在完成此清理工作后安装操作系统。所以我不想破坏这件事。

ssd
Martin Hope
Costa Michailidis
Asked: 2021-07-30 03:53:37 +0800 CST
  • 0

我正在做某事，我的文件突然变成了只读的。我无法打开浏览器。我重新启动，然后卡在这个屏幕上（诊断开启）：

Please unlock disk sda3_crypt:

[ 15.138216] NET: Registered protocol family 38 WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Reading all physical volumes. This may take a while... Found volume group "ubuntu-vg" using metadata type 1vm2 WARNING: Failed to connect to lvmetad. Falling back to device scanning. 2 logical volume (s) in volume group "ubuntu-vg" now active cryptsetup (sda3_crypt): set up successfully

done. Begin: Running /scripts/local-premount done. Begin: Will now check root file system fsck from util-linux 2.31.1

[/sbin/fsck.ext4 (1) /dev/mapper/ubuntu--vg-root] fsck.ext4 -a -CO /dev/mapper/ubuntu--vg-root /dev/mapper/ubuntu--vg-root contains a file system with errors, check forced. Inodes that were part of a corrupted orphan linked list found.

/dev/mapper/ubuntu--vg-root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck exited with status code 4

done.

Failure: File system check of the root filesystem failed The root filesystem on /dev/mapper/ubuntu--vg-root requires a manual fsck

BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands.

(initramfs) [ 17.891055] thunderbolt 0000:06:00.0: stopping RX ring 0

[

[

17.891847] thunderbolt 0000:06:00.0: disabling interrupt at register 0x38200

17.892710] thunderbolt 0000:06:00.0: stopping TX ring 0 17.893492] thunderbolt 0000:06:00.0: disabling interrupt at register 0x38200

[ 17.894282] thunderbolt 0000:06:00.0: control channel stopped
ssd