Reinstalling grub on a RAID 0

I want to make my Arch installation a bit more fancy. So, I installed the grub-gfx package and did the changes to my menu.lst file in /boot/grub. Then I need of course to reinstall grub again so I do
grub-install /dev/mapper/isw_baaggideei_Volume0
but it fails. How do I reinstall grub when using RAID 0 (fake-RAID). I also tried the installation mention in wiki for fake-RAID and I can grub gets installed but no background appears eventhough it is in menu.lst file.
Regards
André

I don't think you can install grub with stripe raid. I'm running a RAID10 setup (MDRAID, so stripe and mirror in one action) and must have a separate RAID1 (mirrored only) array for my boot files. The reason is simply that GRUB cannot read the files off of the striped RAID array.
edit: Just noticed that you said fakeraid, so I assume this is some low-cost hardware solution that does the actual RAID'ing in software drivers. I'm not sure how this will differ from my MDRAID setup. I still don't see why people insist on using fakeraid controllers in RAID mode instead of switching them to SATA mode and using mdadm to setup arrays that are hardware agnostic.
Last edited by iBertus (2008-12-15 22:34:59)

Similar Messages

How to mount encrypted lvm + chroot + reinstall grub?

hey everyone
i can't boot into my system after i tried to reinstall grub (caused by an error in the bios) so i had to reboot and change some settings. unfortenately grub couldn't boot anymore
the problem is that the system is an encrypted lvm and i don't know how to map the volume, decrypt, mount and chroot into it.
could you pls give me a short and handy guide?
best regards :>

I'm afraid it hadn't been answered!
I've got the following as /etc/rc.d/arch32, listed in /etc/rc.conf:
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
case $1 in
start)
stat_busy "Starting Arch32 chroot"
mount --bind /proc /opt/arch32/proc
mount --bind /proc/bus/usb /opt/arch32/proc/bus/usb
mount --bind /dev /opt/arch32/dev
mount --bind /dev/pts /opt/arch32/dev/pts
mount --bind /dev/shm /opt/arch32/dev/shm
mount --bind /sys /opt/arch32/sys
mount --bind /tmp /opt/arch32/tmp
mount --bind /home /opt/arch32/home
mount --bind /var/run /opt/arch32/var/run
mount --bind /var/lib/dbus /opt/arch32/var/lib/dbus
add_daemon arch32
stat_done
stop)
stat_busy "Stopping Arch32 chroot"
umount /opt/arch32/proc/bus/usb
umount /opt/arch32/proc
umount /opt/arch32/dev/pts
umount /opt/arch32/dev/shm
umount /opt/arch32/dev
umount /opt/arch32/sys
umount /opt/arch32/tmp
umount /opt/arch32/home
umount /opt/arch32/var/run
umount /opt/arch32/var/lib/dbus
rm_daemon arch32
stat_done
restart)
$0 stop
sleep 1
$0 start
echo "usage: $0 {start|stop|restart}"
esac
exit 0
Changing 'mount --bind /home...' to '..--rbind' didn't make any difference, but is this maybe because I access the encrypted folders after this has happened?

Reinstall grub, got error 21

Today I reinstalled windows 7 so I have to reinstall grub. Here is the result of my fdisk -l
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 92162047 46080000 7 HPFS/NTFS
/dev/sda2 92203008 92407807 102400 83 Linux
/dev/sda3 92438528 976773119 442167296 5 Extended
/dev/sda5 92470140 100663289 4096575 82 Linux swap / Solaris
/dev/sda6 100702208 151902207 25600000 83 Linux
/dev/sda7 151943168 561543167 204800000 83 Linux
/dev/sda8 561584128 976773119 207594496 7 HPFS/NTFS
Then I went to grub shell and ran root (hd0,1) and got this output
grub> root (hd0,1)
Error 21: Selected disk does not exist
And I'm stuck at here. Have been googling around for hours but still cannot find the solution, hope you guys can help me. Please give me swift responses because this is very urgent.

alababi, if you are using Archbang, you should ask on their forums. I am sure the good people there will help you.
https://wiki.archlinux.org/index.php/Fo … ow_to_Post
Arch Forum Etiquette wrote:Community technical support shall only be provided for official Arch Linux distribution media installations and the Arch User Repository. Threads concerning issues with derivate distributions, or operating systems other than Arch Linux are prohibited and will be closed.

[ SOLVED ] Still not understanding how to reinstall Grub ?

