2TB Drive, only allows for 130gb at a time for plot writing?
-
@HiDevin @AngryChicken That did not solve the issue at all. So when the box opens to let you choose the amountg of hdd you want to plot, the slider initially shows 128 on both left and right sides. If I move the slider, it immediately shows the full 1.82 tb, but still shows only the 128 gb on the right, so the max i can plot is 128gb, thats not right, i have a 4tb and a 2tb being plotted on another system
-
@xaocs that's confusing o-o try reinstalling the wallet again, I never seen this problem before, but I usually use the gpu plotter to plot my drives anyways.
-
Ya like I said before your best bet is to make the bat file yourself.
"You my want to create a bat file for the plotter to run instead of using the GUI.
There's lots of info on how to make the bat files on youtube and even a nonce calculator on the BurstNation downloads page."
-
@xaocs Take a look at the properties of the Windows drive - if it's exFAT or FAT32 you need to reformat as NTFS.
-
@haitch the drive is formatted as ntfs, and has a drive letter F: assigned to it. However, what I am noticing is that I have 128 gb of free space on C:\ so its limiting it to what i have left on my c: drive, although the one i chose to plot IS a 2tb and has 2tb of free space. I am going to try and reformat the drive, do a disk check on it, and try again
-
I can confirm that this is not a problem with it being a vm. Let me explain my setup.
Hardware
Rackable Systems 2U server
2 x AMD Opteron CPU's
194 Gb ram
4 x HDD
2 x 2 tb
1 x 8tb
1x 300gbI have ESXi 6 Running on the server, with vSphere running on my pc to manage the system
I have 1 Windows 10 vm which is where the problem is.
I destroyed that machine, then booted up a windows 7 and the plotting worked just fine. but in Windows 10, it doesn't recognize the full drive for whatever reason.
Any ideas?
-
@xaocs Off hand no idea. I have a VM server running ESX 6.5 hosting a server 2012 VM with 17 drives - so I wouldn't expect it to be ?VMware related.
-
@haitch Yeah, I know. I installed a win 7 copy on a vm, and i think it will do just fine. esxi is the greatest. I'm working out the bugs of my setup for when i get the storage array this weekend and start the verification process
-
@haitch I am in windows 7 now, and am receiving the same error. So whats happening is that it only see's the available space that the OS is installed on. I have it formatted as ntfs, and simple volume. It see's the whole 1.8 tb but it only lets me choose up to whats available on the main hdd. This didn't happen with 3.8 so im wondering if this is a problem with 3.9.1 ? Is there a way you as the admin can test that idea? because i seem to be replicating it. I have a install of 3.8 so im going to install that and see if it does the same.
-
@xaocs I don't have blank space to test with sorry. Talk to daWallet, he'll be able to help
-
I wanted to let everyone know that I think I figured out what it was.
I uninstalled Bursts Wallet version 3.9.1
after, I installed version 3.8.2
logged in to a wallet already made, and
started plotting the full 1.8 tbSo, it's something to do with Burst Wallet 3.9.1
@haitch
-
@xaocs Hi, I found the change in the 0.3.9.1 version that caused it. Though I still don't understand why the function has been reacting this way. Thanks for reporting and not giving up. I repacked 0.3.9.1 and it should work now.
-
This post is deleted!
-
@daWallet said in 2TB Drive, only allows for 130gb at a time for plot writing?:
@xaocs Hi, I found the change in the 0.3.9.1 version that caused it. Though I still don't understand why the function has been reacting this way. Thanks for reporting and not giving up. I repacked 0.3.9.1 and it should work now.
I will try this out later tomorrow after finishing the plots on this drive and report back on it. Thank you for heading this up and repacking 3.9.1 , that was quick!
@Han-Solo said in 2TB Drive, only allows for 130gb at a time for plot writing?:
@xaocs Upgrade to Windows 10. Plotting it's a nightmare with W7. Some memory issues.
I haven't run into any memory issues yet, it's been running at a solid 7gb of use out of 192gb of ram. I'll see what the output is on windows 10 later on after i test 3.9.1 again


