Phych

Members
  • Posts

    12
  • Joined

  • Last visited

Phych's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Sounds reasonable. Normally I pre-clear all my drives before using them. I just picked up the spare drive yesterday so I haven't had a chance of doing that that. Do you see any value of that or just put in the new drive assume if it has not errors after the rebuild it is probably fine? Note: I have 4 data disks and 2 parity. Edit: Made wording less ambigous
  2. I guess I worded my original post poorly. I was wondering if there is anything in the logs I should look for to indicate that there may be a problem with the drive. The drive is still under warranty and I have a spare drive ready to go in. So if there is even a hint that it was a drive issue I want to RMA it while I still can.
  3. The server is in a Supermicro server with hotswap bays. All the drives use a single backplane and the backplane is connected to the Mobo with a single SAS cable. After I removed and reinserted the drive it now shows up to the Unraid OS. My understanding is that right now the red X is because Unraid no longer "trusts" the drive and is not using it.
  4. This morning one of my disks went missing from the array. The best I could tell drive didn't show up to the OS. I took the array offline and re-seated the drive. I could feel the the drive was spinning when I did this so it was at least getting power. After putting the drive back into the system it shows up but now with a red X on the drive. Other posts indicated I should ha ve someone smarter than me take a look at the logs for indications the drive may be bad. I have included the diagnostic dump from before and after I re-seated the drive. unraid-green-diagnostics-20200705-1048.zip unraid-green-diagnostics-20200705-1029.zip
  5. I got my overheating issue figured out and the system locked up again. I am wondering if my problem is related to this persons as I have the same motherboard (GIGABYTE - GA-7PESH2). unraid-green-diagnostics-20191011-0733.zip syslog-1570244850
  6. Turns out my motherboards PWM fan control is dumb. It was running all fans so low that the CPU fans didn't even spin up. Turns out a pair of E5-2650V2 being passively cooled in a case with real bad air flow probably causes instability. Thanks to this post I discovered the fun little fan dance I need to do to get the fans to run at full speed.
  7. Thanks again. Things I have done with my GA-7PESH2 board: 1) Flashed BMC from 1.43 --> 2.43 2) Disabled C states "C State limit == C0" 3) Re-seated 2 RAM sticks that gave errors 4) Re-seated SAS connectors.
  8. I have been have instability with my setup lately and I am not sure how to read the logs. I attached the diag zip collected after the forced restart and the syslog from when it locked up. Squid has already helped me identify a memory problem. I am hoping to verify if this looks like a symptom of the memory problem or 2nd problem. For context I clicked Docker "Update All" button. Everything was going well until tried to stop the Plex docker. I think a parity check was also running at the time. unraid-green-diagnostics-20191002-0236.zip syslog-1569472343
  9. Thanks. I have ECC memory and my understanding is that those where recoverable errors. Any thoughts on how worried I should be. For some background I just ran memtest86+ for about 50 hours earlier this week and it didn't return any errors.
  10. So I got an error from Fix Common Problems that boils down to, "Something is wrong, you should look into that. Maybe the forum will help you." So I was hoping someone might know what I should be looking for.unraid-green-diagnostics-20190929-1957.zip