Jerry, et al., Sorry for the delay in following up with this issue, I had some fires to put out. It looks like it is not going to be feasible for us to upgrade to Anaconda >= 11.5.0.40. There are just too many dependencies in the new one that would need to be upgraded beyond what was in F10. I can live without the label fixes in that revision. I am still having the problem mounting stage2, however. Can you please clarify your statement "Think you might be running into a squashfs change."? What is the squashfs change that I'm hitting? How can I get around it? Thank you, Jason Maestri On 4/7/09 5:32 PM, "Jason Maestri" <jmaestri@xxxxxxxxxxxxxxxxxx> wrote: > Jerry, > I am using 11.4.1.63 out of fedora. That explains a lot! I¹ll update > directly. > > Thanks for the help! > > --Jason > > > On 4/7/09 5:31 PM, "Jerry Vonau" <jvonau@xxxxxxx> wrote: > >> On Tue, 2009-04-07 at 14:42 -0700, Jason Maestri wrote: >>> List, >>> >>> In order to explore the behavior of Anaconda, and pave the way for changes >>> which would allow one to install from a device specified by it's "LABEL" or >>> "UUID", >>> >> >> That is fixed in version 11.5.0.40 of anaconda, what are you testing >> with? >> >>> I am currently trying to install from a known configuration with a >>> specified hard drive. I am installing with my kickstart file inside of my >>> initrd, and my installation media is a hard drive connected to the system >>> via USB. My kernel line (in grub) is as follows: "kernel vmlinuz >>> ks=file:/kickstarts/install.ks stage2=hd:/dev/sdd1:/images/stage2.img". >>> >>> As near as I can tell, this is a valid installation method, with valid >>> syntax. I am, however, unable to perform the install. The error I am >>> seeing indicates that the system was unable to mount the stage2 image >>> because the loop device it was attempting to use (/dev/loop0) does not >>> exist. Here is the actual text of the error: >>> >>> 16:04:21 INFO : mounting device sdd1 for hard drive install >>> 16:05:51 INFO : Path to stage 2 image is /mnt/isodir/images/stage2.img >>> 16:05:51 ERROR : failed to mount loopack device /dev/loop0 on >>> /mnt/runtime as /tmp/install.img: /dev/loop0: No such file or directory >>> 16:05:54 INFO : unmounting loopback /mnt/runtime /dev/loop0 >>> 16:05:54 ERROR : LOOP_CLR_FD failed for /mnt/runtime /dev/loop0: Bad >>> file descriptor >>> >> Think you might be running into a squashfs change. >> >>> Can anyone please help me with this. Am I doing something wrong, or does >>> this code just not work? Has anyone else had success with a similar setup? >>> >>> Thank you, >>> Jason Maestri >> >> I have had luck installing the beta isos, using the updates.img from: >> https://bugzilla.redhat.com/show_bug.cgi?id=491781 >> My boot string was: >> ks=hd:LABEL=XSRepo:/jv.cfg stage2=hd:LABEL=XSRepo:/images/install.img >> repo=hd:LABEL=XSRepo: >> >> Jerry >> >> >> >> >> _______________________________________________ >> Anaconda-devel-list mailing list >> Anaconda-devel-list@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/anaconda-devel-list >> > -- Jason C. Maestri Senior Software Engineer Solera Networks O (801) 623.5192 C (801) 867.7654 http://www.soleranetworks.com The information in this e-mail and in any attachments is confidential and may be privileged. If you are not the intended recipient, please destroy this message, delete any copies held on your systems and notify the sender immediately. You should not retain copy or use this e-mail for any purpose, nor disclose all or any part of its content to any other person. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
