xyzeratul

My old NAS motherboard is dying right now, so I decide to upgrade to a new machine, since this will change nearly all the things in my NAS: motherboard, CPU, RAM and even the PSU, only thing I keep is the SSD, HDD and HBA card. I am a little worried about this major upgrade, I read the documents, it said I should be fine as long as it's the same USB stick, and the appdata and system folder backup, So anything else I should do?

only able to fix this via a reboot, I'd what's the cause of this, a bug or something not working in my browser?

My unraid main page disk info is missing, checking log it shows this error over and over Mar 18 21:52:12 185409 nginx: 2025/03/18 21:52:12 [error] 3836611#3836611: nchan: Out of shared memory while allocating message of size 15145. Increase nchan_max_reserved_memory. Mar 18 21:52:12 185409 nginx: 2025/03/18 21:52:12 [error] 3836611#3836611: *2369758 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Mar 18 21:52:12 185409 nginx: 2025/03/18 21:52:12 [error] 3836611#3836611: MEMSTORE:01: can't create shared message for channel /disks I am on unraid 7.0.1 right now, this never happen in previous version diagnostics-20250318-2149.zip

以前用过你这种方案，后来我是直接在翻墙软件里面自定义规则，因为有些docker容器也需要翻墙，还是这样最灵活

I am using 127.0.0.1/mnt/.... as icon path, no problem so far, I will test for a few more days to see how it goes. update---------------after using this as the icon path, no more this bug. http://127.0.0.1/mnt/user/

I am not using any theme, but I do use CA auto update plugin to handle docker and plugin.

I have set the most of the dockers on my unraid using the custom icons path locally, something like: /mnt/user/isos/icons/ANI-RSS.png But I notice every time the dockers upgrade, they lose their the custom icons, the icon files also got deleted, I try to set the icon folder owner root and read-only, still the same, is there a way to prevent this ?

updated from 6.12.14, removed my RTL8125B driver plugin 1st, so far all things work, will run a few days to see if I need that driver or counter any problem.

holy, 7.0 is out? Still I better hold on to see how the RTL8125B goes in this new version, every since 6.12, each update gives me so many headche with this NIC

in my windows 10 it look like this, I also feel this is something related to windows explorer

sorry, I was checking the windows side, forgot to pull it. 185409-diagnostics-20250104-2210.zip

Recently I need to store and pull alot of video files(.mp4) between my laptop and unraid server, these files store at my cache SSD, it's a exclusive share, I noticed slow than usually smb transfer speed, my home network is all 2.5G, that means both NIC, switch and router are all in 2.5G mode. Other big files such as zip, rar and 3dm are totally fine, max out at 249mb/s but when it's a video .mp4 file from my DJI camera or a simiply a moive, it usually at 50 to 100mb/s, I rarely did this before so maybe this problem exist on previous version, this only happen on smb transfer, downloading or uploading the video file tho unraid webui can also reach nearly the max speed, so I guess there should be some settings I need change in windows maybe?

Running to a strange issue while upgrading: I had RTL8125B plugin installed in my unraid, so before upgrade I uninstalled it, then upgrade to 6.12.14. Slow smb speed in stock driver(60% less), so I install the plugin again, rebooted. Unraid shows my nic was at 100m mode, uninstalled the plugin again and reboot, network back to 2500m, but still slow smb speed. Checking /config/plugins-error found out there is a RTL8125 plugin in there, deleted it and reinstall the plugin, smb speed back to normal 249mb/s Don't know where did it go wrong, but I somehow fix it?

假设你的emby的appdata目录在SSD上面，那把Library---Advanced里面的Metadata path设置为/config/metadata就行了，如果appdata目录不在SSD，那你可以在docker容器里面映射一个新路径，然后把Metadata path设置成这个新路径。 但这样做意义不大，因为emby是在你打开媒体库的时候，周期性的重新读取硬盘上面的实际媒体文件，检查是否更新元数据之类的，所以的确读盘很频繁

你说应该是用户自建docker时候留下的模板吧，在/boot/config/plugins/dockerMan/templates-user里面，保留这个就行了 升级7.0还是要小心，毕竟是大版本号而且现在还是beta

本来准备组第二套NAS尝试7.0 BETA的（没胆子在主力NAS上面用），不过现在暂时还没时间弄。 想问下7.0里面的几个新功能目前是怎么回事： 新的官方版的Proxy manager目前能使用什么类型的代理，能选择什么代理模式呢？比如中国用户访问github和dockerhub安装插件和App能正常使用吗？ 磁盘阵列现在说是比较灵活了，可以指定任何储存池为主储存池了？ 其他还有什么你们觉得很方便或者好用的新功能?

I plan to build a new NAS for my company assigned apartment, where I usually stay 4 or 6 months a year My plan is a small form factor NAS to run EMBY and other media stream services, with no important file storage. CASE: still undecided, but plan for a 2-bay case with 1U PSU support, any suggestions? MB: I plan to go with N100 or i3 1215U RAM: 16G should be enough HDD: 2*8T WD drives left over from my main NAS NVME: a leftover 512GB RD20.

Yea, it's one of SAS drive my friend give me, since my board and case support SAS, I have been using these SAS drive for a bit over a year now. So should I keep using it, or it's time looking for a replacement? PS: shutdown and clean some dust today, restart and unraid told me the disk turns good?

Thanks, attached below, also the disk3 smart test 185409-diagnostics-20240729-1829.zip 185409-smart-20240729-1829.zip

Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450152 Jul 27 01:31:26 185409 kernel: I/O error, dev sdb, sector 4121449968 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121449904 Jul 27 01:31:26 185409 kernel: I/O error, dev sdb, sector 4121450304 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450240 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450248 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450256 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450264 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450272 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450280 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450288 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450296 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450304 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450312 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450320 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450328 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450336 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450344 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450352 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450360 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450368 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450376 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450384 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450392 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450400 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450408 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450416 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450424 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450432 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450440 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450448 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450456 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450464 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450472 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450480 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450488 Jul 27 01:31:26 185409 kernel: I/O error, dev sdb, sector 4121207624 op 0x0:(READ) flags 0x0 phys_seg 21 prio class 2 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207560 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207568 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207576 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207584 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207592 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207600 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207608 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207616 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207624 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207632 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207640 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207648 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207656 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207664 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207672 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207680 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207688 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207696 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207704 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207712 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207720 Watching tv shows on my emby one night, the video stuck and the app crushed, I opened the emby again didn't think much. The next day I found these errors in log run a smart extend test came back with nothing wrong, should I be worried?

自己找合适自己的系统和机器才是正道，别去信网上什么“无脑抄作业”，那些教程其实更会让你走弯路。 我用NAS也是白裙（公司的）---黑裙---OMV---TrueNas---Esxi----Unraid一路过来的，只能说Unraid目前是最适合我的操作系统，每个系统我都自己衡量是不是满足自己需求，而且我把自己的需求也分成几个等级 NAS系统最基本的磁盘管理，Unraid最适合我，因为硬盘增减灵活 应用管理，Unraid的docker管理比较直观，缺点是官方不支持compose 虚拟机管理，Unraid还算比较直观简单 中间我也踩了不少坑，有几个问题到现在都没完全解决，但自己尝试肯定能让你自己最后明白是怎么回事。 下一步我准备尝试PVE，因为感觉PVE也能实现我大部分需求。

80或者443端口被封或者占用了？

Yes, I also deleted any orphan images.

I have a problem with this plugin, don't know if it's a bug or a feature, in the docker update page, it shows some docker app I already uninstalled long ago.

难道是用的那些工程样品U？