Lonnie Abelbeck wrote: > > On Mar 2, 2008, at 5:27 PM, John Novack wrote: > >> --snip-- > >> That seems to now work as advertised. >> Thanks much for that as well. >>> Hopefully this info is useful. >>> >> Now for my problem!! >> >> On boot a message flashes by: >> mounting /dev/loop1 on mnt/asturw failed invalid argument THIS MESSAGE CONTINUES TO SHOW UP!! > > John, > > I posted the following (below) about a month ago, maybe this will help. > > Lonnie > > --- > How do I get my keydisk working? > or, in other words, how do I get /mnt/kd/ to point to CF? > > With unionfs there are two methods. > (Note: genunion is what Derrick created in trunk currently.) > --- > Method 1) The /mnt/kd/ path is a part of the unionfs "rw" overlay to > the base "ro" filesystem. > Note: This method requires the "astkd=" NOT be defined in the KCMD. > > If method 1 is your choice, starting from a single, first FAT16 > partition CF (created with runnix.img.gz) , create a second ext2 > partition. Reboot. > > Next, execute the script "genunion /dev/xxx2" and answer "yes" to the > "continue using a keydisk" question. > > Edit your run.conf to define "asturw=/dev/xxx2", remove "astkd=/dev/ > xxxN". Reboot. > Followed this to the letter! > The /mnt/kd/ path will contain your persistent files, including rc.conf. /mnt/kd is EMPTY!
Then tried Method two: > --- > --- > Method 2) The /mnt/kd/ path is traditional mount-point to a separate > ext2 partition. > Note: This method requires the "astkd=/dev/xxxN" be defiend in the > KCMD, and pointing to a valid ext2 partition. > done as well. > If method 2 is your choice, starting from a single, first FAT16 > partition CF (created with runnix.img.gz) , create two ext2 > partitions. Reboot. > > Next, execute the script "genunion /dev/xxx2" BUT answer "no" to the > "continue using a keydisk" question. > Followed to the letter! > Then, execute the script "genkd /dev/xxx3". > One step left out is umount /dev/hda3 > Edit your run.conf to define "asturw=/dev/xxx2" and "astkd=/dev/ > xxx3", reboot. > Did this as well, before rather than after, probably the reason for the umount. > The /mnt/kd/ path will contain your persistent files, including rc.conf. > --- > BUT - THIS MESSAGE STILL shows up at boot: mounting /dev/loop1 on mnt/asturw failed invalid argument This has to be a clue to something, but it isn't clear to me! On the web interface there are errors, nothing relating to /dev/hda2 show up either Any clues? The boot screen at times scrolls by so fast that I could easily have missed something. John Novack -- Dog is my co-pilot ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
