OpenSUSE Install :: Bootloader Installed On Partition That Does Not Lie Below 128 Gb - System Might Not Boot
Mar 12, 2011
I'm trying to install opensuse 11.4 but I got this error:
"The bootloader is installed on a partition that does not lie entierly below 128 gb. The system might not boot if BIOS support only lba24(result is error 18 during install grub MBR)"
What should I do before click next step to install? I installed opensuse with this error and some times opensuse can boot and some not. At least I was able to boot safemode.
i want to install opensuse on my new lap top i partition my hard (600gb) with 5 parts:
c: 97 gb d: 150 gb e: 150 gb f: 100 gb g: 50 gb and 38 gb unlocated part
in opensuse instalation , the yast makes a 2gb for swap 14gb = root , 21 gb = home, but in Instalation Overview under Booting has a red error: the Boot loader Installed On a Partition that does not Lie Entirely Blew 128 GB .The system maight Not Boot;
Since I had a little time on my hand over christmas break, I decided to do my sister a favor and install linux on her computer (consentually, mind you). But so far, I've caused nothing but trouble, since I can't get Suse to boot. I've reinstalled over and over and over, but everytime I install and reboot, the computer complains that there is no operating system installed.
After a while of reinstalling, I tried to install a boot loader from the live cd instead, but when I open yast to do this, it compains that 'because of the partitions, the bootloader can't be installed properly'.
I've tried pretty much about everything, but nothing seems to work.
Note: I am doing such setup for the first time so I don't know if there is a problem with given opensuse version or problem with what I am doing. System: openSUSE 11.4 RC1
Desired setup: entire system except /boot partition on hard disk, /boot partition on USB (pendrive). Aim -- making impossible to boot from hard disk, forcing boot from the USB (please, don't question my aim, I am just trivializing the issue here to shorten the description).
Setup: I set /home and / partitions on hard disk (/sda), /boot partition on USB (/sdb), I selected the options to Boot From Boot Partition as well as Boot From Master Boot Record. Finally I selected Boot Loader Options and selected Set active flag in Partition Table for Boot Partition. I installed the system.
What works:
a) without pendrive inserted I cannot start the system b) with pendrive inserted GRUB menu shows up and system is ready to boot
The problem: after initial starting, there is long pause, and system switches to text mode with error:
Code: drive "/dev/disk/by-id/id_of_my_pendrive" is not found Since the console worked, I logged in, and yes, actually there was not such disk found. But the disk (pendrive) was there -- the initial booting took place not from void, but from it. So why it is not present? Out of curiosity, I pulled it out, and plugged it in back, now it was visible in "dev/disk/. Question: what should I change/tweak for correct booting the system from pendrive? Or is a bug in 11.4 installer? I would like to setup everything as it should be done -- I mean within installer.
What I found so far: Booting encrypted system from USB stick - Gentoo Linux Wiki it is similar problem to mine, but only similar. I have other symptoms.
LIVECD of 11.3 Gnome works fine in my old PC. I installed several times and each time system freezes/crashes during boot. I am linux newbie, so, I am trying to figure out my problems. In Livecd I noticed Hardware info list's my SATA disk as IDE. Driver Modules: "ata_piix"Attached to: #24 (IDE interface). Is it right? I have posted Hardware information output in 01: None 00.0: 10105 BIOS [Created at bios.186] - Suse 11.3 install problem My machine specs are: Intel DG31PR motherboard, Intel core2duo, 3 GB DDR2 Ram, 250 GB SATA harddisk
I've got a multiboot system with Windozin the first drive and first partition like everyone recommends. I have several distro's and just let them install their bootloaders, but always on hd0 mbr. I installed Debian 5.0.1 this way and it wouldn't boot, so I got SGD to "fix" it, which it said was successful, but all I get is a partition doesn't exist when I try to boot. I put Debian on /dev/sdb3, I loaded Linux Rescueand mounted sdb3 and verified that its menu.lst had the right boot numbers (hd1,2). fdisk even showns /dev/sdb3 as boot as shown by the asterisk under the boot column. Should I do a complete reinstall of grub, maybe using one of the other distro's as the holder of grub? At one time they did all the grub launching as each addition was made
I have a major problem installing opensuse 11.3 on my computer( hp pavilion dv6).I downloaded openSUSE-11.3-GNOME-LiveCD-x86_64 from software.opensuse.org: Download openSUSE 11.3 and made a live usb.I'm a newbie at using linux infact i never used another operating system beside windows.Now i have installed windows 7 (on c disk 100gb).My first problem when i am trying to install opensuse is that he dosn't automatic choose to make my partitions so i have to do it manualy.I was searching how to make it the best way so i desited to make 4 partitons one for ' /boot' one for ' / 'one for '/home' and a swap partition/In windows7 i made 4 new partitons
3:10 gb for /boot 4:10 gb for/ 5:70 gb for /user 6:10 gb for /swap
My first question is :Is this right to make 4 paritions in windows (opensuse can't format or resize my partitions it just can edit it ) so it's my only way to make partitions( If this is wrong how can i make partitions then)
My second question is how to change the bootloader configurtation because everytime when ii try to install opensuse it stops at about 96% and it says to reconfigure the bootloader options.
If i skip this i get the folowing message
=== System Checking === Checking for /usr/bin/chroot binary... Passed Checking for chroot directory /mnt... Passed Checking for chroot directory content (bin boot Checking for binary /mnt/bin/ls... Passed Trying to chroot... Failed
borked the bootloader by my own doing. When I got this machine, I had a single HDD. I partitioned it with a primary partition for Windows, followed by an extended partition with swap, /home/ and /, as well as a FAT32 partition for "general" data. (this was before NTFS write support was common) This worked well with the Win2K install. Eventually, I added a second HDD, which became part data storage, and part Windows XP install. I eventually put Win7 on it, and pulled the other HDD during setup so that the boot order of the drives determines whether I boot Win7/XP or get GRUB.
However, my "data" partition was not visible in Win7... It shows up as an unknown FS in the disk management. OK, I thought. I used Paragon partitioning software to move the "data" partition out of the extended partition and make it a primary. I could now access it from Win7. I didn't realize I had GRUB set to boot from the extended partition, so now when I boot from that HDD, I get "no operating system". No problem, I thought. I'll pop in the install CD (NET), use it to boot the installed 11.3, and run the boot loader setup. Nope- setup just hangs. Tried it with an 11.2 DVD... doing a "boot installed system" nets me a few moments of searching, "evaluating root partition", and then "no valid linux install found". Trying the boot loader reinstall from there nets me an "error changing to target environment" and the install fails.
I can still mount the / partition via rescue mode and all files appear to be intact, so I don't think I've lost any data... just grub/the MBR is borked. I've already moved the data partition back in to the extended partition but no luck. Still the same story... thus I'm stuck booting Windows until I fix this.
we have a server running with Suse linux many years. Meanwhile we changed server hardware about 4 times, mostly also updating to newest Suse version. We used to copy group, passwd and shadow to a backup medium, installed the new system and restored those files onto the new system and all was running fine. Now, some weeks ago we installed 11. on new hardware and after restoring those 3 files after rebooting the system hangs when starting GUI. I can boot into runlevel 3 and login with no problem, but when I boot into runlevel 5 mouse and keyboard are frozen. Also when starting GUI from runlevel 3 with startx mouse and keyboard immediately freeze. If I restore the files group, passwd and shadow as they came from fresh new installation I can reboot and login in runlevel 5 without problems.
OK, if I compare the userlist, as it is generated bei installation,there are some usernames I formerly not had in older Suse versions. I don�t know if this can make problems? I tried to edit the files, to combine the system users from 11.2 with the list of local user names from the old system but without success, again the mouse and keyboard freeze.So some questions arise:1) Why now mouse and keyboard freeze in xsystem, when there are changes in the user list (but only in runlevel 5)2) What is the correct way to save and restore users and groups from old to new system. I googled several hours but did not find a smart way. Maybee someon can point me to a link or a howto where I find the solution
When I installed, I accidently installed the bootloader to the mbr of my hard drive instead of the Ubuntu partition.Is there any way that I can make it so that it shows the Windows bootloader first? (Windows partition is set to active, Windows is on hdd0,sda1, Ubuntu is on hdd0,sda4 with sda5 as swap)
Is it possible to install ubuntu 10.04 on a second partition without overwriting the windows7 bootloader and boot it using grub on a usb stick?
I would be happy with just the second option as I could fix mbr if I have to, I just don't want it to easily visible that linux is installed as well as windows.
Has anyone successfully installed openSUSE 11.2 on a Dell PowerEdge 1850 system?Undoubtedly, it wasn't wise to attempt to upgrade from 10.2 to 11.2 but I was forced into it by a security audit of DMZ systems.It didn't go as smoothly as the jump from 9.3 to 10.2.I've spent the better part of a week getting an openSUSE 11.2 system installed.I went back to reiserfs and managed to get through and apply all the updates to openSUSE 11.2 today.When I got to the final reboot, it failed when I attempted to log into the system.Basically, the keyboard and mouse became inoperable.The only way out of this situation is to mash the reset button.
Rebooting into safe-mode and adding level 3 to the safe mode boot options, I get to the point of starting sshd when the lock-up occurs.It looks like X11 is the culprit.Booting a forensics DVD, I find that there is an xorg.conf.installation but no xorg.conf file.The ATI Radeon VE chip set is used on the PowerEdge.From another openSUSE system that I haven't upgraded, I see that X11 was configured for VESA mode. This is, probably, the mode that is needed as console access is, normally, through a KVM.Can anyone provide a way to get past this problem with a workable keyboard and mouse?
It used to be that the dvd menu offered an option to "repair the installed system". THis was really very convenient. The openSUSE 11.3 dvd for x86 now only gives a "system rescue" option which leads to command line directl. Where have been "the repair the installed system" tools? How can we access them now? What is a reasonable set of tips that's supposed to be used after logging into "system rescue"?
Built new system and installed openSUSE 11.3 x86_64 with Gnome desktop about 6 weeks ago. Have never been able to get the system to shutdown or fully poweroff using the installed OS. If I use the Knoppix live CD - no problem. System boots up fine and shuts down and powers off correctly. With the installed OS, it originally crashed on shutdown and had to power off using the power button. After trying many things, the OS shuts down, powers off the fans etc, but the keyboard is still lit. I cannot restart the system without turning off power at the power supply. Starting my computer by turning off the power supply switch, waiting 10-12 seconds, turning on the power supply switch and then hitting the power button gets to be very annoying after a few weeks.
Installed KDE and switched to that to see what difference it might make. System does not shutdown, but reboots instead. Switched back to Gnome. Have tried sudo /sbin/shutdown -h now and poweroff. Identical behaviour. System is completely up-to-date. BIOS, kernel, video drivers.
I tried to update one of my home machines with a fresh install. This is far from new to me so I did not expect any problem. But I was proven wrong. First: did install the system as usual. First anomaly: system blocked during the install process but did restart it flawlessly one I tried to eject the DVD from the player. It needed actually that intervention to retake working. It then went to install and froze during the first system start. I rebooted with failsafe settings, it then correctly configured. I reached a beautiful desktop. I performed the updates from the update repository and I joined the nvidia proprietary driver repository (which updated to the G02 driver).
I then rebooted the machine and now I am in trouble. In normal mode the system (dual boot Opensuse, XP) does not boot at all and freezes immediately after hitting enter as before. In safe mode it goes further but does not reach X anymore. It blocks with the following line statement: "system console stolen at line 266". I then tried "startx". But the system goes into a scrolling loop that does not allow me to read the output. how to get at least the error message of the loop? I read some line passing by that the system might have an X11 authorization problem.
Athlon Phenom X4 905e Nividea G7600 graphic card Former system installed and running flawlessly: 11.1
Since 11.2 installed but shows blank screen at boot despite booting into runlevel 3 with acpi=off and noapic, I decided to try 11.3 M4 again.Media check is OK for 11.3 M4.Boot from MBR. GRUB menu shows Ubuntu and Windows 7 as well as openSUSE 11.3 desktop default and 11.3 failsafe. Both opensuse11.3 default and 11.3 failsafe return a blank screen despite the following boot options:
33 acpi=off noacpiI still cannot get to a terminal to run sax2. I read from a thread of opensuseforums (Opensuse 11.2 Blank Screen) where similar problem was solved using the correct driver which is actually "ati", NOT "radeon" for ATI Technologies Radeon Xpress 200M.Then because both Windows and Ubuntu boot fine from GRUB menu, it occurs to me I should boot up Ubuntu and try to locate openSUSE's /etc/X11/xorg.conf in order to edit the file and change the driver to "ati".In Ubuntu, xorg.conf of opensuse 11.3 M4 shows:
Section "Device" Identifier "Configured Video Device" EndSection
I created an OpenSUSE 11.4 PV guest on XenServer 5.6, and about half the time, it fails to finish booting. it starts all the services, and fails immediately before it would display the login prompt. I've spent hours googling for this problem, and can't find any reference to it anywhere, meaning that I may be the first to experience it.
has anyone else done OpenSUSE 11.4 on XenServer 5.6 and had this problem? were you able to resolve it, and how?
I'm using Truecrypt to encrypt my Windows 7 OS. I also have unencrypted Ubuntu 10.04 installed on /dev/sda6 on the same hard drive. Since Truecrypt bootloader must be installed in MBR, I have GRUB2 installed on /dev/sda6, so I can use TC bootloader to load GRUB2. When I first install GRUB2 on /dev/sda6, I can use TC bootloader to load Ubuntu. But, if I boot into Windows via TC bootloader, and then later try to boot into Ubuntu, I get the message "no bootable partition found". I have to reinstall GRUB2 onto /dev/sda6, every time after I use windows in order to be able to boot into Ubuntu. It seems that starting Windows somehow overwrites GRUB2. Is there a fix for this?
I've been trying on new installation for opensuse 11.3 on Intel P55 raid5 configured system, one non-raid disk for boot device, a raid5 array as data device. However, installation always gets hung on Searching Linux partition step and I was able to see the vgscan process was the last command to run. Is it a known bug? Does anyone have the same issue as mine?
I have a problem that I can't login to SUSE in graphical mode. I get to the login prompt; enter my username and password; SUSE starts to do the login but then crashes back to the login prompt. Looking in /var/log/messages doesn't tell me anything useful. However, I noticed that my SUSE system partition is full (at 20 GB). So I think this is the culprit that is stopping my login.
Unfortunately, I can't extend my system partition as it is ext4 (SUSE default) but parted (from SUSE 11.2 live cd) complains that it can't do anything with ext4.
I'm using OpenSUSE11.2 x86_64 KDE 4.3.5 Linux 2.6.31.14-0.1-desktop
I have a 500GB hard disk and divided to 3 partitions, 1 for windows, 1 for openSUSE and 1 for Ubuntu. i have installed and reinstalled linux on my laptop for many many times but it is like this, Grub 2 is installed to MBR and it workded fine but i want to add openSUSE and chose not to boot from MBR when installing it.i had to edit the menu.lst and got it to boot to Ubuntu partition. i also share file on partitions directly by booting to openSUSE and take data from Ubuntu and Windows partitions. so sometimes the pc boot i cannot scrool down the grub menu entry and it boot directly to openSUSE. BUT it returns to the start point ( i can see Dell booting, my laptop is Dell Inspiron N5010). and so i decided to reinstall Ubuntu(kubuntu) and set grub to install to its own partition not MBR.
Now i cannot boot to either openSUSE or Ubuntu. Only Windows is available by chance. new problems arise now that i cannot even boot the bootable CD. Did i loose the MBR or sth?
I suspect this is a 'new Grub' problem. I installed OpenSuse 11.2 from DVD into one (sda10) of several partitions (the others containing other operating systems):-
/dev/sda1 * 1 63 506016 6 FAT16 /dev/sda2 64 4865 38572065 5 Extended /dev/sda5 64 960 7205121 7 HPFS/NTFS /dev/sda6 961 1859 7221186 83 Linux /dev/sda7 1860 2759 7229218+ 83 Linux /dev/sda8 2760 3026 2144646 82 Linux swap / Solaris /dev/sda9 3027 3924 7213153+ 83 Linux /dev/sda10 3925 4865 7558551 83 Linux
I use NT Boot Loader for the multi-booting on the basis of chain-loading the boot sector of Linux partitions. (It is not destroyed by MS re-installations; and is actually very easy to use). I also have an older Grub shell boot floppy which can do likewise:- root (hd0,x)chainloader +1 boot FWIW I found the disc partition & boot loader parts of the installation a nightmare. Difficult to know what it is going to do; and I am sure it *did* fiddle with parts I asked it to avoid. Horribly, it did *not* make me a dedicated Suse boot floppy like I checked. (This is always the safest boot option for a new install: it leaves the present boot system intact, and provides an independant way of loading your latest. You can refine things later). I had also checked to have the boot sector on the *root partition*.
I have never been able to get into the Suse. NT Loader does not like the partition boot sector. Nor does (an older) Grub from its boot floppy. I have tried the DVD in 'system repair' mode, when it finds things wrong and corrects them, same next time... It offers a way of directly booting a selected system; that did not work.
Any suggestions? I can provide more precise error msgs, but it is tedious; and system repair from DVD dicey. I feel that *the partition boot sector is not being properly set up*.And I want to be able to make a dedicated boot floppy; how? I have an identical problem with Ubuntu, which makes me think it is related to the 'new' Grub.
I've just recently decided to try Linux, but I want to keep Windows 7 on my computer as well. This is also the first time messing with things like partitions. Could anyone lead me to a good site where I can figure out how to partition my hd, dualboot openSUSE, and fix any problems that may occur?
P4 2.4gHZ 2.0GB Ram I have tried to do some reading on this by googling and such, but it is all a bit overwhelming and so many posts/articles want to deal with dual booting which I am not planning to do on this machine. I am trying to find some info on whether it is better to have a separate boot partition. As in, separate from root partition. I have read that a separate boot partition makes for a quicker start and better recovery if system crashes. I will shortly be installing openSuse 11.2(KDE) [currently on 11.0] and I want to optimise the partition scheme so that it is the most efficient. I have a 160GB HDD that will be housing this new installation, so space is not a problem. I am only user on this machine. Currently, it is just partitioned as such:
2.0GB - swap [because I read it should equal Ram] 32.0GB - / 40.0GB - /home 76.8GB - extra storage [Not really necessary as I have 2 other HDD on system 1 - 320GB and 1 - 200GB]
Also, is it recommended to have separate partitions for /tmp /var or any other /nnn ?
what's the difference (if any) between choosing to boot from the MBR, the root partition or enabling neither? Referring to: pic23-MBR switch.png - Windows Live Would one be better for dual boots for example? (Using Vista too)
Playing on a test rig here and I want to install openSUSE in an already multi-boot Ubuntu family environment. All the 'Buntus play together nicely with grub 1.89, learning the ins-and-outs of which appears to be a lifetime endeavor.SUSE appears to be still on legacy grub, and I don't want that to take over from (almost) grub 2.0. It's fairly trivial to add things to the newer grub. Question is can I install SUSE and tell it NOT to install a bootloader at all?
Currently I am running a dual boot with Windows 7 and openSUSE 11.3. Windows has two partitions, one for the system partition and another for the OS. I have 3 Linux partitions (swap, root, and home). Obviously I am running GRUB to boot, but this seems to be impacting my ability to install Windows 7 SP1. I would like to revert back to the Windows boot loader, install the Service Pack, and then revert back to GRUB. How do I do this?
I just fresh installed openSuse 11.3. Am trying to install Hupervisor and Tools but during the install I get the message that xen itself can't be installed while it needs 20MB space.My boot partition is already maxed. At least that is what the partitioner is telling me that 70MB is the maximum setting.