Hi All
I currently have a dual boot windows 7 & Arch system and i have to wipe the Windows partition and reinstall. But i am still confused as to how to reinstall Grub once i have reinstalled windows 7. The wiki post is not longer available and have not found anything that explains what i need to do ... So can anyone point me in the right direction or explain what i need to do ?
Many Thanks
Last edited by whitetimer (2011-01-03 15:48:49)

# FLAWLESS GRUB REINSTALL GUIDE BY DARKBEANIES ASSUMING YOU USE EXT3 FILESYSTEM
# Boot arch install cd and login as root, and type the following commands in order, replacing X and Y values with the number of the partition/disk(MAKE SURE YOU GET THIS RIGHT, ASK IF YOU DON'T KNOW)
cd /
mount -t ext3 /dev/sdaX /mnt
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
chroot /mnt /bin/bash
#IMPORTANT-ONLY IF YOU HAVE SEPARATE BOOT PARTITION
mount -t ext3 /dev/sdaX /boot
#Then try:
grub-install /dev/sdaX
# -WHEN- this fails type this:
grub
root (hdY,X)
setup (hdY)
#Then reboot:
cd /
umount -a
exit
cd /
umount -a
reboot
#That's it!
Why oh why was this page removed from the wiki I do not know...
Live CDs of various flavours available HERE: (Don't you have the CD or whatever you used to install to begin with?)
http://www.archlinux.org/download/
Last edited by darkbeanies (2011-01-02 17:24:55)

[SOLVED] Reinstall GRUB

Hey guys,
I had to reinstall windows on my dual boot system and in the process lost GRUB and therefore access to my arch install. I tried just using my live cd to chroot into my old arch install and reinstall GRUB from there, but it didn't work, my computer still just boots into windows. I'm using two hard drives with arch installed on one and windows 8.1 on the other. Arch is on my /dev/sda drive.
I'm just not really sure what to do to get GRUB back.
Thanks
Last edited by joethesupercow (2013-12-12 03:00:51)

Hey guys,
I'm realizing now that I have a far weaker understanding of UEFI than I thought. I know that when I'm booting the computer if I go into the setup menu (BIOS?) I have a full graphical environment that I can use a mouse in and everything. However, I read that I could check C:\Windows\Panther\setupact.log on my windows install to find which Windows is booting under. I have a line in that code that says "Code:Callback_BootEnvironmentDetect: Detected boot environment: BIOS" making me think I'm booting under BIOS . So what do I need to do for arch? Boot under BIOS or use UEFI? Is that even a question that makes sense?
Mostly I just want to know how to get back to my arch install.
Last edited by joethesupercow (2013-12-12 02:07:05)

Diskfilter writes error when installing GRUB on a raid

I'm setting up a server running Arch with two raided drives:
cat /proc/mdstat
md127 : active raid1 sda[0] sdb[1]
976631488 blocks super 1.2 [2/2] [UU]
bitmap"1/8 pages [4KB], 65536KB chunk
have the following partition table created with cgdisk:
gdisk /dev/md/a
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 grub
2 20973568 981469183 458.0 GiB 8300 /media
3 981469184 1461716991 229.0 GiB 8300 /var
4 1461716992 1941964799 229.0 GiB 8300 /srv
5 1941964800 1942374399 200.0 MiB 8300 /boot
6 1942374400 1953262942 5.2 GiB 8300 swap
7 4096 20973567 10.0 GiB 8300 /
The command I'm running:
sh-4.3# grub-install --target=i386-pc --recheck --debug /dev/md/a
grub-install: error: diskfilter writes are not supported.
What should I do to fix this error?

Hi Frank,
With all that additional third party hardware it will be difficult to get a proper installation. You can either take out ALL 3rd-party hardware (just leave the 200 GB hard disk in there, but also take out the 120 GB) or you can simply clone the system from the 120 GB disk to the 200 GB disk. You can do that with utilities such as Carbon Copy Cloner.
If this answered your question please consider granting some stars: Why reward points?

Trying to reinstall Grub after windows 8.1 install

Hi All
I have just had to carry out a clean install of windows 8.1 and have trouble trying to get grub to reinstall and grub-mkconfig to run and add the windows menu entry again. This is what I have done.
mount -t ext4 /dev/sda5 /mnt where sda5 is the root installation of arch
arch-chroot /mnt
grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg
unmount
reboot
Any suggestions
Cheers

Windows has probably installed in EFI-mode.
From the chroot environment, post the output of:
lsblk -f
# parted -l
Also, please post in full any error messages given when you run the commands you have listed in the OP.

Can't install grub on Hardware RAID

I am having trouble finding the Grub root device for /dev/cciss/c0d0, any help would be appreciated

Gcool wrote:Don't necrobump old threads.
I don't have a new problem. I don't need a new solution. I simply thought that a more detailed explanation in this thread would not only help me, but would make this thread more useful for the next person. Apparently, the installation media has a problem with my RAID controller. In my mind, that means that anyone who tries to install Arch on an HP server is going to run into this problem. There are a lot of HP servers in the world. When I searched for my server in the forum, I only got 3 hits. That means anyone who has this problem will probably read this thread (1,278 views so far). I was trying to help the next person. One definitive thread that clearly lays out a solution in the simplest possible terms seems much more likely to be helpful then a whole bunch of threads talking about the same thing.
But ok, I'll start another. Sorry.
Last edited by Robert Finley (2012-06-04 12:12:01)

Reinstall grub for dual boot...

Hi all,
I've got Archlinux64 & WinVista64 installed as dual boot... but I'm going to have to re-install Vista again from fresh, so once it's all on again Vista will start to boot auto* 'cos it'll over written grub.
How do I install grub again... do I insert the Archlinux64 disc & ignore all the settings & just install grub?!
many TIA

if you manually mount your root partition on /mnt after booting from the arch install disc, going to setup and then choose to install grub should work I guess (not tested though )

[RAID Install] Can't install Grub - SOLVED

Me & a friend are building a local serveur on Arch (32-bit) for ~10 PCs in our association (half of them allready having AL Wink )
This server will basically have 2 main fonctions :
- NFS/YP server for a few PCs we've built under Arch for young people here
- backing up a few PCs we're using for the association.
Machine is HP with a PIV 1.7GHz, 512Mb SDRAM for now, & a single HDD IDE controller.
We got two UDMA 160GB HDD (Hitachi ) as we planned right from the start to improve on data security (& speed when possible).
I've set up partition as following :
- hda1 & hdb1, 100 Mb both, raid-1 for /boot
- hda2 & hdb2, 2 Gb both, raid-1 for swap
- hda3 & hdb3, 10 Gb both, raid-1 for /
- hda4 & hdb4, 150 Gb both, raid-1 + LVM2
Now I'm setting up Arch 0.7.2-20061104 (latest ISO from tpowa Smile ) , & everything went allright up to the point I wanna install the bootloader (might be the 10th time I set up AL this year)
To do so I'm following "Install Grub on the Primary Hard Drive (and save the RAID config)" (wich I may edit if I succeed this raid setup) with a look on "Reinstalling GRUB" both on the wiki.
1st I'm not 100% sure about mkinitcpio.conf config when it comes to raid; I've added 'raid' to HOOKS + a line just like on "Configuring mkinitpcio" :
Code:
md=2,/dev/hda3,/dev/hdb3
Edited grub/menu.lst, installed the kernel... but I want to chroot in order to install Grub I can't mount /dev :
Code:
# mount -o bind /dev /mnt/dev
keeps complaining about wrong fs type.
I chrooted anyway and launched grub :
grub> root (hd0,<TAB>
Error 21: Selected disk does not exist
I'm purely stuck here with no idea about what went wrong
If someone has spare time & knowledge, it'd be very nice indeed (our schedule says we begin to play with the network services 2morrow
EDIT : corrected the mkinitpcio.conf "md=2" line.

About install gub, I got it thanks to warnaud :
/dev/mdN was unexistent until I launched
# makedevs
Thereafter grub found the disk :
# grub
grub> root (hd0,0)
grub> setup (hd0)
grub> quit
"save the RAID config" was allready done at this point.
Guess I misconfigured something in mkinitcpio.conf / menu.lst, 'cause when I boot it says :
:: Running Hook [raid]
:: Running Hook [filesystems]
:: Loading root filesystem module...-e
Attempting to create root device '/dev/md2'
ERROR: Failed to parse bloc device name for '/dev/md2'
unknown
ERROR: root fs cannot be detected.
Kernel panic...
mkinitcpio misconfiguration maybe.
From wiki :
First add the raid hook to the HOOKS list in /etc/mkinitcpio.conf
OK :
HOOKS="base udev autodetect ide raid filesystems"
Add some Kernel Parameters is less clear, or it maybe after reading "Installing_with_Software_RAID_or_LVM" that says to list the devices in the ROOT array ?
Kernel Parameters: Specify all your md arrays with md= parameter: (only adding the raid array you're booting from is enough)
add the following to the kernel line in grub/menu.lst:
Example: md=0,/dev/sda3,/dev/sda4 md=1,/dev/hda1,/dev/hdb1
working example: kernel /vmlinuz26beyond root=/dev/md0 ro md=0,/dev/sda1,/dev/sdb1
So should one list its / or its /boot array ?

Reinstall Mac Pro and OSX on Raid 0?..

I have several 1TB drives and I want to chain 2 using the built in OSX software to make a Raid 0 drive (for speed) for the main system drive.
How do I go about doing a complete OS X reinstall, and creating a Raid? Which comes first? What are the steps? Any suggestions for settings? (Raid block size...small blocks or large?)
Lastly...does this make sense? So much of my data is on the main drive (iphoto photo sets, imovie projects, etc..all mirrored to another drive via Time Machine) that it seems to make sense that the main system drive should be fastest.
Thanks
Frank

I would not recommend using a RAID for a startup volume. However, if you're dead set on doing this, then you first need to erase the two 1 TB drives you plan to use in the array. Then create the RAID using Disk Utility. If you're not sure how then select Disk Utility Help from the DU Help menu and search for "raid." You should find article and help links on how to create RAID arrays using DU.
Once the RAID array is created clone your current startup volume to the RAID using the Restore option of Disk Utility:
How to Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means the RAID array.
Source means the current startup volume.
Finally, open Startup Disk in System Preferences, select the startup volume on your RAID, then click on the Restart button. Your computer should boot from the RAID array.
Bear in mind that if one of the drives in the array fails your startup volume is lost.
RAID Basics
For basic definitions and discussion of what a RAID is and the different types of RAIDs see RAIDs. Additional discussions plus advantages and disadvantages of RAIDs and different RAID arrays see:
RAID Tutorial;
RAID Array and Server: Hardware and Service Comparison>.
Hardware or Software RAID?
RAID Hardware Vs RAID Software - What is your best option?
RAID is a method of combining multiple disk drives into a single entity in order to improve the overall performance and reliability of your system. The different options for combining the disks are referred to as RAID levels. There are several different levels of RAID available depending on the needs of your system. One of the options available to you is whether you should use a Hardware RAID solution or a Software RAID solution.
RAID Hardware is always a disk controller to which you can cable up the disk drives. RAID Software is a set of kernel modules coupled together with management utilities that implement RAID in Software and require no additional hardware.
Pros and cons
Software RAID is more flexible than Hardware RAID. Software RAID is also considerably less expensive. On the other hand, a Software RAID system requires more CPU cycles and power to run well than a comparable Hardware RAID System. Also, because Software RAID operates on a partition by partition basis where a number of individual disk partitions are grouped together as opposed to Hardware RAID systems which generally group together entire disk drives, Software RAID tends be slightly more complicated to run. This is because it has more available configurations and options. An added benefit to the slightly more expensive Hardware RAID solution is that many Hardware RAID systems incorporate features that are specialized for optimizing the performance of your system.
For more detailed information on the differences between Software RAID and Hardware RAID you may want to read: Hardware RAID vs. Software RAID: Which Implementation is Best for my Application?

WinXP-64 bit corrupts existing RAID array

I've got an MSI K8N Neo2 Platinum motherboard running Win XP Pro SP2 on two 36 gig SATA Raptors. Everything was working fine, but I wanted to try the 64 bit version of XP. Grabbed an old 80 gig PATA drive and threw that in the case. Unplugged the SATA drives so as not to risk messing with the existing working OS. Installed the latest 1218 x64 beta and it worked well.
The problem was that when I shut down and reconnected my old RAID array, windows wouldn't boot from it. I lost everything and had to rebuild Windows from scratch. So now I know to never unplug the SATA drives
Rebuilt WinXP on the RAID array and then tried rebooting with the PATA drive with the 64 bit OS. Came up with the "drive needs checking" screen, and proceeds to "fix" the RAID array while ignoring my frantic pounding on the Logitech USB keyboard to stop. Rebooted and yes, the new install was nuked. Okay, since it's gone anyway, reboot to the 64 bit OS and make sure it's got the 64 bit RAID drivers installed.
Reinstall WinXP on the RAID array, reboot to the 64 bit OS on the other drive and the same old scandisk comes and nukes it AGAIN!
So now the PATA drive is sitting on the shelf again, unless someone here can suggest what is causing this problem.
System Specs
Athlon64 3500
gig of PQI 3200 at 2-2-2-5 2.6
2x36 gig Raptors on ports 3-4
Plextor PX-716a DVD+_RW
Visiontek X800 Pro.

The first time you re-installed Win 32 on the raid that was a bit drastic. A repair ought to have done the job.
The problem was probably that you disconnected the array but that's where the boot.ini was and that file needed to be modified to add the path to the Win64 install.
Since you took out the array the Win64 install created a new boot.ini on the PATA drive. Even when you tell BIOS to boot off the array, Windows has a bad habit of looking at the IDE channels & using the boot.ini if it finds one there - but the file it found didn't point to the array of course.
So basically if you already have Win32 on the array I would leave that array connected normally when installing Win64 on the PATA drive and all should be well.
I've installed Win64 on the same array as my Win32 install and they co-exist happily. I reckon that's the most efficient way to do it. The main thing is to make separate partitions for Win32, Win64 and data files when you install Win32 in the first place. The two OSs can share the same data files, incuding stuff like email.

A Few Issues and Questions I Have (GRUB, pacman, XBMC)

Hi everyone. (Skip to the third paragraph for where my questions start, I got a little carried away in the first two, sorry!)
I installed Arch Linux for the first time around a week ago. I am now on my third install. The first time I reinstalled because I was experimenting too much with window managers, xfce4 and other desktop environments. I tried to tweak too much and couldn't boot into a graphical environment. I know I could of removed everything using pacman and re-installing the programs I liked but I wanted to start a fresh completely, had no real other reason really. All went well and my system was up and running again with GNOME (previously my go to desktop environment). However now and again my laptop wouldn't boot GRUB. It would just stop after my BIOS screen with the Acer logo.
Eventually I started tinkering with window managers and installing just the bare minimum. I really liked what I ended with and so wanted to reinstall again. This time because I was going for the bare minimum approach, had a lot of installed bloat, wanted to move to btrfs and wanted to learn a lot more about how the system works. Previously I had followed a guide and taken very little in, if I was going to be working without a desktop environment I knew I would need to be in the command line a lot and so this time I had my longest install yet, as I read everything slowly and tried to learn what I was doing. Evidently this was my only problem free install. This time I still have my GRUB problem however.
So for my first install GRUB worked fine, however on my second and third it randomly doesn't load (Picture included at the end). After having to power off by holding the power button and restarting it will then load fine. It's unresponsive to just pressing the power button and waiting or CTRL+ALT+Delete. This can happen on a reboot or when turning on after a period of down time. AFAIK I installed GRUB the same way both times. I have tried reinstalling GRUB and the problem remains.
My second question is in regards to my many installs. Is there any easy way to see programmes I have installed so I can remove what I don't need? I have tried pacman -Qe but I still get a lot of programmes that I haven't installed, I assume they are in the base, or base-devel group, so is there anyway I can not have these showing in my list of installed packages? I don't believe an --ignoregroup option exists when running a query with pacman like it does when installing and updating.
Lastly XBMC doesn't recognise my second screen, a projector, after I have enabled it with xrandr. Now I have found a workaround by looking on google, with wmctrl and have embedded the command in my open-box menu. This makes my XBMC believe it is windowed however instead of being true full screen. I was wondering whether anybody knows of an explicit solution instead of working around the problem.
Heres the link to the picture for GRUB, this is all I get after the BIOS: http://imgur.com/a/uhVgp
Please ignore the second picture, I thought my system wasn't updating but turns out the application I thought wasn't updating was in fact in Community-Testing, not Community, oops.
I'm sorry if these solutions can be found elsewhere, I really have tried looking around but don't believe I'm finding what I need. Maybe I'm searching for the wrong terms, I'm not too sure.
Thank you for any help.
EDIT: Minor edit, but wow I've been running Arch now for 2 weeks, not 1, time flies sometimes eh?
EDIT2: FINALLY got Arch to listen to my line-in, my Wii-U audio goes through my external sound card and I have never got it to work under Linux. Been trying for over a year for this to work, had to use Windows to listen to line in. That's one less reason to keep Windows. I love Arch, guess it's time for some Smash Bros and Monster Hunter 3U tonight!
Last edited by BradPJ (2013-06-05 15:34:28)

With regard to 'pacman -Qe' output: http://allanmcrae.com/2011/07/secondary … th-pacman/ or you can exclude some packages from that listing by using grep.
Sidenote: JFC, Allan, what have you done with your blog template??

[SOLVED] Grub Problems Can boot Arch w/ grub edits only

I had 3 Linux OS's installed on this computer, Arch and 2 versions of Ubuntu on one hard drive.
The MBR belonged to Ubuntu, using grub2. I decided to get rid of the older Ubuntu (sda8 and 9) and add it's HDD space to my Arch home (sda12). Used the current Gparted live to modify the partitions and all went well, but of course, the numbers changed getting rid of 2 partitions.
No boot upon restart so I decided to get Arch's grub back to the MBR with the new partition numbering scheme.
Using a live CD, I used the grub shell, find /boot/grub/stage1.....etc, etc. and after a bit of fumbling, grub indicated success in the shell. When I was through though, a reboot was not successful, although the current stable grub was now written to the MBR. I edited the lines using grub edit option, and got Arch to boot, and figured out the correct partition numbers. Next I edited the menu.lst to reflect the new sda numbers.
Now rebooting results in a long delay when grub should be on the screen, and the numbers on the Arch entries reflect the old numbers still!! I double checked thinking I forgot to save the edits to the menu.lst file, but they are correct. I can boot Arch, but have to edit the lines each time.
The current partitions are as follows. I edited the terminal output to show details.
[jeff@Arch2009p2 ~]$ sudo fdisk -l
Password:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000383e7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 91201 732572001 5 Extended
/dev/sda5 1 255 2048224+ 82 Linux swap / Solaris
/dev/sda6 (ubuntu /) 256 1471 9767488+ 83 Linux
/dev/sda7 (ubuntu /home) 1472 22321 167477593+ 83 Linux
/dev/sda8 (arch boot) 22322 22325 32098+ 83 Linux
/dev/sda9 (arch /) 22326 23627 10458283+ 83 Linux
/dev/sda10 (arch /home) 23628 91201 542788123+ 83 Linux
I have a few questions regarding a separate boot partition for Arch.
Should the grub> root (hd0.0) command be directed to the root or boot partition.
My handy printed emergency guide says: Set grubs root device to the partition containing the boot directory.
OK.....Writing it out now, it seems clear, so I'll try reinstalling grub from a live CD.
Why does grub have incorrect partition numbers even though the menu.lst is correct?
There are only 2 OS's on this box now, and one contains grub2.
Is current grub able to interact with grub 2 if I screwed something up on the install?
Last edited by jeff story (2010-05-24 20:05:06)

OK
I managed to fix the problem of grub not reading/using the menu.lst file. Not sure WTF it was reading and where that file was located!
The problem seems to have been the most insignificant detail.
When using the grub terminal, I did not execute the quit command when I was through. I just closed the terminal and rebooted.
After repeating the following code via live CD a few times:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
Grub still didn't read the current menu.lst.
This morning I got things to work correctly and grub to read the current menu.lst by adding a quit command and returning to the linux shell prior to rebooting.
I used the following commands:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
grub> quit

[SOLVED]Unable to install grub "couldn't find /mnt/boot/grub/menu.lst"

Ok so I was trying to install windows after I had arch installed, used an ubuntu cd to use gparted to create a partition, tried to go to the windows installation but it would endlessly send me back to restart the installation even after succesfully writting all files...
So now I decided to not install it, went back into ubuntu/gparted, deleted the partition and rejoined the space with my main arch partition and then selected the "boot" flag to boot...
Cannot boot, grub its still on /boot/ but the MBR its obviously tempered with by windows ( which coincidentally couldn't even find itself after writing mbr to its liking....*sigh* ).
So I try to use my arch install cd to reinstall grub but i get this:
"couldn't find /mnt/boot/grub/menu.lst is grub installed?"
I tried to use the select packages thing to make sure the cd is mounted and mounts fine but it keeps getting me that error message. I managed to boot to my system just fine with arch root=/dev/sda1 but obviosly the kernell does not has my nvidia module which means I can't get into x which means i am using links and since my grub is not loaded i can't even get framebuffer so this is rather inconvenient.
Im sure im missing a very simple and stupid thing but im so annoyed my brain must be saying "ok im done somebody else figure it out". I still have a backup copy of my grub menu.lst I made before. Do I just delete /bood/grub/ and try again? Am I missing something on the install procedure to be able to rewrite grub? Can I just do it from the command line or with pacman? Any help appreciate it thanks.
Last edited by Misanthrope (2008-06-01 17:22:32)

If you can get into your arch and cli then you should just be able to reinstall grub with
install-grub /dev/sda
or reinstall grub with
pacman -S grub
if the package is messed up or missing.

Reinstalling grub on a RAID 0

Similar Messages

Maybe you are looking for