An error occurred while writing to the disk.

[dix]

I was getting "An error occurred while writing to the disk ... xxx.dpdoc was not saved" every time I tried to save files on my newish 1TB SSD project drive. Also, certain audio files would get stuck in BG processing and endlessly be analyzed over and over. Moving the project to a different drive fixed it soo...Seemed like a permissions issue, but the permissions were set the same on both drives:

dix (Me) - Read & Write
staff - Read & Write
everyone - Read only

Just as an experiment I changed 'everyone to Read & Write and applied-to-enclosed-items and that seems to have fixed the problem. What are correct settings for Sharing and Permissions?

Is there something wrong with this drive? ....last night when this first came up Disk Utility reported it couldn't repair it, but today I've run it multiple times (before and after I changed the permissions) and it checks out fine.

[mikehalloran]

Did you Apply to enclosed... for the other two settings as well?

You just copied the project files over. It could have been Word, Adobe or many other file types as well.

I've had to do this on project folders with DP files created on other Macs that weren't moved over with Migration Assistant, Time Machine restore or being zipped first.

Drove me nuts till I figured it out. Wasn't an issue before DP 7.1. MOTU support told me I had corrupt files when I ran into this in 2010. No...

I often have to change disk permissions on USB drives before copying files over or trying to open them.

[dix]

Yes. Apply-to-enclosed fixed the drive. Can I mess anything up by monkeying with the Sharing & Permissions of a drive?

[mikehalloran]

Yes. Apply-to-enclosed fixed the drive. Can I mess anything up by monkeying with the Sharing & Permissions of a drive?

Do not do this to your Boot drive—ever. I tried it to see what would happen, had to wipe my drive and do a Time Machine restore. Just don't.

Folders and files copied from other Macs may need the treatment, especially if not zipped first. Sometimes, that won't work.

My wife gets Word files from her students via DropBox. If not zipped, she can't read them. I figured out that if she zipped them in DropBox, then moved to her desktop and unzipped, that works. I've never tried it with a DP file but could... maybe this weekend.

[dix]

I'm wondering if something like this is what's causing my continuing start-up issues. As you probably don't recall, Mike. I have a weird situation where my Mac Pro will not boot unless a specific SSD is in one of the drive bays (details here viewtopic.php?f=4&t=63426). It's been easy to put off since everything is working fine (as long as that drive is present), but I really need to figure it out. If something were to happen to that drive I wouldn't have working machine.

[Timeline]

I have an issue where my supposedly compatible SSD currently running fine in last version of OS pre Sierra will not allow me to install Sierra claiming issues with drive. I'm afraid to reinstall from backup because its running fine where it is. My drive is a SSD 2TB Crucial and its suposed to work.

[dix]

Did you run First Aid from Disk Utility? Also, reinstalling the OS via Recovery (Cmnd+R) can smooth out weirdness - that operation does not effect user-data btw. Just make sure you're backed up beforehand just in case.

[Timeline]

Did you run First Aid from Disk Utility? Also, reinstalling the OS via Recovery (Cmnd+R) can smooth out weirdness - that operation does not effect user-data btw. Just make sure you're backed up beforehand just in case.

Had not thought that running the utility would do anything but will try. Good idea running the reinstall as that keps everything but the OS.

Will try both. Thanks Dix

[mikehalloran]

I have an issue where my supposedly compatible SSD currently running fine in last version of OS pre Sierra will not allow me to install Sierra claiming issues with drive. I'm afraid to reinstall from backup because its running fine where it is. My drive is a SSD 2TB Crucial and its suposed to work.

In Sierra, you must run Disk Utility from the Repair Partition for most tasks. If the Boot libraries are not up to date, the drive will give you grief.

Sometimes you have to run Repair on the volume first, then the drive; other times the entire drive first, then the volume.

You can also download and reinstall the OS while booted into Repair.

[Timeline]

OK thanks. Sounds like a plan.

OT, Mike.
I'm also having issues with MIDI setup. Using an MPTAV I get setup to recognize the device for a minute and then after playing a few bars it just disappears, even in MIDI monitor . Have you ever seen such issues in this latest version of DP9? Using a keystation 49 but plugged directly into MPTAV via MIDI cable. The USB on the keyboard failed years ago but its plugged for power to a separate breakout powered MIDI box. This one is like a plague.
GB

[mikehalloran]

After installing the latest MOTU MIDI drivers, I had to delete the profile for my MTP AV — a new one immediately appeared and it works. Your firmware is 2.0.1 and your battery is good, yes?

[Timeline]

After installing the latest MOTU MIDI drivers, I had to delete the profile for my MTP AV — a new one immediately appeared and it works. Your firmware is 2.0.1 and your battery is good, yes?

Where is the profile I need to delete? 2.01 yes. Battery not sure. Already redid the Mac MIDI set up over and over

[mikehalloran]

After installing the latest MOTU MIDI drivers, I had to delete the profile for my MTP AV — a new one immediately appeared and it works. Your firmware is 2.0.1 and your battery is good, yes?

Where is the profile I need to delete? 2.01 yes. Battery not sure. Already redid the Mac MIDI set up over and over

Apple Audio MIDI setup. I just couldn't make the profile work so I figured I'd chuck it and start over. When I did, a new one appeared that works fine. ??? What works, works.

The CR2032 battery saves your settings which is why I thought of it. I recently had some problems and thought, "I just changed that" ... oh yea, that was 2012 when I upgraded to 2.0.1. MOTU doesn't seem to have a specified change interval but 5 years appears to be about right.

[Timeline]

After installing the latest MOTU MIDI drivers, I had to delete the profile for my MTP AV — a new one immediately appeared and it works. Your firmware is 2.0.1 and your battery is good, yes?

Where is the profile I need to delete? 2.01 yes. Battery not sure. Already redid the Mac MIDI set up over and over

Apple Audio MIDI setup. I just couldn't make the profile work so I figured I'd chuck it and start over. When I did, a new one appeared that works fine. ??? What works, works.

The CR2032 battery saves your settings which is why I thought of it. I recently had some problems and thought, "I just changed that" ... oh yea, that was 2012 when I upgraded to 2.0.1. MOTU doesn't seem to have a specified change interval but 5 years appears to be about right.

Idont use it except to carry the MIDI to the Mac via USB. Its a default setting. This morning I tried to load an old MIDI driver 2016 and I was able to record half way through the tune until it dropped out. I guess I will try a 2011 MIDI driver next.