Okay, I found the answer to my “Drives already built” problem in the FAQ under 'disk is already built', but I don't understand what initially caused the problem because I never copied any files onto that drive that I know of since I ran the disk-builder image v3. Perhaps the fids directory was created when I tried to copy the files using and older development kernel v2 or v2.01 when it told me that there were no files. Maybe that version of the firmware couldn't read the newer fs on my drives or there was some other major change to the way data is stored and retrieved between v2 and v2 beta 13? I ran v6 of the disk builder this time. And I also learned that version 2, beta 13 with the hijack kernel I was originally trying to copy files with is a developer kernel, or at least it claims to be in a terminal message.


Edited by Hollywood Justin (08/03/2012 08:21)