Bitcoin Forum

Bitcoin => Hardware => Topic started by: Antihackme on March 06, 2022, 05:55:14 PM



Title: recommendations on what to test before buying 2nd hand s9SE 17TH rigs
Post by: Antihackme on March 06, 2022, 05:55:14 PM
Hi,

Would like to have some tips and recommendations on how long should we be testing 2nd hand rigs before buying. Is running it and testing for 10 mins good enough?

What other things should i be looking out for... any guides or tips?


Title: Re: recommendations on what to test before buying 2nd hand s9SE 17TH rigs
Post by: BitMaxz on March 06, 2022, 11:30:28 PM
I think 15 to 30 minutes would be enough to test the miner and a bit shake to check if there is a rattling sound inside the miner if you heard something inside there might be a loose heatsink that could lead to a short circuit.

Also, check the kernel logs you can see other issues and problems there then check the miner status if the miner is running without overheating and running with the right hashrate.


Title: Re: recommendations on what to test before buying 2nd hand s9SE 17TH rigs
Post by: Antihackme on March 09, 2022, 05:40:25 PM
Do you have any guide on teaching how to read the kernal log errors?


Title: Re: recommendations on what to test before buying 2nd hand s9SE 17TH rigs
Post by: BitMaxz on March 09, 2022, 10:51:12 PM
Do you have any guide on teaching how to read the kernal log errors?


All guides are already on Bitmain you just need to search a little bit to find them.

Anyway, check these links below

- 【For S9series】Common problems indicated by miner's kernel log and ways to resolve them (https://support.bitmain.com/hc/en-us/articles/360025531034--For-S9series-Common-problems-indicated-by-miner-s-kernel-log-and-ways-to-resolve-them)
- 【For S17series】Common problems indicated by miner's kernel log and ways to resolve them (https://support.bitmain.com/hc/en-us/articles/900000245886--For-S17series-Common-problems-indicated-by-miner-s-kernel-log-and-ways-to-resolve-them)


It's not complete but it still can help you to troubleshoot the problem through kernel logs.