I had the same issue with one of my S3's, it also had a single line for the blades on initial start-up.  I removed the cover, pushed all the connectors between the controller and blades into the sockets, then reconnected power and now both blades are showing and hash rate is fine (about 431 GH/s avg after 1d 21hr at stock settings).  I suspect workmanship issues with the cables, so I asked Bitmain to send a replacement cable with my next order on B4.
While you wait for a reply, you could try removing the cover (just a few screws, simple) and check out these cables.

Cheers

Same here for 1 of them, but after 24 hours the 250MHz one gradually goes down to similar hash rate as the other at stock frequency.  Decided to leave them at 218.75 for now.

Cheers

B4 sold out, B5 started at 0.64BTC each!

The ban on flights is being lifted (http://www.reuters.com/article/2014/07/24/us-mideast-gaza-idUSKBN0FT06I20140724).
About the performance issues, the SP30 is a leading-edge product, and as it attempts to raise the bar you expect to encounter some issues that needs to be resolved.  If it was so 'trivial' then the average Joe could design/build/sell these.
Rather than falling into 'despair' and 'criticism' one probably needs to give the engineers at SP Tech a chance to focus on the problems at hand and solve them.

Cheers

I had exactly the same issue on one of the S3's.  In my case opening the case, moving and reseating all connectors / cables between the controller and hashing boards seems to have solved it.  Maybe some of the wires do not make a good contact in the IDC (insulation displacement contact) part of the connectors, and just a slight shift of the wire 'fixes' it.  If all else fails, as suggested you could swap parts between the 'good' and 'bad' S3.

Cheers

Maybe that's your issue.  Another user reported a big improvement after cleanup of the excess paste.  Let us know how you go.

Good luck

Just wanted to wish Spondoolies-tech staff that this security situation will finish soon, and you can focus on hashing rates rather than 'colour red' alerts.

Cheers

I had a similar issue on one of the S3s that arrived today.  One of the blades (2nd one) would not show on the status page of the web interface.  I took the cover off, pushed all the connectors of the 2 cables between the controller and the hashing boards into their sockets, and that seems to have rectified it (at least for now).  Maybe there is some workmanship/quality issue with these cables/connectors.  (see my post a bit earlier on this thread).

Good luck

Got my 2 S3's today.  Thanks UPS and Bitmain.
The 1st one worked fine straight away.  The 2nd one had some 'jet lag', only one blade was reported and the hash rate was correspondingly about half.  Swapped power supplies, but that was not the issue.  Opened the cover, pushed the connectors of cables between the controller and hashing boards in, and now both blades come up.  Re-installed the cover, and it's still running both blades.
Average hash rate is about GH/s after almost 2 hours on the 1st one. The 2nd one is has similar performance, but did not have much time to stabilize yet.  Both running at default settings (frequency=218.75 MHz).
Had only a few beeps so far, nothing annoying.

Cheers

Thanks for sharing this.  How did you rectify the excess paste, and what was the impact on hashing performance of that unit?

(Looks like now that BITMAIN has a heatsink also on the component side, this creates an 'opportunity' for this sort of problem)

Cheers

Look at page 4 of the Antminer S3 manual.  You need to power both groups, however if you don't intend to overclock, you may use 1 PCI-E connector per group
"One AntMiner contains  four  power  sockets, which are , formed into two groups as below. Only two sockets are enough to support one unit , but out one of the two sockets of each group must be each group must be  connected to 12V Power line. "

Looks like you supplied power just to one group, so the other one is idle.

Cheers

My B1 shipment has finally left Shenzhen, so probably tomorrow I can get my S3's

Mine too.  Once it moves out of Shenzhen, you know that there is a chance.... good luck

Mine just says "Shenzhen, China    19/07/2014    23:56    Arrival Scan"
It's been there now for about 48 hours.  Trying to find out from UPS what is the reason.

I hope all of our miners get delivered soon

Cheers

Is yours coming by UPS or another shipping company?

I expect no movement on a Sunday, but unclear why Monday is gone without progress.
BITMAIN - can you help sort this out at your end?

My delivery is still scheduled for Wednesday, 23/07/2014.
There is something strange going with these delays.  Have someone at customs developed an appetite for BTC mining, or expectations for kickbacks?

Looks like the same times as mine.  There was another member that had his order stuck for about 3 days until it departed China, never had anything like this with my S1 orders. What's your expected delivery?

Cheers

My B1 order seems to be stuck in China

Location    Date    Local Time    Activity
Shenzhen, China    19/07/2014    23:56    Arrival Scan
   19/07/2014    23:55    Departure Scan
   19/07/2014    23:13    Origin Scan
   19/07/2014    18:10    Collection Scan
China    19/07/2014    2:16    Order Processed: Ready for UPS

Scheduled Delivery Updated To:
    Wednesday, 23/07/2014

Its already late on 21/07 now, there is no holiday today in China....UPS  please move....

I'm from Australia, and fortunately the S3 comes just under the GST (similar to VAT) threshold for imports, so persons in Australia that have received their B1 order already paid no fees... no wonder it is called the 'lucky country'...)
Hopefully your customs fees are not too painful.

Cheers