wierd bootup problem
Hi,
I'm getting this absolutely whacky bootup problem ever sice I upgraded to fedora core 2.I have a dual partition system with debian woody.Each time I shutdown my system from fedora,i can't boot it the next time I power up.The system simply stops after doing the boot checks.I don't get a login prompt and HD led goes off showing no hard disk activity.Fedora boots up fine after power on if I shutdown the system from Debian.I'm totally flumoxxed as to what the problem could be. One possible reason could have been that I had allocated only 100 megs to the boot partition.But when I saw that the boot image was very small,I modifie the boot to 15 megs.But even when I had a 100 mb /boot,I used to get the same problem.Please advise,coz to access fedora I have to first boot to debian and then back. |
What bootmanager are you using, and can you post the contents of it here? Being able to see that data would be helpful in trying to diagnose the issue. -- J.W.
|
so you run fc, reboot fc, nada
but you run fc, reboot to debian, reboot to fc, presto? neat ... erm ... i'm thinking framebuffer/xserver try changing your /etc/inittab to go to a default run level of 3 instead of 5 in FC, if you get something that way ... i'm not sure what to do next ... hee hee hee alternatively i was just thinking, could be that ... do you have two /boot ? ie one for FC and one for debian ? or is your lilo.conf file (or grub) pointing at the right partitions for the corresponding /boot directories? |
u seem to have duplicate /boot partitions.....
check wchich one is being loaded and see the lilo.conf or grub.conf files that are being used... if u cant fix the problem then do linux rescue ....in the distro whose /boot is being mounted each time! |
I'm using GRUB as my boot manager.I tried checking the grub.conf file,but there seemed to be a single boot image in the conf file.To throw more light on the issue,when I upgraded to core 2 from core 1,during the install process i got an error saying that ""a previous bootloader had incorrectly configured the boot image.You may choose to ignore but this can cause problems later.Ï ignored it coz I thought that the install would wipe out the previous boot image and create new one.But now I do have problems.What can I do to correct this error?
|
copy one of the /boot partitions to a common partiotion or a cd ...i know when u r in one of the distros accsseing the other /boot is a pain coz it wont be mounted....but u have to some how make a bck up of those files and then delete that partition and copy non duplicate files to the existing /boot then boot with the first fedora cd
then just before anaconda starts up type linux rescue and then type chmod /mnt/sysimage and rescue the other distro i.e make a proper mbr.... |
All times are GMT -5. The time now is 12:13 PM. |