Mr.win7

Interesting. I will try it but I found that the seagate disk also has the protection but they works well. Strange.

Yes, all the Toshiba disks are tested with extended smart test and passed.

Hi, I just bought a second-hand Dell T630 with 12 second-hand Toshiba 6TB hard disks, and I use them and 4 seagate 6TB from my previous machine to build the array. I format them and now they are empty. I tried to build the parity twice but each time I found that the parity sync will first run very well with high speed, and several (hundreds or thousands) read error begin to happen on some disks, and finally when position comes to around 50%, millions of read errors occurs on multiple Toshiba hard disks (some don't have that but some have). It makes the activity extreme low, and no write will happen to parity disks. However, I run the extended SMART test and ZRS scrub accross all the Toshiba disks and all of them are healthy. I have several questions. Will the read error leads to wrong result of parity? In other words, is it required to have 0 read errors when build the parity? Could you please help figure out where the issue occurs? Is it related to hard disks, cables or broad? It determines which seller I should find and how many component I need to replace. If both SMART test and ZRS scrub cannot detect the issue, how could I detect such issue during daily use? I mean is it normal to see the read error and I can just ignore that, or it is a strong signal once I found I should immedietely replace the disks? I'm looking forward to your response. Here are the logs and diagnostics.tower-syslog-20250906-1148.zip tower-diagnostics-20250906-1933.zip

Interesting, I unplug it and try with hair dryer, then I kick it twice. After plug and reboot it works, laugh.

Nothing change on hardware. Thank you for your help. I will have a try on unplug and plug it again.

Hello, I'm facing the issue with "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." I have run the server on Unraid 6.12.13 for a long time and I have a Quadro P400 on my Dell R720 server. I keep to use the display card for jellyfin transcode and it works well, until I decide to upgrade the server versionto 6.12.14. I also upgrade the plugin version from 2024.12.08 to 2024.07.10. I can't remember which Nvidia driver I use before but I tried to download the newest driver. After restart, the plugin shows the error as above. I'm not quite familiar with the nvidia driver. How could I investigate the error? The diagnostics file is attached. tower-diagnostics-20241211-2028.zip

Hi @JorgeB and @bonienl, could you please share us the progress or plan about the issue? Though we can manually flush the IPv6 address, I still want the Unraid to flush it automatically.

Thanks for your command! at least I don't need to restart.

Thanks JorgeB and bonienl! I've suffered from the issue for a really long time. The behavior about IPv6 was changed for several times and it become worse each time(sigh

Hi JorgeB, do you have any status can be shared about the progress?

tower-diagnostics-20240229-0911.zip

Would you please have a look on my newest update? The issue still exists.

repro it on 6.12.8. The issue still happens. tower-diagnostics-20240229-0911.zip

Updating. Let me try to repro it tomorrow at my local time.

Our ISP will assign a new ipv6 prefix for the home network periodically, and also do it when the router restart. Every time the prefix changes, From dhcpcd log, Unraid will set the route to right value but won't update its own ip. I have to restart the unraid server as a workaround. Any approach to prevent it? I'm using 6.12.6. I tried both SLAAC and DHCPv6 for my router and none of it works for unraid, while the other systems (Windows and Debian) works well. The diagnostics is attached. tower-diagnostics-20240228-2308.zip

Anybody know about that?

Recently I found that I can access the docker service via ipv6 but the webgui and smb can't. We found for docker, it listens the port like: tcp6 0 0 :::30000 :::* LISTEN 20925/docker-proxy But for webgui, it behaves like: tcp6 0 0 1234:5678:90ab:cdef:8888 :::* LISTEN 5198/nginx: master But my network environment is dynamic and the ipv6 address has changed after server started for a while. How could I set the smbd and nginx to listen all the ipv6 addresses like docker?

From 8.22 to now the problem didn't happen again. Seems 12.4 fix the problem. Thank you for your work!

Sure, will updating and have a try.

Thank you @ljm42 But IPv6 is important for me. I've run the fix common problems plugin and it didn't show any useful suggestion about this. Here is my syslog. I think the problem is related to the nginx. Could you please have a look about it? Also, I'm anxiously to wait the new release (maybe 12.4? laugh) to fix it. Do you know any estimate ETA for it? syslog

Have tried some times and after the ipv6 address disappeared, I can never get the diagnostics. Even cannot see the output "Starting diagnostics collection". Maybe some command is stucked and may related to the ipv6 addresss disappear. Here I collect the diagnostics before ipv6 get broken. @ljm42 Could you please also have a look? tower-diagnostics-20230725-1026.zip

Thanks! @ljm42 Would you please have a look?

Sure I'm trying to execute the diagnostics command but seems it didn't work for me. I will keep trying. I'm on a business trip so these two days I cannot access my unraid server(so sad, I accessed it before by unraid's wireguard based on ipv6 endpoint). I will upload my syslog this weekend. Maybe @sbihero bro you can also provide your syslog and diagnostics.zip, right?

When I restart the server, the IPv6 address can be collected by ifconfig command, and webgui works both for IPv4 and IPv6. After some time(short as 1 hour or long as 1 day), IPv6 address can not be collected by ifconfig, and webgui get broken. Restart just repeat the progress above. So I think I have the same problem(situation 2) as yours. When I'm using 11.x, I have never seen this before. The IPv6 works perfectly. I think roll back will work for it.

I upgrade the Unraid from 11.5 to 12.2, then to 12.3. Both of them run normally at first, and then I cannot access the webgui both ipv4 and ipv6. And web page from docker service can be accessed from ipv4 only. ssh is worked from ipv4. I read the nginx log and syslog. Nginx log shows that cannot bind to [::1], so nginx won't start. From syslog I cannot find more info about the reason why ipv6 disappear but we can see after a time, many service cannot get the ipv6 interface, like ntpd. In my home network, I configure the gateway with SLAAC. other devices work perfectly. I cannot get diagnostic from command line since it will stuck for a long time and nothing happens. Restart cannot solve the problem.