关于拷贝大量时候，文件硬盘丢失的问题

it2911 · 2025-4-8 10:12:00

关于拷贝大量时候，文件硬盘丢失的问题

硬件和软件环境

Host使用Proxmox 8.1的直通模式
VM创建飞牛最新版本
通过mini PCI-E 转 PCI x16 转 ASM1160 和 LSI 9260-8i
硬盘为希捷 5 TB的2.5英寸盘两块以 raid1方式搭建

现象

当拷贝大量文件将流量打满后，出现硬盘丢失的情况，这种情况下，需要重启飞牛系统才能解决。但是在黑群晖的环境中，没有出现过类似问题。

uuuuuu · 2025-4-8 15:47:14

查看硬盘问题：ssh root后执行这个看一下 dmesg | grep ata

it2911 · 2025-4-10 13:21:04

[quote][size=2][url=forum.php?mod=redirect&goto=findpost&pid=101261&ptid=21458][color=#999999]uuuuuu 发表于 2025-4-8 15:47[/color][/url][/size] 查看硬盘问题：ssh root后执行这个看一下 dmesg | grep ata[/quote]

不好意思，回复晚了

it2911@JZ-NAS:/var/log$ sudo dmesg | grep ata
[sudo] password for it2911:
[    0.061380] Memory: 3168576K/12582356K available (14336K kernel code, 2256K rwdata, 5604K rodata, 3768K init, 2120K bss, 362924K reserved, 0K cma-reserved)
[    0.115559] MMIO Stale Data: Unknown: No mitigations
[    1.334533] Write protecting the kernel read-only data: 20480k
[    1.334896] Freeing unused kernel image (rodata/data gap) memory: 540K
[    1.845968] libata version 3.00 loaded.
[    1.847289] ata_piix 0000:00:01.1: version 2.13
[    1.868190] scsi host1: ata_piix
[    1.868808] scsi host2: ata_piix
[    1.868984] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 b** 0xf180 irq 14
[    1.868988] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 b** 0xf188 irq 15
[    9.969171] scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   10.218776] scsi 0:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   11.664146] EXT4-fs (sda2): mounted filesystem 15713f38-d720-4208-b8d3-dbd4f77464f6 ro with ordered data mode. Quota mode: none.
[   14.263255] [drm] Found EDID data blob.
[   15.057451] openvswitch: Open vSwitch switching datapath

uuuuuu · 2025-4-10 14:18:31

看日志你这个协商速度只有 MWDMA2表示Multi-Word DMA模式2，最大理论传输速率为16.7 MB/s

，另外好像还是只读，你看看你直通有问题吗

uuuuuu · 2025-4-10 14:19:22

你是直通了硬盘还是直通了转接卡呢

it2911 · 2025-4-11 00:28:31

我是直通了转接卡，proxmox的话，可以直通pci，但是应该没法直通硬盘吧。除非在host上挂载硬盘，然后分配给vm。

我今天提供的数据是基于LSI 9260-8i，但是这个卡有个问题，就是每次重启飞牛需要手动skip她的bios错误，所以我打算周末换回ASM1160，再测试。

今天测试了一下飞牛的百度云下载，感觉应该是因为网线问题，所以下载速率只有10M/s，我调整一下，再收集一下log。当前飞牛os也已经更新到了最新的版本了

it2911 · 2025-4-15 23:16:59

这个是我替换成ASM1166的dmsg输出结果

[    0.061535] Memory: 3168576K/12582356K available (14336K kernel code, 2256K rwdata, 5604K rodata, 3768K init, 2120K bss, 362924K reserved, 0K cma-reserved)
[    0.113572] MMIO Stale Data: Unknown: No mitigations
[    1.343443] Write protecting the kernel read-only data: 20480k
[    1.343777] Freeing unused kernel image (rodata/data gap) memory: 540K
[    1.769255] libata version 3.00 loaded.
[    1.772232] ata_piix 0000:00:01.1: version 2.13
[    1.789803] scsi host0: ata_piix
[    1.790267] scsi host1: ata_piix
[    1.790333] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 b** 0xf080 irq 14
[    1.790336] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 b** 0xf088 irq 15
[    1.906318] ata3: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2100 irq 24
[    1.906323] ata4: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2180 irq 24
[    1.906327] ata5: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2200 irq 24
[    1.906330] ata6: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2280 irq 24
[    1.906334] ata7: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2300 irq 24
[    1.906337] ata8: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2380 irq 24
[    1.906340] ata9: DUMMY
[    1.906341] ata10: DUMMY
[    1.906344] ata11: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2500 irq 24
[    1.906347] ata12: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2580 irq 24
[    1.906351] ata13: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2600 irq 24
[    1.906354] ata14: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2680 irq 24
[    1.906358] ata15: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2700 irq 24
[    1.906361] ata16: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2780 irq 24
[    1.906364] ata17: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2800 irq 24
[    1.906368] ata18: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2880 irq 24
[    1.906371] ata19: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2900 irq 24
[    1.906375] ata20: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2980 irq 24
[    1.906378] ata21: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2a00 irq 24
[    1.906381] ata22: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2a80 irq 24
[    1.906385] ata23: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2b00 irq 24
[    1.906388] ata24: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2b80 irq 24
[    1.906391] ata25: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2c00 irq 24
[    1.906395] ata26: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2c80 irq 24
[    1.906398] ata27: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2d00 irq 24
[    1.906401] ata28: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2d80 irq 24
[    1.906405] ata29: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2e00 irq 24
[    1.906408] ata30: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2e80 irq 24
[    1.906411] ata31: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2f00 irq 24
[    1.906415] ata32: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead2f80 irq 24
[    1.906418] ata33: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead3000 irq 24
[    1.906421] ata34: SATA max UDMA/133 abar m8192@0xfead2000 port 0xfead3080 irq 24
[    2.217288] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.245577] ata3.00: supports DRM functions and may not be fully accessible
[    2.245586] ata3.00: ATA-10: ST5000LM000-2U8170, 0001, max UDMA/133
[    2.254868] ata3.00: 9767541168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    2.258064] ata3.00: Features: Trust
[    2.298732] ata3.00: supports DRM functions and may not be fully accessible
[    2.311113] ata3.00: configured for UDMA/133
[    2.625188] ata4: SATA link down (SStatus 0 SControl 300)
[    2.936883] ata5: SATA link down (SStatus 0 SControl 300)
[    3.249149] ata6: SATA link down (SStatus 0 SControl 300)
[    3.561011] ata7: SATA link down (SStatus 0 SControl 300)
[    3.873064] ata8: SATA link down (SStatus 0 SControl 300)
[    4.185232] ata11: SATA link down (SStatus 0 SControl 300)
[    4.497390] ata12: SATA link down (SStatus 0 SControl 300)
[    4.809120] ata13: SATA link down (SStatus 0 SControl 300)
[    5.125894] ata14: SATA link down (SStatus 0 SControl 300)
[    5.437164] ata15: SATA link down (SStatus 0 SControl 300)
[    5.749118] ata16: SATA link down (SStatus 0 SControl 300)
[    6.061331] ata17: SATA link down (SStatus 0 SControl 300)
[    6.373171] ata18: SATA link down (SStatus 0 SControl 300)
[    6.685076] ata19: SATA link down (SStatus 0 SControl 300)
[    6.996941] ata20: SATA link down (SStatus 0 SControl 300)
[    7.309235] ata21: SATA link down (SStatus 0 SControl 300)
[    7.621342] ata22: SATA link down (SStatus 0 SControl 300)
[    7.933138] ata23: SATA link down (SStatus 0 SControl 300)
[    8.245043] ata24: SATA link down (SStatus 0 SControl 300)
[    8.557067] ata25: SATA link down (SStatus 0 SControl 300)
[    8.868949] ata26: SATA link down (SStatus 0 SControl 300)
[    9.180995] ata27: SATA link down (SStatus 0 SControl 300)
[    9.492851] ata28: SATA link down (SStatus 0 SControl 300)
[    9.805092] ata29: SATA link down (SStatus 0 SControl 300)
[   10.117213] ata30: SATA link down (SStatus 0 SControl 300)
[   10.429194] ata31: SATA link down (SStatus 0 SControl 300)
[   10.741307] ata32: SATA link down (SStatus 0 SControl 300)
[   11.053000] ata33: SATA link down (SStatus 0 SControl 300)
[   11.364976] ata34: SATA link down (SStatus 0 SControl 300)
[   13.077381] EXT4-fs (sda2): mounted filesystem 15713f38-d720-4208-b8d3-dbd4f77464f6 ro with ordered data mode. Quota mode: none.
[   15.900840] [drm] Found EDID data blob.
[   16.500018] openvswitch: Open vSwitch switching datapath
[109682.344313] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[109682.376844] ata5.00: supports DRM functions and may not be fully accessible
[109682.376854] ata5.00: ATA-10: ST5000LM000-2U8170, 0001, max UDMA/133
[109682.412662] ata5.00: 9767541168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[109682.697465] ata5.00: Features: Trust
[109682.737720] ata5.00: supports DRM functions and may not be fully accessible
[109682.749945] ata5.00: configured for UDMA/133

it2911 · 2025-4-15 23:23:48

复现了同一问题。当我大量传输文件之后，硬盘丢失，写入错误。

