Craig, Thank you for your help. The lilo.conf file was set with the right boot and I ran lilo with the -v and now the system boots from the hard drive. I have no idea why the -v would make the difference but it must have. This system is my internal router and it does not seem to be routing. So I ran iptables -L to see if the iptables were setup right. This is the output I get: Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- 192.168.0.0/24 anywhere ACCEPT all -- 192.168.1.0/24 anywhere ACCEPT all -- anywhere anywhere INETIN all -- anywhere anywhere Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- 192.168.0.0/24 anywhere ACCEPT all -- anywhere 192.168.0.0/24 ACCEPT all -- 192.168.1.0/24 anywhere ACCEPT all -- anywhere 192.168.1.0/24 Chain OUTPUT (policy ACCEPT) target prot opt source destination INETOUT all -- anywhere anywhere Chain DMZIN (0 references) target prot opt source destination Chain DMZOUT (0 references) target prot opt source destination Chain INETIN (1 references) target prot opt source destination TREJECT all -- anywhere anywhere state INVALID ACCEPT icmp -- anywhere anywhere icmp echo-request limit: avg 1/sec burst 5 TREJECT icmp -- anywhere anywhere icmp echo-request ACCEPT icmp -- anywhere anywhere icmp !echo-request TCPACCEPT tcp -- anywhere anywhere tcp dpt:ssh UDPACCEPT udp -- anywhere anywhere udp dpt:bootpc UDPACCEPT udp -- anywhere anywhere udp dpt:6112 UDPACCEPT udp -- anywhere anywhere udp dpt:6119 UDPACCEPT udp -- anywhere anywhere udp dpt:4000 ACCEPT all -- anywhere anywhere state ESTABLISHED TCPACCEPT tcp -- anywhere anywhere tcp dpts:1024:65535 state RELATED UDPACCEPT udp -- anywhere anywhere udp dpts:1024:65535 state RELATED TREJECT all -- anywhere anywhere Chain INETOUT (1 references) target prot opt source destination ACCEPT all -- anywhere anywhere Chain LDROP (0 references) target prot opt source destination LOG tcp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `TCP Dropped ' LOG udp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `UDP Dropped ' LOG icmp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `ICMP Dropped ' LOG all -f anywhere anywhere limit: avg 2/sec burst 5 LOG level warning prefix `FRAGMENT Dropped ' DROP all -- anywhere anywhere Chain LREJECT (0 references) target prot opt source destination LOG tcp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `TCP Rejected ' LOG udp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `UDP Rejected ' LOG icmp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `ICMP Dropped ' LOG all -f anywhere anywhere limit: avg 2/sec burst 5 LOG level warning prefix `FRAGMENT Rejected ' REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain LTREJECT (0 references) target prot opt source destination LOG tcp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `TCP Rejected ' LOG udp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `UDP Rejected ' LOG icmp -- anywhere anywhere limit: avg 2/sec burst 5 LOG level info prefix `ICMP Dropped ' LOG all -f anywhere anywhere limit: avg 2/sec burst 5 LOG level warning prefix `FRAGMENT Rejected ' REJECT tcp -- anywhere anywhere reject-with tcp-reset REJECT udp -- anywhere anywhere reject-with icmp-port-unreachable DROP icmp -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain TCPACCEPT (2 references) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp flags:SYN,RST,ACK/SYN limit: avg 20/sec burst 5 LOG tcp -- anywhere anywhere tcp flags:SYN,RST,ACK/SYN limit: avg 2/sec burst 5 LOG level warning prefix `Possible SynFlood ' TREJECT tcp -- anywhere anywhere tcp flags:SYN,RST,ACK/SYN ACCEPT tcp -- anywhere anywhere tcp flags:!SYN,RST,ACK/SYN LOG all -- anywhere anywhere limit: avg 2/sec burst 5 LOG level warning prefix `Mismatch in TCPACCEPT ' TREJECT all -- anywhere anywhere Chain TREJECT (6 references) target prot opt source destination REJECT tcp -- anywhere anywhere reject-with tcp-reset REJECT udp -- anywhere anywhere reject-with icmp-port-unreachable DROP icmp -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain UDPACCEPT (5 references) target prot opt source destination ACCEPT udp -- anywhere anywhere LOG all -- anywhere anywhere limit: avg 2/sec burst 5 LOG level warning prefix `Mismatch on UDPACCEPT ' TREJECT all -- anywhere anywhere There seems to be many errors in this output. What would cause these errors and how do I fix them? David -----Original Message----- From: plug-discuss-admin@lists.plug.phoenix.az.us [mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of Craig White Sent: Monday, January 20, 2003 12:23 PM To: plug-discuss@lists.plug.phoenix.az.us Subject: RE: Boot Problems On Mon, 2003-01-20 at 12:05, David Demland wrote: > I for got to include that right now I am getting a kernel panic. > > VFS: Cannot open root device "303" or 03:03 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 03:03 > > David > > -----Original Message----- > From: plug-discuss-admin@lists.plug.phoenix.az.us > [mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of David > Demland > Sent: Monday, January 20, 2003 11:56 AM > To: Plug-Discuss > Subject: Boot Problems > > > I did an apt-get upgrade and got some update code. As part of this update I > got a new iptables package. After rebooting the iptables complained about > needing an update kerenel. So I got the new 2.4.18-k6 kernel and installed > it. During the reboot I remembered that I did not run LILO. The system did > not boot of course. So I tried to boot the old OS and it would not boot > either. I have since used a rescue disk and I can boot and mount the root > drive and I have ran LILO as well as to check some other things out. The > system still will not boot from the hard drive. Any ideas? > .... you're obviously gonna have to use the rescue disk again...pay attention to which partition the / is on (/dev/hda?) edit /etc/lilo.conf to reflect that (been a while since I used lilo) then run lilo again...make sure that when you run lilo, you specify verbose so if it fails to verify something like the location of the root volume...you don't have to reboot to find out. e.g. lilo -v Craig --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss