how to load linux or win from GRUB after installation gone bad
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It makes sense that XP doesn't show your D drive, as it can't understand the file format of ext2, ext3, reiserfs, etc. that Linux uses. This shouldn't affect use of XP at all and will act to keep Linux safe from being effected by XP once you have reistalled it.
As to why your CD drive is gone, it does seem strange that it disappeared after installing Mandrake. Maybe you got bit by the Mandrake 9.2/LG drive bug that is mentioned above? What brand of PC do you have? Dell, for instance, uses a lot of LG drives in their systems.
Finally, can you open the case a verify that the CD drive is plugged in and hooked up to power? I know you didn't open the case, but stranger coincidences have happened before. Also, if you can pull out the drive to find the manufacturer, then that could help to confirm/dispell the LG problem mentioned above.
well i checked the mandrake site and i think that i got hit with the drive problem, i m not sure cause i haven't open the box to check if i have LG or if there is a cable connection issue. i also read that the same exact thing happen to someone on computing.net so i might just have to buy a new CD-ROM. i m going to check the box 1st. But my problems still are that i m still missing the linux partition and that in order to boot into windows i have to ever commands in the GRUB screen, it wouldn't start automatically. sorry to be a pain but i m lost here... thanks guys
To KDE4me , check : http://support.microsoft.com/support...s/Q69/0/13.ASP
'fdisk /mbr ' doesn't touch the partition table ; it simply rewrites the master boot record (for the whole drive), which is a simple piece of code at the beginning of the drive. As the Windows partition is usually already active this allows you to reboot straight into Windows. Like you said I advise again running MS fdisk straight w.o. options as it got the usual habit of rewriting the partition table by messing up everything not MS.
The thing you have lost is the ability to reboot into the other systems. But that's simply a matter of reinstalling a loader (Lilo, grub,..).
As it happens in Mario's case the Grub loader was correctly installed so rewriting the mbr was not immediately necessary .
To Mario :
for hardware problems the first thing to check in Windows is the Device Manager. The items with problem are expanded and there is a short comment under properties. You can try deleting the item and reboot and back to Device Manager to see if that helped..
where path/to/kernel is your distro's path to the kernel that you want to boot. For my slackware grub installation it is "boot/vmlinuz" but I have no idea for Mandrake. Maybe someone else can fill that in? You could also try to reinstall the mbr from inside of XP, which would stop you having to re-enter the boot info everytime, but it would mean that you won't get linux fixed until you have a working CD rom again. Look for disk management tools inside of XP if you want to try this. I have no real idea where they are, as I barely touch XP and no longer have to support Windows users at work. Again, maybe someone else can point you to them. Otherwise, I'll try to remember to take a look at an XP setup when I am back at work.
Finally, the links from off of the Mandrake page above lead to LG's site where you could get a program to re-flash and repair your existing CD drive. It required use of a DOS floppy (which they even provided for download) though, and you mentioned not having a floppy drive so things could get a little convoluted... Also, maybe try removing any non-working CD drives from Windows and see if they are redetected, as cdlen suggested above.
Good luck. Remember, you don't have to just re-install/replace everything. It is probably the fastest fix, but then you don't learn as much and you did choose to run linux to learn, right?
Thanks PbO, i tried to detect my CD drive with many options from windows server03 and nothing...i ll just gonna have to get a new cd-rom to get linux back...i m gonna stay with suse i think, i do wanna try slack i keep hearing good things so. i doesn't bother to manually boot windows but i would be nice to know how to make it boot automatically... i ll have to research that. linux intrigues me and i want to learn all i can. thanks a bunch.
Distribution: RedHat 9.0 / Slackware 9.0/ FreeBSD 4.8 / Solaris 8 x86 / Mandrake 9.0
I double checked what I said and reaffirmed my belief that the MBR does contain the partition information. I believe what you are confused with is the GRUB loader booting. I believe GRUB refers to the MBR when starting an OS on a partition, and GRUB per se does not contain any actual partition geometry for the disk. Here are some of the references I found by doing a quick http://www.google.com/linux on >> master boot record partition information <<
Note: The following advice will completely wipe your Master Boot Record,
>>>>which contains all your partition information.<<<< DO NOT DO THIS unless you
know that this is exactly the result you want - it will leave your HD in
an unbootable state, in effect bringing it back to "factory-fresh", i.e.,
empty of data and requiring partitioning and formatting.
The Master Boot Record (MBR) is the information in the first sector of any hard disk or diskette that identifies how and where an operating system is located so that it can be boot (loaded) into the computer's main storage or random access memory. >>>>The Master Boot Record is also sometimes called the "partition sector" or the "master partition table" because it includes a table that locates each partition that the hard disk has been formatted into.<<<<< In addition to this table, the MBR also includes a program that >>>>reads the boot sector<<<< record of the partition containing the operating system to be booted into RAM. In turn, that record contains a program that loads the rest of the operating system into RAM.
All I said to mario was to switch the boot sector on the drive so that Windows would load up so he could assess the situation and backup his Windows information if it hadn't already been fried.
Okay, my XP is on a RAID array, it is also the system boot (MBR) drive. Now, when configuring GRUB to point to a loader- or hard disks. Does it count the physical disks in the computer when considering (hd0,0) or does it take into effect RAID arrays- It would make a significant difference in my case because it's currently set to (hd2,2) which is 3rd partition of 3rd harddisk if Im correct (and I hope I am). Should it be pointed at (hd1,2)?
To KDE4me :
You're perfectly right when you say that the mbr contains the partition table. Just have look at : http://www.ranish.com/part/primer.htm
I have never argued the fact either. What i have said is that using :
reinstates the default Windows loader (the IPL on Ranish's page) WITHOUT modifying the partition table. Quite often MBR is used instead of IPL ; this is not strictly correct but lot of people know the word MBR when very few know the word IPL. When using the dd command (in your reference)to rewrite the first 512 bytes you rewrite both the IPL and the partition table.
I refer again to the MS site above: (http://support.microsoft.com/default...NoWebContent=1)
"Fdisk has an undocumented parameter called /mbr that causes it to write the master boot record to the hard disk without altering the partition table information. "
By the way 'fdisk /mbr is the old Win way, for XP it is 'fdiskmbr' (pop the CD and go into the recovery console).
Again i really recommend not to launch fdisk without parameter (and go into interactive mode) because the result on non-MS partitions is completely unpredictable and often destructive ! And here this is by rewriting the partition table !
To set a primary active you could use Ranish's Partition Manager (among many others). But if the IPL on the MBR is fried it doesn't help at all..
Distribution: RedHat 9.0 / Slackware 9.0/ FreeBSD 4.8 / Solaris 8 x86 / Mandrake 9.0
Thanks for that, I'll have to try to install GRUB onto my IPL (aren't you proud! :-> ) next time... And pray and cross my fingers that I didn't just overwrite my MBR's patition table and have to spend hours fixing it up!!! Actually while I was searching, I found an interesting site with programs to rewrite the IPL, guess partition tables etc. here: http://plug.linux.org.au/~steve/mbr.html
cdlen you are going on my linuxquestions buddy list!
PS: No longer use KDE that much, use GNUStep(based on NeXT) or vanilla X with a wm, but now I'm stuck with this damn name!!! KDE and GNOME are too much bloat for me.