Dundee

Thanks for the explanation Trurl!

Last questions, i hope - Replace the SATA cable? Do you mean make sure its in place or change it? - So i need to stop the array, assign the drive as disk2 as previously, and start the array? And the drive will be rebuilt? - Why does the drive need to be rebuilt? The data is all there....

Sorry, smart report fixed in previous post. Array started with the disk unnassigned, this is what i see. Why would the disk have to be completly rebuilt?

Smart Test results (short): Completed without error The disk is now unassigned and when i try to assign it as Disk2 as before, its seems to be detected as a new disk and Unraid wants to rebuild it WDC_WD101EFBX-68B0AN0_VHGGHY6M-20240809-1146.txt

Added diagnostics

One of my disk is in error. I wanted to provide self-test results, but i cant run the test When i click on START for the short or long test, the button changes to STOP for 0.1s and then reverts back to START as it was before, while the button for the other test becomes disabled. unraidnas-diagnostics-20240809-1209.zip

Im trying to setup the tunnel and I have 2 questions. Its partially working: - browser (filebrowser) is working - netdata isnt working, i get the coudflare host error - pihole2 isnt working, i get a "No webpage was found for the web address" error - netdata isnt working, i get the coudflare host error So that's the first question: what's going on? All the addresses in "service" are good. I tried with in an incognito browser to avoid cache problems. My second question is: how can i use the tunnel on both things that have their own ip (ex: filebrowser) and others than use the unraid server ip (192.168.1.50 is the unraid server) Thanks!

Quick update. I discovered that since the beginning of this thread, one my ram stick died. In the first diagnosis i posted here, i had 2x16GB. Now only 1 is detected (yes i swapped them to make sure its not a MB slot problem). Now its been 2 days and everything seems fine. So maybe at the beginning it was a bios / c-state problem, but it might have become a RAM problem. I'll post a final status in a week.

Here's the syslog. Almost nothing there. I started the server on the 20th, then it crashed while i was on vacation. Restarted the server when i came back on the 26th, crashed again during the night. All_2022-8-29-12_30_11.csv

Update: issue is still there, even with newest bios and disabled c-states. I noticed today that even if the server was powered on (power button light, fans, etc), periphericals such as my keyboard werent powered anymore. No power to usb ports. Does this help pinpointing the issue?

It crashed during the night again after being up 2 hours. Almost nothing in the syslog. The TIME_ERROR came after ~30mins, but the server disappeared from the network 90mins later. I had the 3.0 bios version for my asrock motherboard. I saw that i should update, so i did 3 updates (3.0 --> 3.60 --> 5.30 --> 6.60). After a few problems, i now have the latest version. Hopefully it will fix everything All_2022-8-20-6_31_2.csv

I found something about ryzen cpus and c-states. I'll try something and update tomorrow.

Thanks trurl! Yes, i was about to edit my post to add that i had setup syslog on my old synology but you have been faster I attached the diagnostics and also a screenshot of the syslog. unraidnas-diagnostics-20220819-2208.zip

I installed unraid a few days ago and now it always run fine a few hours then it goes unresponsive. Its not accessible on my network and i cant see it on my unifi server. Luckily i have a monitor and keyboard/mouse attached to the server so i was able to check what was going on. I was able type "root" but after i pressed "enter" it stuck there (picture 1) I waited 2 mins, nothing. I tried a few things and i think ctrl-alt-del is what finally triggered something and it went into shutdown. Picture 2. Now ~30 mins later is still stuck at "starting diagnostic collection". Any idea?