Long time ago I experienced some totally random (and false) "Disc full" messages, and there's been posts about them
on the forum quite a few times. It can't be called a bug, because no-one's been able to reproduce the behaviour, AFAIK. That message can, of course, be very generic, and only mean that there's something wrong with HDD connections.
 
Could it simply be a minor, temporary malfunction of the HDD? Has any of you ever gotten that (false) message using SSD?

We digitaze terrabytes of tapes and Vinyl on a dozen of computers.
We get this message, when a harddrive is for a moment not connected to the System.
One second outage of the disc is already too much for Sonar - and Sonar must be restarted.
The power options of the computer may be the reason for a short outage of the disc. 
 
 

I have had this.
 
In my experience, troubleshooting them was always a different culprit. I found a small corruption in the projects each time, in some cases a fade, an effect or a split clip. I would render the fades or effects or join the clips in the offending area and export the project again.
 
To find the bugspot try playing the track all the way through and if the track stops then that is the bug spot, or play the track all the way through and look for a CPU spike.
 
I would recommend letting the Bakers take a look at the project.

Kalle Rantaaho
Long time ago I experienced some totally random (and false) "Disc full" messages, and there's been posts about them
on the forum quite a few times. It can't be called a bug, because no-one's been able to reproduce the behaviour, AFAIK. That message can, of course, be very generic, and only mean that there's something wrong with HDD connections.
 
Could it simply be a minor, temporary malfunction of the HDD? Has any of you ever gotten that (false) message using SSD?

I think I may have the answer. I turned on my computer this morning and I got a message "connection could be faster" or something like that. I had a hard drive crash recently so I got an external HD at a local store so I could continue to save to two separate drives.


I inadvertently plugged it into a usb2 socket instead of usb3. Maybe the "disc full" message might have meant that the connection was too slow?

On post #6 I did ask if you had a removable hard drive. So there's your issue... losing connection with it.
Make sure USB cables work correctly. Yup you might have needed a different socket.
Consider updating your motherboard BIOSs and chipset drivers.
Maybe you are able to update the external hard drive firmware.
 

I have had the same problem. I'm using an internal hard drive with plenty of space, also had low cpu and ram usage, and sonar's performance module indicated less than 30% disk usage. I transfered the project to a different internal hard drive and had the same issue. No region fx were used. Archiving tracks then allowed me to continue recording but caused me to sacrifice those tracks until tracking was complete. No issues on playback, only recording.

Allthough failing connections to external HDDs can most likely cause this message, that's not the (whole) answer, neither is the USB2/3 thing.
This false message was familiar before there was USB3, and as the posts verify, both with internal and external
HDDs.
I have never read about it happening with SSDs, though. Of course, that doesn't prove anything, because SSDs are
so new and this issue is not very common anyway.
 
Greatrockgod ( I like modesty :o), it's a bit weird that archiving tracks made saving possible again, as archiving does not reduce the size of the project.
 
I wonder if VSTs in demo mode could do this? Many of them are "save disabled". Could such a feature affect the whole project??

Try raising your disk IO buffers in preferences/Audio Options advanced. Whatever they are raise them and test if error goes away.This generic warning usually means your disc isn't keeping up.

This error is a generic Windows warning that Sonar has been throwing up since time immemorial.

Haha, we'll the greatrockgod thing is what I strive to be, not what I think I am....guess I should add a "wanabe" at the end.

Please correct me if I'm wrong, but archiving doesn't make the project smaller, however, it stops the hard drive from reading those files that are not in use. So, it acted as if my HD was indeed full because it acted as if I freed up transport bandwidth when I archived tracks; However, the HD was not full and Sonar recognized low HD usage so I find it interesting as well. I finally finished tracking the project and have no problems after un-archiving all the tracks for mixing but it was pretty redundant and anoying to get through the tracking process.

I use a Focusrite Scarlett and I did try adjusting the buffer srttings with no results. The project is all good and finished now with my workaround, but hopefully it doesn't become an ongoing issue with future projects.