[SOLVED] I screwed up my kernel hooks... I think

Question

I upgraded to the newest kernel and when I rebooted... failure. Here's what did manage to printout when I tried:
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60, 0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
registered taskstats version 1
Freeing unused kernel memory: 460k freed
:: Loading Initramfs
:: Running Hook [udev]
:: Loading udev...done
:: Running Hook [resume]
Waiting 10 seconds for device /dev/sda2 ...
Waiting 10 seconds for device /dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29 ...
Root device '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29' doesn't exist, attempting to create it
ERROR: Failed to parse block device ids for '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29'
ERROR: Unable to detect or create root device '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29'
You are being dropped to a recovery shell
Type 'reboot' to reboot
Type 'exit' to try and continue booting
Note: klibc contains no 'ls' binary, use 'echo *' instead
If the device '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29' gets created while you are here,
try adding 'rootdelay=10' or higher to the kernel command-line
ramfs$
Reboot gets me the same and exiting results in a kernel panic.
Ok, so what I think happened. With the old kernel I spent a lot of time screwing around trying to make my comp boot faster. One of the things I did was to delete the [ide] and [sata] hooks from my mkinitcpio.conf. At the time I looked up my computer (Compaq Presario F700) and saw that it had a scsi harddrive and thought that I didn't need the other 2 hooks (Does my laptop need them? All this is a guess based on the fact that it all screwed up and that its probably my fault). Looking back, I don't think I even did that tweak right because I don't remember regenerating the kernel and fallback images. Its probably been sitting there just waiting. So when I updated to the new kernel today it did the regenerating and because I screwed with the settings... failure. It can't read my harddrive anymore.
My questions are this: Am I right in what I did wrong? and how do I fix it?
Thanks in advance.
Last edited by Oliver_Schmid (2009-06-24 00:59:22)

Answer 1

I don't remember where I got that faulty info, but I was a fool for trusting it.
The fallback kernel has the same problem. Probably because it was made using the same hooks.
More updates: I found my recovery disk. Booted into it and mounted my HDD. Changed the hooks in mkinitcpio.conf back to the originals. Ran 'mkinitcpio -g /mnt/boot/kernel26.img' trying to rebuild the image based on correct hooks based on the info on the mkinitcpio page of the ArchWiki. Didn't seem to work though, think I need to reread the man page. Anyone know the command(s) I should be running?