Edgeman56

I have mine downloading and unpacking to cache, my problem was that the unpacker was hung up in that background and used all cpu until the server crashed, and then when it started up it would start all over again. Thanks to the help on here I have the problem resolved. And it is great to have a community that is so knowledgeable and willing to help.

Thank you for all the help, sabnzb is causing the server to lockup. I can now focus on what is wrong. Thanks for you help and time it is much appreciated.

Here is the diagnostic file, the server has been up and running for 30mins or so and is pegged at 100%. So it shouldn't be startup programs. Thanks for the help. server-diagnostics-20220804-1240.zip

I just put the server online so I will let it run for a bit and repost, it has just been pegging the cpu at 100 percent to the point the server shuts down. I will repost the diagnostics after 30 mins or so. Thank you for your input, and your time

Sorry about that here it is. server-diagnostics-20220804-1150.zip

For that past 2 days or so my server is running at 100 percent cpu usage. I updated to the newest version today and I am still having the same problem. I attached the server log and the processes log also. I have tried stopping all apps and it seems to have very little effect. Not sure what the next step should be. Thanks for any help you can provide. server-syslog-20220804-1507.zip processes.txt

I have the fix common problems app running on my Unraid server, and it has warned me that I have call traces? Not sure what that means, but it suggest that I post my diagnostic here and ask for help, so that is what I am doing. So any help or guidance would be greatly appreciated. Thanks. server-diagnostics-20170527-1148.zip

Rebuilt the drive and everything is working, I have it running a parity check. Thanks for the help.

I have it chugging away hopefully in 12 hours or so all will be right again. On the dashboard screen under the parity status in red letters it reads Data is invalid, I guess that must be for the bad drive. Thanks for all the help, hopefully one day I will have a clue and be able to do this on my own. Thanks again. I will report back on the drive rebuild.

Here is another snap of the config that I missed in the first pic.

Here is the the main page shot and the dashboard.

Well that is not good. In that main page it says configuration valid, and on the dashboard under parity status it has data is invalid. So is it worth trying to rebuild or is it just not going to work. And if it is not going to work i just need to uninstall the bad drive and install a new one and do a parity sync to get back to working, then transfer off the old drive from the windows computer. And what caused this big of a failure with just one drive having problems??? Thanks.

The drive finished the extended smart check and found no errors. I have another drive that will be here tomorrow. My parity shows invalid I am assuming that is because the drive error happened during a parity check. So with it showing invalid will I have problems with the rebuild? And is there any way to find out what the cause of the problem was. And is there anything more I need to know to get this rebuilt. Thanks for all the help.

Is there a way to just bring that drive online without a rebuild?? Assuming the extended test comes back fine is there a way to bring the drive back into the drive pool without any risk of data loss?? This is my first drive error so I am worried that I will do somthing stupid and lose data. Thanks.

Ran a parity check and a drive is showing a red x and says device is disabled and being emulated. I grabbed the diagnostic file then shut down the server to make sure all the cables where seated correctly. This is the smart data form the diagnostic file. === START OF INFORMATION SECTION === Vendor: /2:0:1:0 Product: User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes Physical block size: 1549687900 bytes Lowest aligned LBA: 14896 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I shut down the system and rechecked all the cables connections restarted and the smart data from that disc passed, zip attached. I am now running the extended self test. So my question is what should I do? I have read previous post and I believe I should. Stop the array Unassign the disk Start the array. Stop the array Assign the disk Start the array and parity build should start Please let me know if this is what I should do assuming it passes the long test. If this is all wrong please let me know what I should do. Thank you. server-smart-20151015-1220.zip