Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have 3 os installed. I first already had windows xp installed on a raid striped drive, i then installed a sata drive and installed vista ultimate, then i inserted an ide drive and installed Ubuntu. well now ubuntu's boot loader was installed oh hd0 and when i boot i get an error 21 when booting hwo can i fix this. so that grub takes over the boot loader and i see all the other OS's. I have to boot now to cd using super grub in order to select the os i want to login into. how can i fix this so grub comes up and sees the raid config on the first windows xp partition where grub is installed.
Grub won't be able to read it's own stage1_5 files in /boot/grub if the grub directory is in a raid partition. It is best to have /boot on a non raid partition unless you are using Raid-1 and grub can access a partition member directly.
Another potential problem when mixing sata and pata drives is that at boot time, the drive order are seen differently then the kernel sees them after booting. You may need to edit the /boot/grub/device.map to fix this. Otherwise you won't be able to update the grub configuration. If grub booted before from hd0, see if this is the cause.
Grub won't be able to read it's own stage1_5 files in /boot/grub if the grub directory is in a raid partition. It is best to have /boot on a non raid partition unless you are using Raid-1 and grub can access a partition member directly.
Another potential problem when mixing sata and pata drives is that at boot time, the drive order are seen differently then the kernel sees them after booting. You may need to edit the /boot/grub/device.map to fix this. Otherwise you won't be able to update the grub configuration. If grub booted before from hd0, see if this is the cause.
yes when i installed ubuntu it load grub to the hd0 drive. the raid config is on my MB which is a nvidia raid configed as a striped raid i dont knwo if that is raid 1 or raid 0. the options for config are striped and mirror. i did striped and both my hds are now one with space from 400gig a price to 800 gig or technically 740gig.
how can i fix grub? should i try and reinstall ubuntu to move the grub boot loader to a different Hd0.
Grub won't be able to read it's own stage1_5 files in /boot/grub if the grub directory is in a raid partition. It is best to have /boot on a non raid partition unless you are using Raid-1 and grub can access a partition member directly.
Another potential problem when mixing sata and pata drives is that at boot time, the drive order are seen differently then the kernel sees them after booting. You may need to edit the /boot/grub/device.map to fix this. Otherwise you won't be able to update the grub configuration. If grub booted before from hd0, see if this is the cause.
can you give me some straightforward steps to accomplish this .
I have to boot now to cd using super grub in order to select the os i want to login into.
If this works, it (probably) means everything is basically o.k. From Linux, get the bootinfoscript from sf.net, run it from a terminal and post the RESULTS.txt here so we can see what the bootloader is attempting to use.
If this works, it (probably) means everything is basically o.k. From Linux, get the bootinfoscript from sf.net, run it from a terminal and post the RESULTS.txt here so we can see what the bootloader is attempting to use.
i will get that for you and post the output. thanks
If this works, it (probably) means everything is basically o.k. From Linux, get the bootinfoscript from sf.net, run it from a terminal and post the RESULTS.txt here so we can see what the bootloader is attempting to use.
ok i was not able to find this file:
bootinfoscript
where do i go and how do i post the results.txt thanks for your help.
Sorry, missed your earlier response.
That looks very messed up. Try "configfile (hd4,0)" from the grub prompt and see if that gets you the boot menu. If it does, see if Windows will boot. Ubuntu probably won't boot - use the arrow keys to highlight the Ubuntu option, and hit "e" to edit it.
Then highlight the "root" line and hit "e" again and change it to "root (hd4,0)"
Then hit "b" to boot it.
If that (all) works, edit /boot/grub/menu.lst and change the (hd3,0) to (hd4,0). On the next reboot, instead of the configfile command, do this to update the MBR
Code:
root (hd4,0)
setup (hd0)
This may (probably will) break again if you add and/or remove any disks.
Sorry, missed your earlier response.
That looks very messed up. Try "configfile (hd4,0)" from the grub prompt and see if that gets you the boot menu. If it does, see if Windows will boot. Ubuntu probably won't boot - use the arrow keys to highlight the Ubuntu option, and hit "e" to edit it.
Then highlight the "root" line and hit "e" again and change it to "root (hd4,0)"
Then hit "b" to boot it.
If that (all) works, edit /boot/grub/menu.lst and change the (hd3,0) to (hd4,0). On the next reboot, instead of the configfile command, do this to update the MBR
Code:
root (hd4,0)
setup (hd0)
This may (probably will) break again if you add and/or remove any disks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.