No loopback devices are mounted prior to running mkinitrd. I suppose that doesn't preclude mkinitrd tripping over itself, though. Zach ----- Original Message ----- From: "Christoph Wickert" <christoph.wickert@xxxxxx> To: "fedora (rhl) Liste" <fedora-list@xxxxxxxxxx> Sent: Thursday, December 04, 2003 10:51 PM Subject: Re: Error: RAMDISK: incomplete write > Am Fr, den 05.12.2003 schrieb Zach Wilkinson um 04:18: > > Built custom kernel from arjanv 11.1.99 > > ran "mkinitrd /boot/initrd-2.6.0-0.test11.1.99custom.img > > 2.6.0-0.test11.1.99custom" as per usage > > Updated grub.conf > > > > When booting I get: > > RAMDISK: Compressed image found at block 0 > > RAMDISK: incomplete write (-1 != 32768) 4194304 > > Kernel Panic <blah blah> > > > > /lib/modules/2.6.0-0.test11.1.99custom/ looks OK, but who knows... > > > > WTF ;) > > Do you have some loopback device mouted??? > > Unmount them before mkinitrd. > > Christoph > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list >
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
