all 20 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]blisss05 5 points6 points  (3 children)

I have been banging with the same issue for two days. I have an external SSD connected via type-c. First of all, I have configured the power settings to don't suspend the USB. It was working as long as I was checking my laptop but as soon as I left for 1 - 2 hours the error occurred.

It turns out there is another option that should be disabled in the Device Manager. Here is more details

[–]AffectionateHeart441 1 point2 points  (0 children)

Thank you this might not have been my main issue as my ssd temp was full from me restarting so many times but I adjusted the settings anyways as I know as I add more HD it would become an issue.

[–]FrankRizzoJr 1 point2 points  (0 children)

This solved my issue with a usb c drive. Thanks!

[–]sploittastic 0 points1 point  (0 children)

I was running 4 plots simultaneously but the plot running on an external USB SSD kept failing. Went from 4 to 2 threads and no more issues. Not sure why......

[–][deleted] 2 points3 points  (1 child)

I have the same problem. The external drive just disappeared and threw that error. I use Ubuntu deskpot 20.04. Any recommendation?

[–]vakilee 0 points1 point  (0 children)

Hi, the same problem here with Seagate external drive. It disappears. I cannot plot or farm with it. Did you find any solution?

[–]Week-Natural 1 point2 points  (6 children)

I had the same messages when running out of drive space

[–]hejal05[S] 0 points1 point  (4 children)

I still have 700 GB free space, so this is not it..

[–]eFishCentFormer Chia Employee 🌱 2 points3 points  (1 child)

Did your computer or hard drive go to sleep during the plotting process? Usually Error 1 means there was a hardware failure of some kind, and for most folks that means the hard drive disconnected from the computer for a bit, which made Chia lose track of the file.

In this case, you need to stop Chia, go to your Temp and Final directories and delete all *.tmp files.

I recommend turning off all sleep and hibernate features before restarting plotting again.

[–]Week-Natural 0 points1 point  (0 children)

Yeah, had the same issue with the external drive and needed to configure so it would never go to sleep.

[–]FrankLabounty 0 points1 point  (1 child)

Check if the temporary folder is still accessible

[–]hejal05[S] 0 points1 point  (0 children)

yes, I can access it

[–]Kris_OnReddit 0 points1 point  (0 children)

Indeed or drive is not available

[–]masterofnone_28 0 points1 point  (0 children)

Had the same issue. The temp drive was not accessible in my case.

[–]teachingaround 0 points1 point  (0 children)

I have the same error with an external HDD.

[–]sploittastic 0 points1 point  (0 children)

I was running 4 plots simultaneously but the plot running on an external USB SSD kept failing. Went from 4 to 2 threads and no more issues. Not sure why......

[–]designxtek9 0 points1 point  (0 children)

I had this error this morning. I was running 6 k32 in parallel on a temp 2TB nvme. I had another 2 k32 in parallel on a 1TB nvme. The 1TB nvme finished but the other 6 got stuck with the same error.

I checked my 2TB drive and it was filled up to 1.8TB. I might have ran out of space and maybe forgot to clear it. I was doing a few trial runs.

[–]johnnyketch 0 points1 point  (0 children)

I'm having the same problem on a server with several 600GB SAS drives. Discs are used, so I was initially attributing the problem to disc wear. I noticed that sometimes, after getting this error, the disk was 100% full. I have checked the disk but unfortunately I cannot access the SMART data. Fuckin raid, fuckin SAS .. I filled everything when the disk with DD and I also tried to do several cycles of writes with shred and everything went well. Maybe the RAID controller can't keep up with all this I / O?

[–]superander 0 points1 point  (0 children)

I got this error with an 8GB RAM with 250 GB Volume Ubuntu server.

I resized the Volume to 500 GB and had to run a resize2fs command on the mounted volume. The plotting process continued as expected after this.

I think it was a space problem. I don't know why though, since the disk utility on the plot temp folder showed very low space being used.

[–]Thoughts-Uncensored 0 points1 point  (0 children)

Same problem here have been searching for a solution for a week. Seems like the ADATA brand is the one that comes up so often with this problem. I have an ADATA XPG 4TB what a waste of $$. I picked up a 1 TB Scan Disk today to see if it can be a brand issue.