On Fri, 2003-09-12 at 06:33, Sean Estabrooks wrote: > On 12 Sep 2003 00:00:14 -0400 > Jason Dixon <[EMAIL PROTECTED]> wrote:
> > RAMDISK: Couldn't find valid RAM disk image starting at 0. > > Freeing initrd memory: 673k freed > > The initrd is never loaded. Either it is bad or can't be loaded > from the media.. Perhaps even a bad boot parameter? See below. > > EXT2-fs: unable to read superblock > > cramfs: wrong magic > > isofs_read_super: bread failed, dev=09:00, iso_blknum=16, block=32 > > Just sad thrashing about as it tries to boot without the benefit of > a loaded ramdisk. > > > Kernel panic: VFS: Unable to mount root fs on 09:00 > > Oh, looks like you are trying make a bootable tape, bare metal restore > perhaps? I've never tried with Linux allthough i setup some HPUX > systems to do this (Y2K, sigh). Not sure how you go about ensuring > that the initrd is loaded from tape*. Would be interested to know how > you make out with this. Close, but not cigar. I'm actually attempting to modify init.c in the ramdisk for a custom network kickstart. It's actually nothing special, just a timely sleep(30). But I've had lots of problems with the Enterprise spec... particularly with the helpfile sections in %build. They keep crashing on one part of another. Commenting them out (hell, they're not needed anyways) allows the build to complete, but we're obviously left with an unusable ramdisk. -- Jason Dixon, RHCE DixonGroup Consulting http://www.dixongroup.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
