AF Token present before mount (Reason is AF Token File Exists before AF Mount)

Hadn't seen this one before, so thought I'd better get it written down, before I forget how to fix it!

Microlite edgemenu giving the following error:

AF token present before mount

This is another historic site using af0/fsp0 attached file systems, and not SharpDrive.

I can't be fussed to change the config, I just need it to work.

In this example the fsp0 gets mounted onto af0. 

Our af0 is /usr/lib/edge/system/mnt/af0

Change directory to your af0 folder and then check with an ls -al

I expect you to see a .edge_af file - delete it!

rm .edge_af

Test!

Update Oct 2014:
I also had the same but the message was:

Reason is AF Token File Exists before AF Mount 

My mount path has also changed in v3 to :
/opt/microlite/backupedge/system/mnt/af0/

Reason is SharpDrive token file exists before mount

More fun fun fun with Microlite BackupEDGE.

A variation on the theme today and again, one that didn't seem to be covered by the FAQ on their support site.

Failed to initalise my disk :

Reason is SharpDrive token file exists before mount

Turns out that somehow I've managed to get a .edge.token in the directory where the disk gets mounted, but prior to the mount taking place!

For me it was 

/usr/lib/edge/system/mnt/sd.sdc1

ls -lt shows me that I had a token file there, even without the disk mounted.

A quick rm and problem is sorted!

Microlite BackupEdge again...

Info: Restore Failed With Exit Code 64

Helpful error message when attempting an Expert restore today - pulling back an inadvertently deleted file from last nights backup created with Microlite BackupEdge

What it actually meant to say was :

Info: Restore Failed - unable to create directory in restore location.

If you try to restore without selecting Flat Restore AND if a file with the same name as the folder you're attempting to restore exists in the Restore To: path, you'll get this error.

To uninstall microlite backupedge / edgemenu


Simply execute the following command from root ::


/usr/lib/edge/bin/edge.remove

AF Unmount Command Failed / AF Token File Missing

Using Microlite BackupEDGE getting the following error:

Command was: "umount /usr/lib/edge/system/mnt/af0"
Reason is AF Unmount Command Failed          

Setup all looks OK in edgemenu - default resource is:
 fsp!fsp0 (/fsp0) (Directory Resource) 

Using USB HDD as backup media, which can be mounted and unmounted without problems.

Found that the backup was actually going into the directory mentioned in the unmount command. There shouldn't be anything in that folder. Removed the contents and ran the scheduled backup.
New error :

Generic System Error
Reason is AF Token File Missing

Initialised the media - didn't help.
Make sure af0 is empty still.

Rebooted - errors gone, backup ran through OK.
Strange!

-update-
seems that removing the following file will negate the need to reboot and is likely the whole cause of the problem - this file is used to track the mount status. It gets 'mounted' even though the device isn't mounted, then it never attempts to mount and creates the backup in the folder, rather than the USB drive.

/usr/lib/edge/system/locks/af0.lck

You DO still need to initialise the media.