mingshun

Hey everyone, I'm in a bit of a pickle and hoping someone here can lend me a hand. I've been running Unraid version 6.10.3 on my NAS system for quite a few years now. I know, I've been neglecting updates for far too long, but now I'm finally ready to bring my system up to date. The current latest version is 7.0.1, and I'm considering making the jump. However, I'm extremely concerned about potential issues that might arise from such a significant version leap. I'm worried that there could be compatibility problems with my existing apps, plugins, and configurations. I also have a lot of important data stored on my NAS, and the last thing I want is for anything to go wrong during the upgrade process and risk losing that data. Has anyone here ever upgraded Unraid across multiple major versions like this? If so, could you share your experiences? Are there any specific steps I should take before starting the upgrade? Should I create backups of certain files or configurations in particular? Are there any known issues or compatibility problems I should be aware of when moving from 6.10.3 to 7.0.1? I'd be incredibly grateful for any advice, tips, or insights you can offer. I really want to get this upgrade done smoothly without any hiccups. Thanks in advance for your help!

感谢，docker重启后已经解决，上面可能是关闭过程中出现的

有点怀疑不是docker的问题，我把docker整体关掉之后这类日志仍然出现，如下见最后两行： Jan 22 14:32:36 MingShun nmbd[19279]: [2025/01/22 14:32:36.039270, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 22 14:32:36 MingShun nmbd[19279]: ***** Jan 22 14:32:36 MingShun nmbd[19279]: Jan 22 14:32:36 MingShun nmbd[19279]: Samba name server MINGSHUN is now a local master browser for workgroup WORKGROUP on subnet 192.168.50.155 Jan 22 14:32:36 MingShun nmbd[19279]: Jan 22 14:32:36 MingShun nmbd[19279]: ***** Jan 22 14:32:36 MingShun nmbd[19279]: [2025/01/22 14:32:36.039393, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 22 14:32:36 MingShun nmbd[19279]: ***** Jan 22 14:32:36 MingShun nmbd[19279]: Jan 22 14:32:36 MingShun nmbd[19279]: Samba name server MINGSHUN is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Jan 22 14:32:36 MingShun nmbd[19279]: Jan 22 14:32:36 MingShun nmbd[19279]: ***** Jan 22 14:33:16 MingShun nmbd[19279]: [2025/01/22 14:33:16.084620, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 22 14:33:16 MingShun nmbd[19279]: Packet send failed to 172.17.255.255(138) ERRNO=Network is unreachable

已经检查： 1. docker compose里面是空的，上次已经down掉了 2. 查看了所有在运行的docker，都是我常用的，不包含上次安装的； 3. 我的所有docker的IP都是172.17.*.*段的，路由表也是这个号段，也很奇怪为什么日志出现了172.18的IP

前两天安装了一个docker，还发帖咨询怎么删除，自从删除这个docker后，日志中每天都会出现很多如下的报错，看起来是和网络有关，但是又查询不到具体原因，请大家帮忙看看是否遇到过，如何解决，感谢感谢。 Jan 20 14:01:07 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable Jan 20 14:01:07 MingShun nmbd[22979]: [2025/01/20 14:01:07.808483, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 20 14:01:07 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable Jan 20 14:13:15 MingShun nmbd[22979]: [2025/01/20 14:13:15.224124, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 20 14:13:15 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable Jan 20 14:13:15 MingShun nmbd[22979]: [2025/01/20 14:13:15.224164, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 20 14:13:15 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable Jan 20 14:25:17 MingShun nmbd[22979]: [2025/01/20 14:25:17.554246, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 20 14:25:17 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable Jan 20 14:25:17 MingShun nmbd[22979]: [2025/01/20 14:25:17.554285, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 20 14:25:17 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable Jan 20 14:37:19 MingShun nmbd[22979]: [2025/01/20 14:37:19.557647, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 20 14:37:19 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable Jan 20 14:37:19 MingShun nmbd[22979]: [2025/01/20 14:37:19.557686, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jan 20 14:37:19 MingShun nmbd[22979]: Packet send failed to 172.18.255.255(138) ERRNO=Network is unreachable

感谢，第一个方式就解决了

创建后发现无法使用，准备删除，但是发现删除按钮是灰色的无法点击，如下图： 目前安装的所有相关docker已经手动关闭，仍然无法删除，请问该怎么办？

Thank you so much! Following the Docker start time, I was able to identify the most recent container and stopping it resolved the issue with the logs.

I've been running my Unraid system smoothly for a year, but recently I've encountered a strange issue. The webGUI is showing that the log is rapidly growing to almost 100%, and I'm not sure what's causing this. From the logs, I can see that some ports are constantly opening and closing, and it seems to be acquiring an IPv6 address, even though I haven't enabled IPv6 in my network and system settings. What's even stranger is that I restarted the system two days ago, and in just two days, the log has grown to 15%, with the log types remaining the same. I'm hoping to get some help with this issue. Oct 3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered blocking state Oct 3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered disabled state Oct 3 09:10:19 MingShun kernel: device veth6197960 entered promiscuous mode Oct 3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered blocking state Oct 3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered forwarding state Oct 3 09:10:19 MingShun kernel: eth0: renamed from veth31aafdc Oct 3 09:10:19 MingShun kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6197960: link becomes ready Oct 3 09:10:20 MingShun kernel: docker0: port 9(vetha79dc8e) entered disabled state Oct 3 09:10:20 MingShun kernel: vethd77f734: renamed from eth0 Oct 3 09:10:20 MingShun avahi-daemon[22691]: Interface vetha79dc8e.IPv6 no longer relevant for mDNS. Oct 3 09:10:20 MingShun avahi-daemon[22691]: Leaving mDNS multicast group on interface vetha79dc8e.IPv6 with address fe80::a0e5:f2ff:fe83:ec46. Oct 3 09:10:20 MingShun kernel: docker0: port 9(vetha79dc8e) entered disabled state Oct 3 09:10:20 MingShun kernel: device vetha79dc8e left promiscuous mode Oct 3 09:10:20 MingShun kernel: docker0: port 9(vetha79dc8e) entered disabled state Oct 3 09:10:20 MingShun avahi-daemon[22691]: Withdrawing address record for fe80::a0e5:f2ff:fe83:ec46 on vetha79dc8e. Oct 3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered blocking state Oct 3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered disabled state Oct 3 09:10:20 MingShun kernel: device veth9dd70b3 entered promiscuous mode Oct 3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered blocking state Oct 3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered forwarding state Oct 3 09:10:20 MingShun kernel: eth0: renamed from vethec901bb Oct 3 09:10:20 MingShun kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9dd70b3: link becomes ready Oct 3 09:10:21 MingShun avahi-daemon[22691]: Joining mDNS multicast group on interface veth6197960.IPv6 with address fe80::ecfb:f2ff:febd:75a8. Oct 3 09:10:21 MingShun avahi-daemon[22691]: New relevant interface veth6197960.IPv6 for mDNS. Oct 3 09:10:21 MingShun avahi-daemon[22691]: Registering new address record for fe80::ecfb:f2ff:febd:75a8 on veth6197960.*. Oct 3 09:10:22 MingShun avahi-daemon[22691]: Joining mDNS multicast group on interface veth9dd70b3.IPv6 with address fe80::2821:fcff:fe0e:2348. mingshun-syslog-20241003-0113.zip

搞定了，感谢！

请问有什么办法把这个共享文件夹里的内容迁移到B硬盘么？并且设置的共享目录啥的设置都不变，我使用上述插件测试了下，提示很多文件夹的目录权限有问题，我没敢继续操作 我目前最好的方式是不是建立新的共享文件夹，设置好后把文件迁移到硬盘B，然后删除原有共享文件夹。

目前有个共享目录，存储在硬盘A中，目前新增加了一个硬盘B，请问如何将共享目录存储到硬盘B上？ 在该共享目录设置下设置了包含的磁盘中，只选择硬盘B，但是确定后没有任何反应，没有设置已排除的磁盘，担心设置这个会出问题。

本来想通过webdav在虚拟群晖备份unraid中Nextcloud的文件，结果提示没权限，就通过Dynamix File Manager把Nextcloud存储的主文件夹设置了other权限可读写，访问Nextcloud首页提示当前权限被其他人访问需要调整回来否则无法访问，就把之前在Dynamix File Manager调整的Other可读写改成了拒绝，最后结果就是Nextcloud首页报错，看了下日志： Dynamix File Manager中只反复设置了几次other的访问权限，其他没设置过： 怀疑是不是设置整个nextcloud的权限时导致权限错乱而无法读取，所以首页就不让访问了。 首页报错如下：

买的是整机，HPE的家庭微服务器gen10 plus； 估计我也没啥能力改造这个主机增加SATA，非常感谢，我可能会想办法再搞一台小机器专门用来备份了。。。

非常感谢！ 我用的是gen10plus，应该没办法把sata直通给群晖，主力系统还是在unraid上； 请教下sata这个中转占用资源很高么？不知道和网卡哪个大，是否把网卡直通后能极大解决该问题，gen10plus有四个网口，不过好像是在一个网卡上，我一直没尝试直通

最近想把重要的文件做个多硬盘备份，说下目前的系统情况： unraid下一块2快12T硬盘（简称硬盘A） unraid下运行了一个群晖，将一块4T硬盘直通给群晖（简称硬盘B），没有做网卡直通 通过duplicati设置了定时任务，在约定时间将硬盘A的部分目录和文件拷贝到硬盘B，这个任务一旦执行，CPU就会满速100%吃满，机器风扇瞬间就是机场飞机起飞了。 请问如何能解决这种问题，目前的拷贝是因为虚拟网卡把CPU吃满了么？网上看了些文章也有说和网卡没关系的，请大佬们指导。

感谢！

NAS之前只有一块硬盘，最近准备增加两块硬盘，手头有两块一直没放进去： 一块新硬盘一直没拆封 一块旧硬盘运行过几千小时 两个硬盘的存储空间是一样的，计划一块做校验盘一块做存储盘，想请教的问题是： 校验盘和存储盘哪个对硬盘的寿命消耗较大？ 计划以此来确定新硬盘还是老硬盘做校验盘比较好。 感谢大家！

我之前想去掉缓存盘，也不知道咋处理比较好，等待高人解答

求助： 机器断电重启后，Nextcloud无法连接MariaDB数据库，查询下面帖子里说可以通过制定老版本来解决该问题，所以就在存储库后面制定了10.5，没想到更新后提示找不到容易，然后容器列表就没有MariaDB了，当时正好打开着日志窗口，就看到不停在报错找不到容器，数据都还在里面，求救如何恢复这个容器啊。

谢谢，只能重启下docker试试了，硬盘已经不在手上

没有的，当时只是插上移动硬盘通过FileBroswer拷贝了些文件就直接拔了，其他没有做操作

请问去哪里确认？ 安装了Unassigned Devices，在历史设备里有显示，有“移除”按钮，是否从这里移除即可？ 谢谢

日志中经常出现如下警告信息： Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953664) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953665) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953666) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953667) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953668) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953669) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953670) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953671) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953672) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): Directory bread(block 953673) failed Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): FAT read failed (blocknr 192423) Nov 20 12:01:08 MS kernel: FAT-fs (sdd1): FAT read failed (blocknr 192423) 但是我没有sdd1这个硬盘，目前硬盘是一个U盘（sda），一个硬盘（sdb），还有一个直通给虚拟机的硬盘（sdc），奇怪这个sdd1的报错信息是什么。 请教各位，非常感谢。