Chia-Network
getting error "fail to open plot output file"
trying to use bladebit on window server 2012, getting error message and it just stops.
heres the error message https://imgur.com/a/0oEbagW
My apologies for the late reply.
Unfortunately the error isn't being outputted as to why it couldn't open the file for writing. I some work pending to be more specific with I/O errors, but have not gotten to it yet.
However, this is a disk-related, since I don't know the error code I can't be more specific but it simply cannot open a file for writing at the location specified. It could be a number of things like the path being incorrect, the folder not existing, no write permissions, etc.
Bladebit uses unbuffered I/O to write the final plot file, so it may be that the target path has an issue with that.
My apologies for the late reply.
Unfortunately the error isn't being outputted as to why it couldn't open the file for writing. I some work pending to be more specific with I/O errors, but have not gotten to it yet.
However, this is a disk-related, since I don't know the error code I can't be more specific but it simply cannot open a file for writing at the location specified. It could be a number of things like the path being incorrect, the folder not existing, no write permissions, etc.
Bladebit uses unbuffered I/O to write the final plot file, so it may be that the target path has an issue with that.
thanks for the response. my question is, assuming its the last issue you mnetnioned to do with unbuffered I/O target path has issue, then have you gotten it to work on windows? on the same disks, in ubuntu has no issue so we know it can't be the drive.
ok so test few more times this is what is observed, can also been see in my screenshot in the original post.
CLI bladebit.exe -c -f -n 1 D:
will result in error can't allocate and look at the error message near the end, the path it's trying to write to is D:/plot-#### which is weird as / is linux and \ is for windows, so it should say D:\plot-####
if I end the CLI with D:\ rather than D: without any slash, the error message will return D:\ /plot-####
I think the issue is even though bladebit could be used on windows but most uses linux and hence no one really tested under windows. it tries to write the plot while using linux's directory path methodology rather than windows hence it is failing (showing in screenshot the slashes are backwards). is it possible to fix this?
I'm having the exact same error shown in wtfiwinomgs screenshot. It allocates (or fills ram when warm-start is turned on) and then immediately throws the error. It never reaches the Phase 1 stage.
My system: HP DL560 G8 Windows Server 2012 R2 Standard 640 GB DDR3 RAM 4x E5-4610 v2 (64 threads total) Output directory is a RAID array of SAS drives, default format NTFS.
Spent several hours trying everything I can think of...
- Changing Windows Permissions to the write directory
- Running it as administrator
- Destination formatting (D: or D:/ or D:\ or \sharednetworkpath\D and others)
- Toggling warm-start, no-numa, no-cpu-affinity in different combinations
A look online (reddit, etc) shows some people with this same issue but none of these threads have a good solution or resolution.
I'm very inexperienced with compiling and using linux. But it might be the only solution?
I have same issue my destination is on remote location: Phase 1 Total I/O wait time: 138.49 Processing f7s and writing C tables to plot file.
Fatal Error: Failed to write to 'plot-k32-2022-07-13-03-53-226d90a77c8c89a8a5a620723389b0a448e89ca8eea913c3f7ae67691cc3eb5f.plot.tmp.0' work file with error 29 (0x1d).
@harold-b is this issue fixed with the new blade bit version? also would the new version still support the old ram plotting with 416gb?
I believe the current version does output the error as to why it might have failed to open. But the issue of failing to open would be something on the user side. The error code can help diagnose the cause.
As for ram plotting, yes it will be available in the new version via a subcommand, but it's not enabled yet in the current release
Running Ubuntu 22.04 - I have the same error "Error: Failed to open plot output file at ", I get this when trying to have a network drive as a destination as well as any folder within my regular home folder (e.g. documents, downloads...). However it works perfectly when I tried my destinations as "/home"... unfortunately I can only find the plots via terminal. I'm a linux noob so I assume it's a mess up on my end.
Edit: I realized I needed to mount the network folder to /mnt/myfolder, then use bladebit to target that destination... not sure if that helps the OP or not, but maybe helpful for people switching to Linux for plotting (from MacOS and Windows in my case)
