This is an ongoing issue with Bitmain in general. I too was just hit with a failed part, and the turn around on failed product WILL result in serious loss in mining payouts. There is an advantage to going with Bitmain for mining hardware, however due to their support on hardware with issues, you need to factor in as serious losses in revenue .
Yeah I've accepted that I will probably never reach ROI, and its very frustrating/depressing watching your investment go from bad to worse.
Bad to worse => to worser....
Got the blue screen of death.... S2 turns on but only getting a blank blue LCD display on the S2. I've re-imaged SD card but did nothing. Waiting for a Bitmain to reply for a RMA request.
Don't give up yet. i've had the same thing. try removing all the boards (power off first, of course), then power on. watch the controller board for blue lights. they mean the controller has found a usable boot partition on the SD card and booted from it. if you get it to boot, and can connect to the web page of the controller, then the problem may have been a connection to one of the currently-removed boards. you have to put them back in, but there's a good chance that shutting the system off "hot" will botch the SD image, so you have to ssh into it and shut it down gracefully...
shutdown -h now
wait for it to do so, then power off.
keep us posted.
Wow cheers, I managed to get it going again with your advice. I guess I had to be a little more persistent. Since I've turned it back on I've got a whole lot of --x--x---- on 2 of the blades. So I only have 7 functioning 100%, 2 @ about 70% and 1 not 0%.
I'm still waiting for a reply from Bitmain for a support query last week on the reason why a blade is running much cooler and literally not hashing.
I've tried rebooting machine to clear the ---x--- but they dont seem to clear.
Is there a default login and password to SSH into the machine?.. I'm using putty.
Well managed to get going for about 5 days however after 2 days one of the blades malfunctioned again, I don't why but the only evidence shows that the blade cools down and stops hashing. I guess it shows when the avg hash starts dropping. This was my original problem other than the rest of the problems I am experiencing. Today I had to relocate the machine which required me to switch off, unfortunately every time I have to switch off I have to image the SD card and spend about 10min pushing it in and out waiting for the device to get read card and get the machine going again. Definitely not a user friendly nor a reliable device. Really this machine should go back to Bitmain but the opportunity cost of sending it back for replacement is losing at least 2 week hashing time when they decide to pull finger and something about it.
Yeah it just took me 3 hours to start it back up again, and when i did a different blade has a lot xxxxx of in the ASIC status... Forever plagued with problems.