Leozolt

I have segmentation fault (core dumped) program exit issues as well. It fails after 0,5 to 10 days runtime. Ubuntu 16.04 miner 1.8.3 & 1.8.2 using poc1 plots, using mixed...

Yes restarting the miner helps until a fast block comes in before the reading finishes again. Removed ../Burst1 from the config & need some fast block now to verify. It's...

The miner doesn't hang on fast blocks without the exFat drives. Any idea what could cause this behavior (Ubuntu 16.04 with exfat-fuse 1.2.3-1) Update: Running 2 instances of the miner...

For the people that like screenshots: the instance in focus always shows 92,39%, updates the block info but does not read the exfat disks. 

maybe exfat-fuse driver needs a special "reset current read-command"? That is higher than my skill level sadly.. I agree that it could possibly be a machine specific or host system...

Partially resolved the failure by running all non exFat drives in one (server) instance and running the 2 other drives using exFat on individual instances for each drive. First 1.7.16-2...

Maybe it is something with exFat driver (exfat-fuse 1.2.3-1 on ubuntu 16.04) not supporting more than x threads from one instance? But that sould have been noticed by exfat users...

working on the filesystem is abnormally slow, got a touch test pass through after a fast block came in an the miner stuck on 11% read (some disks got read...

The first example should leadt to the bug. The second example should demonstrate that its a recurring bug (its reproduceable) not a missing block. But if a resinc helps all...

Ok I found something, I dont know how to explain, but I think that here the transaction was reorganized in a way that the funds seem to partially come from...