Kernel Panic on PXE Boot - previously working MDs

[cafedumonde]

Hi...

Upon adding a new MD, I got the following error after the MD rebooted in the middle of the creation process.

kernel panic - not syncing: Attempted to kill init!

After this event, two previously existing MDs won't boot either, producing the same error. So, all of my MDs are down and I can't add new ones. The error appears after the initial Kubuntu splash screen.

All of my MDs are Dell GXE 270s, which I've used without issue under 710 and 810 with the onboard Intel NIC. I've seen other posts about this problem in relation to unsupported NICs but I really don't think that thats the issue here, given that two of the MDs worked previously. Help!!

CDM

[Marie.O]

Check to see if the links from /tftpboot/<device-id>/vmlinuz and initrd point to existing files

[cafedumonde]

Files are as follows. They seem to exist.

/tftpboot/61:
lrwxrwxrwx 1 root root   56 2011-05-23 20:33 initrd.img -> /usr/pluto/diskless/61/boot/initrd.img-2.6.27-17-generic
lrwxrwxrwx 1 root root   53 2011-05-23 20:33 vmlinuz -> /usr/pluto/diskless/61/boot/vmlinuz-2.6.27-17-generic


/usr/pluto/diskless/61/boot:
lrwxrwxrwx  1 root root      56 2011-05-23 20:33 initrd.img -> /usr/pluto/diskless/61/boot/initrd.img-2.6.27-17-generic
-rw-r--r--  1 root root 8516695 2011-05-23 20:34 initrd.img-2.6.27-17-generic
lrwxrwxrwx  1 root root      53 2011-05-23 20:33 vmlinuz -> /usr/pluto/diskless/61/boot/vmlinuz-2.6.27-17-generic
-rw-r--r--  1 root root 2252720 2010-03-11 23:56 vmlinuz-2.6.27-17-generic

[Marie.O]

Thanks for the info. I guess, there is a different problem on your system. no idea what it might be.

[purps]

I had a similar problem when I accidently pressed a non-functioning button on the power menu. I believe the button is for switching to and from an OS on a local hard drive, if you have one installed, which I do not, hence it messed up.

Anyway, the solution for me was to select "net" and click "reboot" in the restart menu in web admin. Sorry if this doesn't work for you; it's a complete guess on my part.

You tried rebuilding the images I take it?

Cheers,
Matt.

[cafedumonde]

My Bad.

I was using an old router on my network as a switch but didn't turn off DHCP. The core was correctly responding to the PXE broadcast but then the router was providing the IP on the second stage reboot during installation.

Everything is working now as it should.

Thanks for the thought cycles and I apologize for the waste of bandwidth.

Chris