• Posts

  • Joined

  • Last visited


  • Member Title
    The Future Is Open!


  • Gender
  • URL
  • Location
  • Personal Text
    The Future is Open

LinuxGuyGary's Achievements


Rookie (2/14)



  1. For anyone using glances, there is an update available that resolves the issue above .. Well at least for me it did
  2. My real question is should Reported uncorrect, be looked at like Pending Sectors or more like Reallocated Sectors , e.g. one pretty normal and the other as implying a problem thats not getting corrected by the drives firmware as expected.
  3. What about attribute 187, Reported uncorrect ?
  4. John_M I've managed to secure a bit more memory, I'll replace that, and make sure the BIOS is at the latest version ... I've also disabled the VM Service per your suggestion .. We'll see how that all goes.
  5. hmmm... Curious, I can download the zip from the message and see it, so not sure what that's about, but I've attached another copy of the diagnostics files zipped on another linux box. This PC has only 4 memory slots (all filled) and is an older machine unfortunately I do no have any larger DIMMs to put in it without buying more. I was curious about this that I also see in the syslog... kernel: pmd_set_huge: Cannot satisfy [mem 0xe0000000-0xe0200000] with a huge-page mapping due to MTRR override.
  6. Hi Folks, Helping out a friend here with a trial key and an entry level server. Its currently running Version 6.2.4 on a Dell 755 Core 2 Duo @ 2.6GHz. Using the onboard NIC and sata sockets. There are two Dockers installed, The Limetech/Plex Media Server and Crashplan. Plex is running, but Crashplan is not yet as we have not been able to make the system stable The server has 4GB ram install, Memtest passed 8 passes without issue. The server runs for a few hours or possibly a day or two, and then things seems to deteriorate with multiple lines in the log like : Feb 6 02:06:01 Ninja emhttp: err: _shcmd: system: Cannot allocate memory Feb 6 02:06:01 Ninja emhttp: err: _shcmd: system: Cannot allocate memory Feb 6 02:06:01 Ninja emhttp: err: _shcmd: system: Cannot allocate memory Feb 6 02:06:01 Ninja emhttp: err: _shcmd: system: Cannot allocate memory Eventually things crawl to a stop. SSH to the box and checking memory usually gives numbers similar to this: root@Ninja:~# free total used free shared buff/cache available Mem: 3910884 314160 822772 351868 2773952 2848460 Swap: 0 0 0 Fix Common problems plugin finds no issues except the version update to 6.3.0 I have attached the diagnostics zip .
  7. I did find this that seems like a possibility.
  8. Have you noticed that your /dev/sda speeds are very slow.. /dev/sda: Timing cached reads: 12622 MB in 2.00 seconds = 6318.71 MB/sec Timing buffered disk reads: 60 MB in 3.00 seconds = 20.00 MB/sec
  9. Yes, Still needed, Please send PayPal address
  10. I can use it, PM Me the shipping costs to 84066 and your paypal address and I'll get it sent.
  11. Have you verified that all the drives are connecting at full speed ? I have the same server, and had swapped to some new cables with latches during a server cleanup, and found that my parity check speeds were very low. It turned out that the new cables were junk. I double / triple checked that they were full seated etc, but nothing made the drives connect all full speed. I reverted to the original cables (no latch though) and link speeds were once again solid. use dmesg|grep "SATA link" to look for the speeds, I was seeing some drives at 1.5 Gbps and some at 3.0, moving the new but obviously poor cables around moved the slow link speed to a different drive. dmesg |grep "SATA link" ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Surprisingly, these Monoprice cables were the problem. But nothing against Monoprice because I have used their 8087-sata forward breakout cables with 100% success on other servers.
  12. Perfect ! Thanks for all of your hard work on behalf of the community! -Gary
  13. Badger... Have you had any time/luck with Crashplan ?
  14. I don't believe that motherboard supports iommu ...