[syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init!

Kosolapov Dmitry dk at farpost.com
Sun Apr 9 01:53:01 PDT 2006


Eli Stair wrote:
> 
> Guess: your kernel was built with an initramfs that contains an init
> script... the init script is doing a switch_root to some
> hardcoded/defined/detected local device which doesn't exist (or isn't
> bootable) in your situation.  I'm _guessing_ that you're trying to do an
> old-school nfsroot mount.  That doesn't work anymore, as of 2.6.15. 
> 
> See: ramfs-rootfs-initramfs.txt
> 
> Or I could be entirely off base, I'm basing this scenario on the little
> info you gave... not sure that "root=IP" does in fact do anything.
> (nfsroot= maybe?)  Most likely, this doesn't come down to an issue with
> syslinux, it seems to have done its job
> 
> :)
> 
> /eli

And problem may be in kernel 2.6.16.
# lsmod
nfsd                  223825  15
exportfs                9921  1 nfsd
lockd                  63145  2 nfsd
nfs_acl                 7745  1 nfsd
ipv6                  270081  18
parport_pc             31149  1
lp                     16897  0
parport                40073  2 parport_pc,lp
autofs4                23365  1
rfcomm                 45141  0
l2cap                  32833  5 rfcomm
bluetooth              56357  4 rfcomm,l2cap
sunrpc                150373  11 nfsd,lockd,nfs_acl
video                  19141  0
button                 10577  0
battery                13381  0
ac                      8901  0
ohci1394               38917  0
ieee1394              300697  1 ohci1394
ohci_hcd               25949  0
ehci_hcd               36429  0
snd_intel8x0           36061  0
snd_ac97_codec         92769  1 snd_intel8x0
snd_ac97_bus            6465  1 snd_ac97_codec
snd_seq_dummy           7749  0
snd_seq_oss            35365  0
snd_seq_midi_event     11201  1 snd_seq_oss
snd_seq                54413  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device         13005  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            52721  0
snd_mixer_oss          21441  1 snd_pcm_oss
snd_pcm                88517  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer              28101  2 snd_seq,snd_pcm
snd                    56353  9
snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq,

snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore              13729  1 snd
snd_page_alloc         14665  2 snd_intel8x0,snd_pcm
r8169                  33993  0
dc395x                 38609  0
dm_snapshot            20717  0
dm_zero                 6081  0
dm_mirror              25205  0
ext3                  133705  2
jbd                    60885  1 ext3
dm_mod                 57429  6 dm_snapshot,dm_zero,dm_mirror
sata_sis               11973  0
libata                 62801  1 sata_sis
sd_mod                 22081  0
scsi_mod              136013  3 dc395x,libata,sd_mod

So ext3-support is module and we can't do remote mount of this FS.
But, when I've compiled my own static kernel (without modules) and tried
to boot it remotely I got error: Image is corrupted. It even didn't try
to download to the client PC.
My actions before: when kernel was compiled, I put it into /tftpboot
Nothing more.
What should I do? Is problem actually in it?




More information about the Syslinux mailing list