ezzys

Hi - just experienced another crash. Again could not connect to webui / any services, nor could I ssh in or use the console resulting in me having to force power off. All i noticed was that the fans on the server appeared to have spun up very high when it had crashed. I had a remote syslog running and have attached log. Also attached diagnostics from when rebooted after most recent crash and diagnostics from yesterday when it appeared to be runing fine. Recomended next steps for troubleshooting appreciated. 192.168.1.150.log unraid1-diagnostics-20260518-2109.zip unraid1-diagnostics-20260517-1103.zip

Hi, After bit of help on what to do next. My unraid system keeps crashing / locking up periodically. By crash I mean the web ui becomes unresponsive and I cannot connect to any services running. I can still ping the machine, but nothing appears to be working / responsive. I tried logging in via the console and it timed out. When I pressed the shutdown buttong it said sending terminal signal, but nothing happened. So have to force shutdown. I have updated to latest unraid version to see if it resolves and problem still occuring. I have attached my diagnostics. Welcome thoughts on what to do next. unraid1-diagnostics-20260514-2059.zip

Hi I had a drive failure during a rebuild which has meant my parity is now out of sync and I am missing 1 drive (so unraid cannot rebuild) It has resulted in me loosing the content of 1 drive (not the end of the world just means effort of restoring my important files from backups) How do I go about creating a new array and creating a new parity, but keeping the data I already have on my other HHD's? I also have another drive (to replace the failed one to add back in) Thanks

I am also experiencing the same issue. Has anyone had any luck resolving? But looks like it is a reported bug, https://github.com/jlesage/docker-crashplan-pro/issues/483

Thanks - is the recomendation then a manual update from 6.11.5 to 6.12.14? Do I still need to remove the community apps before as this appears to be the only plugin that is an issue?

Hi I am keen to upgrade from 6.11.5 to 7.0.0 with the hope that it resolves a issue I was having with 6.12.X saying "ERROR* Unexpected DP dual mode adaptor ID 01 (or 03)". In short, reading other forum the error I was experiencing seemed to be Linux Kernal issue and support for the CPU/iGPU, so did not upgrade to 6.12.X. I want to try 7.0.0 to see if this fixes the issues I was having, however I am currently stuck on an old version of communities applications and when I run the update assistant this flags as an issue saying But becuase I am on 6.11.5, I cannot do this as the latest version is not compatable. What should I do? Not upgrade, roceed with the update or remove the existing plugin? If I remove it, how do I get it back?p Thanks!

Did you ever solve this? I am getting same error with upgrade to 6.12.2?

I just upgraded to 6.12.2 and kept getting the following error message "*ERROR* Unexpected DP dual mode adaptor ID 01 (or 03)" to the extent my logs were filling up with the error. I did a google search and the other posts with the error all had AS Rock motherboards, so not sure whether it is related. I have ASRock B360M-HDV. I have now reverted back to 6.11.5. Does anyone have any idea what might be causing this? Diagnostics attached. unraid1-diagnostics-20230707-2359.zip

Thanks changed cabels and appears to be going okay - will monitor and change if I get anymore errors.

An old 2TB drive started showing errors and they have reacurred again after a reboot at the weekend. I have run an extended smart test and is passed (attached). What does this mean? Is the drive okay or should it be replaced. I have bought another 2TB drive as it was cheap so can replace, but want to know whether the drive is knackered or it could be pre-cleared and used again? unraid1-smart-20230510-1854.zip

Thanks that sorted it

I have just installed qbitorrentvpn, however I cannot seem to get the WEBUI to work. I am using PIA VPN. The logs suggest it is all working. The final message in the log afer a restart is: 2023-03-11 17:08:47,265 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8082 I did change the ports as I had a clash, but made sure I was consistant with what I changed. Host Port 1 Containter Port: 6881 = 6881 Host Port 2 Containter Port: 6881 = 6881 Host Port 3 Container Port: 8080 = 8082 Host Port 4 Container Port: 8118 = 8128 Container Variable: WEBUI+PORT = 8082 After leaving it run for a while I just see the following in the log 2023-03-12 19:38:49,166 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '54605' Any suggestions on what to adjust, any log information that will help troubleshoot?

Thanks - going to do that now.

Okay thanks - my approach was to use disk 1 that was disabled for the rebuild. Given it is not showing any errors does that sound okay? Also how to I do that - the disabled disk is not showing as an unassigned device nor when the array is started does it let me select that disk? I assume becuase it is mounted. Do I need to disconnect the disabled drive and reboot and then readd the drive in on a second reboot?

Thanks both, I ran "check file system" on disabled disk 1 - see below: It looks okay? Should I simply create a new array configuration and and rebuild parity?