elnevera

Members
  • Posts

    40
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

elnevera's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. 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.
  2. 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
  3. I'll shut it down then, thank you. Luckily I took the Homebridge docker off last year so smart home stuff will still function.
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. Sorry for the delay. I've done the above. Diagnostics attached.mystique-diagnostics-20220507-1731.zip Thanks
  9. Thanks very much for these instructions! I just upgraded the firmware on my LSI SAS9211-8i and it went very well.
  10. 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
  11. 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.
  12. 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?
  13. 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.