2025-04-15T23:21:06.618855+08:00 JZ-NAS trim[1362]: #033[0;31mpopen_read2: WEXITSTATUS=96, smartctl ]]#033[0m
2025-04-15T23:21:15.006124+08:00 JZ-NAS nmbd[1156]: [2025/04/15 23:21:15.001398,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
2025-04-15T23:21:15.006362+08:00 JZ-NAS nmbd[1156]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.31.46 for name WORKGROUP<1d>.
2025-04-15T23:21:15.006475+08:00 JZ-NAS nmbd[1156]:   This response was from IP 192.168.31.36, reporting an IP address of 192.168.31.36.
2025-04-15T23:21:41.621519+08:00 JZ-NAS trim[1362]: #033[0;31mpopen_read2: WEXITSTATUS=4, smartctl ]]#033[0m
2025-04-15T23:21:41.621811+08:00 JZ-NAS trim[1362]: #033[0;31mpopen_read2: WEXITSTATUS=4, smartctl ]]#033[0m
2025-04-15T23:21:43.762607+08:00 JZ-NAS kernel: [110166.600716] ata5.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x6 frozen
2025-04-15T23:21:43.762643+08:00 JZ-NAS kernel: [110166.600792] ata5.00: cmd 61/00:08:00:30:47/0a:00:04:00:00/40 tag 1 ncq dma 1310720 ou
2025-04-15T23:21:43.762648+08:00 JZ-NAS kernel: [110166.600792]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-04-15T23:21:43.762649+08:00 JZ-NAS kernel: [110166.600831] ata5.00: status: { DRDY }
2025-04-15T23:21:43.762651+08:00 JZ-NAS kernel: [110166.600845] ata5: hard resetting link
2025-04-15T23:21:44.078643+08:00 JZ-NAS kernel: [110166.917759] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-04-15T23:21:48.242476+08:00 JZ-NAS kernel: [110171.081439] ata3.00: cmd 60/00:90:00:10:04/01:00:00:00:00/40 tag 18 ncq dma 131072 in
2025-04-15T23:21:48.242509+08:00 JZ-NAS kernel: [110171.081439]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-04-15T23:21:48.242513+08:00 JZ-NAS kernel: [110171.082488] ata3.00: status: { DRDY }
2025-04-15T23:21:48.242515+08:00 JZ-NAS kernel: [110171.083013] ata3.00: failed command: WRITE FPDMA QUEUED
2025-04-15T23:21:48.242516+08:00 JZ-NAS kernel: [110171.083542] ata3.00: cmd 61/00:e8:00:e0:46/0a:00:04:00:00/40 tag 29 ncq dma 1310720 ou
2025-04-15T23:21:48.242518+08:00 JZ-NAS kernel: [110171.083542]          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-04-15T23:21:48.242519+08:00 JZ-NAS kernel: [110171.084667] ata3.00: status: { DRDY }
2025-04-15T23:21:49.102537+08:00 JZ-NAS kernel: [110171.940782] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-04-15T23:21:49.102569+08:00 JZ-NAS kernel: [110171.941399] ata5: hard resetting link
2025-04-15T23:21:49.526635+08:00 JZ-NAS kernel: [110172.364729] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-04-15T23:21:54.734499+08:00 JZ-NAS kernel: [110177.572738] ata3.00: qc timeout after 5000 msecs (cmd 0xec)
2025-04-15T23:21:54.734530+08:00 JZ-NAS kernel: [110177.572754] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-04-15T23:21:54.734533+08:00 JZ-NAS kernel: [110177.572757] ata3.00: revalidation failed (errno=-5)
2025-04-15T23:21:54.734535+08:00 JZ-NAS kernel: [110177.573442] ata3: hard resetting link
2025-04-15T23:21:55.406506+08:00 JZ-NAS kernel: [110178.244626] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-04-15T23:21:59.598580+08:00 JZ-NAS kernel: [110182.436610] ata5.00: qc timeout after 10000 msecs (cmd 0xec)
2025-04-15T23:21:59.598614+08:00 JZ-NAS kernel: [110182.436627] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-04-15T23:21:59.598618+08:00 JZ-NAS kernel: [110182.436630] ata5.00: revalidation failed (errno=-5)
2025-04-15T23:21:59.598620+08:00 JZ-NAS kernel: [110182.437246] ata5: limiting SATA link speed to 3.0 Gbps
2025-04-15T23:21:59.598622+08:00 JZ-NAS kernel: [110182.437252] ata5: hard resetting link
2025-04-15T23:22:00.274484+08:00 JZ-NAS kernel: [110183.112637] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
2025-04-15T23:22:05.486553+08:00 JZ-NAS kernel: [110188.324679] ata3.00: qc timeout after 10000 msecs (cmd 0xec)
2025-04-15T23:22:05.486586+08:00 JZ-NAS kernel: [110188.324695] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-04-15T23:22:05.486590+08:00 JZ-NAS kernel: [110188.324698] ata3.00: revalidation failed (errno=-5)
2025-04-15T23:22:05.486592+08:00 JZ-NAS kernel: [110188.325366] ata3: limiting SATA link speed to 3.0 Gbps
2025-04-15T23:22:05.486593+08:00 JZ-NAS kernel: [110188.325373] ata3: hard resetting link

it2911 · 2025-5-2 12:44:20

我换成了ASM1064，速度下降到了30MB/s，系统的稳定性提告了，但是当CPU占用率过高时，依旧会产生IO错误。所以我怀疑是飞牛在CPU过高的情况下，对IO的处理产生了问题。

2025-05-02T12:33:49.464147+08:00 JZ-NAS kernel: [  644.202484] ata6.00: exception Emask 0x0 SAct 0x460 SErr 0x0 action 0x6 frozen
2025-05-02T12:33:49.464180+08:00 JZ-NAS kernel: [  644.202530] ata6.00: failed command: WRITE FPDMA QUEUED
2025-05-02T12:33:49.464182+08:00 JZ-NAS kernel: [  644.202544] ata6.00: cmd 61/00:28:90:2a:a6/0a:00:01:00:00/40 tag 5 ncq dma 1310720 ou
2025-05-02T12:33:49.464184+08:00 JZ-NAS kernel: [  644.202544]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-05-02T12:33:49.464185+08:00 JZ-NAS kernel: [  644.202583] ata6.00: status: { DRDY }
2025-05-02T12:33:49.464187+08:00 JZ-NAS kernel: [  644.202594] ata6.00: failed command: WRITE FPDMA QUEUED
2025-05-02T12:33:49.464188+08:00 JZ-NAS kernel: [  644.202607] ata6.00: cmd 61/08:30:10:08:00/00:00:00:00:00/40 tag 6 ncq dma 4096 out
2025-05-02T12:33:49.464189+08:00 JZ-NAS kernel: [  644.202607]          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-05-02T12:33:49.464190+08:00 JZ-NAS kernel: [  644.202645] ata6.00: status: { DRDY }
2025-05-02T12:33:49.464191+08:00 JZ-NAS kernel: [  644.202655] ata6.00: failed command: READ FPDMA QUEUED
2025-05-02T12:33:49.464192+08:00 JZ-NAS kernel: [  644.202668] ata6.00: cmd 60/00:50:00:10:04/01:00:00:00:00/40 tag 10 ncq dma 131072 in
2025-05-02T12:33:49.464194+08:00 JZ-NAS kernel: [  644.202668]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-05-02T12:33:49.464195+08:00 JZ-NAS kernel: [  644.202705] ata6.00: status: { DRDY }
2025-05-02T12:33:49.464196+08:00 JZ-NAS kernel: [  644.202718] ata6: hard resetting link
2025-05-02T12:33:50.680118+08:00 JZ-NAS kernel: [  645.418441] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-05-02T12:33:55.832047+08:00 JZ-NAS kernel: [  650.570366] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-05-02T12:33:55.832080+08:00 JZ-NAS kernel: [  650.570369] ata6.00: revalidation failed (errno=-5)
2025-05-02T12:33:55.832083+08:00 JZ-NAS kernel: [  650.570403] ata6: hard resetting link
2025-05-02T12:33:56.268117+08:00 JZ-NAS kernel: [  651.006393] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-05-02T12:34:06.327978+08:00 JZ-NAS kernel: [  661.066037] ata6.00: qc timeout after 10000 msecs (cmd 0xec)
2025-05-02T12:34:06.328012+08:00 JZ-NAS kernel: [  661.066053] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-05-02T12:34:06.328015+08:00 JZ-NAS kernel: [  661.066056] ata6.00: revalidation failed (errno=-5)
2025-05-02T12:34:06.328016+08:00 JZ-NAS kernel: [  661.066083] ata6: limiting SATA link speed to 3.0 Gbps
2025-05-02T12:34:06.328017+08:00 JZ-NAS kernel: [  661.066089] ata6: hard resetting link
2025-05-02T12:34:07.600128+08:00 JZ-NAS kernel: [  662.338233] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
2025-05-02T12:34:36.149818+08:00 JZ-NAS dockermgr[2249]: [12:34:36.148] [info] [2267] [SAC]Clear all docker ports
2025-05-02T12:34:36.149980+08:00 JZ-NAS dockermgr[2249]: [12:34:36.149] [info] [2267] [SAC]Unregister for all dockers
2025-05-02T12:34:36.150458+08:00 JZ-NAS dockermgr[2249]: [12:34:36.150] [info] [2267] [SAC]Unregister for all succeed
2025-05-02T12:34:36.152008+08:00 JZ-NAS dockermgr[2249]: [12:34:36.151] [info] [2267] [SAC]Try to update ports for baiduapp(bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2)
2025-05-02T12:34:36.152087+08:00 JZ-NAS dockermgr[2249]: [12:34:36.151] [info] [2267] [SAC]Register 1 ports for bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2
2025-05-02T12:34:36.153124+08:00 JZ-NAS dockermgr[2249]: [12:34:36.152] [info] [2267] [SAC]Register 1 ports finished
2025-05-02T12:34:38.584095+08:00 JZ-NAS kernel: [  693.321687] ata6.00: qc timeout after 30000 msecs (cmd 0xec)
2025-05-02T12:34:38.584134+08:00 JZ-NAS kernel: [  693.321706] ata6.00: revalidation failed (errno=-5)
2025-05-02T12:34:38.584138+08:00 JZ-NAS kernel: [  693.321753] ata6.00: disable device
2025-05-02T12:34:38.919994+08:00 JZ-NAS kernel: [  693.660858] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.935244+08:00 JZ-NAS kernel: [  693.672819] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.935285+08:00 JZ-NAS kernel: [  693.673389] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.935289+08:00 JZ-NAS kernel: [  693.673916] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.935291+08:00 JZ-NAS kernel: [  693.674503] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.935293+08:00 JZ-NAS kernel: [  693.674989] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.935294+08:00 JZ-NAS kernel: [  693.675507] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.935296+08:00 JZ-NAS kernel: [  693.675556] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:34:38.991987+08:00 JZ-NAS kernel: [  693.726538] md: super_written gets error=-5
2025-05-02T12:34:39.040423+08:00 JZ-NAS kernel: [  693.778257] md: super_written gets error=-5
2025-05-02T12:34:39.040455+08:00 JZ-NAS kernel: [  693.781438] md: super_written gets error=-5
2025-05-02T12:34:39.040470+08:00 JZ-NAS kernel: [  693.782045] md: super_written gets error=-5
2025-05-02T12:34:39.044985+08:00 JZ-NAS kernel: [  693.783683] md: super_written gets error=-5
2025-05-02T12:34:39.045019+08:00 JZ-NAS kernel: [  693.784995] md: super_written gets error=-5
2025-05-02T12:34:39.048232+08:00 JZ-NAS kernel: [  693.789048] md: super_written gets error=-5
2025-05-02T12:34:39.060602+08:00 JZ-NAS kernel: [  693.799290] md: super_written gets error=-5
2025-05-02T12:34:39.060655+08:00 JZ-NAS kernel: [  693.801420] md: super_written gets error=-5
2025-05-02T12:34:39.065292+08:00 JZ-NAS kernel: [  693.803010] md: super_written gets error=-5
2025-05-02T12:34:39.065320+08:00 JZ-NAS kernel: [  693.804726] md: super_written gets error=-5
2025-05-02T12:34:39.104850+08:00 JZ-NAS kernel: [  693.843770] md: super_written gets error=-5
2025-05-02T12:34:39.104884+08:00 JZ-NAS kernel: [  693.845534] md: super_written gets error=-5
2025-05-02T12:34:39.104887+08:00 JZ-NAS kernel: [  693.846023] md: super_written gets error=-5
2025-05-02T12:34:39.108751+08:00 JZ-NAS kernel: [  693.849808] md: super_written gets error=-5
2025-05-02T12:34:39.219926+08:00 JZ-NAS kernel: [  693.958678] md: super_written gets error=-5
2025-05-02T12:34:39.327932+08:00 JZ-NAS kernel: [  694.067950] md: super_written gets error=-5
2025-05-02T12:34:39.388885+08:00 JZ-NAS kernel: [  694.129687] md: super_written gets error=-5
2025-05-02T12:34:39.388917+08:00 JZ-NAS kernel: [  694.129850] md: super_written gets error=-5
2025-05-02T12:34:39.388921+08:00 JZ-NAS kernel: [  694.129999] md: super_written gets error=-5
2025-05-02T12:34:39.453264+08:00 JZ-NAS kernel: [  694.186422] md: super_written gets error=-5
2025-05-02T12:34:39.453295+08:00 JZ-NAS kernel: [  694.187603] md: super_written gets error=-5
2025-05-02T12:34:39.453300+08:00 JZ-NAS kernel: [  694.187784] md: super_written gets error=-5
2025-05-02T12:34:39.453301+08:00 JZ-NAS kernel: [  694.188546] md: super_written gets error=-5
2025-05-02T12:34:39.453302+08:00 JZ-NAS kernel: [  694.189530] md: super_written gets error=-5
2025-05-02T12:34:39.453304+08:00 JZ-NAS kernel: [  694.191077] md: super_written gets error=-5
2025-05-02T12:34:39.503942+08:00 JZ-NAS kernel: [  694.243287] md: super_written gets error=-5
2025-05-02T12:34:39.503968+08:00 JZ-NAS kernel: [  694.243543] md: super_written gets error=-5
2025-05-02T12:34:39.503971+08:00 JZ-NAS kernel: [  694.244200] md: super_written gets error=-5
2025-05-02T12:34:39.503972+08:00 JZ-NAS kernel: [  694.244335] md: super_written gets error=-5
2025-05-02T12:34:39.503973+08:00 JZ-NAS kernel: [  694.244463] md: super_written gets error=-5
2025-05-02T12:34:39.617059+08:00 JZ-NAS kernel: [  694.354367] md: super_written gets error=-5
2025-05-02T12:34:39.617090+08:00 JZ-NAS kernel: [  694.356508] md: super_written gets error=-5
2025-05-02T12:34:39.617093+08:00 JZ-NAS kernel: [  694.357389] md: super_written gets error=-5
2025-05-02T12:34:39.617094+08:00 JZ-NAS kernel: [  694.358082] md: super_written gets error=-5
2025-05-02T12:34:39.617095+08:00 JZ-NAS kernel: [  694.358217] md: super_written gets error=-5
2025-05-02T12:34:39.617097+08:00 JZ-NAS kernel: [  694.358345] md: super_written gets error=-5
2025-05-02T12:34:39.729121+08:00 JZ-NAS kernel: [  694.463331] md: super_written gets error=-5
2025-05-02T12:34:39.729153+08:00 JZ-NAS kernel: [  694.464044] md: super_written gets error=-5
2025-05-02T12:34:39.729156+08:00 JZ-NAS kernel: [  694.464181] md: super_written gets error=-5
2025-05-02T12:34:39.729157+08:00 JZ-NAS kernel: [  694.464310] md: super_written gets error=-5
2025-05-02T12:34:39.784508+08:00 JZ-NAS kernel: [  694.520721] md: super_written gets error=-5
2025-05-02T12:34:39.784541+08:00 JZ-NAS kernel: [  694.522099] md: super_written gets error=-5
2025-05-02T12:34:39.784544+08:00 JZ-NAS kernel: [  694.522264] md: super_written gets error=-5
2025-05-02T12:34:39.784545+08:00 JZ-NAS kernel: [  694.522891] md: super_written gets error=-5
2025-05-02T12:34:39.784546+08:00 JZ-NAS kernel: [  694.523025] md: super_written gets error=-5
2025-05-02T12:34:39.784548+08:00 JZ-NAS kernel: [  694.523150] md: super_written gets error=-5
2025-05-02T12:34:39.841347+08:00 JZ-NAS kernel: [  694.574505] md: super_written gets error=-5
2025-05-02T12:34:39.841376+08:00 JZ-NAS kernel: [  694.577341] md: super_written gets error=-5
2025-05-02T12:34:39.841378+08:00 JZ-NAS kernel: [  694.577560] md: super_written gets error=-5
2025-05-02T12:34:39.841379+08:00 JZ-NAS kernel: [  694.578208] md: super_written gets error=-5
2025-05-02T12:34:39.841380+08:00 JZ-NAS kernel: [  694.578342] md: super_written gets error=-5
2025-05-02T12:34:39.841382+08:00 JZ-NAS kernel: [  694.578468] md: super_written gets error=-5
2025-05-02T12:34:39.892236+08:00 JZ-NAS kernel: [  694.630436] md: super_written gets error=-5
2025-05-02T12:34:39.892264+08:00 JZ-NAS kernel: [  694.630594] md: super_written gets error=-5
2025-05-02T12:34:39.892268+08:00 JZ-NAS kernel: [  694.631267] md: super_written gets error=-5
2025-05-02T12:34:39.892269+08:00 JZ-NAS kernel: [  694.631401] md: super_written gets error=-5
2025-05-02T12:34:39.892270+08:00 JZ-NAS kernel: [  694.631525] md: super_written gets error=-5
2025-05-02T12:34:39.940429+08:00 JZ-NAS kernel: [  694.680153] md: super_written gets error=-5
2025-05-02T12:34:39.940459+08:00 JZ-NAS kernel: [  694.681532] md: super_written gets error=-5
2025-05-02T12:34:39.944269+08:00 JZ-NAS kernel: [  694.683156] md: super_written gets error=-5
2025-05-02T12:34:39.944297+08:00 JZ-NAS kernel: [  694.683845] md: super_written gets error=-5
2025-05-02T12:34:39.944300+08:00 JZ-NAS kernel: [  694.683979] md: super_written gets error=-5
2025-05-02T12:34:39.944303+08:00 JZ-NAS kernel: [  694.684106] md: super_written gets error=-5
2025-05-02T12:34:40.112642+08:00 JZ-NAS kernel: [  694.852970] md: super_written gets error=-5
2025-05-02T12:34:40.112677+08:00 JZ-NAS kernel: [  694.853498] md: super_written gets error=-5
2025-05-02T12:34:40.173606+08:00 JZ-NAS kernel: [  694.907284] md: super_written gets error=-5
2025-05-02T12:34:40.173638+08:00 JZ-NAS kernel: [  694.909522] md: super_written gets error=-5
2025-05-02T12:34:40.173641+08:00 JZ-NAS kernel: [  694.910279] md: super_written gets error=-5
2025-05-02T12:34:40.173644+08:00 JZ-NAS kernel: [  694.910915] md: super_written gets error=-5
2025-05-02T12:34:40.173645+08:00 JZ-NAS kernel: [  694.911047] md: super_written gets error=-5
2025-05-02T12:34:40.173647+08:00 JZ-NAS kernel: [  694.911173] md: super_written gets error=-5
2025-05-02T12:34:40.226471+08:00 JZ-NAS kernel: [  694.959105] md: super_written gets error=-5
2025-05-02T12:34:40.226504+08:00 JZ-NAS kernel: [  694.960304] md: super_written gets error=-5
2025-05-02T12:34:40.226507+08:00 JZ-NAS kernel: [  694.960489] md: super_written gets error=-5
2025-05-02T12:34:40.226508+08:00 JZ-NAS kernel: [  694.961185] md: super_written gets error=-5
2025-05-02T12:34:40.226509+08:00 JZ-NAS kernel: [  694.961330] md: super_written gets error=-5
2025-05-02T12:34:40.226511+08:00 JZ-NAS kernel: [  694.962626] md: super_written gets error=-5
2025-05-02T12:34:40.259921+08:00 JZ-NAS kernel: [  695.001183] md: super_written gets error=-5
2025-05-02T12:34:40.259952+08:00 JZ-NAS kernel: [  695.001500] md: super_written gets error=-5
2025-05-02T12:34:40.264321+08:00 JZ-NAS kernel: [  695.004146] md: super_written gets error=-5
2025-05-02T12:34:40.367922+08:00 JZ-NAS kernel: [  695.106270] md: super_written gets error=-5
2025-05-02T12:34:40.367950+08:00 JZ-NAS kernel: [  695.107389] md: super_written gets error=-5
2025-05-02T12:34:40.367954+08:00 JZ-NAS kernel: [  695.107575] md: super_written gets error=-5
2025-05-02T12:34:40.367955+08:00 JZ-NAS kernel: [  695.108277] md: super_written gets error=-5
2025-05-02T12:34:40.367956+08:00 JZ-NAS kernel: [  695.108414] md: super_written gets error=-5
2025-05-02T12:34:40.367958+08:00 JZ-NAS kernel: [  695.108563] md: super_written gets error=-5
2025-05-02T12:34:40.415928+08:00 JZ-NAS kernel: [  695.156100] md: super_written gets error=-5
2025-05-02T12:34:40.415956+08:00 JZ-NAS kernel: [  695.157099] md: super_written gets error=-5
2025-05-02T12:34:40.419946+08:00 JZ-NAS kernel: [  695.159094] md: super_written gets error=-5
2025-05-02T12:34:40.419974+08:00 JZ-NAS kernel: [  695.159799] md: super_written gets error=-5
2025-05-02T12:34:40.419976+08:00 JZ-NAS kernel: [  695.159943] md: super_written gets error=-5
2025-05-02T12:34:40.419978+08:00 JZ-NAS kernel: [  695.160070] md: super_written gets error=-5
2025-05-02T12:34:40.469227+08:00 JZ-NAS kernel: [  695.208093] md: super_written gets error=-5
2025-05-02T12:34:40.469260+08:00 JZ-NAS kernel: [  695.209522] md: super_written gets error=-5
2025-05-02T12:34:40.507966+08:00 JZ-NAS kernel: [  695.247024] md: super_written gets error=-5
2025-05-02T12:34:40.508006+08:00 JZ-NAS kernel: [  695.247965] md: super_written gets error=-5
2025-05-02T12:34:40.508009+08:00 JZ-NAS kernel: [  695.248848] md: super_written gets error=-5
2025-05-02T12:34:40.594422+08:00 JZ-NAS kernel: [  695.333147] md: super_written gets error=-5
2025-05-02T12:34:40.595900+08:00 JZ-NAS kernel: [  695.336260] md: super_written gets error=-5
2025-05-02T12:34:40.595918+08:00 JZ-NAS kernel: [  695.336930] md: super_written gets error=-5
2025-05-02T12:34:40.595920+08:00 JZ-NAS kernel: [  695.337066] md: super_written gets error=-5
2025-05-02T12:34:40.595921+08:00 JZ-NAS kernel: [  695.337196] md: super_written gets error=-5
2025-05-02T12:34:40.692089+08:00 JZ-NAS kernel: [  695.429640] md: super_written gets error=-5
2025-05-02T12:34:40.692129+08:00 JZ-NAS kernel: [  695.430490] md: super_written gets error=-5
2025-05-02T12:34:40.692132+08:00 JZ-NAS kernel: [  695.431162] md: super_written gets error=-5
2025-05-02T12:34:40.692133+08:00 JZ-NAS kernel: [  695.431853] md: super_written gets error=-5
2025-05-02T12:34:40.692135+08:00 JZ-NAS kernel: [  695.432692] md: super_written gets error=-5
2025-05-02T12:34:40.692137+08:00 JZ-NAS kernel: [  695.432905] md: super_written gets error=-5
2025-05-02T12:34:40.784602+08:00 JZ-NAS kernel: [  695.525331] md: super_written gets error=-5
2025-05-02T12:34:40.880573+08:00 JZ-NAS kernel: [  695.617479] md: super_written gets error=-5
2025-05-02T12:34:40.880602+08:00 JZ-NAS kernel: [  695.620280] md: super_written gets error=-5
2025-05-02T12:34:40.880605+08:00 JZ-NAS kernel: [  695.620466] md: super_written gets error=-5
2025-05-02T12:34:40.880606+08:00 JZ-NAS kernel: [  695.621107] md: super_written gets error=-5
2025-05-02T12:34:40.880608+08:00 JZ-NAS kernel: [  695.621249] md: super_written gets error=-5
2025-05-02T12:34:40.880610+08:00 JZ-NAS kernel: [  695.621376] md: super_written gets error=-5
2025-05-02T12:34:40.968434+08:00 JZ-NAS kernel: [  695.707087] md: super_written gets error=-5
2025-05-02T12:34:40.968468+08:00 JZ-NAS kernel: [  695.708080] md: super_written gets error=-5
2025-05-02T12:34:40.968471+08:00 JZ-NAS kernel: [  695.708259] md: super_written gets error=-5
2025-05-02T12:34:40.968472+08:00 JZ-NAS kernel: [  695.709676] md: super_written gets error=-5
2025-05-02T12:34:40.968473+08:00 JZ-NAS kernel: [  695.709862] md: super_written gets error=-5
2025-05-02T12:34:40.988019+08:00 JZ-NAS kernel: [  695.728612] md: super_written gets error=-5
2025-05-02T12:34:40.991939+08:00 JZ-NAS kernel: [  695.730019] md: super_written gets error=-5
2025-05-02T12:34:40.991971+08:00 JZ-NAS kernel: [  695.730675] md: super_written gets error=-5
2025-05-02T12:34:40.991973+08:00 JZ-NAS kernel: [  695.730810] md: super_written gets error=-5
2025-05-02T12:34:40.991974+08:00 JZ-NAS kernel: [  695.730937] md: super_written gets error=-5
2025-05-02T12:34:41.160039+08:00 JZ-NAS kernel: [  695.900127] md: super_written gets error=-5
2025-05-02T12:34:41.168184+08:00 JZ-NAS kernel: [  695.905597] md: super_written gets error=-5
2025-05-02T12:34:41.168217+08:00 JZ-NAS kernel: [  695.906671] md: super_written gets error=-5
2025-05-02T12:34:41.168220+08:00 JZ-NAS kernel: [  695.907908] md: super_written gets error=-5
2025-05-02T12:34:41.223950+08:00 JZ-NAS kernel: [  695.962469] md: super_written gets error=-5
2025-05-02T12:34:41.223979+08:00 JZ-NAS kernel: [  695.963189] md: super_written gets error=-5
2025-05-02T12:34:41.223982+08:00 JZ-NAS kernel: [  695.963333] md: super_written gets error=-5
2025-05-02T12:34:41.223983+08:00 JZ-NAS kernel: [  695.963462] md: super_written gets error=-5
2025-05-02T12:34:41.484849+08:00 JZ-NAS kernel: [  696.222760] md: super_written gets error=-5
2025-05-02T12:34:41.484886+08:00 JZ-NAS kernel: [  696.223978] md: super_written gets error=-5
2025-05-02T12:34:41.484889+08:00 JZ-NAS kernel: [  696.224877] md: super_written gets error=-5
2025-05-02T12:34:41.539960+08:00 JZ-NAS kernel: [  696.280159] md: super_written gets error=-5
2025-05-02T12:34:41.539992+08:00 JZ-NAS kernel: [  696.281512] md: super_written gets error=-5
2025-05-02T12:34:41.544081+08:00 JZ-NAS kernel: [  696.284238] md: super_written gets error=-5
2025-05-02T12:34:41.544107+08:00 JZ-NAS kernel: [  696.284405] md: super_written gets error=-5
2025-05-02T12:34:41.544109+08:00 JZ-NAS kernel: [  696.284600] md: super_written gets error=-5
2025-05-02T12:34:41.603987+08:00 JZ-NAS kernel: [  696.344111] md: super_written gets error=-5
2025-05-02T12:34:41.604054+08:00 JZ-NAS kernel: [  696.345605] md: super_written gets error=-5
2025-05-02T12:34:41.804014+08:00 JZ-NAS kernel: [  696.542787] md: super_written gets error=-5
2025-05-02T12:34:41.804046+08:00 JZ-NAS kernel: [  696.544024] md: super_written gets error=-5
2025-05-02T12:34:41.869058+08:00 JZ-NAS kernel: [  696.609105] md: super_written gets error=-5
2025-05-02T12:34:41.991947+08:00 JZ-NAS kernel: [  696.730647] md: super_written gets error=-5
2025-05-02T12:34:41.991978+08:00 JZ-NAS kernel: [  696.731124] md: super_written gets error=-5
2025-05-02T12:34:42.060052+08:00 JZ-NAS kernel: [  696.799542] md: super_written gets error=-5
2025-05-02T12:34:42.120339+08:00 JZ-NAS kernel: [  696.861694] md: super_written gets error=-5
2025-05-02T12:34:42.308121+08:00 JZ-NAS kernel: [  697.046572] md: super_written gets error=-5
2025-05-02T12:34:42.363947+08:00 JZ-NAS kernel: [  697.103553] md: super_written gets error=-5
2025-05-02T12:34:42.368210+08:00 JZ-NAS kernel: [  697.106431] md: super_written gets error=-5
2025-05-02T12:34:42.368239+08:00 JZ-NAS kernel: [  697.106598] md: super_written gets error=-5
2025-05-02T12:34:42.368241+08:00 JZ-NAS kernel: [  697.108425] md: super_written gets error=-5
2025-05-02T12:34:42.368243+08:00 JZ-NAS kernel: [  697.108618] md: super_written gets error=-5
2025-05-02T12:34:42.368243+08:00 JZ-NAS kernel: [  697.108748] md: super_written gets error=-5
2025-05-02T12:34:42.424229+08:00 JZ-NAS kernel: [  697.162336] md: super_written gets error=-5
2025-05-02T12:34:42.424258+08:00 JZ-NAS kernel: [  697.165613] md: super_written gets error=-5
2025-05-02T12:34:42.424269+08:00 JZ-NAS kernel: [  697.165801] md: super_written gets error=-5
2025-05-02T12:34:42.540517+08:00 JZ-NAS kernel: [  697.278638] md: super_written gets error=-5
2025-05-02T12:34:42.540552+08:00 JZ-NAS kernel: [  697.279092] md: super_written gets error=-5
2025-05-02T12:34:42.603921+08:00 JZ-NAS kernel: [  697.341775] md: super_written gets error=-5
2025-05-02T12:34:42.603950+08:00 JZ-NAS kernel: [  697.343014] md: super_written gets error=-5
2025-05-02T12:34:42.603953+08:00 JZ-NAS kernel: [  697.344825] md: super_written gets error=-5
2025-05-02T12:34:42.660008+08:00 JZ-NAS kernel: [  697.400034] md: super_written gets error=-5
2025-05-02T12:34:42.660036+08:00 JZ-NAS kernel: [  697.401199] md: super_written gets error=-5
2025-05-02T12:34:42.660040+08:00 JZ-NAS kernel: [  697.401395] md: super_written gets error=-5
2025-05-02T12:34:42.959947+08:00 JZ-NAS kernel: [  697.697627] P2PClient[3364]: segfault at 10 ip 00007fc7e956c765 sp 00007fc7e1ffa030 error 4 in libkernel.so[7fc7e8d29000+b3a000] likely on CPU 0 (core 0, socket 0)
2025-05-02T12:34:42.959979+08:00 JZ-NAS kernel: [  697.697653] Code: 00 00 00 00 00 48 8b 41 30 49 8b 54 24 20 48 89 50 20 b8 01 00 00 00 eb ce 0f 1f 40 00 49 8b 04 24 48 85 c0 74 bf 48 8b 40 30 <48> 8b 40 10 eb b7 0f 1f 44 00 00 89 5f 1c b8 01 00 00 00 eb a8 66
2025-05-02T12:34:42.988096+08:00 JZ-NAS kernel: [  697.725534] md: super_written gets error=-5
2025-05-02T12:34:42.988130+08:00 JZ-NAS kernel: [  697.728570] md: super_written gets error=-5
2025-05-02T12:34:48.056024+08:00 JZ-NAS kernel: [  702.793643] scsi_io_completion_action: 155306 callbacks suppressed
2025-05-02T12:34:48.056059+08:00 JZ-NAS kernel: [  702.793655] sd 5:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:34:48.056062+08:00 JZ-NAS kernel: [  702.793664] sd 5:0:0:0: [sda] tag#1 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
2025-05-02T12:34:48.056063+08:00 JZ-NAS kernel: [  702.793672] blk_print_req_error: 155307 callbacks suppressed
2025-05-02T12:34:48.056088+08:00 JZ-NAS kernel: [  702.793674] I/O error, dev sda, sector 2064 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
2025-05-02T12:34:48.056091+08:00 JZ-NAS kernel: [  702.793949] md: super_written gets error=-5
2025-05-02T12:34:58.296049+08:00 JZ-NAS kernel: [  713.033405] sd 5:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:34:58.296081+08:00 JZ-NAS kernel: [  713.033418] sd 5:0:0:0: [sda] tag#19 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
2025-05-02T12:34:58.296084+08:00 JZ-NAS kernel: [  713.033424] I/O error, dev sda, sector 2064 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
2025-05-02T12:34:58.296085+08:00 JZ-NAS kernel: [  713.033699] md: super_written gets error=-5
2025-05-02T12:35:01.480104+08:00 JZ-NAS CRON[4020]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2025-05-02T12:35:09.336013+08:00 JZ-NAS kernel: [  724.073419] ata5.00: exception Emask 0x0 SAct 0x600000 SErr 0x0 action 0x6 frozen
2025-05-02T12:35:09.336050+08:00 JZ-NAS kernel: [  724.073717] ata5.00: failed command: READ FPDMA QUEUED
2025-05-02T12:35:09.336053+08:00 JZ-NAS kernel: [  724.073973] ata5.00: cmd 60/00:a8:00:00:00/01:00:00:00:00/40 tag 21 ncq dma 131072 in
2025-05-02T12:35:09.336055+08:00 JZ-NAS kernel: [  724.073973]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-05-02T12:35:09.336056+08:00 JZ-NAS kernel: [  724.074522] ata5.00: status: { DRDY }
2025-05-02T12:35:09.336058+08:00 JZ-NAS kernel: [  724.074808] ata5.00: failed command: READ FPDMA QUEUED
2025-05-02T12:35:09.336059+08:00 JZ-NAS kernel: [  724.075109] ata5.00: cmd 60/00:b0:00:08:00/01:00:00:00:00/40 tag 22 ncq dma 131072 in
2025-05-02T12:35:09.336060+08:00 JZ-NAS kernel: [  724.075109]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
2025-05-02T12:35:09.336061+08:00 JZ-NAS kernel: [  724.075744] ata5.00: status: { DRDY }
2025-05-02T12:35:09.336062+08:00 JZ-NAS kernel: [  724.076122] ata5: hard resetting link
2025-05-02T12:35:09.652082+08:00 JZ-NAS kernel: [  724.389353] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-05-02T12:35:11.096102+08:00 JZ-NAS kernel: [  725.834260] btrfs_dev_stat_inc_and_print: 349 callbacks suppressed
2025-05-02T12:35:11.096139+08:00 JZ-NAS kernel: [  725.834267] BTRFS error (device dm-1: state EA): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 360, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:35:11.108035+08:00 JZ-NAS kernel: [  725.845607] BTRFS error (device dm-1: state EA): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 363, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:35:11.116009+08:00 JZ-NAS kernel: [  725.855424] BTRFS error (device dm-1: state EA): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 365, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:35:11.119994+08:00 JZ-NAS kernel: [  725.860426] BTRFS error (device dm-1: state EA): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 366, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:35:16.223996+08:00 JZ-NAS kernel: [  730.963610] BTRFS error (device dm-1: state EA): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 373, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:36:01.768983+08:00 JZ-NAS MAINEVENT[1443]: MAINEVENT:{"cat":1,"template":"StorageBroken","volume":1}
2025-05-02T12:36:01.833654+08:00 JZ-NAS kernel: [  776.569564] sd 5:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:36:01.833684+08:00 JZ-NAS kernel: [  776.569574] sd 5:0:0:0: [sda] tag#20 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
2025-05-02T12:36:01.833689+08:00 JZ-NAS kernel: [  776.569577] I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 31 prio class 2
2025-05-02T12:36:01.836106+08:00 JZ-NAS kernel: [  776.575147] sd 5:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:36:01.836136+08:00 JZ-NAS kernel: [  776.575156] sd 5:0:0:0: [sda] tag#21 CDB: Read(16) 88 00 00 00 00 00 00 00 08 00 00 00 01 00 00 00
2025-05-02T12:36:01.836139+08:00 JZ-NAS kernel: [  776.575159] I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 12 prio class 2
2025-05-02T12:36:01.837743+08:00 JZ-NAS minidlnad[1457]: minidlna.c:199: warn: received signal 15, good-bye
2025-05-02T12:36:01.837853+08:00 JZ-NAS minidlnad[1457]: minidlna.c:1324: warn: shutdown(): Interrupted system call
2025-05-02T12:36:01.838388+08:00 JZ-NAS systemd[1]: Stopping minidlna.service - minidlnad...
2025-05-02T12:36:01.839677+08:00 JZ-NAS minidlnad[1457]: EXIT_SUCCESS
2025-05-02T12:36:01.839938+08:00 JZ-NAS minidlnad[1457]: : No such file or directory
2025-05-02T12:36:01.843977+08:00 JZ-NAS kernel: [  776.579281] sd 4:0:0:0: [sdd] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:36:01.844013+08:00 JZ-NAS kernel: [  776.579328] sd 4:0:0:0: [sdd] tag#20 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
2025-05-02T12:36:01.844019+08:00 JZ-NAS kernel: [  776.579331] I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 2
2025-05-02T12:36:01.847979+08:00 JZ-NAS kernel: [  776.585039] sd 4:0:0:0: [sdd] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:36:01.848010+08:00 JZ-NAS kernel: [  776.585048] sd 4:0:0:0: [sdd] tag#21 CDB: Read(16) 88 00 00 00 00 00 00 00 08 00 00 00 01 00 00 00
2025-05-02T12:36:01.848015+08:00 JZ-NAS kernel: [  776.585051] I/O error, dev sdd, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 2
2025-05-02T12:36:01.848016+08:00 JZ-NAS kernel: [  776.586954] sd 5:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:36:01.848018+08:00 JZ-NAS kernel: [  776.586962] sd 5:0:0:0: [sda] tag#22 CDB: Read(16) 88 00 00 00 00 00 00 04 10 00 00 00 01 00 00 00
2025-05-02T12:36:01.848020+08:00 JZ-NAS kernel: [  776.586965] I/O error, dev sda, sector 266240 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 2
2025-05-02T12:36:01.854096+08:00 JZ-NAS systemd[1]: minidlna.service: Deactivated successfully.
2025-05-02T12:36:01.854229+08:00 JZ-NAS systemd[1]: Stopped minidlna.service - minidlnad.
2025-05-02T12:36:01.873143+08:00 JZ-NAS systemd[1]: Started minidlna.service - minidlnad.
2025-05-02T12:36:01.932694+08:00 JZ-NAS minidlnad[4119]: minidlna.c:1170: warn: Starting MiniDLNA version 1.3.3.
2025-05-02T12:36:01.934607+08:00 JZ-NAS minidlnad[4119]: minidlna.c:421: warn: Creating new database at /usr/trim/var/minidlna/files.db
2025-05-02T12:36:01.953618+08:00 JZ-NAS nmbd[1378]: [2025/05/02 12:36:01.952583,  0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-05-02T12:36:01.955378+08:00 JZ-NAS nmbd[1378]:   dump_workgroups()
2025-05-02T12:36:01.955824+08:00 JZ-NAS minidlnad[4119]: minidlna.c:1218: warn: HTTP listening on port 8200
2025-05-02T12:36:01.956005+08:00 JZ-NAS minidlnad[4119]: getifaddr.c:342: info: Enabling interface 192.168.31.46/255.255.255.0
2025-05-02T12:36:01.956145+08:00 JZ-NAS nmbd[1378]:    dump workgroup on subnet      172.18.0.1: netmask=    255.255.0.0:
2025-05-02T12:36:01.956968+08:00 JZ-NAS minidlnad[4126]: playlist.c:135: warn: Parsing playlists...
2025-05-02T12:36:01.957215+08:00 JZ-NAS minidlnad[4126]: playlist.c:269: warn: Finished parsing playlists.
2025-05-02T12:36:01.957377+08:00 JZ-NAS nmbd[1378]:   #011WORKGROUP(1) current master browser = JZ-NAS
2025-05-02T12:36:01.957543+08:00 JZ-NAS nmbd[1378]:   #011#011JZ-NAS 40849a03 (JZ-NAS server (Samba TRIM))
2025-05-02T12:36:01.957683+08:00 JZ-NAS nmbd[1378]: [2025/05/02 12:36:01.953159,  0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-05-02T12:36:01.957973+08:00 JZ-NAS nmbd[1378]:   dump_workgroups()
2025-05-02T12:36:01.958116+08:00 JZ-NAS nmbd[1378]:    dump workgroup on subnet      172.19.0.1: netmask=    255.255.0.0:
2025-05-02T12:36:01.958275+08:00 JZ-NAS nmbd[1378]:   #011WORKGROUP(1) current master browser = JZ-NAS
2025-05-02T12:36:01.958416+08:00 JZ-NAS nmbd[1378]:   #011#011JZ-NAS 40849a03 (JZ-NAS server (Samba TRIM))
2025-05-02T12:36:01.958573+08:00 JZ-NAS nmbd[1378]: [2025/05/02 12:36:01.953289,  0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-05-02T12:36:01.958686+08:00 JZ-NAS nmbd[1378]:   dump_workgroups()
2025-05-02T12:36:01.958844+08:00 JZ-NAS nmbd[1378]:    dump workgroup on subnet      172.17.0.1: netmask=    255.255.0.0:
2025-05-02T12:36:01.959095+08:00 JZ-NAS nmbd[1378]:   #011WORKGROUP(1) current master browser = JZ-NAS
2025-05-02T12:36:01.959417+08:00 JZ-NAS nmbd[1378]:   #011#011JZ-NAS 40849a03 (JZ-NAS server (Samba TRIM))
2025-05-02T12:36:01.962118+08:00 JZ-NAS nmbd[1378]: [2025/05/02 12:36:01.953413,  0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-05-02T12:36:01.962212+08:00 JZ-NAS nmbd[1378]:   dump_workgroups()
2025-05-02T12:36:01.964151+08:00 JZ-NAS nmbd[1378]:    dump workgroup on subnet   192.168.31.46: netmask=  255.255.255.0:
2025-05-02T12:36:01.964260+08:00 JZ-NAS nmbd[1378]:   #011WORKGROUP(1) current master browser = JZ-NAS
2025-05-02T12:36:01.964338+08:00 JZ-NAS nmbd[1378]:   #011#011JZ-NAS 40849a03 (JZ-NAS server (Samba TRIM))
2025-05-02T12:36:01.964412+08:00 JZ-NAS nmbd[1378]:   #011#011JZ 40809a03 ()
2025-05-02T12:36:01.964489+08:00 JZ-NAS nmbd[1378]:   #011#011DESKTOP-BBGR7CD 40001003 ()
2025-05-02T12:36:01.971645+08:00 JZ-NAS minidlnad[4119]: getifaddr.c:342: info: Enabling interface 172.17.0.1/255.255.0.0
2025-05-02T12:36:02.161640+08:00 JZ-NAS minidlnad[4119]: getifaddr.c:342: info: Enabling interface 172.19.0.1/255.255.0.0
2025-05-02T12:36:02.390878+08:00 JZ-NAS minidlnad[4119]: getifaddr.c:342: info: Enabling interface 172.18.0.1/255.255.0.0
2025-05-02T12:36:02.621383+08:00 JZ-NAS minidlnad[4119]: minidlna.c:1310: info: Scanner exited
2025-05-02T12:36:02.700878+08:00 JZ-NAS trim_file_monitor[1482]: [StorageListener]Received unknow message
2025-05-02T12:36:36.153835+08:00 JZ-NAS dockermgr[2249]: [12:36:36.152] [info] [2267] [SAC]Clear all docker ports
2025-05-02T12:36:36.153998+08:00 JZ-NAS dockermgr[2249]: [12:36:36.153] [info] [2267] [SAC]Unregister for all dockers
2025-05-02T12:36:36.154518+08:00 JZ-NAS dockermgr[2249]: [12:36:36.154] [info] [2267] [SAC]Unregister for all succeed
2025-05-02T12:36:36.156354+08:00 JZ-NAS dockermgr[2249]: [12:36:36.156] [info] [2267] [SAC]Try to update ports for baiduapp(bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2)
2025-05-02T12:36:36.156862+08:00 JZ-NAS dockermgr[2249]: [12:36:36.156] [info] [2267] [SAC]Register 1 ports for bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2
2025-05-02T12:36:36.157988+08:00 JZ-NAS dockermgr[2249]: [12:36:36.157] [info] [2267] [SAC]Register 1 ports finished
2025-05-02T12:37:18.980179+08:00 JZ-NAS kernel: [  853.716788] sd 4:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:37:18.980218+08:00 JZ-NAS kernel: [  853.716799] sd 4:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 57 90 98 00 00 00 08 00 00
2025-05-02T12:37:18.980221+08:00 JZ-NAS kernel: [  853.716802] I/O error, dev sdd, sector 5738648 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:37:18.980222+08:00 JZ-NAS kernel: [  853.717444] sd 4:0:0:0: [sdd] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:37:18.980224+08:00 JZ-NAS kernel: [  853.717451] sd 4:0:0:0: [sdd] tag#22 CDB: Read(16) 88 00 00 00 00 00 00 57 90 98 00 00 00 08 00 00
2025-05-02T12:37:18.980226+08:00 JZ-NAS kernel: [  853.717453] I/O error, dev sdd, sector 5738648 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:37:18.980227+08:00 JZ-NAS kernel: [  853.717960] Buffer I/O error on dev sdd, logical block 717331, async page read
2025-05-02T12:37:18.980229+08:00 JZ-NAS kernel: [  853.718925] sd 5:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:37:18.980230+08:00 JZ-NAS kernel: [  853.718933] sd 5:0:0:0: [sda] tag#23 CDB: Read(16) 88 00 00 00 00 00 00 6b 26 e0 00 00 00 08 00 00
2025-05-02T12:37:18.980231+08:00 JZ-NAS kernel: [  853.718935] I/O error, dev sda, sector 7022304 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:37:18.980233+08:00 JZ-NAS kernel: [  853.719556] sd 5:0:0:0: [sda] tag#31 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:37:18.980234+08:00 JZ-NAS kernel: [  853.719562] sd 5:0:0:0: [sda] tag#31 CDB: Read(16) 88 00 00 00 00 00 00 6b 26 e0 00 00 00 08 00 00
2025-05-02T12:37:18.980235+08:00 JZ-NAS kernel: [  853.719563] I/O error, dev sda, sector 7022304 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:37:18.980236+08:00 JZ-NAS kernel: [  853.720105] Buffer I/O error on dev sda, logical block 877788, async page read
2025-05-02T12:37:46.024492+08:00 JZ-NAS trim[1443]: [DEBUG] start cgi 'netsvr'.
2025-05-02T12:38:18.984421+08:00 JZ-NAS kernel: [  913.721667] sd 4:0:0:0: [sdd] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:38:18.984456+08:00 JZ-NAS kernel: [  913.721678] sd 4:0:0:0: [sdd] tag#23 CDB: Read(16) 88 00 00 00 00 00 00 1d 54 e0 00 00 00 08 00 00
2025-05-02T12:38:18.984459+08:00 JZ-NAS kernel: [  913.721681] I/O error, dev sdd, sector 1922272 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:38:18.984460+08:00 JZ-NAS kernel: [  913.722414] sd 4:0:0:0: [sdd] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:38:18.984461+08:00 JZ-NAS kernel: [  913.722421] sd 4:0:0:0: [sdd] tag#1 CDB: Read(16) 88 00 00 00 00 00 00 1d 54 e0 00 00 00 08 00 00
2025-05-02T12:38:18.984462+08:00 JZ-NAS kernel: [  913.722423] I/O error, dev sdd, sector 1922272 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:38:18.984463+08:00 JZ-NAS kernel: [  913.723004] Buffer I/O error on dev sdd, logical block 240284, async page read
2025-05-02T12:38:18.984464+08:00 JZ-NAS kernel: [  913.724123] sd 5:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:38:18.984466+08:00 JZ-NAS kernel: [  913.724134] sd 5:0:0:0: [sda] tag#2 CDB: Read(16) 88 00 00 00 00 00 00 17 b6 50 00 00 00 08 00 00
2025-05-02T12:38:18.984467+08:00 JZ-NAS kernel: [  913.724136] I/O error, dev sda, sector 1554000 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:38:18.984469+08:00 JZ-NAS kernel: [  913.724854] sd 5:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:38:18.984470+08:00 JZ-NAS kernel: [  913.724862] sd 5:0:0:0: [sda] tag#3 CDB: Read(16) 88 00 00 00 00 00 00 17 b6 50 00 00 00 08 00 00
2025-05-02T12:38:18.984471+08:00 JZ-NAS kernel: [  913.724864] I/O error, dev sda, sector 1554000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:38:33.703104+08:00 JZ-NAS systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
2025-05-02T12:38:33.818333+08:00 JZ-NAS systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
2025-05-02T12:38:33.818722+08:00 JZ-NAS systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
2025-05-02T12:38:33.821941+08:00 JZ-NAS systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
2025-05-02T12:38:36.159116+08:00 JZ-NAS dockermgr[2249]: [12:38:36.158] [info] [2267] [SAC]Clear all docker ports
2025-05-02T12:38:36.159410+08:00 JZ-NAS dockermgr[2249]: [12:38:36.158] [info] [2267] [SAC]Unregister for all dockers
2025-05-02T12:38:36.159555+08:00 JZ-NAS dockermgr[2249]: [12:38:36.159] [info] [2267] [SAC]Unregister for all succeed
2025-05-02T12:38:36.162161+08:00 JZ-NAS dockermgr[2249]: [12:38:36.161] [info] [2267] [SAC]Try to update ports for baiduapp(bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2)
2025-05-02T12:38:36.162461+08:00 JZ-NAS dockermgr[2249]: [12:38:36.161] [info] [2267] [SAC]Register 1 ports for bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2
2025-05-02T12:38:36.162853+08:00 JZ-NAS dockermgr[2249]: [12:38:36.162] [info] [2267] [SAC]Register 1 ports finished
2025-05-02T12:39:18.989663+08:00 JZ-NAS kernel: [  973.726928] sd 4:0:0:0: [sdd] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:39:18.989700+08:00 JZ-NAS kernel: [  973.726939] sd 4:0:0:0: [sdd] tag#24 CDB: Read(16) 88 00 00 00 00 00 00 17 c2 38 00 00 00 08 00 00
2025-05-02T12:39:18.989703+08:00 JZ-NAS kernel: [  973.726941] I/O error, dev sdd, sector 1557048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:39:18.989705+08:00 JZ-NAS kernel: [  973.727662] sd 4:0:0:0: [sdd] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:39:18.989706+08:00 JZ-NAS kernel: [  973.727669] sd 4:0:0:0: [sdd] tag#2 CDB: Read(16) 88 00 00 00 00 00 00 17 c2 38 00 00 00 08 00 00
2025-05-02T12:39:18.989707+08:00 JZ-NAS kernel: [  973.727671] I/O error, dev sdd, sector 1557048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:39:18.989707+08:00 JZ-NAS kernel: [  973.728276] Buffer I/O error on dev sdd, logical block 194631, async page read
2025-05-02T12:39:18.989708+08:00 JZ-NAS kernel: [  973.729391] sd 5:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:39:18.989710+08:00 JZ-NAS kernel: [  973.729400] sd 5:0:0:0: [sda] tag#4 CDB: Read(16) 88 00 00 00 00 00 00 47 d6 60 00 00 00 08 00 00
2025-05-02T12:39:18.989712+08:00 JZ-NAS kernel: [  973.729402] I/O error, dev sda, sector 4707936 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:39:18.989713+08:00 JZ-NAS kernel: [  973.730056] sd 5:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:39:18.989714+08:00 JZ-NAS kernel: [  973.730064] sd 5:0:0:0: [sda] tag#5 CDB: Read(16) 88 00 00 00 00 00 00 47 d6 60 00 00 00 08 00 00
2025-05-02T12:39:18.989715+08:00 JZ-NAS kernel: [  973.730066] I/O error, dev sda, sector 4707936 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:40:18.992269+08:00 JZ-NAS kernel: [ 1033.732140] sd 4:0:0:0: [sdd] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:40:18.992305+08:00 JZ-NAS kernel: [ 1033.732152] sd 4:0:0:0: [sdd] tag#3 CDB: Read(16) 88 00 00 00 00 00 00 75 e2 c8 00 00 00 08 00 00
2025-05-02T12:40:18.992308+08:00 JZ-NAS kernel: [ 1033.732154] I/O error, dev sdd, sector 7725768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:40:36.163742+08:00 JZ-NAS dockermgr[2249]: [12:40:36.162] [info] [2267] [SAC]Clear all docker ports
2025-05-02T12:40:36.163938+08:00 JZ-NAS dockermgr[2249]: [12:40:36.163] [info] [2267] [SAC]Unregister for all dockers
2025-05-02T12:40:36.169043+08:00 JZ-NAS dockermgr[2249]: [12:40:36.168] [info] [2267] [SAC]Unregister for all succeed
2025-05-02T12:40:36.171318+08:00 JZ-NAS dockermgr[2249]: [12:40:36.170] [info] [2267] [SAC]Try to update ports for baiduapp(bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2)
2025-05-02T12:40:36.171572+08:00 JZ-NAS dockermgr[2249]: [12:40:36.170] [info] [2267] [SAC]Register 1 ports for bf8fd4c495e57843c7388ea5daaffdcdabf94bd1e848ec20970d13da6a96d7f2
2025-05-02T12:40:36.171840+08:00 JZ-NAS dockermgr[2249]: [12:40:36.171] [info] [2267] [SAC]Register 1 ports finished
2025-05-02T12:40:57.405599+08:00 JZ-NAS systemd[1]: Created slice user-1000.slice - User Slice of UID 1000.
2025-05-02T12:40:57.429301+08:00 JZ-NAS systemd[1]: Starting user-runtime-dir@1000.service - User Runtime Directory /run/user/1000...
2025-05-02T12:40:57.451362+08:00 JZ-NAS systemd[1]: Finished user-runtime-dir@1000.service - User Runtime Directory /run/user/1000.
2025-05-02T12:40:57.455540+08:00 JZ-NAS systemd[1]: Starting user@1000.service - User Manager for UID 1000...
2025-05-02T12:40:57.776489+08:00 JZ-NAS systemd[4651]: Queued start ** for default target default.target.
2025-05-02T12:40:57.778482+08:00 JZ-NAS systemd[4651]: Created slice app.slice - User Application Slice.
2025-05-02T12:40:57.778605+08:00 JZ-NAS systemd[4651]: Reached target paths.target - Paths.
2025-05-02T12:40:57.778713+08:00 JZ-NAS systemd[4651]: Reached target timers.target - Timers.
2025-05-02T12:40:57.782860+08:00 JZ-NAS systemd[4651]: Starting dbus.socket - D-Bus User Message Bus Socket...
2025-05-02T12:40:57.783212+08:00 JZ-NAS systemd[4651]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
2025-05-02T12:40:57.783599+08:00 JZ-NAS systemd[4651]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
2025-05-02T12:40:57.783773+08:00 JZ-NAS systemd[4651]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
2025-05-02T12:40:57.783976+08:00 JZ-NAS systemd[4651]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
2025-05-02T12:40:57.784108+08:00 JZ-NAS systemd[4651]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
2025-05-02T12:40:57.793788+08:00 JZ-NAS systemd[4651]: Listening on dbus.socket - D-Bus User Message Bus Socket.
2025-05-02T12:40:57.793922+08:00 JZ-NAS systemd[4651]: Reached target sockets.target - Sockets.
2025-05-02T12:40:57.794029+08:00 JZ-NAS systemd[4651]: Reached target basic.target - Basic System.
2025-05-02T12:40:57.794120+08:00 JZ-NAS systemd[4651]: Reached target default.target - Main User Target.
2025-05-02T12:40:57.794208+08:00 JZ-NAS systemd[4651]: Startup finished in 310ms.
2025-05-02T12:40:57.794927+08:00 JZ-NAS systemd[1]: Started user@1000.service - User Manager for UID 1000.
2025-05-02T12:40:57.797858+08:00 JZ-NAS systemd[1]: Started session-4.scope - Session 4 of User it2911.
2025-05-02T12:41:19.000771+08:00 JZ-NAS kernel: [ 1093.737966] sd 4:0:0:0: [sdd] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:41:19.000811+08:00 JZ-NAS kernel: [ 1093.737978] sd 4:0:0:0: [sdd] tag#26 CDB: Read(16) 88 00 00 00 00 00 00 08 18 40 00 00 00 08 00 00
2025-05-02T12:41:19.000814+08:00 JZ-NAS kernel: [ 1093.737980] I/O error, dev sdd, sector 530496 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:41:19.000815+08:00 JZ-NAS kernel: [ 1093.738759] sd 4:0:0:0: [sdd] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:41:19.000817+08:00 JZ-NAS kernel: [ 1093.738766] sd 4:0:0:0: [sdd] tag#4 CDB: Read(16) 88 00 00 00 00 00 00 08 18 40 00 00 00 08 00 00
2025-05-02T12:41:19.000821+08:00 JZ-NAS kernel: [ 1093.738768] I/O error, dev sdd, sector 530496 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:41:19.000822+08:00 JZ-NAS kernel: [ 1093.739438] Buffer I/O error on dev sdd, logical block 66312, async page read
2025-05-02T12:41:19.003963+08:00 JZ-NAS kernel: [ 1093.742881] sd 5:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:41:19.003990+08:00 JZ-NAS kernel: [ 1093.742891] sd 5:0:0:0: [sda] tag#8 CDB: Read(16) 88 00 00 00 00 00 00 41 24 80 00 00 00 08 00 00
2025-05-02T12:41:19.003994+08:00 JZ-NAS kernel: [ 1093.742893] I/O error, dev sda, sector 4269184 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
2025-05-02T12:41:19.006346+08:00 JZ-NAS kernel: [ 1093.744490] sd 5:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:41:19.006380+08:00 JZ-NAS kernel: [ 1093.744499] sd 5:0:0:0: [sda] tag#9 CDB: Read(16) 88 00 00 00 00 00 00 41 24 80 00 00 00 08 00 00
2025-05-02T12:41:19.006383+08:00 JZ-NAS kernel: [ 1093.744502] I/O error, dev sda, sector 4269184 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
2025-05-02T12:41:19.006385+08:00 JZ-NAS kernel: [ 1093.745090] Buffer I/O error on dev sda, logical block 533648, async page read

it2911 · 2025-5-2 12:56:19

我将cpu扩展到3 core，占用率得到了缓解，但是问题依旧发生了，我觉得是飞牛需要对ASM驱动进行优化。

2025-05-02T12:51:27.962216+08:00 JZ-NAS kernel: [  332.960503] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-05-02T12:51:32.998264+08:00 JZ-NAS kernel: [  337.993252] ata6.00: qc timeout after 5000 msecs (cmd 0xec)
2025-05-02T12:51:32.998302+08:00 JZ-NAS kernel: [  337.993267] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-05-02T12:51:32.998305+08:00 JZ-NAS kernel: [  337.993270] ata6.00: revalidation failed (errno=-5)
2025-05-02T12:51:32.998308+08:00 JZ-NAS kernel: [  337.993301] ata6: hard resetting link
2025-05-02T12:51:33.850241+08:00 JZ-NAS kernel: [  338.845337] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-05-02T12:51:44.006343+08:00 JZ-NAS kernel: [  349.001029] ata6.00: qc timeout after 10000 msecs (cmd 0xec)
2025-05-02T12:51:44.006377+08:00 JZ-NAS kernel: [  349.001046] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-05-02T12:51:44.006380+08:00 JZ-NAS kernel: [  349.001049] ata6.00: revalidation failed (errno=-5)
2025-05-02T12:51:44.006383+08:00 JZ-NAS kernel: [  349.001081] ata6: limiting SATA link speed to 3.0 Gbps
2025-05-02T12:51:44.006384+08:00 JZ-NAS kernel: [  349.001086] ata6: hard resetting link
2025-05-02T12:51:44.922353+08:00 JZ-NAS kernel: [  349.916921] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
2025-05-02T12:51:45.632181+08:00 JZ-NAS nmbd[1278]: [2025/05/02 12:51:45.631463,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
2025-05-02T12:51:45.632330+08:00 JZ-NAS nmbd[1278]:   *****
2025-05-02T12:51:45.632405+08:00 JZ-NAS nmbd[1278]:
2025-05-02T12:51:45.632512+08:00 JZ-NAS nmbd[1278]:   Samba name server JZ-NAS is now a local master browser for workgroup WORKGROUP on subnet 172.19.0.1
2025-05-02T12:51:45.632632+08:00 JZ-NAS nmbd[1278]:
2025-05-02T12:51:45.632708+08:00 JZ-NAS nmbd[1278]:   *****
2025-05-02T12:51:45.632784+08:00 JZ-NAS nmbd[1278]: [2025/05/02 12:51:45.631733,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
2025-05-02T12:51:45.632860+08:00 JZ-NAS nmbd[1278]:   *****
2025-05-02T12:51:45.632936+08:00 JZ-NAS nmbd[1278]:
2025-05-02T12:51:45.633009+08:00 JZ-NAS nmbd[1278]:   Samba name server JZ-NAS is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
2025-05-02T12:51:45.633083+08:00 JZ-NAS nmbd[1278]:
2025-05-02T12:51:45.633156+08:00 JZ-NAS nmbd[1278]:   *****
2025-05-02T12:51:45.633229+08:00 JZ-NAS nmbd[1278]: [2025/05/02 12:51:45.631927,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
2025-05-02T12:51:45.633313+08:00 JZ-NAS nmbd[1278]:   *****
2025-05-02T12:51:45.633383+08:00 JZ-NAS nmbd[1278]:
2025-05-02T12:51:45.633457+08:00 JZ-NAS nmbd[1278]:   Samba name server JZ-NAS is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1
2025-05-02T12:51:45.633532+08:00 JZ-NAS nmbd[1278]:
2025-05-02T12:51:45.633606+08:00 JZ-NAS nmbd[1278]:   *****
2025-05-02T12:52:01.010443+08:00 JZ-NAS trim[1444]: [DEBUG] start cgi 'netsvr'.
2025-05-02T12:52:06.010833+08:00 JZ-NAS trim[1444]: #033[0;31mpopen_read2: WEXITSTATUS=4, smartctl ]]#033[0m
2025-05-02T12:52:06.010963+08:00 JZ-NAS trim[1444]: #033[0;31mpopen_read2: WEXITSTATUS=4, smartctl ]]#033[0m
2025-05-02T12:52:14.978349+08:00 JZ-NAS kernel: [  379.972070] ata6.00: qc timeout after 30000 msecs (cmd 0xec)
2025-05-02T12:52:14.978385+08:00 JZ-NAS kernel: [  379.972087] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2025-05-02T12:52:14.978389+08:00 JZ-NAS kernel: [  379.972089] ata6.00: revalidation failed (errno=-5)
2025-05-02T12:52:14.978391+08:00 JZ-NAS kernel: [  379.972119] ata6.00: disable device
2025-05-02T12:52:15.293905+08:00 JZ-NAS kernel: [  380.288826] I/O error, dev sdb, sector 39135744 op 0x1:(WRITE) flags 0x0 phys_seg 13 prio class 2
2025-05-02T12:52:15.293941+08:00 JZ-NAS kernel: [  380.288837] sd 5:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:15.293945+08:00 JZ-NAS kernel: [  380.288852] sd 5:0:0:0: [sdb] tag#24 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
2025-05-02T12:52:15.293946+08:00 JZ-NAS kernel: [  380.288856] I/O error, dev sdb, sector 2064 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
2025-05-02T12:52:15.293948+08:00 JZ-NAS kernel: [  380.288862] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=77s
2025-05-02T12:52:15.293949+08:00 JZ-NAS kernel: [  380.288882] md: super_written gets error=-5
2025-05-02T12:52:15.293950+08:00 JZ-NAS kernel: [  380.288883] sd 5:0:0:0: [sdb] tag#4 CDB: Read(16) 88 00 00 00 00 00 00 04 10 00 00 00 01 00 00 00
2025-05-02T12:52:15.293952+08:00 JZ-NAS kernel: [  380.288885] I/O error, dev sdb, sector 266240 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 2
2025-05-02T12:52:15.293953+08:00 JZ-NAS kernel: [  380.288898] sd 5:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:15.293954+08:00 JZ-NAS kernel: [  380.288919] sd 5:0:0:0: [sdb] tag#16 CDB: Write(16) 8a 00 00 00 00 00 02 57 50 00 00 00 0a 00 00 00
2025-05-02T12:52:15.293956+08:00 JZ-NAS kernel: [  380.288921] I/O error, dev sdb, sector 39276544 op 0x1:(WRITE) flags 0x4000 phys_seg 21 prio class 2
2025-05-02T12:52:15.293957+08:00 JZ-NAS kernel: [  380.288944] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
2025-05-02T12:52:15.293959+08:00 JZ-NAS kernel: [  380.288984] sd 5:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:15.293960+08:00 JZ-NAS kernel: [  380.288987] sd 5:0:0:0: [sdb] tag#17 CDB: Write(16) 8a 00 00 00 00 00 02 57 5a 00 00 00 0a 00 00 00
2025-05-02T12:52:15.293962+08:00 JZ-NAS kernel: [  380.288989] I/O error, dev sdb, sector 39279104 op 0x1:(WRITE) flags 0x4000 phys_seg 21 prio class 2
2025-05-02T12:52:15.293963+08:00 JZ-NAS kernel: [  380.289001] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
2025-05-02T12:52:15.293964+08:00 JZ-NAS kernel: [  380.289046] sd 5:0:0:0: [sdb] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:15.293965+08:00 JZ-NAS kernel: [  380.289050] sd 5:0:0:0: [sdb] tag#27 CDB: Write(16) 8a 00 00 00 00 00 00 04 c1 c0 00 00 00 20 00 00
2025-05-02T12:52:15.293967+08:00 JZ-NAS kernel: [  380.289052] I/O error, dev sdb, sector 311744 op 0x1:(WRITE) flags 0x800 phys_seg 4 prio class 2
2025-05-02T12:52:15.293968+08:00 JZ-NAS kernel: [  380.289094] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
2025-05-02T12:52:15.293969+08:00 JZ-NAS kernel: [  380.289107] sd 5:0:0:0: [sdb] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:15.293970+08:00 JZ-NAS kernel: [  380.289111] sd 5:0:0:0: [sdb] tag#18 CDB: Write(16) 8a 00 00 00 00 00 02 57 64 00 00 00 0a 00 00 00
2025-05-02T12:52:15.293971+08:00 JZ-NAS kernel: [  380.289113] I/O error, dev sdb, sector 39281664 op 0x1:(WRITE) flags 0x4000 phys_seg 20 prio class 2
2025-05-02T12:52:15.293972+08:00 JZ-NAS kernel: [  380.289158] sd 5:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:15.293973+08:00 JZ-NAS kernel: [  380.289161] sd 5:0:0:0: [sdb] tag#19 CDB: Write(16) 8a 00 00 00 00 00 02 55 20 00 00 00 00 01 00 00
2025-05-02T12:52:15.293975+08:00 JZ-NAS kernel: [  380.289163] I/O error, dev sdb, sector 39133184 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
2025-05-02T12:52:15.302187+08:00 JZ-NAS kernel: [  380.299201] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.310283+08:00 JZ-NAS kernel: [  380.305115] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.310315+08:00 JZ-NAS kernel: [  380.307667] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.314500+08:00 JZ-NAS kernel: [  380.308818] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.314534+08:00 JZ-NAS kernel: [  380.310302] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.318391+08:00 JZ-NAS kernel: [  380.315008] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.326250+08:00 JZ-NAS kernel: [  380.319933] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.326288+08:00 JZ-NAS kernel: [  380.321259] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.334232+08:00 JZ-NAS kernel: [  380.328403] BTRFS error (device dm-1): bdev /dev/mapper/trim_53f72bd2_f1ff_4173_87ed_daabb4056194-0 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
2025-05-02T12:52:15.490479+08:00 JZ-NAS kernel: [  380.487650] md: super_written gets error=-5
2025-05-02T12:52:15.530514+08:00 JZ-NAS kernel: [  380.524579] md: super_written gets error=-5
2025-05-02T12:52:15.530555+08:00 JZ-NAS kernel: [  380.526052] md: super_written gets error=-5
2025-05-02T12:52:15.530558+08:00 JZ-NAS kernel: [  380.527522] md: super_written gets error=-5
2025-05-02T12:52:15.643709+08:00 JZ-NAS kernel: [  380.637561] md: super_written gets error=-5
2025-05-02T12:52:15.643738+08:00 JZ-NAS kernel: [  380.637980] md: super_written gets error=-5
2025-05-02T12:52:15.746220+08:00 JZ-NAS kernel: [  380.743288] md: super_written gets error=-5
2025-05-02T12:52:15.746252+08:00 JZ-NAS kernel: [  380.743988] md: super_written gets error=-5
2025-05-02T12:52:15.750403+08:00 JZ-NAS kernel: [  380.745332] md: super_written gets error=-5
2025-05-02T12:52:15.750435+08:00 JZ-NAS kernel: [  380.747472] md: super_written gets error=-5
2025-05-02T12:52:15.750441+08:00 JZ-NAS kernel: [  380.747826] md: super_written gets error=-5
2025-05-02T12:52:15.754223+08:00 JZ-NAS kernel: [  380.749244] md: super_written gets error=-5
2025-05-02T12:52:15.862437+08:00 JZ-NAS kernel: [  380.856857] md: super_written gets error=-5
2025-05-02T12:52:15.862465+08:00 JZ-NAS kernel: [  380.858281] md: super_written gets error=-5
2025-05-02T12:52:15.970229+08:00 JZ-NAS kernel: [  380.967375] md: super_written gets error=-5
2025-05-02T12:52:16.012203+08:00 JZ-NAS trim[1444]: #033[0;31mpopen_read2: WEXITSTATUS=2, smartctl ]]#033[0m
2025-05-02T12:52:16.086276+08:00 JZ-NAS kernel: [  381.082888] md: super_written gets error=-5
2025-05-02T12:52:16.086310+08:00 JZ-NAS kernel: [  381.083079] md: super_written gets error=-5
2025-05-02T12:52:16.086313+08:00 JZ-NAS kernel: [  381.083712] md: super_written gets error=-5
2025-05-02T12:52:16.086316+08:00 JZ-NAS kernel: [  381.083862] md: super_written gets error=-5
2025-05-02T12:52:16.086330+08:00 JZ-NAS kernel: [  381.084051] md: super_written gets error=-5
2025-05-02T12:52:16.142223+08:00 JZ-NAS kernel: [  381.136365] md: super_written gets error=-5
2025-05-02T12:52:16.142255+08:00 JZ-NAS kernel: [  381.137426] md: super_written gets error=-5
2025-05-02T12:52:16.142257+08:00 JZ-NAS kernel: [  381.137611] md: super_written gets error=-5
2025-05-02T12:52:16.194894+08:00 JZ-NAS kernel: [  381.190669] md: super_written gets error=-5
2025-05-02T12:52:16.194920+08:00 JZ-NAS kernel: [  381.190888] md: super_written gets error=-5
2025-05-02T12:52:16.194923+08:00 JZ-NAS kernel: [  381.191589] md: super_written gets error=-5
2025-05-02T12:52:16.194925+08:00 JZ-NAS kernel: [  381.191735] md: super_written gets error=-5
2025-05-02T12:52:16.194926+08:00 JZ-NAS kernel: [  381.191866] md: super_written gets error=-5
2025-05-02T12:52:16.335608+08:00 JZ-NAS kernel: [  381.330905] md: super_written gets error=-5
2025-05-02T12:52:16.335638+08:00 JZ-NAS kernel: [  381.331100] md: super_written gets error=-5
2025-05-02T12:52:16.335641+08:00 JZ-NAS kernel: [  381.331237] md: super_written gets error=-5
2025-05-02T12:52:16.335642+08:00 JZ-NAS kernel: [  381.331903] md: super_written gets error=-5
2025-05-02T12:52:16.335644+08:00 JZ-NAS kernel: [  381.332092] md: super_written gets error=-5
2025-05-02T12:52:16.335645+08:00 JZ-NAS kernel: [  381.332226] md: super_written gets error=-5
2025-05-02T12:52:16.530225+08:00 JZ-NAS kernel: [  381.526677] md: super_written gets error=-5
2025-05-02T12:52:16.530264+08:00 JZ-NAS kernel: [  381.526887] md: super_written gets error=-5
2025-05-02T12:52:16.530268+08:00 JZ-NAS kernel: [  381.527878] md: super_written gets error=-5
2025-05-02T12:52:16.630215+08:00 JZ-NAS kernel: [  381.625308] md: super_written gets error=-5
2025-05-02T12:52:16.630246+08:00 JZ-NAS kernel: [  381.625510] md: super_written gets error=-5
2025-05-02T12:52:16.630249+08:00 JZ-NAS kernel: [  381.625649] md: super_written gets error=-5
2025-05-02T12:52:16.630250+08:00 JZ-NAS kernel: [  381.626320] md: super_written gets error=-5
2025-05-02T12:52:16.630251+08:00 JZ-NAS kernel: [  381.626470] md: super_written gets error=-5
2025-05-02T12:52:16.630254+08:00 JZ-NAS kernel: [  381.626601] md: super_written gets error=-5
2025-05-02T12:52:16.738209+08:00 JZ-NAS kernel: [  381.732616] md: super_written gets error=-5
2025-05-02T12:52:16.738241+08:00 JZ-NAS kernel: [  381.732841] md: super_written gets error=-5
2025-05-02T12:52:16.738244+08:00 JZ-NAS kernel: [  381.732979] md: super_written gets error=-5
2025-05-02T12:52:16.810638+08:00 JZ-NAS kernel: [  381.805019] md: super_written gets error=-5
2025-05-02T12:52:16.810679+08:00 JZ-NAS kernel: [  381.807976] md: super_written gets error=-5
2025-05-02T12:52:16.814224+08:00 JZ-NAS kernel: [  381.810520] md: super_written gets error=-5
2025-05-02T12:52:16.814255+08:00 JZ-NAS kernel: [  381.810708] md: super_written gets error=-5
2025-05-02T12:52:16.814258+08:00 JZ-NAS kernel: [  381.810873] md: super_written gets error=-5
2025-05-02T12:52:16.826498+08:00 JZ-NAS kernel: [  381.823279] md: super_written gets error=-5
2025-05-02T12:52:16.826536+08:00 JZ-NAS kernel: [  381.823982] md: super_written gets error=-5
2025-05-02T12:52:16.896849+08:00 JZ-NAS kernel: [  381.891395] md: super_written gets error=-5
2025-05-02T12:52:16.899223+08:00 JZ-NAS kernel: [  381.895881] md: super_written gets error=-5
2025-05-02T12:52:16.899259+08:00 JZ-NAS kernel: [  381.896653] md: super_written gets error=-5
2025-05-02T12:52:16.966338+08:00 JZ-NAS kernel: [  381.962062] md: super_written gets error=-5
2025-05-02T12:52:16.966373+08:00 JZ-NAS kernel: [  381.962876] md: super_written gets error=-5
2025-05-02T12:52:16.966376+08:00 JZ-NAS kernel: [  381.963045] md: super_written gets error=-5
2025-05-02T12:52:16.966377+08:00 JZ-NAS kernel: [  381.963867] md: super_written gets error=-5
2025-05-02T12:52:17.162230+08:00 JZ-NAS kernel: [  382.158052] md: super_written gets error=-5
2025-05-02T12:52:17.162260+08:00 JZ-NAS kernel: [  382.158247] md: super_written gets error=-5
2025-05-02T12:52:17.162263+08:00 JZ-NAS kernel: [  382.158384] md: super_written gets error=-5
2025-05-02T12:52:17.162264+08:00 JZ-NAS kernel: [  382.159069] md: super_written gets error=-5
2025-05-02T12:52:17.162267+08:00 JZ-NAS kernel: [  382.159224] md: super_written gets error=-5
2025-05-02T12:52:17.162268+08:00 JZ-NAS kernel: [  382.159356] md: super_written gets error=-5
2025-05-02T12:52:17.322220+08:00 JZ-NAS kernel: [  382.316399] md: super_written gets error=-5
2025-05-02T12:52:17.322257+08:00 JZ-NAS kernel: [  382.316600] md: super_written gets error=-5
2025-05-02T12:52:17.322260+08:00 JZ-NAS kernel: [  382.316753] md: super_written gets error=-5
2025-05-02T12:52:17.322261+08:00 JZ-NAS kernel: [  382.317539] md: super_written gets error=-5
2025-05-02T12:52:17.322262+08:00 JZ-NAS kernel: [  382.317732] md: super_written gets error=-5
2025-05-02T12:52:17.322265+08:00 JZ-NAS kernel: [  382.317880] md: super_written gets error=-5
2025-05-02T12:52:17.398215+08:00 JZ-NAS kernel: [  382.393528] md: super_written gets error=-5
2025-05-02T12:52:17.403134+08:00 JZ-NAS kernel: [  382.397217] md: super_written gets error=-5
2025-05-02T12:52:17.403164+08:00 JZ-NAS kernel: [  382.397405] md: super_written gets error=-5
2025-05-02T12:52:17.403168+08:00 JZ-NAS kernel: [  382.398478] md: super_written gets error=-5
2025-05-02T12:52:17.403169+08:00 JZ-NAS kernel: [  382.399138] md: super_written gets error=-5
2025-05-02T12:52:17.403172+08:00 JZ-NAS kernel: [  382.399329] md: super_written gets error=-5
2025-05-02T12:52:17.498191+08:00 JZ-NAS kernel: [  382.495199] md: super_written gets error=-5
2025-05-02T12:52:17.562264+08:00 JZ-NAS kernel: [  382.557470] md: super_written gets error=-5
2025-05-02T12:52:17.562298+08:00 JZ-NAS kernel: [  382.557667] md: super_written gets error=-5
2025-05-02T12:52:17.562301+08:00 JZ-NAS kernel: [  382.557811] md: super_written gets error=-5
2025-05-02T12:52:17.562302+08:00 JZ-NAS kernel: [  382.558486] md: super_written gets error=-5
2025-05-02T12:52:17.562303+08:00 JZ-NAS kernel: [  382.558633] md: super_written gets error=-5
2025-05-02T12:52:17.562306+08:00 JZ-NAS kernel: [  382.558770] md: super_written gets error=-5
2025-05-02T12:52:17.666210+08:00 JZ-NAS kernel: [  382.662224] md: super_written gets error=-5
2025-05-02T12:52:17.666241+08:00 JZ-NAS kernel: [  382.663410] md: super_written gets error=-5
2025-05-02T12:52:17.666244+08:00 JZ-NAS kernel: [  382.663605] md: super_written gets error=-5
2025-05-02T12:52:17.726245+08:00 JZ-NAS kernel: [  382.723639] md: super_written gets error=-5
2025-05-02T12:52:17.726278+08:00 JZ-NAS kernel: [  382.723935] md: super_written gets error=-5
2025-05-02T12:52:17.802236+08:00 JZ-NAS kernel: [  382.798494] md: super_written gets error=-5
2025-05-02T12:52:17.802289+08:00 JZ-NAS kernel: [  382.799973] md: super_written gets error=-5
2025-05-02T12:52:17.882212+08:00 JZ-NAS kernel: [  382.879675] md: super_written gets error=-5
2025-05-02T12:52:17.970223+08:00 JZ-NAS kernel: [  382.965292] md: super_written gets error=-5
2025-05-02T12:52:17.970252+08:00 JZ-NAS kernel: [  382.966479] md: super_written gets error=-5
2025-05-02T12:52:18.079553+08:00 JZ-NAS kernel: [  383.074375] md: super_written gets error=-5
2025-05-02T12:52:18.079587+08:00 JZ-NAS kernel: [  383.074580] md: super_written gets error=-5
2025-05-02T12:52:18.079592+08:00 JZ-NAS kernel: [  383.074735] md: super_written gets error=-5
2025-05-02T12:52:18.079596+08:00 JZ-NAS kernel: [  383.075550] md: super_written gets error=-5
2025-05-02T12:52:18.079597+08:00 JZ-NAS kernel: [  383.075712] md: super_written gets error=-5
2025-05-02T12:52:18.079598+08:00 JZ-NAS kernel: [  383.075845] md: super_written gets error=-5
2025-05-02T12:52:18.182239+08:00 JZ-NAS kernel: [  383.177350] md: super_written gets error=-5
2025-05-02T12:52:18.182275+08:00 JZ-NAS kernel: [  383.177620] md: super_written gets error=-5
2025-05-02T12:52:18.186232+08:00 JZ-NAS kernel: [  383.180549] md: super_written gets error=-5
2025-05-02T12:52:18.186272+08:00 JZ-NAS kernel: [  383.181336] md: super_written gets error=-5
2025-05-02T12:52:18.186275+08:00 JZ-NAS kernel: [  383.181508] md: super_written gets error=-5
2025-05-02T12:52:18.186279+08:00 JZ-NAS kernel: [  383.181643] md: super_written gets error=-5
2025-05-02T12:52:18.290512+08:00 JZ-NAS kernel: [  383.288097] md: super_written gets error=-5
2025-05-02T12:52:18.295661+08:00 JZ-NAS kernel: [  383.292809] md: super_written gets error=-5
2025-05-02T12:52:18.295699+08:00 JZ-NAS kernel: [  383.293041] md: super_written gets error=-5
2025-05-02T12:52:18.295702+08:00 JZ-NAS kernel: [  383.293204] md: super_written gets error=-5
2025-05-02T12:52:18.298202+08:00 JZ-NAS kernel: [  383.294110] md: super_written gets error=-5
2025-05-02T12:52:18.298231+08:00 JZ-NAS kernel: [  383.294374] md: super_written gets error=-5
2025-05-02T12:52:18.298233+08:00 JZ-NAS kernel: [  383.294511] md: super_written gets error=-5
2025-05-02T12:52:18.364434+08:00 JZ-NAS kernel: [  383.361794] md: super_written gets error=-5
2025-05-02T12:52:18.364496+08:00 JZ-NAS kernel: [  383.362011] md: super_written gets error=-5
2025-05-02T12:52:18.375322+08:00 JZ-NAS kernel: [  383.372519] md: super_written gets error=-5
2025-05-02T12:52:18.375350+08:00 JZ-NAS kernel: [  383.372719] md: super_written gets error=-5
2025-05-02T12:52:18.375353+08:00 JZ-NAS kernel: [  383.372855] md: super_written gets error=-5
2025-05-02T12:52:18.382534+08:00 JZ-NAS kernel: [  383.376632] md: super_written gets error=-5
2025-05-02T12:52:18.382565+08:00 JZ-NAS kernel: [  383.376812] md: super_written gets error=-5
2025-05-02T12:52:18.382568+08:00 JZ-NAS kernel: [  383.376964] md: super_written gets error=-5
2025-05-02T12:52:18.382572+08:00 JZ-NAS kernel: [  383.377896] md: super_written gets error=-5
2025-05-02T12:52:18.382573+08:00 JZ-NAS kernel: [  383.378086] md: super_written gets error=-5
2025-05-02T12:52:18.382574+08:00 JZ-NAS kernel: [  383.378228] md: super_written gets error=-5
2025-05-02T12:52:18.382575+08:00 JZ-NAS kernel: [  383.379206] md: super_written gets error=-5
2025-05-02T12:52:18.382576+08:00 JZ-NAS kernel: [  383.379422] md: super_written gets error=-5
2025-05-02T12:52:18.382577+08:00 JZ-NAS kernel: [  383.379587] md: super_written gets error=-5
2025-05-02T12:52:18.386990+08:00 JZ-NAS kernel: [  383.380574] md: super_written gets error=-5
2025-05-02T12:52:18.387022+08:00 JZ-NAS kernel: [  383.380766] md: super_written gets error=-5
2025-05-02T12:52:18.387027+08:00 JZ-NAS kernel: [  383.380921] md: super_written gets error=-5
2025-05-02T12:52:18.387028+08:00 JZ-NAS kernel: [  383.382620] md: super_written gets error=-5
2025-05-02T12:52:18.387029+08:00 JZ-NAS kernel: [  383.382799] md: super_written gets error=-5
2025-05-02T12:52:18.387030+08:00 JZ-NAS kernel: [  383.382972] md: super_written gets error=-5
2025-05-02T12:52:18.387031+08:00 JZ-NAS kernel: [  383.383956] md: super_written gets error=-5
2025-05-02T12:52:18.387032+08:00 JZ-NAS kernel: [  383.384147] md: super_written gets error=-5
2025-05-02T12:52:18.387033+08:00 JZ-NAS kernel: [  383.384291] md: super_written gets error=-5
2025-05-02T12:52:18.406222+08:00 JZ-NAS kernel: [  383.402353] md: super_written gets error=-5
2025-05-02T12:52:18.406257+08:00 JZ-NAS kernel: [  383.402525] md: super_written gets error=-5
2025-05-02T12:52:18.406260+08:00 JZ-NAS kernel: [  383.402659] md: super_written gets error=-5
2025-05-02T12:52:18.786462+08:00 JZ-NAS kernel: [  383.780123] md: super_written gets error=-5
2025-05-02T12:52:18.786501+08:00 JZ-NAS kernel: [  383.781126] md: super_written gets error=-5
2025-05-02T12:52:23.942356+08:00 JZ-NAS kernel: [  388.936004] sd 5:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:27.730453+08:00 JZ-NAS systemd[1]: Created slice user-1000.slice - User Slice of UID 1000.
2025-05-02T12:52:27.759251+08:00 JZ-NAS systemd[1]: Starting user-runtime-dir@1000.service - User Runtime Directory /run/user/1000...
2025-05-02T12:52:27.784239+08:00 JZ-NAS systemd[1]: Finished user-runtime-dir@1000.service - User Runtime Directory /run/user/1000.
2025-05-02T12:52:27.787919+08:00 JZ-NAS systemd[1]: Starting user@1000.service - User Manager for UID 1000...
2025-05-02T12:52:28.202622+08:00 JZ-NAS systemd[3698]: Queued start ** for default target default.target.
2025-05-02T12:52:28.204632+08:00 JZ-NAS systemd[3698]: Created slice app.slice - User Application Slice.
2025-05-02T12:52:28.204765+08:00 JZ-NAS systemd[3698]: Reached target paths.target - Paths.
2025-05-02T12:52:28.204878+08:00 JZ-NAS systemd[3698]: Reached target timers.target - Timers.
2025-05-02T12:52:28.206777+08:00 JZ-NAS systemd[3698]: Starting dbus.socket - D-Bus User Message Bus Socket...
2025-05-02T12:52:28.207256+08:00 JZ-NAS systemd[3698]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
2025-05-02T12:52:28.207647+08:00 JZ-NAS systemd[3698]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
2025-05-02T12:52:28.207847+08:00 JZ-NAS systemd[3698]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
2025-05-02T12:52:28.208069+08:00 JZ-NAS systemd[3698]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
2025-05-02T12:52:28.208360+08:00 JZ-NAS systemd[3698]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
2025-05-02T12:52:28.219245+08:00 JZ-NAS systemd[3698]: Listening on dbus.socket - D-Bus User Message Bus Socket.
2025-05-02T12:52:28.219396+08:00 JZ-NAS systemd[3698]: Reached target sockets.target - Sockets.
2025-05-02T12:52:28.219497+08:00 JZ-NAS systemd[3698]: Reached target basic.target - Basic System.
2025-05-02T12:52:28.219600+08:00 JZ-NAS systemd[1]: Started user@1000.service - User Manager for UID 1000.
2025-05-02T12:52:28.220883+08:00 JZ-NAS systemd[3698]: Reached target default.target - Main User Target.
2025-05-02T12:52:28.221007+08:00 JZ-NAS systemd[3698]: Startup finished in 405ms.
2025-05-02T12:52:28.221555+08:00 JZ-NAS systemd[1]: Started session-1.scope - Session 1 of User it2911.
2025-05-02T12:52:34.178366+08:00 JZ-NAS kernel: [  399.171678] sd 5:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
2025-05-02T12:52:34.178401+08:00 JZ-NAS kernel: [  399.171690] sd 5:0:0:0: [sdb] tag#20 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
2025-05-02T12:52:34.178404+08:00 JZ-NAS kernel: [  399.171699] I/O error, dev sdb, sector 2064 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
2025-05-02T12:52:34.178407+08:00 JZ-NAS kernel: [  399.171955] md: super_written gets error=-5

		自动登录	找回密码
密码			立即注册

关于拷贝大量时候，文件硬盘丢失的问题

关于拷贝大量时候，文件硬盘丢失的问题

硬件和软件环境

现象

点评

本帖子中包含更多资源

本帖子中包含更多资源

社区上线纪念勋章

社区共建团荣誉勋章

飞牛百度网盘玩家