|
BorisAlt
|
 |
January 07, 2014, 01:19:10 AM |
|
I would venture to guess that worker 2 is dead. Either that or my F5 voodoo is failing.
|
|
|
|
|
gh2k
|
|
January 07, 2014, 01:24:22 AM |
|
Maybe a blog, twitter, facebook where you do some updates? Its hard for your coop members also to not know what's up or what thread to look at and sometimes miss the thread updates from you if others have posted a lot.
+1 for twitter. You need a broadcast mechanism to avoid having to update so many individual threads. Someone would be bound to read it and update the thread they're interested in if the info hasn't already been posted there. |
|
|
|
|
|
thomas_s
|
|
January 07, 2014, 01:31:13 AM |
|
I would venture to guess that worker 2 is dead. Either that or my F5 voodoo is failing.
Its the breaker that's being installed, power needs to be split up as to not blow everything. |
|
|
|
|
|
BorisAlt
|
|
January 07, 2014, 01:24:53 PM |
|
Workers 3 and 4 are hashing !
|
|
|
|
|
gh2k
|
|
January 07, 2014, 10:58:49 PM |
|
Just worker 4 now. Hopefully this means things are being worked on, and not just that our boxes are really flaky.
|
|
|
|
|
|
sf2
|
|
January 08, 2014, 03:20:36 AM
Last edit: August 21, 2014, 09:18:32 AM by sf2 |
|
|
|
|
|
|
|
sf2
|
|
January 08, 2014, 03:25:45 AM
Last edit: August 21, 2014, 09:18:51 AM by sf2 |
|
|
|
|
|
|
|
thomas_s
|
|
January 08, 2014, 11:26:53 PM |
|
Before anyone says anything.
Worker 2 is not working, its something knc needs to fix so until they get back to the email it won't be online.
|
|
|
|
|
|
BorisAlt
|
|
January 09, 2014, 03:34:06 AM |
|
Worker 4 was on 485 for many hours. Is it also a HW issue?
|
|
|
|
|
thomas_s
|
|
January 09, 2014, 03:42:17 AM |
|
Worker 4 was on 485 for many hours. Is it also a HW issue?
1's been fine for the most part 2 has a hardware issue where it just doesn't want to turn on and stay on 3 has something on the board loose where if it gets nudged it could crash 4 randomly reboots |
|
|
|
|
|
gh2k
|
|
January 09, 2014, 11:05:47 AM |
|
Thanks for the update.
It's a shame that the hardware is flaky. Is this typical of knc hardware? What's their RMA process like?
|
|
|
|
|
|
sf2
|
|
January 09, 2014, 03:22:48 PM
Last edit: August 21, 2014, 09:19:19 AM by sf2 |
|
|
|
|
|
|
|
BorisAlt
|
|
January 10, 2014, 01:43:57 PM |
|
Should we ALL write to KnC to ask to fix our worker and demand refund? What's the plan?
|
|
|
|
railzand
Sr. Member
 Offline
Activity: 462
Merit: 250
Lux e tenebris
|
|
January 11, 2014, 02:09:10 PM |
|
Should we ALL write to KnC to ask to fix our worker and demand refund? What's the plan?
Beginning to focus all my spite on a certain Swedish company. They should either send us the btc or a few of the rumoured new jupes |
|
|
|
|
BorisAlt
|
|
January 11, 2014, 05:56:56 PM |
|
#2 failed on January 6th. I wonder if we are in a LONG queue to get answers from KnC? Was it sent back?
|
|
|
|
|
gh2k
|
|
January 11, 2014, 10:23:46 PM |
|
#2 failed on January 6th. I wonder if we are in a LONG queue to get answers from KnC? Was it sent back?
Yep, any news? There should have at least been an email by now? |
|
|
|
|
|
sf2
|
|
January 12, 2014, 11:08:54 PM
Last edit: August 21, 2014, 09:19:39 AM by sf2 |
|
|
|
|
|
|
|
BorisAlt
|
|
January 13, 2014, 07:23:37 PM |
|
One week with 70% capacity. I would like to know answers. Thanks.
|
|
|
|
|
bobsag3
|
|
January 13, 2014, 07:46:55 PM
Last edit: January 13, 2014, 08:49:47 PM by bobsag3 |
|
The average reply time for KnC is 48-36 hours... plus all the needles bulshit they make me do again to test it... means it can take weeks before I even get an RMA number. This is not my first time around the block with having to RMA modules.
EDIT: After god knows how many reboots and me cursing at it, it seems to have come back to life.
|
|
|
|
|
|
sf2
|
|
January 13, 2014, 09:33:17 PM
Last edit: August 21, 2014, 09:19:54 AM by sf2 |
|
|
|
|
|
|
|
