Just set up two s3 b9's with identical PSU's and ran fine for 4 days till I needed to change one of the configuration settings on both devices.
I changed the setting (password field for the first pool, actually getting used as a hashing control for a lower limit of payout acceptable) and then clicked the "Save&Apply". I monitored for a while and just got to wondering "did the setting actually take effect properly" as things didn't seem kosher, so I used the reboot option from the web page on both devices.
On reboot one would not display a good status LED (although the NIC LED's look good). Both the red and green LED's are dark, not even brief flashing (even though they did light till the NIC cycled). If I try to access it with the browser I get the initial page "LuCI - Lua Configuration Interface" but the auto link to the status overview eventually times out. It also doesn't generate heat (I have them side by side and there is a big difference in heat output between the working one and the failing one)
I tried leaving the failing one off for 20 minutes or so. That didn't help. I then swapped the PSU's on the theory that there wasn't enough electrical output on one PSU. That made no difference, working one with the other PSU still worked, failing one with the "working" PSU still failed.
Thoughts on what I could try that won't make it so I can't return it?
For those with S3's acting up, try to go back to the original image. Or, if its slow, try the S3+ firmware. These are nice miners, but they are not consistent. In order to get all miners going, either go backwards or forwards with the firmware. Just my 2 cents for you to try. Have you tried the S3+ firmware yet?
I doubt you will brick it, I have done many S3+ compatible firmware update, and I also went backwards. No issues. Email tech support, and if they ask if you should upgrade it, that way you can say you were just following their instructions. I think there was a security issue with the original firmware.
I just tried an SSH access and the one device just times out the connection, the working one lets me log on as root. I think it's interesting that the first LuCI page comes up even though other pages and SSH don't work. At this point, without better diagnostics, I'd be inclined to let bitmain tell me what to do.
Trouble is that the downed miner won't bring up the HTTP interface, so there is no possibility at installing different firmware. Anyone know how to reset the device? We've tried the instructions for reset shown here, but no joy.
Can you ping it? If so try another browser? Default should be 192.168.1.99.
I've noticed that if I ssh into an S3 and command halt, unless I cold boot I can't get in. The device will acknowledge a ping but port 80 seems closed. And the halt command stops the cgminer-monitor so it doesn't restart at otherwise 3 minutes most.