掉盘，经常提示【存储空间已损坏】

徐哈哈

[i=s] 本帖最后由 徐哈哈 于 2024-12-4 09:32 编辑 [/i]<br /> <br />

【我的环境】

60W电源

整机峰值功耗15W

---

经常提示【存储控件已损坏】，但是能正常读储空间中的文件，重启后可能会解决(有时无法解决)，如下图

---

这个问题出现了2周左右，暂时没有找到有效的解决办法

有知道如何处理的大佬，麻烦请帮忙给出建议，谢谢

---

---

【新状况】

刚写完帖子，又有新状况，未进行任何操作，一个存储空间变成了【已移除】，且空间内的文件无法查看

重启无法解决。

我的解决方法：

关机 -> 拔出硬盘 -> 开机 -> 删除存储空间 -> 关机 -> 插入硬盘 -> 重新挂载存储空间

7xx

用的是那家的主板

7xx

如果用了扩展板，就考虑一下扩展板的原因，或者电源

Melody

发一下日志

徐哈哈

使用的畅网 p5 n100开发板

徐哈哈

[i=s] 本帖最后由 徐哈哈 于 2024-12-4 13:25 编辑 [/i]<br /> <br />

下面是昨晚到现在全部日志：

徐哈哈

等级,模块,时间,用户,事件
普通,登录连接,2024-12-04 13:15:53,XuHaha,XuHaha登录成功 IP:*****,
普通,文件传输,2024-12-04 09:56:27,XuHaha, pam_unix(samba:session): session closed for user XuHaha,
普通,文件传输,2024-12-04 09:55:27,XuHaha, pam_unix(samba:session): session opened for user XuHaha(uid=1000) by (uid=0),
普通,文件传输,2024-12-04 09:52:19,XuHaha, pam_unix(samba:session): session closed for user XuHaha,
普通,文件传输,2024-12-04 09:51:19,XuHaha, pam_unix(samba:session): session opened for user XuHaha(uid=1000) by (uid=0),
普通,文件传输,2024-12-04 09:50:57,XuHaha, pam_unix(samba:session): session closed for user XuHaha,
普通,文件传输,2024-12-04 09:49:57,XuHaha, pam_unix(samba:session): session opened for user XuHaha(uid=1000) by (uid=0),
普通,文件传输,2024-12-04 09:48:48,XuHaha, pam_unix(samba:session): session closed for user XuHaha,
普通,文件传输,2024-12-04 09:47:48,XuHaha, pam_unix(samba:session): session opened for user XuHaha(uid=1000) by (uid=0),
普通,登录连接,2024-12-04 09:47:05,XuHaha,XuHaha登录成功 IP:*****
普通,登录连接,2024-12-04 08:15:29,XuHaha,XuHaha登录成功 IP:::1,
错误,硬盘存储,2024-12-03 23:05:19,system,存储空间3已损坏,
普通,文件传输,2024-12-03 22:59:59,XuHaha, pam_unix(samba:session): session opened for user XuHaha(uid=1000) by (uid=0),
普通,文件传输,2024-12-03 22:59:59,XuHaha,用户通过smb删除了文件：/vol3/1000/Mi_Camera/xiaomi_camera_videos/78DF7250BFF4/20241127155549_20241127160656.mp4,
普通,文件传输,2024-12-03 22:59:59,nobody, pam_unix(samba:session): session closed for user nobody,
普通,硬盘存储,2024-12-03 22:59:02,system,存储空间3已恢复正常。,

奔跑的蜗牛

我来告诉你,我同样遇到你的问题了,我是改了外置硬盘盒独立供电就没有出现问题了.

徐哈哈

这这这。。。我的外置硬盘盒就是独立供电的呀，呜呜呜

徐哈哈

莫非真是我电源的问题，您用的是什么电源呢

奔跑的蜗牛

徐哈哈 发表于 2024-12-4 15:51
莫非真是我电源的问题，您用的是什么电源呢

我用48W的供电,你检测一下你的硬盘,还有usb接口看看

徐哈哈

