Aperture Library Issues on NAS - Advice Needed

Question

List-
Need some practical advice here. I've got a 90GB Aperture library that resides on a NAS (QNAP 419P II) that is experiencing major issues. Understood that having the library live on a non-HFS+, non-local drive is not advised by Apple, but it's been there for two years with no issues to speak of.
I had a power failure occur that seems to have done some damage to the library in some way. Upon opening the library, I got an error that said that there were inconsistencies with the file and that it needed to be repaired. I repaired it, and noticed something strange. In almost all files, the picture resolution was poor and both the camera and lens information was gone--in addition to the fact that the Adjustments capability was disabled.
I ran the Aperture first aid and ran all three processes--concluding with the full library rebuild. It looked to be successful and resolution, previews, and picture info returned--but halfway through the preview reprocessing the process just stopped and the beach ball of death ensued. I let it run overnight and it never recovered. I had to force quit and now if I reopen the file it say that there are inconsistencies and that the library needs to be repaired, which won't help.
I also tried to move the library off of the NAS an onto the local drive, but encountered an Error - 50 message--something that apparently is well known in the NAS world where Mac permissions get screwy when dealing with non HFS+ drives.
I have a backup of the original library, but it is sitting in a cloud repository (CrashPlan) that will take time and money to restore.
All of the masters are intact in the Aperture directory, and I have very few major adjustments made to any photos. Aperture is really just a repository for me.
So any practical advice would be appreciated as to how I can create a new local Aperture library and get all of the existing photo files there. I am pretty much giving up on the idea of getting the existing NAS-based library to work properly, so this is more of a real-world question on how to create a new library and eliminate whatever issues there are with the other Aperture files. It looks like everything in the Aperture package is in place, but the library itself is just malfunctioning.
I am also considering moving everything into iPhoto as well, as Aperture may simply be more than I need for my usage. If is is faster and a but simpler to manage, that could be the right answer as well.
Thanks in advance for any ideas or guidance.

Answer 1

The problem is most likely with the library itself being located on the NAS.
But you can have a hybrid solution where the library is located on your internal drive while the actual image files are located externally, eg on your NAS. Image files stored within the Apeture library are called "managed" while image files stored externally are called "referenced". Whichever approach you take, the process is the same:
If you try to make a new Library from your masters, you will lose your project structure. The resulting mess will be in accordance to how you created your projects. Basically, if you look at your Masters folder, that's what you'll end up with when you import your masters. If that isn't a problem, the process is simple
Step 1: Prep.
Move or copy your masters out of the library bundle to a folder (to make them more accesible in finder).
Step 2: Create new library.
Within Aperture, from the File menu "Switch to Library -> Other/New..." to create a new Library on your internal drive.
Set the preferences to indicate previews/faces etc. I'd turn these off for now as they will slow you down.
Step 3: Import your images.
Within your new library, File -> Import - Folders as Projects. This gives you a dialog where you specifiy what and where to import.
If you choose "Import folders as: Folders and Projects" you will get a folder structure that matches the Masters folder, with projects at the end of the chain with names like 20120213-200100.
If you choose "Import folders as: Projects and Albums" you will get a single Project called "Masters" with a folder and Album structure that matches the Masters folder.
Neither of these will look particularly great. If you want to avoid this mess, here's what I'd try.
Fix your library again like you did before. After the rebuild, go to the Aperture activity window (SHIFT + CMD + 0) and cancel the preview generation process before it has chance to hang. This should give you a sem-functional library, hopefully functional enough for the next step:
Select all images and use File -> Relocate Original to move your original files out of the library. During this process you can specify that the originals are stored in sub-folders that match the project name, within a parent folder if required.
This gives you a much neater structure for importing into your new library where the projects will get the folder names (which will be your existing project names). It may not be perfect, for example if you have the same project name in different folders and don't/can't segregate them, but it's a lot cleaner than just importing your masters folder.
Andy