Topic: Antminer S9 - No data in Miner Status page - page 2. (Read 1846 times)

Got it.

Changed network cable and installed Firmware from  April 2017 without hash boards, set pool adresses and i get the bmminer version. Reconnected hash boards and after 28 Minutes i got a mining Maschine

I did changed the firmware however i got connected to antpool after 30 mins.....

however the issue i am facing now the temperature field is displaying ' - ' ....
see image:  https://imgur.com/68LltUL

Not sure why ?

Anybody else facing similar issue...

Haudini,

              Antminer-S9-all-201705031838-650M-user-Update2UBI-NF.tar.gz worked for me. I tried all the others and none worked.

Tuaris and Haudini,

after I installed the older firmware and replaced the ethernet cable, the message "socket Connect failed" also appeared. However, after 2 or 3 minutes it disappeared and my S9 connected to the pools. I have NiceHash as my 1st pool, and slush as my 2nd pool.

I also have a cable modem. I will try this next days

Short questions, which file Version are on  your miners?

I will tell yall what happened to me, and I think this is everyones problem or maybe just a few peoples problems.
I purchased 3 s9's for the january 2-10 shipping, i got them around dec 15th.
I set them up to mine at home. I also have 3 old machines running in a datacenter for the last couple years. I am not new to mining at all.
I set them up and finally after a long time they connected to the pool. it took like 30 minutes for all 3 to connect and start mining, which is too long. i have the connection straight from my cable modem going to a netgear router then connected to 3 miners. after about 8 hours of mining it would drop a miner and disappear from the pool. then another unspecified time went by and it would drop another one, then i decided to shut all off and restart them. they never would reconnect at all. I reset the miners settings and reconfigured all. nothing would connect. I reset my router, nothing would connect,meaning I had internet on a laptop i was using to work on it all but the miners would not connect to the pool.
I finally went and reset my cable modem, then reset my router then started all the miners and they finally would reconnect to the pool and mine. it mined 10 hours then dropped one miner again and would not reconnect no matter what i did.
I started working on just that miner being scared to shut the others off because of the work it would take to make them mine again.
I noticed all 3 pools set in the miner said dead. I checked my other 2 miners and both had only one pool active the other 2 showed dead. knowing I had already made every change to my router I knew to make to fix the problem,I concentrated on my cable modem as the problem. I went in and messed around with all my setting in the modem and ended up doing something in it that wouldnt give me any connection at all lol.
finally I reset my cable modem to defaults. went into it to study all my settings to understand why the default settings wouldnt let my miners run like they should. this is what I did.
I made one change from the default settings in my cable modem and it instantly fixed every problem I had. My modem by default has IPV6 enabled. I unselected that setting and let the modem run on IPV4. restarted the modem and reconnected my computer to the connection and now the webpages load a split second faster. so i reconnected my router and started the miners up and now the miners connect and start mining within about 5 minutes. I now have had 9 solid days of mining without the first problem. they run rock solid from the minute I changed that setting. also now anytime you connect to the miners thru the lan and check the status, all 3 miners have all 3 pools showing live..
if you are having problems connecting your miners and your using a cable modem, try disabling the IPV6 in your modem. if this helps one person it was worth all this typing lol. good luck

If I have posted this is the wrong place , please move it to where it should be.

I read  some solutions. First try a good quality network cable. The next one is remove all cables of one hashboard and install one of the firmware updates from bitmain. In another thread somebody tried  the 550m Version but i wouldn't do that. Take the auto frequency first. Another guy wrotes  he insert all 3 pool adresses from  antpool an it works but he said nothing about bis Firmware. And one guy had issues with one fan so the miner reboot every  3 minutes  and doesn't load bmminer Version.

I have no time Next days to try out, maybe you. Pls tell me all

Hi,

I'm having the same issue "Empty miner status" as reported in this thread, tried to revert back to the firmware but got "Socket connect failed: Connection refused" in the hardware version and the original issue still persists as well. My antminer and PSU are part of January batch.

Have anyone tried any other solution and made it work?

Hello i tried the 201704270135 but Hardware Version shows me socket Connect failed. What can i do?

I'm seeing a similar issue.  What was ultimately the problem? Firmware or having to wait for the self test to complete?

Glad it worked out for u man.

Dear all,

the fan problem was a mistake on my part. I unbolted the metal protection in the intake to see if I could fit a 3D printed part. When I bolted it on again, I put it in the reverse direction and it was blocking one fan blade. I bolted it the proper way and now everything is fine.

So, the solve the "No data in Miner Status page", what I did was to install an older version of the firmware, specifically, Antminer-S9-all-201704270135-autofreq-user-Update2UBI-NF.tar.gz, which is bitmain's suggestion to replace Antminer-S9-all-201704280713-autofreq-user-Update2UBI-NF.tar, the file proposed by fanatic26. I also changed my ethernet cable as porposed by Sandal_Hat.

Thank you very much fanatic26! Thank you very much Sandal_Hat! I would also like to thank all the users that shared their advice with me in this thread:
BitMaxz
Seven_Little_Guys
jafolkerts
fanatic26
jafolkerts
je_mario
KWMiner
LENIN12345
Sandal_Hat

Best regards,
Paulo

Thank you jafolkerts, fanatic26, je_mario, KWMiner, LENIN12345 and Sandal_Hat for your responses.


I tried to install the newest firmware (last row of the table in the link bellow) and I couldn't connect to the pool. Then I installed the one you recommended (first row of the table in the link bellow) and I was able to connect. However one of the fans (the front/intake fan) stopped being recognized, it does not even spin, and a fan-related error appeared in the Kernel file.

Does anyone have an idea on how to solve the fab not being recognized problem?

Best regards,
Paulo


Link to firmware:
https://shop.bitmain.com/support.htm?pid=00720161126080548570Q2tDBXAH065D

Guys, change your internet cable. I was using a right angled ugreen ethernet cable and I changed it to a normal non-right angled one and now, all hashboards work FINE!! Try it. It may work for u.

This worked for 2 of my antminers!!!!

Same was with me. The only problem is an error in worker name or password. And yes - default antpool addresses  in miner setings are void ATM so you never see it working through them hence U dont see mines status info.

I tried to up date the firm multiple times, even tried s9_upgrade_fix.tar, and read "incorrect firmware" everytime. I tried pointing the pool at another address (one from another user on here) and the S9 came to life. After I changed it back to antpools address the miner went dead again.

While I can't definitively claim that this won't work for everyone, I attempted to roll my firmware back and it didn't help. Sent a note to bitmain as I'm guessing it's a bad controller board.

How do I go about rolling the firmware back?

I had a few miners from my last batch with that issue. I rolled the firmware back and they all came up within 15 minutes.

The firmware I used was Antminer-S9-all-201704280713-autofreq-user-Update2UBI-NF.tar

Quick update - 3 out of 4 S9s came up after about 15 minutes. The one troublemaker has been up for about five hours and continues to exhibit the same problem. I let it 'idle' for about an hour and then try a hard reboot (pull the power, wait 30 sec, apply power). I'll let it continue for the remainder of the day and contact Bitmain if it continues on like this.