extrakaese

Okay, thanks! I'll test the nVME in my second server tonight, so it won't be such a big deal if there are any problems. If it's not the nVME, what do you think could be causing the problem yesterday? Maybe a problem with the motherboard?

Thanks for the quick reply! So you think the nVME might not be broken after all and that it's something else? Should I reinstall the old nVME and also add the commands you wrote in this config and test it? (The server has been running stable with this nVME for 2 ½ years without any errors. Can they just suddenly occur without any changes to the server?) Thank you!

Hi, I'm having a problem with my server. When I tried to move data in a pool earlier, Windows suddenly told me that I didn't have the necessary permissions. I checked Unraid and saw that one of my two 2 TB nVME drives from my RAID1 pool was showing as missing. I saved the logs, restarted the server, and checked again. It was still missing. I then removed the nVME from the server and installed it in my PC as a test. It was recognized there and all S.M.A.R.T. values were reported as OK. I have now installed a new 2 TB nVME in the server and restored the RAID1. There are no errors in the logs, the rebuild of the nearly 800 GB ran without errors, and all Docker etc. are running again. But now I'm a little worried that maybe it's not the nVME that's defective, but something else? Unfortunately, I don't know much about this, but here are my logs. (I also saved them on the nVME so that I still have access to them in case of crashes, which is why there are some errors with “syslog-127.0.0.1.log” at the bottom of the logs. Can anyone help me and tell me whether it was definitely the nVME or whether something else might be defective? Many thanks in advance. unraid-syslog-20251211-1705.zip

Hi, I have a small problem. My server runs on 7.0.1, I haven't had any problems so far and everything went well (I updated from 7.0.0 to 7.0.1 15 days ago), but yesterday I noticed that several hard disks start at the same time and something is read from them again and again. That's why I installed the “FileActivity” plugin, but nothing is displayed there either. I haven't installed anything new in the last few days that could cause this, I think. I'm a bit at a loss as to what the problem could be and what I can do? Because it's really annoying when lots of hard disks come on at random and then go out again after a while. If it's relevant, I have a DELL H310 installed in IT mode, but only a few hard disks are connected to it, the rest are on the mainboard itself. Maybe someone can help me? Many thanks in advance! unraid-diagnostics-20250313-1838.zip

Interessant, bei meinem Build mit gleichem Board + CPU dasselbe, auch keine tiefen C-States. (i5 12400 ASRock Z690 Pro RS 2x 16GB G.Skill RipJaws V 3200MHz be quiet 550W Pure Power 12 M) Was bei mir aber noch der Fall war, dass es nicht stabil lief, sobald ich ASPM + C-States aktiviert habe, alle paar Tage (maximal 4 Tage) hat sich der Server selbstständig aus- & wieder eingeschaltet. Logs haben nichts angezeigt, als hätte man einfach den Stecker raus- & wieder reingemacht. Seitdem ich im BIOS ASPM + C-States wieder deaktiviert habe, läuft er seit Wochen problemlos. Hast du eine ähnliche Problematik erlebt? Oder lag es an mir?

Ahhh, now I understand. Did not know that there are also SATA splitters. Then I'm on the safe side with the Molex-SATA. Thanks for the explanation

Sorry, don't quite understand what you mean by that? I don't understand that much about these things so far. Am still relatively new to these things. 😕

Ok, thanks. Apparently it is not so easy to find "crimped" 2-1 in Germany, so now I ordered the 4-1 and will install it tomorrow and connect to only 2 hard drives. Is there anything else I need to consider? The harddisk is connected to a HBA controller, so I'll use one of the other SATA connectors, if that's the problem. So it probably can not be something else, just power/connection? If there are errors again, I'll post it here again. Thanks for your help

Ok, thanks, then I look that I find one with two. Alternatively, I would take the one with 4, but only plug in 2, should then have the same effect, right?

Ok, I have a Molex/SATA adapter there, but one of those that are separate and not tight together. And the errors came last time and this time, right when the hard drive started from the spindown. Is it safe to use such a cable? Because of "Molex to SATA, lose all your data". Thanks for the quick reply.

Restored the data and everything ran smoothly for 2 days, now 32 errors again, last time it was 128. This time I have saved the diagnostics. I hadn't replaced the cable yet because I don't have a replacement. Maybe @JorgeB can help me again? If it's really just the cable, I'll order a new one later to install it tomorrow. Thanks in advance unraid-diagnostics-20230904-1522.zip

Okay, then I'll do it that way. Thanks for your quick reply!

Have the server unfortunately already restarted and only afterwards read that i can only save them before. Just did a SMART test on the hard drive and I was recommended by a friend to restore the data, so data rebuild because everything else is ok only the hard drive was disabled, should I do that?

Hi, suddenly I had read errors on two hard drives. One was disabled, the other was not. Both SMART values are ok, both hard drives are on the same power cable. After I stopped the array and restarted, the errors on both hard drives were gone, but one hard drive remains disabled and as emulated. I don't know much about this and am afraid I am doing something wrong. I have two parity hard drives. Is there anyone out there that can help me? I also have the logs since this morning. Thank you very much in advance. syslog.txt

Okay, I'll put the HBA card in another slot first and test it after my vacation to see if it also crashes in safe mode. Currently have the card in one of the lower PCIe from the AsRock Z690 Pro RS. Should I put it in the top slot where I would normally put a graphics card? Right now Plex and pihole are the only Dockers running, no VMs.