硬盘都进行检测了，都没有问题。
请问您使用的主板也是n100开发板嘛。
我的主板供电和硬盘盒供电是两个供电口，电源是一个60W的双5.5*2.5cm接口供电电源。
我准备换成两个5.5*2.5cm单接口电源，分别供电试试，不知道行不行

奔跑的蜗牛

我觉得你试试更新主板bios试试.不然有可能会是主板的问题

徐哈哈

好的， 我都试一下，有进展我会在这个贴子反馈，感谢您的回答

徐哈哈

附件：dmesg.zip

附件是掉盘的dmesg日志

吴小剑

主板或者供电的问题，优先排查供电问题

$$x

我觉得是电源问题，我也装了好几块硬盘，只要对硬盘进行大文件读写操作就会掉盘。后来换了个电源就好了。不过我的是台式机电源，你的应该是用DC电源吧。换个大功率的DC电源试试。

lohengrin

我也是X86P5全闪，配了个60W的电源，待机才20W多点，大概一周就要提示一次存储空间损坏，几块盘检测都是好的。。
但是我这一套以前用在unrai时候几个月也没碰到过。。。感觉是不是飞牛后台对于存储空间损坏的检测太严格？唤醒慢了就会判定是硬盘损坏？

GxDong_GpfC1

我的外置硬盘盒也是这个问题还没解决，不是供电的问题，因为这个硬盘盒，之前装的windows一点问题都没有。但是换了飞牛os总是掉盘，一直是这个问题

GxDong_GpfC1

我的也是，掉盘

-M-

我笔记本也是这个问题

神经蛙_SmDD3

官方要赶紧关注了，这个问题很严重。
我一直以为是自己买的硬盘不好，换了硬盘昨天又掉盘了，而且重启也无法挂载。。。

Alex丶☜

同样问题，开机突然就提示存储空间5损坏 ，硬盘检测一点问题没有；存在存储空间5上的数据还可以访问。。。。有啥好的解决办法吗 我得是拓展卡接过来得

永世の摇篮

解决了吗，我也是这个问题

zgpshx

我已经把硬盘休眠关掉了。还是经常掉盘。不知道啥原因。

KLNC

我的也是一个raid0一个raid5来回掉，还好没存什么重要文件，供电也查了都足量，装电脑上啥事都没有，

三皮x

我这几天也是被掉盘困扰，一直以为是盘的问题。看日志还是有给提示的：

唔简单

我认为不是电源和硬盘问题，这已经是第二次了，重新删除创建好了几天又这样，之前用群晖一直没问题

唔简单

吴小剑 发表于 2024-12-5 10:27
主板或者供电的问题，优先排查供电问题

我认为不是电源和硬盘问题，我的已经是第二次了，重新删除创建好了几天又这样，之前用群晖一直没问题，下面的用户也说了笔记本也出现这样的情况

henry126

我用的台式机（g2200 cpu + am4 主板 + 2T nas机械盘），大概是3月份开始就出现这个问题，重新装fnos后会识别，然后一定会出现已损坏。

YOLO_ZSiSp

我也出现这个问题了

比巴卜

我也是。以为是硬盘和硬盘盒的问题。全部换新的，也检测过了，没问题。但是还是2-3天就出现空间已移除或损坏。麻烦官方关注一下，解决了把

xiaowang666

是不是外接机械盘不稳定，试试固态

Sun🌝_PZ5qe

