Jump to content

tdoane

Members
  • Posts

    2
  • Joined

  • Last visited

  • Days Won

    1

tdoane last won the day on March 15 2014

tdoane had the most liked content!

tdoane's Achievements

Newbie

Newbie (1/3)

1

Reputation

  1. Drashna -- I'll create the dump file as soon as I finish the server migration from WHS to SE2012. I'll need to do some hardware mounting in the rack regardless and within a hour the lock up will occur. In regards to components: - Norco 4220 case - ASRock EP2C602-4L/D16 SSI EEB Server Motherboard Dual LGA 2011 Intel C602 DDR3 1600/1333/1066 - 2 x Intel Xeon E5-2630 v2 Ivy Bridge-EP 2.6GHz LGA 2011 80W Six-Core Server Processor BX80635E52630V2 - 4 x Kingston 8GB 240-Pin DDR3 SDRAM DDR3 1600 ECC Unbuffered Server Memory w/TS Model KVR16E11/8 - 1x 1 x ADATA Premier Pro SP900 ASP900S3-256GM-C 2.5" 256GB SATA III MLC Internal Solid State Drive (SSD) (server o/s drive) - 5x 4TB red WD, 4x 2 TB green 1x 1 1.5 TB green (more to be added as old server removed) Please let me know if you want any additional details outside the memory dump. Thanks for your response -- hoping to get this working soon! -Tim
  2. , I believe I've isolated my issue of server lockups being caused by the Scanner software. The situation I have is a two week old new Server 2012 Essential build, that is migrating from a 35 TB WHS v1 box. During the course of setup I installed both the drive pool software (love it btw) and the scanner software. Every hour to two hours the machine would drop all shares, RDS would become unresponsive, and the box became unreachable over the network by both tracert's and pings. Subsequent removal of the scanner software eliminated the issue that I just described which occurred a half dozen times prior to removal. After migrating the vast majority of the data, I reinstalled the scanner software last night - I was hoping it was being caused by software updates by our MSFT friends, however once again within two hours the machine became unresponsive. Is there any recommendations, debugging that I can do to determine what aspect of the program is causing this behavior? Thanks! -Tim
×
×
  • Create New...