linux issue

canaancanaan Member Posts: 46 ■■□□□□□□□□
I'm reformating a PC that had linux redhat on it. I ran fdisk and formatted the hard drive with no problems.
However, when I'm installing Win 2000, after the first reboot I get a blank screen with "LI" on top of it and it hangs.

Would anybody know a way around this.

Thank you in advance


  • Ricka182Ricka182 Member Posts: 3,359
    You could always try a low-level format. That will bring the disk back to factory level.
    i remain, he who remains to be....
  • RussSRussS Member Posts: 2,068 ■■■□□□□□□□
    Ummm - MS fdisk is kind of hopeless in my opinion. I use System Commander to do my disk preparation for just about everything these days.
    FIM website of the year 2007
  • Ricka182Ricka182 Member Posts: 3,359
    True, M$ is worthless.....a good 3rd party program is Partition Magic 8.0.
    i remain, he who remains to be....
  • skaeightskaeight Member Posts: 130
    Redhat's install program will partion and format your drive for you. It sounds like you may have problem with your bootloader (grub, or lilo). The config file probably wasn't written properly and it doesn't know where your kernel is.
  • DisleyDisley Member Posts: 13 ■□□□□□□□□□
    I cant remember how LILO displays its errors now, but the number of letters displayed tells you where the problem lies (but i cant remember them exactly ><)

    Are you just removing RedHat completely to put Win2k onto it? If so you should be able to partition the drives just by putting the installation CD in and moving through it (i hardly ever bother using fdisk for partitioning, at least not with any distros that include their own partitioning functions)
  • xeviousxevious Member Posts: 59 ■■□□□□□□□□
    try fdisk /mbr to clean the master boot record.
  • mwgoodmwgood Member Posts: 293
    According to the book "Linux Administration..." this normally means that the entire boot partition doesn't exist in the first 1024 cylinders - which means having to repartition and reinstall.
  • rcooprcoop Member Posts: 183
    It looks to be the boot loader within the master boot record (MBR) that is either damaged or has just been removed without replacing the original boot strap of the primary partition.

    If you do not want to dual boot with another OS, then you should just need to repair the master boot record of the primary hard disk.

    If you have a DOS/Win95/98 boot disk with FDISK on it xevious' recommendation of FDISK /mbr will most likely fix the problem.

    Also, if you want to do it using Win2000/XP, just boot using the installation CD and go into recovery console. Once at the recovery console command prompt, use the FIXMBR command and that should work as well. If you are still having problems you might also use recovery console's FIXBOOT command to write a new partition boot sector on the system partition (system drive).

    If you are planning to dual boot between multiple OSes I also would recommend using the third-party product System Commander.

    Take Care,
    Working on MCTS:SQL Server 2005 (70-431) & Server+
  • canaancanaan Member Posts: 46 ■■□□□□□□□□
    Thanks guys for all your replies. They were all informative.

    As xevious and rcoop recommended, "Fdisk /mbr" seemed to have fixed the problem.

    Thanks again.
  • infosecboyinfosecboy Member Posts: 6 ■□□□□□□□□□
    That is because the old boot info was still resided in the MBR. You can try fdisk /mbr to restore the standard MBR. I normally use AEFDSK and it works 98% of the time. Do a GOOGLE search to download AEFDSK.
  • GhentGhent Member Posts: 310
    Fdisks debug will fix anything short of a physically destoryed disk. Check out this link to see how to use it.
    Prais'd be the fathomless universe, for life and joy, and for objects and knowledge curious.' Whalt Whitman
  • GhentGhent Member Posts: 310
    Oops, accidentally subimtted duplicates. :)
    Prais'd be the fathomless universe, for life and joy, and for objects and knowledge curious.' Whalt Whitman
Sign In or Register to comment.