ssh

Members
  • Posts

    32
  • Joined

  • Last visited

Recent Profile Visitors

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

ssh's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I have basically been getting the following error log message in my syslog for I can't remember how long. Just wondering if there is anything I can (or should) do about it? The error always occurs during the scheduled maintenance I've configured for Plex (4AM-8AM daily). Jun 17 04:38:25 Shadow kernel: Plex Media Scan[4616]: segfault at 0 ip 00001494512fc4fd sp 00007ffd50e675f0 error 4 in libavcodec.so.58[1494512ca000+292000] Jun 17 04:38:25 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 18 05:57:44 Shadow kernel: Plex Media Scan[29552]: segfault at 0 ip 0000145664ffd4fd sp 00007ffc26983900 error 4 in libavcodec.so.58[145664fcb000+292000] Jun 18 05:57:44 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 19 04:08:04 Shadow kernel: Plex Media Scan[28061]: segfault at 0 ip 0000153f40b7b4fd sp 00007fff647c3320 error 4 in libavcodec.so.58[153f40b49000+292000] Jun 19 04:08:04 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 20 04:08:08 Shadow kernel: Plex Media Scan[20383]: segfault at 0 ip 0000152cd7f444fd sp 00007ffc886db4b0 error 4 in libavcodec.so.58[152cd7f12000+292000] Jun 20 04:08:08 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 21 04:11:38 Shadow kernel: Plex Media Scan[17870]: segfault at 0 ip 0000148fc03224fd sp 00007fff2f9837c0 error 4 in libavcodec.so.58[148fc02f0000+292000] Jun 21 04:11:38 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 22 04:08:02 Shadow kernel: Plex Media Scan[3855]: segfault at 0 ip 0000148c070174fd sp 00007ffca8d24060 error 4 in libavcodec.so.58[148c06fe5000+292000] Jun 22 04:08:02 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 23 04:12:40 Shadow kernel: Plex Media Scan[21991]: segfault at 0 ip 00001537100214fd sp 00007ffc70a78cf0 error 4 in libavcodec.so.58[15370ffef000+292000] Jun 23 04:12:40 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 24 04:15:51 Shadow kernel: Plex Media Scan[22382]: segfault at 0 ip 000014dbd254b4fd sp 00007fff70a65340 error 4 in libavcodec.so.58[14dbd2519000+292000] Jun 24 04:15:51 Shadow kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f
  2. I have my parity check scheduled to run on the last day of each month at 0:00. This always ran fine (for multiple years), except for today when it suddenly did not. It didn't start at 0:00. I've waited till 01:05, but it never started. Looking at the root file in /etc/cron.d it shows that "the last day of the month" is calculated as follows: [[ $(date +%e -d +1day) -eq 1 ]]. I suspect this to be an issue with the fact that today is the day when daylight saving time ends, as 31st 0:00 + 1 day will probably result in 31st 23:00, getting just the day value of that is 31 which is not equal to 1, so the cron job results in false and won't run.
  3. Thanks for your reply JorgeB. I already ran a short and an extended SMART test which did not find any errors.
  4. My server runs a parity check every last day of the month, which in this case ran yesterday. About an hour before it finished I received an email from my server about a disk (disk sdi, my parity disk) with read errors. The unraid GUI is showing the disk has 383 read errors. The parity check did however complete without any errors. The SMART info of this disk did not show any errors. To make sure the disk was fine I ran both types of SMART self-tests. SMART short self-test finished in under 2 minutes, without any errors. SMART extended self-test finished in about about 17-18 hours,(similar to the time it takes to do a parity check) ,without any errors. Can I still trust this harddrive? Could these read errors have been caused by something else other than the drive, for example the cable or the SATA controller? Some things that might be relevant: This drive is 2 years and 5 months old. It has been in the server 24/7 since and only powered off a few times (hdd sleep is disabled). This drive is connected to 1 of my 6 SATA ports on my motherboard. It has always been connected to the motherboard directly, but I've recently (2 weeks ago) replaced it's no-brand SATA cable with an 18" CablesMatters one. I've had 2 system crashes 3 weeks ago because of 1 bad ram stick. I've replaced all RAM sticks since which all passed 7 passes of mem86+. All 383 errors happened within a few minutes/seconds from each other and have been logged as "disk0 read error" in the syslog (attached). Diagnostics are attached. shadow-diagnostics-20210701-1750.zip
  5. Turns out one of my modules is bad. Tested them separately, module A seems to be fine: no errors after 5 hours (3 passes), module B started spitting out errors during the 2nd pass (or after 1 hour). This was repeatable on another system with another motherboard and cpu, so it's definitely the module itself. I've replaced both sticks with 1x 8GB stick that I had laying around and completed 8 passes on that without any errors. I've started up the server again and did another parity check (luckily still 0 sync errors, so it seems that the memory was faulty, but not faulty enough to cause any data loss on the array yet). Hopefully replacing the bad RAM fixed the issue I've requested an RMA on the faulty memory kit.
  6. Not sure if this error could be related to RAM, but I decided to do a RAM test anyways. At around 36% of the first pass, errors started appearing. So I am starting to suspect my memory modules / motherboard / cpu now (or can it only be the memory itself with these kind of errors?). I am using 2 sticks of 16 GB DDR4-2400 memory (CMK32GX4M2A2400C16) in dual-channel mode with XMP disabled, using the "Auto" frequency setting in the BIOS. So what I am doing now is testing each stick individually to see if the errors remain (will post results here).
  7. Today I had this problem again. Attached the syslog again via manual copy, as it was not possible to download diagnostics when the server was in this state. I have recorded a video of what I saw on screen, not sure if its helpful: syslog.txt
  8. Parity check finished with 0 errors found/corrected. No weird behaviour since the reboot. Still no clue what happened though.
  9. Hi everyone, Today I noticed that my server had become unresponsive. I was able to login and see that the disk activity was 0, 1% CPU usage and 11% ram usage - temps were all in check (disks under 40, CPU under 45). The syslog (which I could still open) showed a lot of red error logs. But I was not able to download the diagnostics anymore - the system had become too unresponsive. I did managed to connect via SSH. The top command showed nothing to be concerned about, but the top command crashed after 5 seconds with a "Segmentation fault" error. (see screenshot attached) That's when I decided to reboot the server entirely with the Unraid "powerdown -r" command, which again resulted in a Segmentation fault error. Trying again did show the "going down" message, but after waiting another 10 minutes it still didn't power down. Even the terminal when connecting to the server directly with keyboard and display, was unresponsive. I could still type but the commands didn't actually do anything. I eventually restarted the server by holding down the power button and then starting the server again. The boot up process proceeded as it normally would, except that it started a parity check immediately, but I think that is expected when the server experienced an unclean shutdown. == Does anyone have any suggestions as to what could have caused this? Or any recommendations in terms of next steps? I was thinking of maybe doing a memory test - but this memory kit has been running fine 24/7 since I bought it (4 months ago) and is running stock (non-xmp). syslog-manual.rtf
  10. I have two cache pools. One of which is dedicated for my vms. This "vm" pool contains 1 device (a 250 GB SSD) is formatted as XFS. There are currently 2 "vdisk1.img" files stored on that disk. They are listed as being 64.4 GB each. Besides those, the only other thing that is on this SSD is the libvirt.img, which obtains 1.07 GB. In my Unraid Main page, it shows that only 75.9 GB of the total 250 GB is used which is half of what I'd expect. Is this a bug in calculating / showing the storage space used? Or do these .img files only take up the size according to how full they are? If the latter is true, does that mean that I can in theory have more than 250GB of .img files stored on this disk? As long as they are not all full of course.
  11. Okay, thanks Just for my curiosity; does that scale with the total disk size?
  12. Just installed a new WD 8TB RED WD80EFAX hdd in my system. Ran a preclear (zeroing) with the preclear plugin. Stopped the array, added the new disk to the array, started the array, formatted the new disk (as xfs). The overview now shows that 56GB of the 8TB of that new disk is used. Investigating the disk with the terminal shows it contains 1 folder with 16 small files (between 1 and 250KB in size). I know there always is some os overhead, sure. But 56GB? What could be going on here?
  13. I have everything installed in the server right now, and it works perfect Currently I have only 1 SFF-8087->SATA(s) cable connected to it, as well as only one drive, because thats all I need for now. I have set a fan to blow over the H310 to cool it down as it gets quite hot. The card shows up as "[1000:0072] 01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)" in 'System Devices' in unraid. Is that correct?
  14. I am happy to say I just bought a second hand H310 I am searching for the right cables now, and I've found a few SFF-8087 to 4x sata cables between 15 and 40 euros. Anything I need to look out for specifically (except that they are forward breakout cables :))?