[Darryl Ramm]

"It's a mess and it not work" ...

Lets back way up and start with you providing the expected basic info about your computers, configs, OS X and Pro Tools versions.

You may be confusing things a bit with language here. I would sure suspect you have a *corrupt session*, which is what you likely mean by "corrupt insert". You may also have corrupt or incompatible plugins causing problems, even if both systems have neatly identical or actually identical plugin installations... because plugins can cause all sorts of problems, and maybe something like a minor session corruption or different plugin data saved in a session trigger some bad behavior, maybe bad behavior from a plugin not even being used... so just always suspect plugins, and you start that plugin testing by moving all plugin files out of the plugin folder(s).

You are talking about "start up disk directory" is damaged? You mean the /boot directory? Your home directory?

First thing to do is preserve all current backup/archive copies of your sessions, you should have those already on multiple different drives and ideally on cloud storage. Don't do anything that risks losing those backups, and don't copy current suspect sessions off of any computer over old, maybe healthier, backups.

If the filesystem on one of your computers is corrupt then make one part of this project being to get that fixed: recover the drive from a clone backup or reinstall OS X and restore your sessions etc. from their backups. If the drive hardware is faulty replace the drive first. "My filesystem is corrupted and..." cannot be part of your thought process. Fix the corruption problem first. You don't give any real details of this corruption, or if you are working on the other computer with a session backup from before the first computer seemed to get corrupted or not? If you have significant recent work on the faulty drive that is not backed up and cannot recover it, then you should have stopped using that drive, removed it from the computer and consulted a drive recovery company... and maybe get running again on that computer with a new drive.

Things behave different on different computers likely because the software installation/setup on them *is* different. All it might take is one config parameter different in a preference file or a slightly different version of a plugin on one system. You solve problems not by making absolute assumptions like the computer software setup are identical but by doing experiments/tests as you simplify setups and make them more similar, especially starting by doing some of the standard troubleshooting tests described under "help us help you" up the top of every DUC web page. Do this on both computers (after fixing the corrupt file system/drive problem on the computer that has that issue) especially paying attention to trashing prefs, testing by moving all plugin files out of the plugin folder(s), testing by saving session to a new session folder, testing from creating a new admin user account, and testing with 'Built-In Output' as the playback engine if you can. When you post again, make clear exactly what you did test and the results.

Having a whole album in a single session has always seemed a very unnecessary risk to me, you might want to change that when you get out of this current mess.

What *exact* DAE error are you getting? if its the drive too slow/fragmented then what exact drive make/model are you recording to? Is that a dedicated separate audio/session drive? What filesystem is on the drive? How exactly is that drive attached to the computer?

What are the session sample rate and H/W Buffer size? Many VIs or non-TDM plugins used in these songs?

There are likely many posts on DUC and in the Avid knowledge-base about tracking down specific DAE errors so it is often useful to search for those using your error message.