I faced the same dilemma recently. First, I bought a USB 3.0 external Seagate hard drive. With an ambient room temperature average around 80-85F, the hard drive runs at 112F (~44C). Honestly, anything over 100F is too hot and killing the life of the hard drive. My new method involved getting 2 of these: http://www.newegg.com/Product/Product.aspx?Item=N82E16817182245&cm_re=rosewill_enclosure-_-17-182-245-_-Product as Shell Shockers at $20 (now $22) and two of these: http://www.newegg.com/Product/Product.aspx?Item=N82E16822145911. As NAS drives, they can handle higher temperatures and made to run 24/7 (I believe Seagate externals over 3TB run less than 7200 RPM). With the variable fan speed on the enclosures, they have never exceeded 100F. This is the slightly more expensive method, but should improve hard drive lifespans. Most external drives do not have NAS drives in them.
Another method is this not so crazy expensive rack for $30: http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=4173135&CatId=4269. Connecting all of the hard drives to your motherboard could pose a major problem since most cases do not have 5 ESata ports (assuming you have SATA to ESATA conversion).
Lastly, assuming you have more SATA ports available on your motherboard, you can convert unused 5.25" drive bays into a hard drive rack. The best ones convert 2 bays into 3 hard drive slots or 3 bays into 4 hard drive slots with a fan in front to keep it all cool.
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 610. (Read 2171065 times)
October 28, 2014, 11:33:17 PM
October 28, 2014, 10:28:23 PM
How are external drives for mining?
I was thinking about getting a external 4tb drive with usb 3.
My main concerns are heat and the lifespan of the drive. It's a bit more expensive but I dont have any more room inside of my computer and not too eager to change the power supply..
I was thinking about getting a external 4tb drive with usb 3.
My main concerns are heat and the lifespan of the drive. It's a bit more expensive but I dont have any more room inside of my computer and not too eager to change the power supply..
October 28, 2014, 09:30:51 PM
Storj lead dev here. I really don't see Burst as a competitor, I think it is a really cool concept that could be useful to us. For example, we might want to make sure there is excess unused capacity on the network for expansion. I think that would be a good use case for the Burst algo.
If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare.
If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare.
I have a possible second use for storj/BURST. It won't be an issue initially, but eventually, like almost every other cryptocurrency, storj may be faced with very low profitability as selling exceeds buying. The solution will be to swap Driveshare space for plot files when BURST is more profitable. As people switch over and the selling pressure gets too high, then they can switch back to storj until BURST improves (buys catch up to sells). I can easily see a BURST miner/Driveshare auto-switching program. By that time, optimized plot files should be easy to generate in a short amount of time to make this possible.
It all depends on how the numbers line up. It is still too early to tell what will happen, but as a warning to the storj developer, a good chunk of your network may fill with a lot of plot files and will hopefully not bottleneck overall network space too much for actual files (won't be an issue at least for a while). On the flip side, BURST and storj may help relieve the other one of some of the selling pressure that is bound to happen and possibly help increase the number of buys as the two gain popularity together.
What you are thinking of is dynamic Storj. For example, you tell Storj to take up to X percentage of free space on your hdd. As you fill up your disk with whatever files (like plot files) Storj backs off.
That would work fine.
You are right. Thank you for reminding me. I forgot about the network speed bottleneck.
I like your idea of dynamic Storj. Instead of being forced into giving 100% of your available space to one specific coin, you could modulate the amount to each coin. To minimize stress to hard drives, it would probably be in 100GB increments or larger for the slider if BURST is programmed into Driveshare. Otherwise, it would be automatic as you suggested. Keep up the brainstorming!
October 28, 2014, 08:40:16 PM
Storj lead dev here. I really don't see Burst as a competitor, I think it is a really cool concept that could be useful to us. For example, we might want to make sure there is excess unused capacity on the network for expansion. I think that would be a good use case for the Burst algo.
If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare.
If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare.
I have a possible second use for storj/BURST. It won't be an issue initially, but eventually, like almost every other cryptocurrency, storj may be faced with very low profitability as selling exceeds buying. The solution will be to swap Driveshare space for plot files when BURST is more profitable. As people switch over and the selling pressure gets too high, then they can switch back to storj until BURST improves (buys catch up to sells). I can easily see a BURST miner/Driveshare auto-switching program. By that time, optimized plot files should be easy to generate in a short amount of time to make this possible.
It all depends on how the numbers line up. It is still too early to tell what will happen, but as a warning to the storj developer, a good chunk of your network may fill with a lot of plot files and will hopefully not bottleneck overall network space too much for actual files (won't be an issue at least for a while). On the flip side, BURST and storj may help relieve the other one of some of the selling pressure that is bound to happen and possibly help increase the number of buys as the two gain popularity together.
What you are thinking of is dynamic Storj. For example, you tell Storj to take up to X percentage of free space on your hdd. As you fill up your disk with whatever files (like plot files) Storj backs off.
That would work fine.
October 28, 2014, 08:33:04 PM
Storj lead dev here. I really don't see Burst as a competitor, I think it is a really cool concept that could be useful to us. For example, we might want to make sure there is excess unused capacity on the network for expansion. I think that would be a good use case for the Burst algo.
If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare.
If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare.
I have a possible second use for storj/BURST. It won't be an issue initially, but eventually, like almost every other cryptocurrency, storj may be faced with very low profitability as selling exceeds buying. The solution will be to swap Driveshare space for plot files when BURST is more profitable. As people switch over and the selling pressure gets too high, then they can switch back to storj until BURST improves (buys catch up to sells). I can easily see a BURST miner/Driveshare auto-switching program. By that time, optimized plot files should be easy to generate in a short amount of time to make this possible.
It all depends on how the numbers line up. It is still too early to tell what will happen, but as a warning to the storj developer, a good chunk of your network may fill with a lot of plot files and will hopefully not bottleneck overall network space too much for actual files (won't be an issue at least for a while). On the flip side, BURST and storj may help relieve the other one of some of the selling pressure that is bound to happen and possibly help increase the number of buys as the two gain popularity together.
October 28, 2014, 07:04:48 PM
@uray - I'm assuming your repo (https://github.com/uraymeiviar/burst-pool) isn't current with your pools? Any plans to open that code up? I might be inclined to add a few features and fix some CSS issues I've noticed 
October 28, 2014, 06:32:22 PM
Neither firefox nor chrome seem to like the chart.js script on uray's US pool, in both browsers I need to stop the script but it will restart with every new block. Anyone else have the same problem..?
its for current new layout, or it was like that before? it might be because too many canvas, since each miner has one chart canvas, multiplied that for 200+ miners
No, it has been fine since I joined your pool. It started recently, today or yesterday probably.
October 28, 2014, 05:57:12 PM
Neither firefox nor chrome seem to like the chart.js script on uray's US pool, in both browsers I need to stop the script but it will restart with every new block. Anyone else have the same problem..?
its for current new layout, or it was like that before? it might be because too many canvas, since each miner has one chart canvas, multiplied that for 200+ miners
October 28, 2014, 05:09:58 PM
Still got problems with mining I got one machine working fine now. However 2nd machine and exct same info getting following errors still.
Any advise and help to solve problem would be good. Thanks in advance
Any advise and help to solve problem would be good. Thanks in advance
for 2nd machine config file:
{
"Mode" : "pool",
"Server" : "IP_your_1st_machine",
"Port": 8126,
"UpdaterAddr" : "burstpool.ddns.net",
"UpdaterPort": 80,
"EnableProxy": false,
"Paths":["C:\\plots"],
"CacheSize" : 200000,
"ShowMsg" : false ,
"ShowUpdates" : false,
"UseSorting" : true,
"Debug": false,
"UseResponseMaxTime": false,
"ResponseMaxTime": 5000,
"UseFastRcv" : false,
"SendInterval": 100,
"UpdateInterval": 2000
}
Still not working doing exact the same as before and crashes
October 28, 2014, 04:58:05 PM
Neither firefox nor chrome seem to like the chart.js script on uray's US pool, in both browsers I need to stop the script but it will restart with every new block. Anyone else have the same problem..?
October 28, 2014, 04:18:39 PM
Will get better one for testing. Hdds are fastest I could get. WD purple.
WD Blacks > WD purples.
Yes, yes, I know, I just could not get 60 pcs of black WD in descent time.
So I choose purple over red ones. More intuition than knowledge.
I will try with different hardware, but I have SATA3 mb, SATA3 hdds, SATA3 cables... really nice case and cooling.
Will post my pictures soon, but I am a bit frustrated with results.
Would really really be thankful for setup help.
BTW. Stack of 8 pcs of these purple ones is noiseless. Like not working
Temps also ok, but I got Sunon fans just for the case... October 28, 2014, 04:02:43 PM
A simpler diagram for non-techies. 
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
That's awesome, majere. Sent you 20K burst.
Thank you! The image is not mine, but the author told me he much appreciates the donation.
Will get better one for testing. Hdds are fastest I could get. WD purple.
WD Blacks > WD purples.
WD purples should be very fast. Quoting specs:
6 tb - 175 MB/s
5 tb - 170 MB/s
4 tb - 150 MB/s
3 tb - 145 MB/s
2 tb - 145 MB/s
1 tb - 110 MB/s
WD black:
4 tb - 171 MB/s or 154 MB/s depending on model
3 tb - 168 MB/s or 154 MB/s
2 tb - 164 MB/s
1 tb - 150 MB/s or 126 MB/s (I have the second one)
WD red 4tb - 150 MB/s.
My 1 TB WD black vibrates like crazy, I wouldn't recommend it to anyone. Newer models may be better, I don't know. Also blacks are desktop drives. Reds or purples are probably better for mining.
October 28, 2014, 03:32:00 PM
Will get better one for testing. Hdds are fastest I could get. WD purple.
WD Blacks > WD purples.
October 28, 2014, 01:31:19 PM
A simpler diagram for non-techies.
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
That's awesome, majere. Sent you 20K burst.
October 28, 2014, 01:12:00 PM
A simpler diagram for non-techies.
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
Really, really nice
But I would put Burst on the left and other cryptos on the right so people start looking at the image from the most important.
This is true for Western Audiences.
October 28, 2014, 01:11:46 PM
Is there any significant difference of mining performance between 5400rpm hd and ssd if they are of the same capacity?
In theory yes but currently no. The bottleneck is not the hard drive or SSD speed its more of the RAM and CPU when plotting and mining (although with mining the requirements are significantly lower). Usb 2 may see less performance but a usb3 hard drive or any internal hard drive will never be the bottleneck
October 28, 2014, 01:10:42 PM
Sorry, I confused Blago's miner with Uray's. You are right, it spawns one thread per folder and reads files sequentially.
I love it! Nice work! Can I post it places and just give you credit?
Sure. No credit is neccessary, it's public domain. I'm not the author, but he reads this forum.
A simpler diagram for non-techies.
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
I love it! Nice work! Can I post it places and just give you credit?
Sure. No credit is neccessary, it's public domain. I'm not the author, but he reads this forum.
October 28, 2014, 01:07:55 PM
A simpler diagram for non-techies.
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
Really, really nice
But I would put Burst on the left and other cryptos on the right so people start looking at the image from the most important.
October 28, 2014, 01:03:33 PM
A simpler diagram for non-techies.
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
I love it! Nice work! Can I post it places and just give you credit?
This is very well done and good subliminal
October 28, 2014, 12:57:20 PM
A simpler diagram for non-techies.
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX
I love it! Nice work! Can I post it places and just give you credit?
Jump to: