Bitcoin Forum
May 13, 2024, 10:38:52 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Antminer S9 bmminer not starting  (Read 351 times)
tim-bc (OP)
Full Member
***
Offline Offline

Activity: 538
Merit: 175


View Profile
May 05, 2018, 12:47:04 PM
 #1

I am seeing more and more antminer s9s that will not boot and are stuck in an endless loop of grep bmminer, any suggestions on how to address this issue?

https://pastebin.com/BTAzQE7m

Code:
bmminer not found= 1369 root       0:00 grep bmminer
 
bmminer not found, restart bmminer ...
bmminer not found= 1387 root       0:00 grep bmminer
 
bmminer not found, restart bmminer ...
bmminer not found= 1396 root       0:00 grep bmminer
 
bmminer not found, restart bmminer ...
bmminer not found= 1405 root       0:00 grep bmminer
 
bmminer not found, restart bmminer ...
bmminer not found= 1414 root       0:00 grep bmminer
 
bmminer not found, restart bmminer ...
bmminer not found= 1432 root       0:00 grep bmminer

etc...

Ignore scammers on Skype, Telegram, etc. I will only ever contact you via forum PMs. See profile for fingerprint.
1715596732
Hero Member
*
Offline Offline

Posts: 1715596732

View Profile Personal Message (Offline)

Ignore
1715596732
Reply with quote  #2

1715596732
Report to moderator
1715596732
Hero Member
*
Offline Offline

Posts: 1715596732

View Profile Personal Message (Offline)

Ignore
1715596732
Reply with quote  #2

1715596732
Report to moderator
1715596732
Hero Member
*
Offline Offline

Posts: 1715596732

View Profile Personal Message (Offline)

Ignore
1715596732
Reply with quote  #2

1715596732
Report to moderator
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715596732
Hero Member
*
Offline Offline

Posts: 1715596732

View Profile Personal Message (Offline)

Ignore
1715596732
Reply with quote  #2

1715596732
Report to moderator
1715596732
Hero Member
*
Offline Offline

Posts: 1715596732

View Profile Personal Message (Offline)

Ignore
1715596732
Reply with quote  #2

1715596732
Report to moderator
1715596732
Hero Member
*
Offline Offline

Posts: 1715596732

View Profile Personal Message (Offline)

Ignore
1715596732
Reply with quote  #2

1715596732
Report to moderator
fanatic26
Hero Member
*****
Offline Offline

Activity: 756
Merit: 560


View Profile
May 07, 2018, 07:24:59 PM
 #2

That error has been exclusively showing up on 1117 firmware machines. The downgrade to the april firmware always fixes it for me.

Stop buying industrial miners, running them at home, and then complaining about the noise.
tim-bc (OP)
Full Member
***
Offline Offline

Activity: 538
Merit: 175


View Profile
May 08, 2018, 03:15:53 AM
 #3

That error has been exclusively showing up on 1117 firmware machines. The downgrade to the april firmware always fixes it for me.
Thanks! I should have guessed, that did the trick for about 90-95% of them. It seems on a select few the issue still persists, although the kernel log hangs on "Start bmminer ..." instead of giving endless output.

Also, what is your preferred method of flashing firmware when you encounter the code 413 - Request Entity Too Large? Is there any other method besides using a microSD card, and how exactly do you put the firmware on the microSD? Do you extract the files first? And what format, is FAT32 sufficient?

Ignore scammers on Skype, Telegram, etc. I will only ever contact you via forum PMs. See profile for fingerprint.
fanatic26
Hero Member
*****
Offline Offline

Activity: 756
Merit: 560


View Profile
May 09, 2018, 03:12:28 PM
 #4


Thanks! I should have guessed, that did the trick for about 90-95% of them. It seems on a select few the issue still persists, although the kernel log hangs on "Start bmminer ..." instead of giving endless output.

Also, what is your preferred method of flashing firmware when you encounter the code 413 - Request Entity Too Large? Is there any other method besides using a microSD card, and how exactly do you put the firmware on the microSD? Do you extract the files first? And what format, is FAT32 sufficient?

Ive honestly never seen that error before, and I run almost 10k S9/T9s. I know its been mentioned a few times on the forum here but I dont recall seeing a good answer :/

Stop buying industrial miners, running them at home, and then complaining about the noise.
tim-bc (OP)
Full Member
***
Offline Offline

Activity: 538
Merit: 175


View Profile
May 09, 2018, 03:57:15 PM
 #5

Alright, I will see if bitmain will do a warranty repair. I really appreciate your experience with these issues because otherwise I would be way more clueless Huh

Ignore scammers on Skype, Telegram, etc. I will only ever contact you via forum PMs. See profile for fingerprint.
tim-bc (OP)
Full Member
***
Offline Offline

Activity: 538
Merit: 175


View Profile
May 22, 2018, 03:46:15 AM
 #6

Ive honestly never seen that error before, and I run almost 10k S9/T9s. I know its been mentioned a few times on the forum here but I dont recall seeing a good answer :/
Thanks, I worked out a warranty repair with bitmain. I assume you use dhcp also? And do you have any suggestions for internal servers besides dhcp dns and ntp?

Ignore scammers on Skype, Telegram, etc. I will only ever contact you via forum PMs. See profile for fingerprint.
fanatic26
Hero Member
*****
Offline Offline

Activity: 756
Merit: 560


View Profile
May 22, 2018, 03:10:04 PM
 #7

Ive honestly never seen that error before, and I run almost 10k S9/T9s. I know its been mentioned a few times on the forum here but I dont recall seeing a good answer :/
Thanks, I worked out a warranty repair with bitmain. I assume you use dhcp also? And do you have any suggestions for internal servers besides dhcp dns and ntp?

Actually I do not allow DHCP on the production floor, everything is set static and each vlan is locked down pretty well. DNS and NTP are the only ones I run for the servers. I have tried various proxy pools at different times but they all have issues so I nixed that idea.

Stop buying industrial miners, running them at home, and then complaining about the noise.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!