Jump to content
  • 0

file could not be accessed


Gudehus

Question

About half the time I perform a backup from my Mac to DVDs, the backup fails with a message such as

"the file .393-215125994-24. could not be accessed. data fork, -50". Searching for a file with this name always is unsuccessful. Why can't Toast simply disregard the "inaccessible" file and continue? Because I can never find the "bad" file why doesn't Toast give the name of the last accessible file? Toast for me is a pretty frustrating, poorly designed, and useless program.

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

If you are backing up files that are in a Library or System folder then i suggest using Deja Vu or other backup application. There's a reason Roxio bundled Deja Vu with Toast. Also, do not use the Finder to access any files or folders being backed up by Toast because that changes the invisible files and can cause a verification error.

Link to comment
Share on other sites

If you are backing up files that are in a Library or System folder then i suggest using Deja Vu or other backup application. There's a reason Roxio bundled Deja Vu with Toast. Also, do not use the Finder to access any files or folders being backed up by Toast because that changes the invisible files and can cause a verification error.

 

I wasn't backing files in a Library or System folder, and wasn't using the Finder to access files during the backup. I eventually found the bad file by rewriting smaller and smaller sets of files to a rewriteable DVD until I was down to just a small number of folders/files. Then with Terminal I saw the file causing the problem. It was uneditable with vi, couldn't be dumped with od. Using "strings" it showed the single string "bus error". After deleting it, the backup went smoothly. Altogether, it took from 8 AM until 6 PM to write to 10 DVDs. I will check out Deja Vu. Thanks for the tips.

 

Hey, I live in Eugene too! North of Ayres Rd.

Link to comment
Share on other sites

I wasn't backing files in a Library or System folder, and wasn't using the Finder to access files during the backup. I eventually found the bad file by rewriting smaller and smaller sets of files to a rewriteable DVD until I was down to just a small number of folders/files. Then with Terminal I saw the file causing the problem. It was uneditable with vi, couldn't be dumped with od. Using "strings" it showed the single string "bus error". After deleting it, the backup went smoothly. Altogether, it took from 8 AM until 6 PM to write to 10 DVDs. I will check out Deja Vu. Thanks for the tips.

 

Hey, I live in Eugene too! North of Ayres Rd.

Good job troubleshooting the problem. Really a shame about how the Ducks' season collapsed. I live near the foot of Spencer Butte.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...