QRecallDownloadIdentity KeysForumsSupport
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Groups] Back to home page 
Error on opening archive  XML
Forum Index » Problems and Bugs
Author Message
Mats Jacobson



Joined: 23-Jan-13 07:25
Messages: 6
Offline

First I get this in Capture in the log:
"Action 2014-08-15 16:25:41 The layer created by this capture is incomplete and may be missing items. Use caution when recalling items in this layer. "

Then later I have in one item "Action2014-09-04 14:26:28 Failure Unable to start LS API isolation process; will use local process "
AND

Action 2014-09-04 14:26:33 Curious Could not determine display name
Action 2014-09-04 14:26:33 cannot get display name
Action 2014-09-04 14:26:33 Error: Unexpected internal error
Action 2014-09-04 14:27:44 Library/Application Support/FXpansion/Tremor/System/Presets/Factory/Drums
Action 2014-09-04 14:27:44 Percussion
Action 2014-09-04 14:27:41 file Bongo rez H.tremordrum
Action 2014-09-04 14:27:41 Failure Could not capture file
Action 2014-09-04 14:27:41 failed to write envelope header
Action 2014-09-04 14:27:44 file Bongo riz H.tremordrum
Action 2014-09-04 14:27:44 Failure Could not capture file
Action 2014-09-04 14:27:44 folder Percussion
Action 2014-09-04 14:31:40 Failure Failed
Action 2014-09-04 14:31:40 archive I/O error
Action 2014-09-04 14:31:52 Failure Capture failed
Action 2014-09-04 14:31:52 A storage or disk error occurred while writing to the archive data. This could indicate a hard drive failure, or the drive or volume was disconnected. The archive may need to be repaired.
Action 2014-09-04 14:31:52 ------- Capture incomplete (06:29)

Note that those files exists.
AND

QRecall 2014-09-05 18:51:29 Warning Unexpected file system error
QRecall 2014-09-05 18:51:29 Error: Error removing
QRecall 2014-09-05 18:51:29 Path: /Volumes/Safe House/Dagligen/dagligdags.quanta/.lock
QRecall 2014-09-05 18:51:29 Failure Problem recovering from failed attempt to open archive
QRecall 2014-09-05 18:51:29 could not remove lock file
QRecall 2014-09-05 18:51:29 Error: package 5 not present / Invalid argument
QRecall 2014-09-05 18:51:29 Message: [NSFileManager removeFileAtPath:handler:]
QRecall 2014-09-05 18:51:29 Warning Unable to open document dagligdags.quanta
QRecall 2014-09-05 18:51:29 path: /Volumes/Safe House/Dagligen/dagligdags.quanta
QRecall 2014-09-05 18:51:29 docType: com.qrecall.repository
QRecall 2014-09-05 18:51:29 could not remove lock file
QRecall 2014-09-05 18:51:29 Error: package 5 not present / Invalid argument
QRecall 2014-09-05 18:51:29 Message: [NSFileManager removeFileAtPath:handler:]


Checking the disk gives no errors. I also tried Drive Genius.

And when running cat in the archive that gives this uplifting result:

archive.quanta user$ cat * > /dev/null && echo "No read problems"
No read problems


Is this a real error or just some missing or unreadable file on my originating HD? I can't delete the .lock file with "sudo rm" either.

This message was edited 2 times. Last update was at 05-Sep-14 15:03

James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1473
Online

Mats,

It’s difficult to guess what’s going on here. If you haven’t already, send a diagnostic report (Help > Send Report).

The archive I/O error would indicate a (possibly transient) drive failure. The fact the disk utility give the volume a clean bill of health is excellent news, and your read test of the archive.quanta file is also excellent. While it doesn’t test the writability of the file, these are all good signs and would indicate (to me) that this was a transient error, probably a bus failure.

The .Lock file is very strange. Is this a local (directly connected) volume? If so, I can’t see anything that would prevent a sudo rm /Volumes/Safe House/Dagligen/dagligdags.quanta/.lock command from failing, beyond something seriously wrong with the operating system or the volume structure. If this is networked volume, then sudo will have no effect and you’ll need to delete the .Lock file (or just repair the archive, which will delete the .Lock file) on the computer that’s directly connect to the volume.

I’d be able to look into the further with a diagnostic report.

- QRecall Development -
[Email]
Mats Jacobson



Joined: 23-Jan-13 07:25
Messages: 6
Offline

James Bucanek wrote:Mats,

It’s difficult to guess what’s going on here. If you haven’t already, send a diagnostic report (Help > Send Report).


OK, just did. Please respond here.

James Bucanek wrote:
Is this a local (directly connected) volume?


FireWire disk. It's a removable 1TB Western Digital Green.

This message was edited 1 time. Last update was at 05-Sep-14 15:13

James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1473
Online

Something is seriously wrong, but I’m not sure what it is.

If I had to guess, I’d say you had volume structure corruption. You said you checked the drive, but I want to make sure you checked the volume the archive is on (not the volume you were capturing).

The initial error was MacOS error -47 (file busy). This makes no sense on a file that’s on a local drive and is already open. Then, your repair actions fail because the stale .lock file can’t be deleted. The error returned was 22. This is either a dsNoPk5 (no package 5) error or EINVAL (invalid argument). Again, neither of these errors make any sense unless something internal to OS X is botched up.

My suggestions would be (a) restart the system, (b) run disk repair on the volume containing the archive, and (c) make sure you are NOT running any anti-virus, disk optimization, or disk virtualization software that might be interfering with QRecall’s ability to read, write, or delete files on that volume. If your external drive is using ownership and permissions, make sure the files belong to your QRecall user and have read and write access. If they don’t, either fix that or turn ownership and permissions off for that drive.

Then try to repair the archive. Repair should delete the .lock file and verify/restore the integrity of the data in the archive.

- QRecall Development -
[Email]
 
Forum Index » Problems and Bugs
Go to:   
Powered by JForum 2.1.8 © JForum Team