nomisco

Unfortunately the server crashed again in the night, just after 3AM. I've attached the log from the flash which shows just over an hour and twenty minutes of errors. The midnight spin up will be for the Plex library scan, then the disks go to sleep until an hour and ten minutes later when I get this massive block of errors until the box dies. I can't see what is causing the error, but it may be more obvious to someone here. Hopefully. Or perhaps someone can suggest a more verbose logging effort if they have a suspect in mind. Thanks syslog.txt

Thank you Jorge. I only use that driver for Plex transcoding but can do without. I remember adding some lines to a config file or two; but can't remember how I'd remove them. I suppose a reboot of the server would be required after they're removed? Update: I removed some lines from the 'Go' file: #enable module for iGPU and perms for the render device modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri And also the relevant lines from the Plex container. I'll give this a try, and report back either way, but it may be a week! Any other suggestions in the meantime would be welcome.

Looking for some pointers as to what may be causing my server to crash. At the moment, from memory, it will run for between a day and 7 to 10 days before crashing. It's a headless machine, so as it's sat behind my TV, I've connected it to the HDMI port and added a keyboard to see if anything happens onscreen when it crashes. It just sits at the login prompt (untouched since boot), but that is also unresponsive to the keyboard. There are plugins on the machine which may not have been on there when it was stable, but the nature of the crashing means it difficult to rule some out by removing them as I don't know which ones it could be - if any. I'm a total Linux noob, so I set the log to be mirrored to the flash drive. Looking at the syslog file in the logs directory does not show any event when it crashes (I've taken the flash drive to my Windows PC to look at the file). Attached are the system diagnostics, plus the syslog file just after it crashed which I may have inadvertently deleted from the flash before rebooting the server. Just to add that I've switched between the stable and RC release with the same outcome. unraid-diagnostics-20211222-0932.zip syslog

Managed to get the cable changed the weekend, and so far so good. The fact that the errors started to appear fairly quickly after starting the array leads me to think that it's fixed 👍

Me too. A message from 'Clara' who joined two hours ago. Can't see a button to block the user, or report them.

Use code LIFETIMEOFCOMFORT Works for my UK account £94.99 - 25% = £71.24 May work for other regions?

Thank you. I shall swap it over and try to remember to report back in a couple of days just to confirm cause.

log.txt

As per the title. I notice that there are a couple of entries in the log file which indicate the same sector (CRC failure) - so I could logically guess that it might be the disk failing, or, that as the interface has auto-slowed to 1.5 Gbps fro 6.0 Gbps without any errors past that point in time, so there's an interface / cabling issue. Of course it's possible that unraid has downgraded the interface speed and coincidentally there are no reads to the failing sectors after. Grateful for any pointers.

Don't you just click in the box and it allows you to browse?