2025-07-19T17:44:37.161697+08:00 Sun-fnOS kernel: [ 687.099130] scsi host1: uas_eh_device_reset_handler start
2025-07-19T17:44:37.281682+08:00 Sun-fnOS kernel: [ 687.219431] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
2025-07-19T17:44:37.297667+08:00 Sun-fnOS kernel: [ 687.235777] usb 2-1: device firmware changed
2025-07-19T17:44:37.305797+08:00 Sun-fnOS kernel: [ 687.243080] scsi host1: uas_eh_device_reset_handler FAILED err -19
2025-07-19T17:44:37.305824+08:00 Sun-fnOS kernel: [ 687.243096] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305827+08:00 Sun-fnOS kernel: [ 687.243140] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305828+08:00 Sun-fnOS kernel: [ 687.243145] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305831+08:00 Sun-fnOS kernel: [ 687.243149] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305833+08:00 Sun-fnOS kernel: [ 687.243153] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305834+08:00 Sun-fnOS kernel: [ 687.243157] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305836+08:00 Sun-fnOS kernel: [ 687.243161] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305838+08:00 Sun-fnOS kernel: [ 687.243164] sd 1:0:0:0: Device offlined - not ready after error recovery
2025-07-19T17:44:37.305840+08:00 Sun-fnOS kernel: [ 687.243185] sd 1:0:0:0: [sdb] tag#22 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=30s
2025-07-19T17:44:37.305842+08:00 Sun-fnOS kernel: [ 687.243193] sd 1:0:0:0: [sdb] tag#22 CDB: Read(16) 88 00 00 00 00 00 00 07 8b 00 00 00 00 20 00 00
2025-07-19T17:44:37.305844+08:00 Sun-fnOS kernel: [ 687.243197] I/O error, dev sdb, sector 494336 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
2025-07-19T17:44:37.305846+08:00 Sun-fnOS kernel: [ 687.243228] BTRFS error (device dm-1): bdev /dev/mapper/trim_7fc95517_e39b_4313_b593_22b0985c4cc2-0 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0
2025-07-19T17:44:37.305848+08:00 Sun-fnOS kernel: [ 687.243276] sd 1:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=55s
2025-07-19T17:44:37.305850+08:00 Sun-fnOS kernel: [ 687.243286] sd 1:0:0:0: [sdb] tag#11 CDB: Write(16) 8a 00 00 00 00 00 09 9b 41 48 00 00 04 00 00 00
2025-07-19T17:44:37.305852+08:00 Sun-fnOS kernel: [ 687.243292] I/O error, dev sdb, sector 161169736 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
2025-07-19T17:44:37.305854+08:00 Sun-fnOS kernel: [ 687.243335] sd 1:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=55s
2025-07-19T17:44:37.305855+08:00 Sun-fnOS kernel: [ 687.243341] sd 1:0:0:0: [sdb] tag#12 CDB: Write(16) 8a 00 00 00 00 00 09 9b 45 48 00 00 04 00 00 00
2025-07-19T17:44:37.305857+08:00 Sun-fnOS kernel: [ 687.243345] I/O error, dev sdb, sector 161170760 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
2025-07-19T17:44:37.305859+08:00 Sun-fnOS kernel: [ 687.243364] sd 1:0:0:0: rejecting I/O to offline device
2025-07-19T17:44:37.305861+08:00 Sun-fnOS kernel: [ 687.243376] sd 1:0:0:0: [sdb] tag#13 CDB: Write(16) 8a 00 00 00 00 00 09 9b 49 48 00 00 04 00 00 00
2025-07-19T17:44:37.305863+08:00 Sun-fnOS kernel: [ 687.243393] I/O error, dev sdb, sector 2591488 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
2025-07-19T17:44:37.305865+08:00 Sun-fnOS kernel: [ 687.243424] sd 1:0:0:0: [sdb] tag#14 CDB: Write(16) 8a 00 00 00 00 00 09 9b 4d 48 00 00 04 00 00 00
2025-07-19T17:44:37.305867+08:00 Sun-fnOS kernel: [ 687.243429] BTRFS error (device dm-1): bdev /dev/mapper/trim_7fc95517_e39b_4313_b593_22b0985c4cc2-0 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
2025-07-19T17:44:37.305869+08:00 Sun-fnOS kernel: [ 687.243466] sd 1:0:0:0: [sdb] tag#15 CDB: Write(16) 8a 00 00 00 00 00 09 9b 51 48 00 00 04 00 00 00
2025-07-19T17:44:37.305871+08:00 Sun-fnOS kernel: [ 687.243513] sd 1:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=55s
2025-07-19T17:44:37.305872+08:00 Sun-fnOS kernel: [ 687.243528] I/O error, dev sdb, sector 161332576 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
2025-07-19T17:44:37.305874+08:00 Sun-fnOS kernel: [ 687.243550] BTRFS error (device dm-1 state A): bdev /dev/mapper/trim_7fc95517_e39b_4313_b593_22b0985c4cc2-0 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0
2025-07-19T17:44:37.305876+08:00 Sun-fnOS kernel: [ 687.243585] BTRFS info (device dm-1 state EA): forced readonly
2025-07-19T17:44:37.305878+08:00 Sun-fnOS kernel: [ 687.243591] BTRFS error (device dm-1 state EA): failed to run delayed ref for logical 6523199488 num_bytes 8192 type 178 action 2 ref_mod 1: -5
2025-07-19T17:44:37.305880+08:00 Sun-fnOS kernel: [ 687.243611] BTRFS: error (device dm-1 state EA) in btrfs_run_delayed_refs:2215: errno=-5 IO failure
2025-07-19T17:44:37.305882+08:00 Sun-fnOS kernel: [ 687.244000] sd 1:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=55s
2025-07-19T17:44:37.305883+08:00 Sun-fnOS kernel: [ 687.244014] sd 1:0:0:0: [sdb] tag#21 CDB: Write(16) 8a 00 00 00 00 00 09 9b 55 48 00 00 01 88 00 00
2025-07-19T17:44:37.305886+08:00 Sun-fnOS kernel: [ 687.244021] I/O error, dev sdb, sector 161174856 op 0x1:(WRITE) flags 0x4800 phys_seg 49 prio class 0
2025-07-19T17:44:37.305887+08:00 Sun-fnOS kernel: [ 687.244052] BTRFS error (device dm-1 state EA): bdev /dev/mapper/trim_7fc95517_e39b_4313_b593_22b0985c4cc2-0 errs: wr 2, rd 2, flush 0, corrupt 0, gen 0
2025-07-19T17:44:37.305889+08:00 Sun-fnOS kernel: [ 687.245344] usb 2-1: USB disconnect, device number 2
2025-07-19T17:44:37.305891+08:00 Sun-fnOS kernel: [ 687.245420] I/O error, dev sdb, sector 161333600 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
2025-07-19T17:44:37.305893+08:00 Sun-fnOS kernel: [ 687.245599] md: sdb1 flush io error -5
2025-07-19T17:44:37.305895+08:00 Sun-fnOS kernel: [ 687.245920] BTRFS warning (device dm-1 state EA): lost super block write due to IO error on /dev/mapper/trim_7fc95517_e39b_4313_b593_22b0985c4cc2-0 (-19)
2025-07-19T17:44:37.305897+08:00 Sun-fnOS kernel: [ 687.245936] BTRFS error (device dm-1 state EA): bdev /dev/mapper/trim_7fc95517_e39b_4313_b593_22b0985c4cc2-0 errs: wr 3, rd 2, flush 0, corrupt 0, gen 0
2025-07-19T17:44:37.305899+08:00 Sun-fnOS kernel: [ 687.245968] BTRFS error (device dm-1 state EA): 1 errors while writing supers
2025-07-19T17:44:37.305900+08:00 Sun-fnOS kernel: [ 687.246006] BTRFS: error (device dm-1 state EA) in btrfs_sync_log:3186: errno=-5 IO failure
2025-07-19T17:44:37.305902+08:00 Sun-fnOS kernel: [ 687.247132] BTRFS error (device dm-1 state EA): bdev /dev/mapper/trim_7fc95517_e39b_4313_b593_22b0985c4cc2-0 errs: wr 4, rd 2, flush 0, corrupt 0, gen 0
2025-07-19T17:44:37.675592+08:00 Sun-fnOS (udev-worker)[10219]: sdb1: Process '/sbin/mdadm -If sdb1 --path pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0' failed with exit code 1.
2025-07-19T17:44:37.808456+08:00 Sun-fnOS MAINEVENT[1616]: MAINEVENT:{"cat":0,"template":"EjectDisk","name":"sdb","model":"ST4000HKVS002-3FC104","serial":"WW65Q1GG"}
2025-07-19T17:44:37.857728+08:00 Sun-fnOS kernel: [ 687.795098] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
2025-07-19T17:44:37.877653+08:00 Sun-fnOS kernel: [ 687.815442] scsi host3: uas
2025-07-19T17:44:37.881647+08:00 Sun-fnOS kernel: [ 687.820043] sd 3:0:0:0: Attached scsi generic sg1 type 0
2025-07-19T17:44:37.897686+08:00 Sun-fnOS kernel: [ 687.836366] sd 3:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
2025-07-19T17:44:37.897702+08:00 Sun-fnOS kernel: [ 687.836372] sd 3:0:0:0: [sdd] 4096-byte physical blocks
2025-07-19T17:44:37.897704+08:00 Sun-fnOS kernel: [ 687.836485] sd 3:0:0:0: [sdd] Write Protect is off
2025-07-19T17:44:37.897705+08:00 Sun-fnOS kernel: [ 687.836488] sd 3:0:0:0: [sdd] Mode Sense: 43 00 00 00
2025-07-19T17:44:37.897706+08:00 Sun-fnOS kernel: [ 687.836641] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
2025-07-19T17:44:37.945654+08:00 Sun-fnOS kernel: [ 687.883224] sd 3:0:0:0: [sdd] Preferred minimum I/O size 4096 bytes
2025-07-19T17:44:37.993644+08:00 Sun-fnOS kernel: [ 687.932098] sdd: sdd1
2025-07-19T17:44:37.993665+08:00 Sun-fnOS kernel: [ 687.932242] sd 3:0:0:0: [sdd] Attached SCSI disk
2025-07-19T17:44:38.241730+08:00 Sun-fnOS MAINEVENT[1616]: MAINEVENT:{"cat":1,"template":"StorageBroken","volume":2}
2025-07-19T17:44:38.293286+08:00 Sun-fnOS monitor[1644]: Received command, data size: 64
2025-07-19T17:44:38.293387+08:00 Sun-fnOS monitor[1644]: Command, id:101, length:56, data:#024
2025-07-19T17:44:38.293556+08:00 Sun-fnOS monitor[1644]: Received command, id:5, path:/vol2/@snapshot, mask:0x000007c0, level:0
2025-07-19T17:44:38.296555+08:00 Sun-fnOS monitor[1644]: Couldn't remove monitor '/vol2/@snapshot': No such file or directory
2025-07-19T17:44:38.298452+08:00 Sun-fnOS monitor[1644]: Received command, data size: 64
2025-07-19T17:44:38.298596+08:00 Sun-fnOS monitor[1644]: Command, id:101, length:56, data:#024
2025-07-19T17:44:38.298682+08:00 Sun-fnOS monitor[1644]: Received command, id:5, path:/vol1/@snapshot, mask:0x000007c0, level:0
2025-07-19T17:44:38.298752+08:00 Sun-fnOS monitor[1644]: Couldn't remove monitor '/vol1/@snapshot': No such file or directory
2025-07-19T17:44:38.307995+08:00 Sun-fnOS systemd[1]: Stopping minidlna.service - minidlnad...
2025-07-19T17:44:38.308712+08:00 Sun-fnOS minidlnad[1628]: minidlna.c:199: warn: received signal 15, good-bye
2025-07-19T17:44:38.308798+08:00 Sun-fnOS minidlnad[1628]: minidlna.c:1324: warn: shutdown(): Interrupted system call
2025-07-19T17:44:38.318096+08:00 Sun-fnOS minidlnad[1628]: EXIT_SUCCESS
2025-07-19T17:44:38.318203+08:00 Sun-fnOS minidlnad[1628]: : No such file or directory
2025-07-19T17:44:38.362127+08:00 Sun-fnOS trim_file_monitor[1644]: [StorageListener]Received unknow message
2025-07-19T17:44:38.367492+08:00 Sun-fnOS nmbd[1208]: [2025/07/19 17:44:38.366338, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-07-19T17:44:38.367617+08:00 Sun-fnOS nmbd[1208]: dump_workgroups()
2025-07-19T17:44:38.367692+08:00 Sun-fnOS nmbd[1208]: dump workgroup on subnet 172.18.0.1: netmask= 255.255.0.0:
2025-07-19T17:44:38.367763+08:00 Sun-fnOS nmbd[1208]: #011WORKGROUP(1) current master browser = SUN-FNOS
2025-07-19T17:44:38.367832+08:00 Sun-fnOS nmbd[1208]: #011#011SUN-FNOS 40849a03 (Sun-fnOS server (Samba TRIM))
2025-07-19T17:44:38.367899+08:00 Sun-fnOS nmbd[1208]: [2025/07/19 17:44:38.367181, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-07-19T17:44:38.367994+08:00 Sun-fnOS nmbd[1208]: dump_workgroups()
2025-07-19T17:44:38.368064+08:00 Sun-fnOS nmbd[1208]: dump workgroup on subnet 172.17.0.1: netmask= 255.255.0.0:
2025-07-19T17:44:38.368130+08:00 Sun-fnOS nmbd[1208]: #011WORKGROUP(1) current master browser = SUN-FNOS
2025-07-19T17:44:38.368224+08:00 Sun-fnOS nmbd[1208]: #011#011SUN-FNOS 40849a03 (Sun-fnOS server (Samba TRIM))
2025-07-19T17:44:38.368277+08:00 Sun-fnOS nmbd[1208]: [2025/07/19 17:44:38.367287, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-07-19T17:44:38.368325+08:00 Sun-fnOS nmbd[1208]: dump_workgroups()
2025-07-19T17:44:38.368380+08:00 Sun-fnOS nmbd[1208]: dump workgroup on subnet 192.168.68.210: netmask= 255.255.255.0:
2025-07-19T17:44:38.368432+08:00 Sun-fnOS nmbd[1208]: #011WORKGROUP(1) current master browser = UNKNOWN
2025-07-19T17:44:38.368482+08:00 Sun-fnOS nmbd[1208]: #011#011SUN-FNOS 40819a03 (Sun-fnOS server (Samba TRIM))
2025-07-19T17:44:38.376989+08:00 Sun-fnOS systemd[1]: minidlna.service: Deactivated successfully.
2025-07-19T17:44:38.377267+08:00 Sun-fnOS systemd[1]: Stopped minidlna.service - minidlnad.
2025-07-19T17:44:38.422291+08:00 Sun-fnOS systemd[1]: Started minidlna.service - minidlnad.
2025-07-19T17:44:38.467353+08:00 Sun-fnOS minidlnad[10263]: minidlna.c:1170: warn: Starting MiniDLNA version 1.3.3.
2025-07-19T17:44:38.468015+08:00 Sun-fnOS minidlnad[10263]: minidlna.c:421: warn: Creating new database at /usr/trim/var/minidlna/files.db
2025-07-19T17:44:38.475640+08:00 Sun-fnOS minidlnad[10263]: minidlna.c:1218: warn: HTTP listening on port 8200
2025-07-19T17:44:38.475827+08:00 Sun-fnOS minidlnad[10263]: getifaddr.c:342: info: Enabling interface 192.168.68.210/255.255.255.0
2025-07-19T17:44:38.476811+08:00 Sun-fnOS minidlnad[10269]: playlist.c:135: warn: Parsing playlists...
2025-07-19T17:44:38.476866+08:00 Sun-fnOS minidlnad[10269]: playlist.c:269: warn: Finished parsing playlists.
2025-07-19T17:44:38.479444+08:00 Sun-fnOS minidlnad[10263]: getifaddr.c:342: info: Enabling interface 172.18.0.1/255.255.0.0
2025-07-19T17:44:38.669290+08:00 Sun-fnOS minidlnad[10263]: getifaddr.c:342: info: Enabling interface 172.17.0.1/255.255.0.0
2025-07-19T17:44:38.816849+08:00 Sun-fnOS MAINEVENT[1616]: MAINEVENT:{"cat":0,"template":"InsertDisk","name":"sdd","model":"ST4000HKVS002-3FC104","serial":"WW65Q1GG"}
2025-07-19T17:44:38.897874+08:00 Sun-fnOS minidlnad[10263]: minidlna.c:1310: info: Scanner exited
2025-07-19T17:44:39.877582+08:00 Sun-fnOS nmbd[1208]: [2025/07/19 17:44:39.876387, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-07-19T17:44:39.877715+08:00 Sun-fnOS nmbd[1208]: dump_workgroups()
2025-07-19T17:44:39.877786+08:00 Sun-fnOS nmbd[1208]: dump workgroup on subnet 172.18.0.1: netmask= 255.255.0.0:
2025-07-19T17:44:39.877848+08:00 Sun-fnOS nmbd[1208]: #011WORKGROUP(1) current master browser = SUN-FNOS
2025-07-19T17:44:39.877910+08:00 Sun-fnOS nmbd[1208]: #011#011SUN-FNOS 40849a03 (Sun-fnOS server (Samba TRIM))
2025-07-19T17:44:39.877969+08:00 Sun-fnOS nmbd[1208]: [2025/07/19 17:44:39.876502, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-07-19T17:44:39.878078+08:00 Sun-fnOS nmbd[1208]: dump_workgroups()
2025-07-19T17:44:39.878190+08:00 Sun-fnOS nmbd[1208]: dump workgroup on subnet 172.17.0.1: netmask= 255.255.0.0:
2025-07-19T17:44:39.878249+08:00 Sun-fnOS nmbd[1208]: #011WORKGROUP(1) current master browser = SUN-FNOS
2025-07-19T17:44:39.878303+08:00 Sun-fnOS nmbd[1208]: #011#011SUN-FNOS 40849a03 (Sun-fnOS server (Samba TRIM))
2025-07-19T17:44:39.878359+08:00 Sun-fnOS nmbd[1208]: [2025/07/19 17:44:39.876556, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)
2025-07-19T17:44:39.878412+08:00 Sun-fnOS nmbd[1208]: dump_workgroups()
2025-07-19T17:44:39.878459+08:00 Sun-fnOS nmbd[1208]: dump workgroup on subnet 192.168.68.210: netmask= 255.255.255.0:
2025-07-19T17:44:39.878513+08:00 Sun-fnOS nmbd[1208]: #011WORKGROUP(1) current master browser = UNKNOWN
2025-07-19T17:44:39.878571+08:00 Sun-fnOS nmbd[1208]: #011#011SUN-FNOS 40819a03 (Sun-fnOS server (Samba TRIM))
2025-07-19T17:44:41.118193+08:00 Sun-fnOS trim[1616]: #033[1;32mget_spare_disk_stor_uuid[rc:0]: sdd#033[0m
2025-07-19T17:44:41.118284+08:00 Sun-fnOS trim[1616]: #033[0;31mpopen_read2: WEXITSTATUS=32, mount ]]#033[0m
2025-07-19T17:44:41.118339+08:00 Sun-fnOS trim[1616]: [0]mount
2025-07-19T17:44:41.118388+08:00 Sun-fnOS trim[1616]: [1]/dev/sdd1
2025-07-19T17:44:41.118434+08:00 Sun-fnOS trim[1616]: [2]/vol00/ST4000HKVS002-3FC104
2025-07-19T17:44:41.118480+08:00 Sun-fnOS trim[1616]: #033[0;31mpopen_read2: WEXITSTATUS=32, mount ]]#033[0m
2025-07-19T17:44:41.118526+08:00 Sun-fnOS trim[1616]: [0]mount
2025-07-19T17:44:41.118569+08:00 Sun-fnOS trim[1616]: [1]/dev/sdd
2025-07-19T17:44:41.118609+08:00 Sun-fnOS trim[1616]: [2]/vol00/ST4000HKVS002-3FC104
2025-07-19T17:44:48.307045+08:00 Sun-fnOS trim_file_monitor[1644]: Saved done!

贴一下报错日志，官方麻烦排查下吧

大东x

这问题有办法解决吗，我现在又出现了，我已经把机箱上连接硬盘的背板，电源（电源是1u全汉300W的），数据线全都换过了，目前还是出现这种情况，就差换主板了，用的是蜗牛星际B款的机箱和主板，大家有找到解决办法的吗