i wanted to see the red hat side of things and do some virtualization with CentOS, so i am trying to dual boot ubuntu 10.04 LTS and CentOS 5.5. the machine is a laptop, toshiba A100 series. what I did was to create the following partitioning scheme via Ubuntu LiveCd
Code:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 19457 156288290+ 5 Extended
/dev/sda5 1 2103 16892284+ 83 Linux
/dev/sda6 2104 9988 63336231 83 Linux
/dev/sda7 9995 12623 21117411 83 Linux
/dev/sda8 12624 18800 49616721 83 Linux
/dev/sda9 18801 19457 5277321 82 Linux swap / Solaris
created an extended partition and in there have made sda5 and sda6 as / and home for ubuntu and sda7 and sda8 as / and home for CentOS. and sda9 as swap. I installed ubuntu first and then installed CentOS with no bootloader. Run sudo update-grub through ubuntu and now i have both Ubuntu and CentOS available. But when i select CentOS, i have an error which reads "invalid magic number".
I have grub2 installed, haven't downgraded or done anything to it and the ubuntu install is fresh, one week since i updated to 10.04 from scratch. I have found much contradictory stuff on google, but not something that provides a definite solution and also this post but the second command provided in the solution is one i cannot understand very well and it doesn't seem to work. what I am doing wrong here and how to make this work. I would prefer to do things via Ubuntu since debian stuff is what i am comfortable with and i am installing CentOS to learn not to do work on it.
This has to be the sixth time I am going to have to reinstall Ubuntu (Can't get enough of that Linux greatness) in the past 6 months. I just don't understand what exactly is wrong, I don't install anything extra (but the ubuntu restricted extras) yet updates that ask me to reboot will take me to a GRUB command line screen and trying to boot through the command line interface gives me an, "Invalid Magic Number", error.
There should be an official tool for when problems like this come up, so that users like me can easily move their files off their HDD before reinstalling. I didn't come here to rant but, does anyone know what may be causing this everytime, how it can be avoided maybe even how to deal with the Magic Number error and boot in (I wouldn't mind typing in the commands every time BTW)?
My system Hp Compaq 6730s 2.0Ghz 575 Celeron 4GB RAM Intel X4500MHD Broadcom 802.11b/g
I tried the steps usually offered (modifying the grub.cfg file, replacing the wubildr files), it still wouldn't boot.
I booted in with the LiveCD to try to chroot into the environment and try running 'update-grub'. However, whenever I tried to chroot, it said it could not execute /bin/bash!
Trying to modify the grub commands manually (which originally gave the error: you need to load the kernal first), in the end said "invalid magic number"
There are some configuration things set in this installation I would like to not lose. Is it hopeless?
I've compiled and added a kernel in Gentoo before. It doesn't seem to go quite as smoothly in Kubuntu 9.10 These are the steps I followed: I unpacked the kernel in /usr/src and ran make && make modules_install succesfully. Then I copied the kernel in arch/x86/boot/bzImage to /boot/bzImage-2.6.32 This entry is the one given by Kubuntu:
Code:
menuentry "Ubuntu, Linux 2.6.31-14-generic" { recordfail=1 if [ -n ${have_grubenv} ]; then save_env recordfail; fi set quiet=1
[code]....
I just read the script that update grub uses. Changed the name of the kernel from xyz to vmlinuz-2.6.32-generic and it worked.
After several crashes during videos it seemed like a good idea to fsck root. Downloaded the latest systemrescuecd and ran it at boot. The error message was 'bad magic number, corrupt superblock' with a suggested command to try another superblock. That failed with the same message. Tried tune2fs to force fsck at boot and got the same message. The drive is less than 6 months old and the installed system is working more or less ok. The command I used was 'fsck.ext4 /dev/sdc2'. What am I doing wrong?
I loaded all required files inside the Innovate ARM board.When It starts booting from that location it is showing a error "Bad magic number" How I can get out of this error.
I am a long time Windows user and attempting to install Ubuntu Netbook 10 on my Acer Aspire netbook.I followed the steps:1) Downloading the Ubuntu ISO to my netbook hard drive.2) Installed Ubuntu from the netbook HD to USB using USB universal installer (also using the universal installer to format the USB)3) Set bios to first read USB deviceI receive the following message during the boot "Invalid system disk. Replace the disk, and then press any key.I have retried this process several times.
I have a fairly old computer, (4 years) it is has an Intel Pentium 4 3,4 Ghz processor with 1,5Gb RAM, and had been running XP Home on a 80Gb HDD. About three weeks ago, I purchased a 500Gb HDD, and disconnected my old drive. I partitioned the new drive to 120 Gb and 380Gb. I put XP Pro on the 120Gb partition, and Ubuntu 9.10 on the balance.
On reboot, startup menu (grub?) gave me the option to boot from, among others, Ubuntu 9.10, and XP Pro. Both worked fine! I then reconnected the old drive, and if I wanted to boot up in XP Home, would tap "F8" on start-up, and select the old HDD to boot from. This was working fine and I was happy with the way it worked! This morning, when I re-booted, the Start-up menu now had XP Home added to the list.
If I select either Ubuntu 9.10 or XP Home, they both work fine, but if I select XP Pro, it give me the message "error: invalid signature" and when I press any key, brings me back to the menu.
# sudo dpkg -i vasre-se-1.1.1~Debian_5-i386.deb dpkg: error processing vasre-se-1.1.1~Debian_5-i386.deb (--install): parse error, in file '/var/lib/dpkg/tmp.ci/control' near line 2 package 'vasre-se': error in Version string '1.1.1~Debian_5': invalid character in version number Errors were encountered while processing: vasre-se-1.1.1~Debian_5-i386.deb
I did install same package ok in 10.4 but now after I upgrade to 10.10 I am getting this error. I have already tried: # sudo dpkg --clear-avail # sudo aptitude update # sudo aptitude upgrade
I had a working dual boot Ubuntu 10 and Windows 7. Anyways long story short, I got it working again but have lost the boot option for windows 7. If i run fdisk -l, I get the following.
I installed gparted and can see that windows 7 is installed in dev/sda6. In another forum, i read that someone had to edit their menu.lst so i did with the following.
I've been setting up a number of netbooks for friends in a group I belong to. I am installing Ubuntu 10.04 and/or Linux Mint 9 on all of the netbooks. The netbooks are all identical. Everything has seemed OK until yesterday. I tried to set the label on the new disk using: # e2label /dev/sda newlabel The error is Bad magic number in super-block while trying to open /dev/sda. Couldn't find valid filesystem superblock.
But the filesystem seems fine. It is mounted. It booted up without errors. But all the e2* tools give the same error. So I checked another netbook with an identical fresh install of Ubuntu 10.04 32-bit. It gives the same error although the system appears to work fine. Next I went and checked my own netbook. It is identical except I swapped out the HDD for an OCZ Vertex SSD. I aligned the partitions and prepared that drive carefully. It seems to work great. But when I ran e2label on it I got the same error message.
All the other installs are fresh, clean, standard installs where I let the installer use the whole disk and do the partitioning automatically. All are using ext4. I did a fresh install of Linux Mint 9 and it has the same error as Ubuntu 10.04. Kubuntu 10.04 on my desktop gives the same error too.
I have a problem trying to install CentOS 5 as a dual-boot with my Windows 7. Using Windows tools, I shrunk my main partition and created about a 100GB of unallocated free space. Then, I restarted my computer, booting from the CentOS dvd, but when choosing "Use free space on selected drives and create default layout" option during installation, I get an error saying that partitions couldn't be allocated as primary partitions and that there is not enough space left to create partition for /boot.
3 partitions (in order): Windows 7, CentOS and shared data partition.
I need to increase the size of the Windows 7 partition (c:windowswinsxs seems to be something not easily remedied).
GParted didn't work in moving things around (bad sector) so I wiped out its partition (# 2 out of 3) and I was able to increase the size of the Windows 7 partition (I can reinstall CentOS easily and not much work lost).
Except ... no more grub menu (unsurprising). This incantation does allow me to boot into Windows 7.
Is there any way of rebuilding the grub menu short of reinstalling CentOS (5.5)?
I have a netbook running Windows XP as standard. There is also a recovery partition which came from the factory.
In the past I installed Ubuntu (I think 9.something) from USB key and all worked fine. However my XP became corrupted and I needed to do a repair on it. After this, Ubuntu became removed from the boot select menu.
Since then, Ubuntu has become updated to 10.04, which I now cannot install.
The Live CD tells me there is a "file IO error" and simply stops installation at around 70%.
I did manage to get into Ubuntu from a Live USB using Wubi. However when I chose to install Ubuntu to a Harddrive, the option to "install side by side" was missing.
After reading on the forums, I did a chkdsk /f on Windows and tried again. Now my liveUSB does not show a boot menu!
When I select to boot from USB stick, the screen goes blank with a flashing cursor. Ctrl+alt+dlt reboots.
I'm really lost here! It seems when I fix one problem, another problem arises!
Also when trying to instal Ubuntu within Windows, the process goes through to 100% and asks me to reboot. When I do so, the option for Ubuntu does show in the boot menu. However when I select it, I get an error "Windows boot failed: file wubildr.mbr and status: 0xc00000f - something is corrupt".
I have a (slightly complicated) dual/multi boot system.
I keep getting boot errors (when choosing ubuntu from the grub2 menu)
Code: Serious errors were found while checking the disk drive for /boot
If I switch off and restart, ubuntu will then start without issue.
My setup is like this ....3 disks, one with 10.10 clean install - so Grub2, separate partitions for /, /boot and /home, one with windows 7, one with windows XP and 10.04 wubi (this is my old disk which I will trash once I'm happy with my upgrade to 10.10 & 7 on separate disks.
I installed 7 and 10.10 with ONLY their disks installed. After both were working, I added all disks and rejigged the grub2 menu (using update-grub and StartUp-Manager).
This problem only seems to occur if my previous boot was not 10.10 ( I will investigate this further). It's as if something (grub2 ?, the bios ?) is remembering part of the previous boot and not using the grub2 menu completely.
I have two SAS RAID controller cards in a Dell server in slots 2 & 3, both with an array hanging off them. I went to install a third card into slot 1, but then when it boots it says two of my sd's have bad magic number in the super-block and it wants me to create an alternative one, which I don't want to do. If i remove the new card, the server boots perfectly like it did before I added the new card. Is the new card trying to control stuff that isn't hooked up to it because its in slot 1, so its confusing RHEL?
I'm trying to install a dual booting machine with OpenSUSE v11.1 32bit and CentOS v5.2 64bit. I installed OpenSUSE first and allowed it to install and configure grub in the MBR and after that I wanted to proceed with CentOS v5.2. The installation went fine with two notable exceptions:- when I had to configure grub installation parameters, CentOS offered me only 2 solutions: either install it on the MBR of the first hard disk or not installing it at all. Other distributions are more flexible allowing you to install it in the boot sector of the root partition for example. Because I didn't want to ruin the existent grub onfiguration, I reluctantly accepted not to install it for CentOS assuming that I could manually configure the entry later in grub's menu.lst file.
- when I was presented with the options for software components installation, I've clicked on virtualization category/function because I intend to use the machine as a VMware host. There was no guidance on screen at that point and I blindly assumed that by choosing the virtualization function I would get necessary tools and drivers that will help me further on. It seems that this was a wrong move as you can see it below.
After completing the installation, I tried to search for a template or guiding on how the menu entry in menu.lst should look like but the grub directory was empty, not surprisingly because I've told CentOS earlier not to install it. Using the files in the /boot directory from the CentOS installation I tried to improvise a menu entry but it's not working. The boot stops with famous Error 13: Invalid or unsupported executable format. Using the file command to check what kind of files I'm trying to load as kernels I'm getting :
marte:~ # file /mnt/vmlinuz-2.6.18-92.el5xen /mnt/vmlinuz-2.6.18-92.el5xen: gzip compressed data, from Unix, last modified: Tue Jun 10 19:20:51 2008, max compression
I did the online upgrade from 9.10 to 10.04, using 64 bit. I was forced to as the 2 solutions to my incedibly slow internet lookups both required new package installs, both of which failed, so hoped it was sorted out in 10.04 TLS.
It all went to plan until it tried to reboot. I get this:
mount: mounting /dev/disk/by-uuid/1e4e276c-8741-42e7-b52e-05c195790d28 on /root failed: invalid argument mount:mounting /dev on /root/dev failed: No such file or directory
[Code].....
I don't have RAID at all a single Samsung 200GB SATA drive as the boot drive. Can someone tell me where to start looking? Also how can a TLS release screw up so badly on a common Gigabyte motherboard?
The problem is when I boot from the lubuntu CD & select Try Lubuntu or Install Lubuntu the computer hangs. Xubuntu 10.04 was aready installed & I could easily boot to it. I thought may be some partition table error is causing that issue & I deleted all the existing partitions with Parted Magic Cd in Console Mode.
NB: When I tried to boot to the Parted Magic graphical session the PC hanged then too.I am totally confused. Cant understand what is going wrong here. I am now left with a broken system.
I installed Ubuntu 9.10 on my laptop. Thereafter, I installed Fedora 12 on another partition. Now when I boot, my bootloader lets me select Fedora 12 or Ubuntu, kind of. When I select Ubuntu I get ERROR 13. Now... when I installed Fedora 12, I selected Ubuntu (or I thought) as another OS. Guess I messed up.
I need to know how I would fix this problem. I know it has something to do with GRUB, either its' conf file or the menu list, but I really don't know how to make the changes.
have a problem with my latest install as follows:1) If I install Fedora 15 so its bootloader is in the MBR (/dev/sdc1) and Centos 6's bootloader into the first sector of the boot partition (/dev/sdc3) I have no problem chainloading from Fedora 15 into Centos6 with the following in Fedora's grub.conf. This has always been the way I have set up multiple OS's (I like the chainloader method).
I managed somehow to successfully install a dual boot with Ubuntu 9.02 and Windows XP. Ubuntu was on a PATA drive and the WinXP was on a SATA drive. The SATA drive was configured to boot first. As I was having problems with Ubuntu I booted into WinXP, re-formatted the PATA drive, then restarted the computer and installed Ubuntu 9.10. It all went well.I rebooted the machine and the following message was on the screen:
I rebooted, changed the boot order so that the PATA disk (Ubuntu) started first, then the SATA(WinXP). Ubuntu loaded up the dual boot screen.I chose WINXP, but I was greeted with a black screen.I rebooted again and chose to load Ubuntu, which it did without a hitch.what I should do to restore my access to WinXP? Or should I start again? If so, how?
I am trying to create a dual boot setup with Windows XP. Everything goes smoothly untill the final reboot. I get a text screen giving me the two options of booting into Windows XP or Mythbuntu. When I select Mythbuntu I get a second text screen with a rectangle only showing Windows XP as an option -nothing else. Hitting enter causes error message. If I selext the Windows XP option on the first screen system boots into windows without a problem. I suspect this should be fairly easy to fix - but being a complete noob to Linux I am lost as to what to do to correct this.
This will make the third time I have tried to load Ubuntu and it has wiped out my Win OS twice and am not sure it hasn't done it again. I installed a 40gb hdd as a slave, have XP on the master. In the process of installing I picked the drive that corresponded to the slave. Didn't understand the the names or titles Ubuntu used but proceeded and the installation went fine although I never saw a place to load Grub on the master drive. After rebooting a couple of times saw the option to click Esc for boot menu but the only choices given were Ubuntu, ubuntu recovery and ubuntu kernel. Can find no mention of my W OS. Have tried to unplug the slave drive but can't boot then as get error message of Grub error.
After upgrading to 10.04 from 9.10 Win7 wouldn't startup any more. So I tried this HowTo: [URL] to restore Grub2. But now each time I boot up I get this two lines: error file not found grub rescue> I have NO idea what to do.
I keep getting this error during the XP and Linux Ubuntu 9.10 dual boot installation. I have tried many things. Here is the current status of the installation: I have used wubi.exe to install the contents onto the drive. I did not install it onto my windows C: Drive because my Dad does not want to mess with it anymore. We have accidentally blown up Windows Twice trying to dual boot already. So we have another drive in our computer that we have it installed on so we don't mess with Windows. Ok so every time I boot up the computer it goes to the dual boot menu i choose Ubuntu and it tries to finish the installation. Whenever i get to the part where it says "Setting up Partitioner"(Or something like that.), a pop-up appears that says "No root directory is specified. Please correct this from the partitioning menu."
I am pretty sure that the installer is supposed to make the partitions for you. It is impossible to close out the pop-up so i had to hard boot the computer. Then i went into the Linux Ubuntu Demo Mode. I used GPartEd to create the partitions manually. I came across the problem that there were too many partitions on the drive becuase we had some other partitions that we needed on that drive so I had to create an Extended Partition to house the Linux Partitions (For more information on my partition setup, see the bottom of the post.). While still in the Linux Demo I had clicked on the "Install Ubuntu" icon. I got through the first 3 steps (The steps where it askes for Language, location, etc.) After that it went to some setup partitions menu but nothing was on it so i clicked on "Forward" and it said "No root directory is specified. Please correct this from the partitioning menu." That is as far as I am right now.
I just tried to install Ubuntu 10.04 on my windows machine. Unfortunately there was an installation error and now the computer will not boot up in windows anymore (I get grub error 17). I had Ubuntu 7.04 before, but when installing 10.04, I deleted the 7.04 partitions. Is there a way to recover the ability to boot into windows?
My system has Windows XP Pro SP2 installed on /sda1 and originally a 10.04 on /sdb1-3, now upgraded to 11.04. The Ubuntu system works fine (teething troubles with nvidia drivers on upgrade but fixed now), and the Windows system shows up in the grub menu, but when it's selected, I just get `GRUB Hard Disk Error' and nothing else. Windows installed properly, and booted successfully until I installed Ubuntu in the first place. I can still access the files on that drive from within Ubuntu.
I've tried fixboot in the Win Recovery Console, which sounded like it did something, but didn't fix the problem. This problem isn't new to grub2, by the way - I just haven't needed Windows in a year.
I am new to Fedora, having used Ubuntu for 2 years. However, I am a little dissappointed in the latest Ubuntu releases and want to try something new. So I installed Fedora 10 on my second hard drive, deleting Ubuntu. On my first hard drive, I have Vista installed. During installation I followed a guide for dual-booting and it said not to install Grub to the MBR of the Windows partition, so I followed that advice...
This caused a Grub error 15 on the next boot. I booted the Fedora installation from the second hard drive. My hypothesis is that the Grub bootloader of Ubuntu was still installed somewhere and it could not find the Ubuntu linux kernel. Therefore, it gave error 15. So I installed Vista again and am hesitant to try Fedora again... How can I install Fedora alongside Vista properly (as dual boot)?
Or should I stay away, because it is apparently too difficult for me? Is it worthwhile to make a separate /home partition as I read that it is preferred to do a clean install every release? Could I just do that with Gparted and then assign the partition as /home in the Anaconda installer? The downside is that I then need to create a swap and / partition too, right?
