Nashlake

Hi, Fix common problems is saying: "/var/log is getting full (currently 100 % used)" Can someone explain what that is and how to fix it beyond just constantly restarting my server? Thanks olympus-diagnostics-20250712-1711.zip

Hey, I've been having intermittent errors with the drives in my server disconnecting or developing write errors that are always solved with several on/off cycles and unplugging and plugging in the SATA power cable. The most recent time started with my parity drive disappearing than when I tried to fix that everything vanished. I then disconnected everything and firmly plugged the cables back in and everything was perfectly fine. It managed to do the Parity rebuild overnight with no write errors or any other issues I'm wondering if anyone else has had issues with the SATA power connectors slowly working themselves out and has a solution. I'm currently thinking about trying to wrap rubber bands around the drive to hold the connectors in. My case is the Fractal R5.

I removed that problem disk and added the new drive to the array. When it started the rebuild it was moving extremely slow and sounded like something was grinding in a pulse pattern. None of my data is critical, would it be better to wipe and start new. I have attached a new diagnostic file. olympus-diagnostics-20220305-1630.zip

Thanks, I have a drive ready to go in the array, but I did an extended Smart test last week and it came back as healthy. I'll try to post that after work but if it is dying I guess I will try to rma it.

I can now add it back to the array but there is a little blue square next to the Device Name that says when hovered over "New Device."

I did a couple of cable swaps and this is my current diagnostics. olympus-diagnostics-20220305-0540.zip

Hi, I did an upgrade to my server adding another 4 Tb drive and an SSD cache and in the process had to unplug all SATA cables and they didn't go to the same ports or drives. The server boots but there is a drive that has been giving me errors first showed as unmountable: not mounted. I then tried to repair the file system following the XFS repair guide. I didn't mind losing the data because it wasn't my parity drive. After attempting repair the drive now shows up in Unassigned Devices. The drive in question is Dev 3 (ST4000VN008_ZDHA5SV9. I've attached a screenshot of what it shows now and my diagnostics log. Do I run preclear to empty it than reformat it or am I screwed? Thanks, and let me know if you need any more info! olympus-diagnostics-20220304-2001.zip

Thanks for the quick reply, I unplugged the sata data and power cables and really shoved them back in and that worked. I must have done that 10 times yesterday with different ports but just never shoved the power cable into the drive enough! I was able to assign the drive and format it so I think it's working now. Is there a way to mark this thread as answered/ solved?

Hello, I'm trying to set up a new server with some old hardware and I'm having some issues. I picked up a new 4 tb Ironwolf drive for my NAS and while I can see it after starting the server, if I try to select it to add to an array the screen blanks? than refreshes and the drive is no longer in the drop down menu and there are no start array or format options. I can always see it in the Unassigned Devices section but I can't find a good link to install Unassigned Devices Plus to format it there. Please let me know if there is a bios setting or something that is messing with it, this hardware is from my old gaming rig so something might be messing with the server stuff. Thanks! tower-diagnostics-20210917-2029.zip