Kernel Panic with Mount Error 19

Now here is some interesting stuff (for me, anyway):

This is whatboot looks like:

config-2.6.12-1.1372FC3 memtest86+-1.26 config-2.6.12-1.1378FC3 System.map-2.6.12-1.1372FC3 config-2.6.12-1.1380FC3 System.map-2.6.12-1.1378FC3 config-2.6.9-1.667 System.map-2.6.12-1.1380FC3 grub System.map-2.6.9-1.667 initrd-2.6.12-1.1372FC3.img vmlinuz-2.6.12-1.1372FC3 initrd-2.6.12-1.1378FC3.img vmlinuz-2.6.12-1.1378FC3 initrd-2.6.12-1.1380FC3.img vmlinuz-2.6.12-1.1380FC3 initrd-2.6.9-1.667.img vmlinuz-2.6.9-1.667

Here is what grub looks like:

# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have aboot parbreastion. This means that # all kernel and initrd paths are relative toboot-, eg. # root (hd0,0) # kernelvmlinuz-version ro root=-dev-VolGroup00-LogVol00 # initrdinitrd-version.img #boot=-dev-hda default=0 timeout=5 splashimage=(hd0,0)-grub-splash.xpm.gz hiddenmenu breastle Fedora Core (2.6.12-1.1380FC3) root (hd0,0) kernelvmlinuz-2.6.12-1.1380FC3 ro root=-dev-VolGroup00-LogVol00 rhgb quiet initrdinitrd-2.6.12-1.1380FC3.img breastle Fedora Core (2.6.12-1.1378FC3) root (hd0,0) kernelvmlinuz-2.6.12-1.1378FC3 ro root=-dev-VolGroup00-LogVol00 rhgb quiet initrdinitrd-2.6.12-1.1378FC3.img breastle Fedora Core (2.6.12-1.1372FC3) root (hd0,0) kernelvmlinuz-2.6.12-1.1372FC3 ro root=-dev-VolGroup00-LogVol00 rhgb quiet initrdinitrd-2.6.12-1.1372FC3.img breastle Fedora Core (2.6.9-1.667) root (hd0,0) kernelvmlinuz-2.6.9-1.667 ro root=-dev-VolGroup00-LogVol00 rhgb quiet initrdinitrd-2.6.9-1.667.img

OK, now that we have that out of the way, when I attempt to boot with any version EXCEPT 2.6.12-1.1372, there is a kernal panic and the following messages:

mount: error 19 mounting auto mount: error 2 mounting none umountINITRD-dev failed: 2 Kernel Panic! Not syncing attempted to kill init!

Now here is my guess .. there is a set of instructions in automount which is fscked up.

Here is a look at some boot messages:

smartd - failed automount - no mount points defined lockd shutdown failed rc.sysint failednfslock - lockd failed open ARM faileddev-apm dave

I looked for automount but did not file the script, buttuming maybe I have to create one? Or maybe using the term "auto" in fstab causes this?

Other that these messages and the fact that when I rebooted a couple of days ago (first reboot in about 3 weeks) the whole system worked excellently.

Got advice. ideas, insults? Or you can just plug in a number to save 60 baud bandwidth and paper on my KSR-33 teletype tty device:

1. RTFM ya Maroon 2. Google is your friend 3. Dogpile is also your friend (may be combined with 2) 4. RTFM again 5. You are too cheerful for such an early morning post 6. do man ya maroon 7. *&#^%^#*&^$) (Peter only, please, your invective is quite refreshing) 8. Hey! I've forgotten more about Linux than Linus knows 9. Hey! I AM Linus using my sockpuppet 10. I got yourroot, foole .... heh heh heh

Cheers,

Dave