luisv

Members
  • Posts

    195
  • Joined

  • Last visited

Everything posted by luisv

  1. Upgraded docker to the 1.12.3 and receiving this error today. Any ideas? kernel: makemkvcon[4276]: segfault at 8 ip 000000000060c65d sp 000014cf32b8beb0 error 4 in makemkvcon[400000+5db000]
  2. Updated both servers without issue and my Windows 10 VMs started without issue.
  3. Upgraded form rc-3 to rc-4 without issue.
  4. Not sure if it's been previously reported, but if you use a custom schedule under Scheduler and use the black theme, some fields are unreadable.
  5. Upgrade from 6.5.3 was painless and as someone else reported, the docker "Check for Updates" button doesn't work. In stead of the numerous and rather larger oranage boxes on the bottom of the main page, is it possible to underline the options as is performed for the various tabs? Is there a way to control the contrast or brightness of the server info section? It seems very muted to me.
  6. Same here, really liking the new website, forum and for sure, that 6.6 screenshot looks great!
  7. New site / forum looks nice... very nice!
  8. Upgraded one of my servers from 6.5.3-rc2 and so far so good.
  9. Just updated one of my servers, so far so good.
  10. Upgrade on both servers was quick and painless. Kudos to @limetech, @bonienl and the rest of the team.
  11. Which Noctua cooler did you purchase? I originally purchased the NH-U9S CPU cooler, but the motherboard power cable was very close to the fan, so to avoid any issues I swapped it out for the NH-D9L. You should be fine with the PSU you selected as it's fully modular, I went with an EVGA G3 650w PSU.
  12. I recently built a system with that board and case, specs in my signature. Cable management was initially a little frustrating, but managable. If you have any build questions feel free to PM me.
  13. Upgrade 2 servers from 6.5.0 to 6.5.1... both were quick and painless.
  14. It's the logged in user avatar. Not sure how nor where it's pulling it from, but mine is set.
  15. I removed it along with v1 and started net new... I ran the appdata cleanup plugin to make sure all was gone. Before I cleaned up, I took screenshots of my v2 beta settings and while I was at it, I copied my v1 advanced.yaml file to a safe location. Took an extra min or so, but everything is up and running on the new v2... I like the integration of stats from Tautulli within the email. Very nice!
  16. Thanks! I'll see what I can do.
  17. Current cables are 18" long, going with 8 - 10" instead, but yes, I'll make sure there's no strain on the connectors. Thanks!
  18. It's a small form factor ITX build, so yes, cable management is tight with SATA and power cables in close proximity of one another. I used a SATA power cable adapter as it was easier to route than the PSU SATA cable, but I can remove it and reroute things. I also ordered shorter SATA data cables to help with the rats nest. I'm using an EVGA G3 650w power supply. The preclear completed successfully and no additional errors were found; however, here are the UDMA CRC error counts: Parity - 2 Disk 1 - 3 Disk 2 - 2 Disk 3 -1 After 2 Parity checks, the CRC errors remained the same... no other errors found.
  19. For sure, many thanks and kudos to @dlandon @Squid @Frank1940 and those behind the scenes that worked on this!
  20. Just noticed this in the log. Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT3._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ata4.00: configured for UDMA/133 Mar 30 09:29:40 MiniVault kernel: ata4: EH complete Mar 30 09:29:40 MiniVault kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ata1.00: configured for UDMA/133 Mar 30 09:29:40 MiniVault kernel: ata1: EH complete Mar 30 09:29:40 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:40 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:40 MiniVault kernel: ata3.00: configured for UDMA/133 Mar 30 09:29:40 MiniVault kernel: ata3: EH complete Mar 30 09:29:41 MiniVault kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) Mar 30 09:29:41 MiniVault kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT1._GTF, AE_NOT_FOUND (20170728/psparse-550) Mar 30 09:29:41 MiniVault kernel: ata2.00: configured for UDMA/133 Mar 30 09:29:41 MiniVault kernel: ata2: EH complete
  21. No sure totally understandable. Just wanted to indicate that parts weren't repurposed.
  22. Everything being used in this second smaller system is brand new, no drive enclosure, no additional controller card, using the built-in controller of the Asrock Z370M-ITX Motherboard.
  23. Hmm... new cables and new 650w PSU. Safe to assume, nothing to worry about at this point of time?
  24. Currently running this on four HGST 6TB drives and on step 2 zeroing, all four indicated a UDMA CRC error count with a count of 1.