|peerce||um, if it gets to the grub prompt, its probably past the MBR|
|mshade||well it doesn't get to the grub prompt, perse..|
|peerce||the MBR has two things in it, the first level boot code, and the primary partition table.|
that usually means grub can't read the .conf file in /boot/grub/grub.conf
where /boot is usually /dev/hda1 or /dev/sda1
|mshade||the partition scheme on this box is a single / partition, /boot included|
|peerce||with soft raid?!?|
|rsimpkins||well, it is raid1, that makes it easier.|
so any ideas on how to get it booting again?
|peerce||use hte rescue disk to repair grub ?|
|rsimpkins||mshade: install grub on it?|
|peerce||first fsck it from said rescue|
|mshade||yeah, it's been fsck'd, comes back clean. grub.conf is readable|
|peerce||md5sum the kernel in /boot and compare it with another copy of the same kernel|
|mshade||is there a way to run the repair from a chroot? i've got it mounted on another box right now.|
|peerce||you can tell grub where the disk is to repair|
|marc\cba||$IPT -A udp_inbound -p UDP -s 220.127.116.11/26 --destination-port 10000:20000 -j ACCEPT|
this will allow any udp traffic from 18.104.22.168/26 to any port between 10,000 and 20,000 ?
|rado_||peerce, latest word on 5.0 still around the 15th?|
|peerce||um, not sure on that range notatation|
rado_; i have no idea.
|mshade||anyone have the vmlinuz-2.6.9-42.0.10.EL image to compare my MD5 to?|
|peerce||mshade; which arch ?|
|Evolution||why not use rpm's built in md5sum ?|
rpm -V kernel
|peerce||oh yeah, hah!|
|peerce||i386? not i686 ??|
|Evolution||that will tell you if the permissions, owner, md5sum etc is off.|
if it generates output, then something is different.
if not, then it's fine.
|mshade||k, no output. looks good.|
|action||Evolution wanders off to do useful things (like drink)|
|Evolution||wanders off to do useful things (like drink)|
|mshade||thanks for the rpm -V tip, Evolution|