-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I did the reload of Win2K, and getting Linux back was nothing short of a nightmare. As expected, Win2K destroyed the ability to get to SuSE. The real blame for what happens belongs to Microsoft, as they don't know how to play nicely with other systems. There's a bit of blame to go around, though. As expected, the floppy boot disk is useless for getting back to SuSE. It goes to the MBR, which pointed only to Windows. OK, let's go to the boot DVD. I got to the "Boot Installed System" prompt, told it to go. At this point, I got the error message that it couldn't boot all the partitions, look at /var/log/YaST2/y2log for details. Of course, at this point in the process, it's not possible to get to a console to look at the log so as to try to fix it. The only way I got Linux back was to do a new installation, telling Yast that it could only format my /boot partition and not to load anything else. All in all, that's not a bad option as my other partitions / directories were left untouched. It would be kinda nice to have an option on the CD to restore MBR and Grub without doing anything else. Total time to reload Windows with all software: 3 hours. Total time to get Linux running again after this: 4.5 hours. There's gotta be a better way. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/kvpejeziQOokQnARAsRXAJ49rpppKZqzTX9g6rNviVd1mM3oNACbBi28 WxoM8tZ9H73az2GvbPowqC0= =IcOj -----END PGP SIGNATURE-----
Michael Satterwhite wrote:
I did the reload of Win2K, and getting Linux back was nothing short of a nightmare.
As expected, Win2K destroyed the ability to get to SuSE. The real blame for what happens belongs to Microsoft, as they don't know how to play nicely with other systems. There's a bit of blame to go around, though.
As expected, the floppy boot disk is useless for getting back to SuSE. It goes to the MBR, which pointed only to Windows.
OK, let's go to the boot DVD. I got to the "Boot Installed System" prompt, told it to go. At this point, I got the error message that it couldn't boot all the partitions, look at /var/log/YaST2/y2log for details. Of course, at this point in the process, it's not possible to get to a console to look at the log so as to try to fix it.
The only way I got Linux back was to do a new installation, telling Yast that it could only format my /boot partition and not to load anything else. All in all, that's not a bad option as my other partitions / directories were left untouched. It would be kinda nice to have an option on the CD to restore MBR and Grub without doing anything else. Total time to reload Windows with all software: 3 hours. Total time to get Linux running again after this: 4.5 hours. There's gotta be a better way.
Don't depend on the MBR. If you're going to have Linux & windoze sharing a disk, try it this way, using a smart partitioner: /dev/hda1 7.8-200MB for Linux /boot and Grub or Lilo /dev/hda2 1 cylinder reserved for a boot manager (use fully optional, but make the reservation on day 1) (type 11 or 12 will do nicely) /dev/hda3 windoze boot drive C: /dev/hda5 swapper /dev/hda6 / /dev/hda7 /home /dev/hda8+ carved however you like for additional Linux & windoze partitions Now that you've carved the disk up this way, it doesn't matter what gets installed first. Windoze will install to /dev/hda3 as long at it is either marked active or the only suitably formatted primary (fat32 or ntfs), but it won't matter what it does to the MBR. All the MBR has to do is transfer control to the active primary (which all MBR code can do), which you will want to be /dev/hda1 for Linux, but the windoze installer will change to /dev/hda3. That's OK, because changing it back can be done with any number of tools in a jiffy. Doze won't mess with /dev/hda1, which holds your Linux boot manager, Lilo or Grub. So, once you have /dev/hda1 active, you have your Linux boot manager back in business, ready to choose windoze or Linux as you choose on each boot. -- "The fear of the Lord is the beginning of wisdom...." Proverbs 9:10 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/partitioningindex.html
The 03.10.19 at 15:55, Michael Satterwhite wrote:
OK, let's go to the boot DVD. I got to the "Boot Installed System" prompt, told it to go. At this point, I got the error message that it couldn't boot all the partitions, look at /var/log/YaST2/y2log for details. Of course, at this point in the process, it's not possible to get to a console to look at the log so as to try to fix it.
¿No? ¿Did you try ctrl-alt-f1..f4?
The only way I got Linux back was to do a new installation, telling Yast that it could only format my /boot partition and not to load anything else. All in all, that's not a bad option as my other partitions / directories were left untouched. It would be kinda nice to have an option on the CD to restore MBR and Grub without doing anything else.
Lilo saves a backup copy of the original sector on a file, which can be used to restore the original boot before installing lilo. And running lilo from the rescue system will restore the lilo boot. Grub doesn't have an uninstall option, but you can still make a backup copy manually (with dd). There is also a method somewhere to restore grub, but at the moment I have a headache and I don't feel like searching for it. Manually, from the rescue CD, and probably documented - but i agree, it should be easier to find. -- Cheers, Carlos Robinson
Michael Satterwhite <michael@weblore.com> wrote the Oct 19, 2003 8:55 PM:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I did the reload of Win2K, and getting Linux back was nothing short of a nightmare.
As expected, Win2K destroyed the ability to get to SuSE. The real blame for what happens belongs to Microsoft, as they don't know how to play nicely with other systems. There's a bit of blame to go around, though.
As expected, the floppy boot disk is useless for getting back to SuSE. It goes to the MBR, which pointed only to Windows.
OK, let's go to the boot DVD. I got to the "Boot Installed System" prompt, told it to go. At this point, I got the error message that it couldn't boot all the partitions, look at /var/log/YaST2/y2log for details. Of course, at this point in the process, it's not possible to get to a console to look at the log so as to try to fix it.
The only way I got Linux back was to do a new installation, telling Yast that it could only format my /boot partition and not to load anything else. All in all, that's not a bad option as my other partitions / directories were left untouched. It would be kinda nice to have an option on the CD to restore MBR and Grub without doing anything else. Total time to reload Windows with all software: 3 hours. Total time to get Linux running again after this: 4.5 hours. There's gotta be a better way.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQE/kvpejeziQOokQnARAsRXAJ49rpppKZqzTX9g6rNviVd1mM3oNACbBi28 WxoM8tZ9H73az2GvbPowqC0= =IcOj -----END PGP SIGNATURE-----
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Here's how I do it. A small FAT partition (5M or so) to install a boot manager. I use the one from Partition Magic but YMMV. Install Windows using the next partition (D:) as the install drive. If you need you can reinstall the Boot Manager after this point with a floppy to overwrite the MBR. Install Linux on any other Drive/Partition. Install Grub or LiLO on the Linux partition (/boot or / depending on how you want to go) not on the FAT partition with the Boot Manager. The boot manager then sees the Linux partition and a menu entry can be added. Now when the machine boots the boot manager chooses either the Win partition or the Linux partition and GRUB takes over. -- Pat Malone Systems Administrator Mansfields http://www.mansfieldsdesign.co.uk
On 10/20/2003 04:55 AM, Michael Satterwhite wrote:
I did the reload of Win2K, and getting Linux back was nothing short of a nightmare.
As expected, Win2K destroyed the ability to get to SuSE. The real blame for what happens belongs to Microsoft, as they don't know how to play nicely with other systems. There's a bit of blame to go around, though.
Hmm. I installed a machine, installed win98 first, then SuSE 8.0, upgraded the SuSE to 8.2 (reinstall, not upgrade of packages), and then upgraded the Windows to XP home. When I installed XP, it of course took over the MBR. I then booted from the CD, chose boot installed system, it prompted me for which one, XP or SuSE, I chose SuSE, and it booted to 8.2. I then ran the Yast boot Loader module, and it restored Grub, and I was back in business in no time for Linux. Must be something different with Win2K. It doesn't surprise me, Win2K is....well, win2k. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On Sunday 19 October 2003 19:26, Joe Morris (NTM) wrote:
Hmm. I installed a machine, installed win98 first, then SuSE 8.0, upgraded the SuSE to 8.2 (reinstall, not upgrade of packages), and then upgraded the Windows to XP home. When I installed XP, it of course took over the MBR. I then booted from the CD, chose boot installed system, it prompted me for which one, XP or SuSE, I chose SuSE, and it booted to 8.2. I then ran the Yast boot Loader module, and it restored Grub, and I was back in business in no time for Linux. Must be something different with Win2K. It doesn't surprise me, Win2K is....well, win2k.
And I'm the first to say that all my problems were caused by having to workaround Microsoft's arrogant hijacking of everything on the machine. Knowing this is going to happen again (to others as well as me), I'd like to try to put together a procedure to fix it, maybe for the Unofficial FAQ
On Sun, 19 Oct 2003, Michael Satterwhite wrote:
On Sunday 19 October 2003 19:26, Joe Morris (NTM) wrote:
Hmm. I installed a machine, installed win98 first, then SuSE 8.0, upgraded the SuSE to 8.2 (reinstall, not upgrade of packages), and then upgraded the Windows to XP home. When I installed XP, it of course took over the MBR. I then booted from the CD, chose boot installed system, it prompted me for which one, XP or SuSE, I chose SuSE, and it booted to 8.2. I then ran the Yast boot Loader module, and it restored Grub, and I was back in business in no time for Linux. Must be something different with Win2K. It doesn't surprise me, Win2K is....well, win2k.
And I'm the first to say that all my problems were caused by having to workaround Microsoft's arrogant hijacking of everything on the machine. Knowing this is going to happen again (to others as well as me), I'd like to try to put together a procedure to fix it, maybe for the Unofficial FAQ
This happens to me all the time. I usually boot from an emergnecy linux ISO I have, then mount my drives, chroot and grub_install /dev/hda takes care of it right off. I must say, SuSE has a nice option to do all most of this if you boot from their CD, then you just need to do the grub_install /dev/hda after logging in. --- Pine v4.5.3 --- SuSE Linux Pro v8.2 --- Registered Linux User #201684 Machine # 214067 Running Madly Into The Wind And Screaming
If I remember correctly, and it's over a year since I had to do this, but if you boot from the SuSE rescue disk, it gives you an option to restore the MBR setup. On Monday 20 October 2003 07:03, Hemo wrote:
On Sun, 19 Oct 2003, Michael Satterwhite wrote:
On Sunday 19 October 2003 19:26, Joe Morris (NTM) wrote:
Hmm. I installed a machine, installed win98 first, then SuSE 8.0, upgraded the SuSE to 8.2 (reinstall, not upgrade of packages), and then upgraded the Windows to XP home. When I installed XP, it of course took over the MBR. I then booted from the CD, chose boot installed system, it prompted me for which one, XP or SuSE, I chose SuSE, and it booted to 8.2. I then ran the Yast boot Loader module, and it restored Grub, and I was back in business in no time for Linux. Must be something different with Win2K. It doesn't surprise me, Win2K is....well, win2k.
And I'm the first to say that all my problems were caused by having to workaround Microsoft's arrogant hijacking of everything on the machine. Knowing this is going to happen again (to others as well as me), I'd like to try to put together a procedure to fix it, maybe for the Unofficial FAQ
This happens to me all the time. I usually boot from an emergnecy linux ISO I have, then mount my drives, chroot and grub_install /dev/hda takes care of it right off.
I must say, SuSE has a nice option to do all most of this if you boot from their CD, then you just need to do the grub_install /dev/hda after logging in.
--- Pine v4.5.3 --- SuSE Linux Pro v8.2 --- Registered Linux User #201684 Machine # 214067 Running Madly Into The Wind And Screaming
You may also have to change the /etc/fstab file to mount the root and other partitions correctly, because windoze messes everything up. For example if you had the root partition on the /dev/hda3 partition maybe now this partition is /dev/hda2 or else. So you have to change the fstab file. You may also have to change the /boot/grub/menu.lst file to tell to grub where can it find the root partition. Zsolt Hemo wrote:
On Sun, 19 Oct 2003, Michael Satterwhite wrote:
On Sunday 19 October 2003 19:26, Joe Morris (NTM) wrote:
Hmm. I installed a machine, installed win98 first, then SuSE 8.0, upgraded the SuSE to 8.2 (reinstall, not upgrade of packages), and then upgraded the Windows to XP home. When I installed XP, it of course took over the MBR. I then booted from the CD, chose boot installed system, it prompted me for which one, XP or SuSE, I chose SuSE, and it booted to 8.2. I then ran the Yast boot Loader module, and it restored Grub, and I was back in business in no time for Linux. Must be something different with Win2K. It doesn't surprise me, Win2K is....well, win2k.
And I'm the first to say that all my problems were caused by having to workaround Microsoft's arrogant hijacking of everything on the machine. Knowing this is going to happen again (to others as well as me), I'd like to try to put together a procedure to fix it, maybe for the Unofficial FAQ
This happens to me all the time. I usually boot from an emergnecy linux ISO I have, then mount my drives, chroot and grub_install /dev/hda takes care of it right off.
I must say, SuSE has a nice option to do all most of this if you boot from their CD, then you just need to do the grub_install /dev/hda after logging in.
--- Pine v4.5.3 --- SuSE Linux Pro v8.2 --- Registered Linux User #201684 Machine # 214067 Running Madly Into The Wind And Screaming
participants (8)
-
Carlos E. R. -
Felix Miata -
Hemo -
Joe Morris (NTM) -
Lukacs Zsolt -
Michael Satterwhite -
Patrick Malone -
Örn Hansen