you know what?
You may just have the answer....
as most of us know, it is always recommended to "Eject" the drive before shutting down or unplugging the drive.
This could very well be a typical old Microsoft design issue, (FAT32) if the drive was not finished doing what it was doing when it last lost power (like shutting off the DL32R at the end of a gig),
the next time it is awakened, it gives the ERROR!
Although now that I think of it...
I have done hundreds and hundreds of jobs with my DL32R and I always leave the drive connected and only eject it when I literally want to transfer files from it which is almost never.
So, why is this becoming an issue just occasionally?
retorical question