T800

My server has been crashing on me. I put a new PSU in a few months ago and it's been fine a for while and now it's going down a lot. I got it to complete a parity check the other day but now it won't stay on for long. I got it up and running and typed in: tail /var/log/syslog -f > /boot/taillog.txt I've attached a screenshot and a diagnostics zip. The ip address in the screenshot is my phone. Not sure why. Can anyone highlight for me what's happening? Thanks tower2-diagnostics-20190407-2352.zip

Took the server to work and sat it in my office. Ran parity fine and stayed on for over 24 hours. Put it back in the garage now the temp has risen and so far so good.

Could it be because it's in my garage and it's been abnormally cold recently?

My server keeps crashing. It went offline the other day. I didn't have a monitor to check the screen or do anything. I turned it off and back on again. Parity check started. By the next day the server had gone down again. I did the same again, parity check started with an eta of 12-13 hours. I also turned on Fix Common Problem troubleshooting. About 13 hours later it had gone down again. I've now got it sent up with a monitor. I've ran memtest through a couple of passes without an error. I've attached some logs/files. Can anyone see whats going wrong? FCPsyslog_tail.txt tower2-diagnostics-20190202-1138.zip syslog.txt

That did it, thank you!

My array is stopped. How do I resync the parity drive?

I've tried the email settings before but I can never get it past the "Test" phase and get it to work. That being said I will this time.

Both drives are back and have no issues via smart report. Disk1 is back in the array as normal. Parity1 is still saying disabled. Do I need to do a new config? Will that effect the rebuilding of Disk5?

Okay thanks. Will it not matter that it has wrote errors to parity1? Won't Disk5 be rebuilt from parity1?

I checked on my server last night to see how much free space I had and one of the disks was disabled and being emulated (Disk5). The error pointed to a possible cable issue. I shutdown the server, reseated the cables for Disk5 and rebooted. This morning I removed Disk5 from the array, started the array, stopped the array and re-enabled Disk 5 and started up again. The array started and the contents started being reconstructed. I'm at work 2 hours later and I check how it's going. One of my parity drives is now disabled and Disk1 has millions of errors on it. See pic I must have disturbed the other cables when I was sorting Disk5 (idiot). I immediately stopped the sync. I'm guessing I've lost the contents of Disk5? What do I do next? tower-diagnostics-20181210-0909.zip

It doesn't wake at a consistent time, it's all over the place. That's a good point, if I tell it to sleep and drops off the network and then later reappears if it wakes up by itself or I wake it. What else should I be doing?

Is there no command i can type in terminal that tells me what it was? Like for windows: powercfg -lastwake

I've had my server sleeping okay for a while now. Just recently it's started waking up and I don't know what is doing it. How do nail down what is causing it?

Well I think I sussed it. I unplugged my SAS cables (connecting 8 of the 16 drives). Started it up and went to the BIOS. Selected boot device and order without an issue. Booted into unRAID. Shut it down, plugged SAS cables back and it and now it auto boots.

I don't understand why it says I have so many IDE drives.

I'm on the latest version. I never had a problem booting with 16 drives until the PSU debacle. I will try it with the SAS and PCI cards out and see if it makes any difference. I wonder if I accidentally found a workaround in the order I added everything and wiping the settings has spoilt it.

Motherboard turned up. I stripped the server down, replaced the motherboard and refreshed all my cables. When I built this 7 years ago it was my first PC build that used more than one sata port. I used so many more molex adapters than I needed too. It much tidier now. Booted the server, set up the BIOS aaaannndddd the same problem is there! Gutted! I thought maybe it's the USB stick? Put it in my other server and it auto booted fine. I then went looking on why it won't boot via USB, I found all sorts of things to try from:Legacy USB enabledQuick Boot offDisable Secure Boot (couldn't find it)USB 3.0 offEmulation type Forced FDD and Harddisk Different USB ports All of them weren't set. I guess it could have been something I missed when I reset it after the PSU dying. Tried changing them but none of them worked. I've added some images. - As you can see the USB drive shows up when I press F8 and select it to boot. - These are my USB settings - This is my boot priority, it states than any device enclosed in parenthesis is disabled, which the USB drive is. - This is a list of drives available to boot. I could have sworn I've seen the USB drive there over the last week but it's not there now. For some reason it lists many IDE drives that don't exist. I'm close to giving up on this.

I tried a reset just after it happened. I've found a replacement that's coming Friday. Gonna fit that at the weekend and replace all my sata cables

All the settings, in the motherboard are kept after powering off/om except the boot order. Gonna look for another motherboard. There was a direct replacement on ebay yesterday but I just missed it.

The motherboard doesn't lose time when it's unplugged for a few hours. Did the update, went well, still the same issue.

No, I haven't. It has a button cell that I have replaced. I will try what you suggested. Thanks

It seems that the settings in the BIOS just aren't being saved. I'm gonna try updating it as they've been a few since I installed it.

It was Ebay, the seller is called "leetomi"

I think it was most likely the PSU that fried the drives. I do plan on replacing the mobo and cpu soon anyway all being well. EDIT: I didn't realize pwm had responded to this.

Thanks, I hadn't even thought about it as getting 8TB back as stupid as that sounds, just that I'd saved the faulty drives. It's a lot!