I have fourteen (14) IBM 2880W PSU's with breakout boards sitting around the house waiting to be used on something. Maybe I will get lucky and not have to worry about a stock PSU going out on my S4's. If it occurs, I will be ready.
PS - Is anyone else having issues with not being notified of a post in a forum you are "watching" and have told it to "notify" you?
I am also about to give a try to those 2880W PSU for my faulty S4 PSU's. I still have to figure things out about what plugs/connectors/wires I need. Working with 240V is not something usual for me. Hey, I thought there was no new messages in most of the thread I'm watching... Which doesn't make sense. So I guess there's something wrong with the forums right now.
|
|
|
I plan to order more of those PSU's and cables once i figure out how to replace the PSU of an S4 with one of these.
Thanks Man
If you get them to work well with an S4 with screws instead of PCI-e, take some pictures and write step-by-step instructions (what adapter needed, what wire to cut, etc.), I am interested. Thanks!
|
|
|
Congrats! 3.8TH/s... that's about what I've got in hardware... maybe I should just throw it on here full time instead of just a day or so a week Yahoo.. Thanks guys. This month i was mining with 500TH about 2 days and nothing. With 4TH it takes less than a week. It is very strange universe.) Hard to find logic in luck! ;-) Congrats!!
|
|
|
Hey there!
My guess is +1.26 to +1.50.
Good luck all!
|
|
|
Hey congrats alh, winner for the second time!
|
|
|
2088$
|
|
|
Speaking of dust, I bought 2 used S4s this week from someone local in Montreal who was running 16 S4s in a "data center". I've never seen more disgusting hardware in my life! Dirt was literally baked on everything, the picture doesn't really do it justice especially since the top of the hash boards were the cleanest part. Take a look: Pre-cleaning (middle and bottom were much worse): https://i.imgur.com/RUyQBlH.jpgAfter cleaning and installing a proper replacement PSU: https://i.imgur.com/e1xsEde.jpgAnd now she's purring: https://i.imgur.com/WgjcaKB.pngI wish I would have weighed the S4 before and after cleaning. No kidding, there must have been a pound of dirt and filth in there. I'd love to see where this person is running their machines. This unit actually had a huge defect, BITMAIN used a wrong nut and one of the 12v connections on a lower hash board was completely loose. It barely even touched the bolt's threads, slipping right off when trying to tighten it. I've never seen this nut before in an S4, so some asshole at BITMAIN's assembly line was too fucking lazy to get off his ass and fetch a proper nut right before he finished his shift on a Friday night. The wire's terminal was completely charred along with the nut and washer, the rubber insulation almost completely melted away, and the hash board looks damaged but works fine as far as I can tell. I don't know why I didn't take pics, but I still have the charred connector on the PSU if anyone wants a look. I'm putting the blame on BITMAIN since, judging by the sorry state the S4 was in when I got it, the previous owner had never bothered to open it up. Amusingly, somehow both units PSUs still worked even though they were stuffed with dirt/dust. Pretty funny considering I run my other S4s in a clean environment with very little dust, and I've had 4 out of 5 PSUs die on me. Edit: Just noticed that you can see the charred washer in the second picture, beside the screw driver's handle. Hi Prelude, What is your PSU? I have a few PSU's here but they have PCI-e connectors. Do you know how I can convert the wires to connect to the screws in that series of S4? Is it as simple as cutting the wire and screw it directly on the board? Thanks!
|
|
|
It's very nice to wake up to a new block on the pool. It's sooo much more exciting when the block has been mined by one of my miners!! Yayyy! Very proud to contribute to the payouts, guys!
|
|
|
Hi! thanks )) 33 pcs S4 miner winner block)
Congrats! It's been a while since last block, it's kind of comforting.
|
|
|
Well that was a pretty big 393% Diff - lets hope for fewer of them in the future That's the first block with the new payout addresses so if you didn't notice my comments before, the Payments page has links to both the old and new address. Got a nice 12.23% one right after! Good job to thedreamer! Good job indeed with 3.9THs! Woohoo! My first. Right after some got rented and pulled off the pool. Lolol I'm getting 3 more miners back on soon though. No worries. Congrats! You saved the week.
|
|
|
Man, this block is killing us. Lol.
It hurts!!
|
|
|
Ouch it's not looking like a good change so far. I hope it slows downl
well late guessing may be smart for the prize here. lots of numbers in the the + 5 to +12 area since you can guess up to march 29 th 2 am utc time there is more then 4 days time to wait. Right... Pretty sure I will change my guess for something higher in a few days. Looks like some mining farms that turned the switch off a week ago just turned it back on. Be ready to change the list, I probably won't be the only one!
|
|
|
+0.51 to +0.75 for me!
Thanks!!
|
|
|
Congrats alh! That was borderline!! See you all on the next thread!
|
|
|
Those two blocks are good! Congrats Tinua and -ck!! Yayy!
|
|
|
Well, I'm happy to report that my attempt at repairing the fans was a success. I had quite a few fans that needed repair. I was never a big "fan" of buying fans. Even in the old GPU days, I'd find tricks to repair the fans instead of buying new ones. I ordered 3mm retaining rings from McMaster-Carr http://www.mcmaster.com/#98541a111/=wdsnjk$5.00 for a bag of 100 pieces Also ordered the requisite pliers http://www.mcmaster.com/#58225a21/=wdso3i$16.98 Remove the sticker on the fan to expose the bearing and most likely a bunch of dried up grease and the old retaining ring that wore off. I found a few that look like the ring completely disintegrated because I was unable to find any evidence of an old one. https://i.imgur.com/d9Yyssd.jpgRemove the fan blade, remove the bearings, and carefully remove the spring from the shaft. Don't lose the spring If the old retaining ring is still under the sticker and it didn't disintegrate you'll be able to see the wear that happened. Here's a pic of a new retaining ring alongside a worn one. https://i.imgur.com/yIGNf5v.jpgI had to do some trimming of the retaining ring pliers since it didn't fit into the bearing area. Used a dremel to carefully remove some material so that the fingers of the retaining ring pliers would reach into the hole. Here's the pliers with one side done: https://i.imgur.com/rSmp7uf.jpgand then both sides: https://i.imgur.com/lQcM1U6.jpgI used denatured alcohol to clean everything well (the fan housing, area where the bearings sit, the bearings and the fan shaft). Liberally dabbed some lithium grease on the first bearing that sits on the spring. Don't place any grease on the other bearing until you have it seated and the ring installed. Then hit it with some grease. If the ring is not placed correctly, the fan will not spin frictionless. You'll feel and hear the shaft grinding. If there's any grinding, the most likely culprit is that the ring isn't installed on the shaft groove properly. I used some gorilla duct tape to seal the end. I averaged about 7 minutes per fan. Thanks for the info! I got problems with 3 or 4 fans up to now and my guess is I will have some more defect ones in the near future. Now I have another dead S4 PSU. I think it's the 4th one I am having problems with! Last one, it took Bitmain 1 month to replace. Hoping to have more luck with this one. If you have DIY instructions to repair the PSU, let us know! EDIT: Removed images
|
|
|
... I'm not sure what the confusion is, but there was no pool outage. As it says, uptime is 14hrs. As I said, it was a ckdb restart. The pool is made up of 2 parts: 1) ckpool that you mine to that handles all of that on the mining side 2) ckdb that gets all the data and deals with it on the data storage and web side. An outage of 1) affects the miner. An outage of 2) doesn't. Great idea that hey Hi Kano, when ckdb is down, does ckpool keep data in memory until ckdb comes back up and then send all kept data for ckdb to persist? Or does it keep it in a file and you have to manually transfer data to ckdb? Not that it's important, I was just wondering. Firstly, ckdb is a memory resident DB. The postgresql backend is simply the permanent storage that is only read on a restart and written to with all the permanent data. ckpool logs all it's data to hourly logfiles (about 1-1.5GB each at the moment) as well as sending it to ckdb. A ckdb restart reloads the permanent storage DB, then using the info there, it goes and reloads the log files from where the DB was up to. It can currently reload the log files about 50 times faster than they fill up, so a 1hr log file often takes less than a minute. It obviously only needs to look in the last 1 or 2 log files since the down time is always very short It is sometimes 2 logfiles since it may happen just around the time of the log file change over. At the same time, it has been getting all the new incoming data from ckpool queued up. When it hits a match in the log file vs the 1st incoming queued message from ckpool, it knows it has all the data it needs from the log files. At this point everything is back to working - but out of sync. It then has to sync/catch up on all the data queued in ram, that was transferred from ckpool while ckdb was reloading the log files. That sync number is the number it shows on the bottom left of the web site That number also grows whenever ckdb gets behind processing the data from ckpool, usually due to DB write delays. Currently the reload takes from 3 to 5 minutes and the sync usually only takes a minute or two after that to get back down to zero. I didn't have the chance to thank you for taking the time to explain various technical aspects of your system. I'm particularly interested on those aspects, being myself a software developer trying to find the time to invest my knowledge in the Bitcoin world. I think 24 hours in a day is not enough. Too many things I want to touch and do. Well in the meantime, my miners are working for me. Thanks again Kano!
|
|
|
Yep not much more to go, also nearing 14 million coins generated Doubt it will have much impact on mining speed though but it seemed like an interesting note. 13,950,550 when I posted I always wonder how many of those coins have been lost for all time, due to misplaced keys or corrupted hard drives, etc. This one surely looks lost https://blockchain.info/address/1111111111111111111114oLvT2Wow never seen one so full of 1's with money in it. If someone truly has that I would like to know how long they used vanitygen to make it. Or how ever they got it. Look at the hash160 which is all 0's... Strange. Somewhat impressive actually.
|
|
|
Is the pool down? EDIT: Looks OK now .... had 0's all over
No, just a ckdb restart which only affects the web page. That ckdb restart means the next ckpool restart can include the change to fix the random problem with user specified difficulty when ckpool restarts. Edit: the pool uptime at the top of the stats page is correct unless it's not showing due to a ckdb restart. I'm not sure what the confusion is, but there was no pool outage. As it says, uptime is 14hrs. As I said, it was a ckdb restart. The pool is made up of 2 parts: 1) ckpool that you mine to that handles all of that on the mining side 2) ckdb that gets all the data and deals with it on the data storage and web side. An outage of 1) affects the miner. An outage of 2) doesn't. Great idea that hey Hi Kano, when ckdb is down, does ckpool keep data in memory until ckdb comes back up and then send all kept data for ckdb to persist? Or does it keep it in a file and you have to manually transfer data to ckdb? Not that it's important, I was just wondering.
|
|
|
Sorry everyone, my fault. The luck switch on my miner got switched to "bad" somehow. I just didn't notice it before. I think it may have been the cat sneaking around back there that hit it. Anyway, I have switched it back to "good" so things should turn around from here. Again, really sorry about that.
Thanks! Really appreciated. Watch your cat.
|
|
|
|