This is a discussion on Suse 9.1 keeps corrupting MBR for Windows (need help with GRUB) within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> On Thu, 19 Aug 2004 00:01:32 GMT, res <suse.rtoledo@spamgourmet.com> wrote: >On 17 Aug 2004 09:33:21 -0700, szcs@abuse.co.uk (Sz. Csetey) ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Thu, 19 Aug 2004 00:01:32 GMT, res <suse.rtoledo@spamgourmet.com> wrote: >On 17 Aug 2004 09:33:21 -0700, szcs@abuse.co.uk (Sz. Csetey) wrote: > >>Hello, >> >>Mark Burgo <mfburgo@atlanticbb.net> wrote in message >>> First, You should have searched google groups or the suse site. In version >>> 9.1 of suse ( actually it is a kernel 2.6 issue ) there was an issue with >>> repartitioning NTFS file systems. >> >>It's not NTFS related because sometimes it happens on FAT32 too and >>even if one used commercial partitioner before installation or a >>second disk. Parted corrupts the partition table on 2.6 kernels. >> >>SUSE fix: >>http://portal.suse.com/sdb/en/2004/0...booting91.html >> >>Parted fix: >>http://lists.gnu.org/archive/html/bu.../msg00046.html >> >>> The problem you ran into has happened to >>> many and the Suse Support Database has a write up on the problem. The >>> actual issue is ( if I remember correctly ) the 2.6 kernel and versio of >>> parted with suse 9.1 reports the wrong fs type and sets it incorrectly on >>> the disk. This causes the partion to be un bootable via grub or lilo... >> >>Parted changes the geometry in the partition table therefore Windows >>can't boot anymore in some rare cases. Not even if it's reinstalled. >> >>> Second, If you ever need to get the windows MBR back boot into Windows from >>> the CD exit the install process and run fdisk /MBR. This rewrites the MBR >>> to the windows standard. >> >>Rewriting the MBR doesn't help because the problem is the corrupted >>partition table. But the above SUSE fix should work. > >Is it possible to downlaod this 1.6.12 ? and find wich of the 5 cd's >holds this program and re-burn a new cd with the new file in it like >they do with Windows slip streaming a SP2 release? > > >PS. after reading those 2 links posted by you helpful folks, I went >back and rebooted and checked my BIOS and it seems it's on AUTO and >when I change it to LBA on the clean new install/repartition I just >did the geometry is seen differently and the machine will not BOOT. > > I tought that BIOSes changed years ago to the default of LBA, >and that is how they dealt with these huge drives, AAMOF one the >BIOS updates at Iwill for the MPX2 (this machine) is for updating it >to see larger drives. Anyways looks like I can start fresh one more >time with the BIOS in LBA and repartion/install it all or gamble and >re-burn a CD with the correct PARTED and see if IT gets along with the >AUTO setting and then if that fails start with a fresh repartitioning >in LBA. > >any more positive advice is welcomed. > >thanks to all that have given your valuable advice. since I set these >messages with the x-no archive OFF future searches on this subject >in GOOGLE will be easier to find I hope Sorry for the post on post, but I left out a observation and need advice/opinions. I noticed parted 1.6.12 looks to me as if it was released August 16, 2004, YET the Suse site points to a download work around that, which I downloaded and when I open the .iso and look in linux\i386-9.1\install\instsys\usr\lib\libparted-1.6.so-006 it's dated 05/19/2004 and the name does not include the 12 in the build name is this a PRE- 12 workaround ?? I looked around at http://mirrors.sunsite.dk/gnu/parted/ and it shows a date of 8/16/2004 I looked around at Suse's ftp site but did not find a parted file at all. |
| |||
| On Wed, 18 Aug 2004 10:03:46 GMT, "Luc" <luc.rems@nospam_pi.be> wrote: > >"res" <suse.rtoledo@spamgourmet.com> wrote in message >news:b3g2i09vfl3jvs20rci5k96d2clo3bjose@4ax.com.. . >> Hello everyone, I thought I would share my experiences >> with Suse Linux 9.1. >> >> Before I do, I want you to know that I searched a lot thrugh >> GOOGLE, for GRUB howto's , read the man pages, and on several online >> forums. From what I found it seems the "usual" problem is where >> Windows trashes GRUB and you can't boot into LINUX or GRUB IS SOMEHOW >> CORRUPTED. >> >> My problem is the OPPOSITE, GRUB boots up and it can boot into >> Linux, but can NOT boot Windows. Now most Linux users will tell me >> hey that's not a problem > ><snip rest> > > >Go into your PC's BIOS and change the hard disk configuration from AUTO to >LBA mode. >This should fix the problem. > here's an update. I left the BIOS in the AUTO setting and downlaoded the SUSE patch from ftp://ftp.suse.com/pub/suse/i386/upd...1/misc/parted/ which is discussed here http://portal.suse.com/sdb/en/2004/0...booting91.html I tried installing Suse doing the F6 and a image burnt on a CD and loaded the PARTED driver from the top lonk above when Suse tries to re-boot after installing the base from the fist CD, it comes up with the grub command and won't go any further. I went ahead and rebooted and grub> comes up with NO MENU at all. I then typed rootnoverify (hd0,0) chainloader +1 boot Windows boots up fine and I am posting this way. when I try to grub> find /boot/vmlinuz I get a error not found, when I try root (hdo,5) I immediately get a error 18: selected cylinder exceeds maximum supported by BIOS I also tried root (hd0,6) (just in case and same error 18) so maybe this week end I will do the BIOS back to LBA and start fresh one more. I put this out so you all know, that the version at the SUSE site might not be as robust or the same level .12 that was just posted a couple of days ago, since I did not find IT at the suse FTP site , I will just do the fresh and not know whether this .12 REALLY fixes this incompatability. thanks to all again |
| |||
| > > ps. I've been installing many Linux distributions lately, and I must > say SUSE really looks good except for this MBR fiasco, is this a GRUB? > thing? would LILO be any safer? > > should I just make a boot floppy and burn that image to a cd? > I am brand new to Linux. I have tried Red Hat for about a week, but could not get on the net. That was three or four years ago. I was still retarded to the Windows environment. Anyways, I have a duel boot system (WinXP and SuSE) myself and instead of the GRUB try using LILO. I have not had one issue in roughly a month now since I have started using SuSE. I got on the net. Pat |
| |||
| Leo (Bing) Whiteway wrote: > res wrote: > >> Hello everyone, I thought I would share my experiences >> with Suse Linux 9.1. >> > Do you realize this is a SLACKWARE group? > > <snip> > Wrong group bub:-) Pat |
| ||||
| On Fri, 20 Aug 2004 04:01:28 -0500, patc6 <patc6@cox.net> wrote: > >> >> ps. I've been installing many Linux distributions lately, and I must >> say SUSE really looks good except for this MBR fiasco, is this a GRUB? >> thing? would LILO be any safer? >> >> should I just make a boot floppy and burn that image to a cd? >> > >I am brand new to Linux. I have tried Red Hat for about a week, but >could not get on the net. That was three or four years ago. I was still >retarded to the Windows environment. Anyways, I have a duel boot system >(WinXP and SuSE) myself and instead of the GRUB try using LILO. I have >not had one issue in roughly a month now since I have started using >SuSE. I got on the net. >Pat thanks, I've found a cure too, enjoy Linux |