On Tue, May 13, 2008 at 07:57:30AM +1000, Alex Samad wrote: > On Mon, May 12, 2008 at 09:49:17AM -0700, Andrew Sackville-West wrote: > > On Mon, May 12, 2008 at 01:14:04AM -0700, Bill wrote: > > > Hi folks, > > > > > Begin: Running /scripts/init-bottom > > > mount: mounting /dev on /root/dev failed: Invalid argument > > > Done. > > > run-init: making initramfs contents: Directory not empty > > > kernel-panic: not syncing : attempted to kill init! > > > > I would focus on that failed mount command. Look in > > /usr/share/initramfs-tool/scripts/init-bottom/ and you will find some > > scripts. Pick through the sh code looking for the appropriate mount > > statement. See if you can debug that thing. > > > > I've mentioned this before, but I don't have clear evidence that it's > > not my fault and so haven't pursued it closely (time is a factor as > > well). Namely, several of the commands appear to be broken or at > > least "different" in the current crop of initrds. I see this cropping > > up in my custom boot scripts that unlock luks partitions in > > particular. at least mount and sed aren't working properly (as I'd > > expect anyway). There may be others. > > > > A > I found it helpful to place busbox entries in certain places (rebuild > the initramfs) and work through the scripts by hand then you can see > what is happening and maybe fix on the fly ++ that very helpful. I need to dig into mine again and see if anything has been fixed by updates. I've been running crippled versions of some of my scripts because of weird bits with mount not working properly... A
Attachment:
signature.asc
Description: Digital signature