elnevera

Nothing notable in the Syslog, The last entry in Syslog was 15:32 on the 20th but I know that the server was still active until 03:39 on the 21st as my Scrypted container was still sending video to HomeKit until that point.

Hi all, My server has been having a few unclean shutdowns. As you can see from the above syslog file, things stopped on the 20th and started when I powered it up this morning. I had setup Syslog server to try and capture what was going on but got nothing. Does this point to hardware failure? Thanks

I'll shut it down then, thank you. Luckily I took the Homebridge docker off last year so smart home stuff will still function.

I'll have to wait a week or so to do a memtest. Still not sure if it is safe to leave it running or not. Interestingly, having done nothing to the server, it managed to finish the parity check (with errors) but has been up for 30 hours now. Latest diagnostics attached. Some errors to work through. mystique-diagnostics-20230202-1547.zip

Thanks - Is there anyway to run Memtest without connecting a keyboard mouse and monitor? It's in my loft and I don't have a spare monitor to take up there. If not, I'll just shut it down until I can get it down.

Hi All, I've been finding that my server is shutting down in the early morning. It has happened 4 times in 4 days, each day I get a Discord notification that a parity check is starting. I setup the syslog server function to try and see what is happening before the shutdown but I am having trouble understanding the logs. I would really appreciate some help please. I'm always willing to learn but understanding what is happening is a bit beyond me right now. I have attached the diagnostics and have included a syslog server file within the Logs folder. Cheers, Simon mystique-diagnostics-20230201-1330.zip

I am still getting UDMA CRC Errors on two drives. I will reseat the LSI card this weekend and check the cables to see if that helps.

Thank you very much!

Sorry for the delay. I've done the above. Diagnostics attached.mystique-diagnostics-20220507-1731.zip Thanks

Thanks very much for these instructions! I just upgraded the firmware on my LSI SAS9211-8i and it went very well.

Well, the firmware update went without a hitch, thanks very much @JorgeB Once the array was back up, my 'not connected' disk has appeared in unassigned devices. I'm not sure what to make of that. Can someone please take a look at the attched SMART report and tell me if I should bin the drive or not? ST4000VN008-2DR166_ZGY3DVHM-20220505-2128.txt

Thank you, it was your instructions thread that I was looking at. Very useful! I might as well try the update now I've learnt how to do it.

Is this what I need?

D'oh! I checked my history on here and found the details of the card. Description from the listing; LSI SAS9211-8i 8-Port 6Gb/s SAS/SATA HBA Intergrated RAID PCI-e2 x8 "flashed to IT mode" works with Freenas/XigmaNas/Nas4Free etc LSI is the brand?

Hi all, I've been having some drive problems recently. 1 failed/not connected, 1 with pending sectors. New drives on route to swap in but I've noticed most of my drives in the array (7) have UDMA CRC error counts agains them. My SAS controller (LSISAS2008) is showing in the diagnostics as; May 3 17:44:16 Mystique kernel: mpt2sas_cm0: LSISAS2008: FWVersion(19.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00) May 3 17:44:16 Mystique kernel: mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) May 3 17:44:16 Mystique kernel: scsi host10: Fusion MPT SAS Host Is it worth updating the formware? I haven't touched it since buying it and I can't even remember what brand it is. Is there a way of telling what model it is without taking it out of the system? I know I bought it from eBay but it is long gone from my purchase history. If a firmware update will help, i'd like to make sure I get the correct model. Thanks.

35 hours and no lock up. Still none the wiser as to why a power cut changed anything.

Well..... I was wrong. Memory was set to 3200 in the BIOS. I have set it to default and also changed the power supply idle setting. I have also attached another diagnostic and it hasn't locked up since coming back on. I am still confused as to why after the power cut it became unstable with no changes to the bios...... Also, can anyone recommend a UPS that will allow a clean shut down in the event of another power cut? mystique-diagnostics-20200707-2128.zip

Thanks for replying. I will check the bios whem Memtest has finished but I don't think I have any overclocks (CPU or Memory) in place.

Hi All, My Unraid server (6.8.2) was running just fine when we had a couple of powercuts a few days ago. I had been meaning to look into a UPS but never got around to it.... Anyway, I powered the system back up and let it do the usual parity check. All okay, but since then the server has repeatadly locked up/crashed. I have attached the diagnostics I grabbed between lock ups. What ever the problem is, it appears to be getting worse as the time between lock ups is decreasing. I am currently running memtest. I have tried running without Dockers and it still locked up. Can anyone help me with the next steps should the memtest pass okay? Server is running on Ryzen 5 1600 and 32gb memory. Cheers. mystique-diagnostics-20200707-1835.zip

Thanks Squid. So far so good. I've been able to do more than before. This SSD is 4-5 years old so it might be worth replacing. Can I ask why it makes a difference connecting it via the HBA vs Motherboard? It has been working fine for the last 2-3 months connected to the HBA. Cheers

I've gone in and connected it to the motherboard. Booted back up but the crc count on the ssd has gone from 52 to 75 now.

Another update.... If I reboot the PC I get about 10 minutes of use before FCP alerts me to the fact the cache drive has gone read only. I was trying to rebuild my dockers after deleting and recreating the image but the install failed when the drive flipped to read only (see attached image) This is bizarre

When I try and use unBalance to move the files it has this message; skipping:deletion:(rsync command was flagged):(/mnt/cache/appdata/FileBot/amc-exclude-list.txt) the files never make it to the cache drive

Thanks Squid. I hav tried mover with the docker disabled and with prefer set but Mover runs for a few seconds and is then done. I've no idea how the docker appdata got onto the array but I seem to be in a situation where any writes or deletes that invlove the cache drive are just not working what so ever. I've tried using unBalance to move the files back to the cache drive but that isn't working either....

I've noticed that my appData share was sitting in the array rather than cache. I have set it to use cache only but running mover isn't moving anything.