You are not logged in.
Pages: 1
Hello, I am trying to install Arch-64 2008.06 CD on nforce4 Fake-RAID, but I can not make Grub boot it.
I followed this wiki entry http://wiki.archlinux.org/index.php/Ins … _Fake-RAID
At the end Grub seems to install correctly, but when I try boot Arch it says:
root (hd0,1)
Filesystem type is reiserfs, partition type 0x83
kernel /vmlinuz26 root=/dev/mapper/nvidia_jjcaejaj2 ro
Error 15: File not found/dev/mapper/nvidia_jjcaejaj is my RAID array, wich has 3 partitions:
1- NTFS
2- Reiserfs -> This is boot partition
3- Swap
I think my problem is the Grub config because it is installed (it runs at start up) and it can boot my windows partition.
I installed Grub on MBR (/dev/mapper/nvidia_jjcaejaj) with following settings:
# (0) Arch Linux
title Arch Linux
root (hd0,1) # I also tryed (hd0,0) as wiki says
kernel /boot/vmlinuz26 root=/dev/mapper/nvidia_jjcaejaj2 ro
initrd /boot/kernel26.img
title Windows
rootnoverify (hd0,0)
chainloader +1Please somebody help me to make grub work and update wiki entry.
Last edited by juan_sck (2008-06-29 16:59:04)
Offline
I suggest that device-mapper is not in the kernel...check out /var/abs for a PKGBUILD..................
My ailment? Lackatesla!
Tesla fails smog test..no gas!
Favorite song...Tesla On My Mind....
Offline
I suggest that device-mapper is not in the kernel...check out /var/abs for a PKGBUILD..................
I can't probe it, but it should as I edited /etc/mkinitcpio.conf and added dmraid to hooks and dm-mod (the module needed for nforce4) to modules during the install process, and then it bulds the kernel.
Offline
I get a note when I use /sbin/lilo -v to load the new kernel parameters ...the note says to the effect that device-mapper is not in the kernel....therefore, it needs to be built via PKGBUILD. I assume that it was dropped from the kernel because only a few mobos have fake raid........
If device-mapper is not included in the kernel, then the mkinitcpio hooks won't do a thing and modprobe won't find it either.
There is a PKGBUILD in /var/abs for device-mapper.
I queried TPOWA about this and received no answer as yet. I have never had /sbin/lilo -v end up with a message of this type until kernel 2.6.25 and it caused a kernel panic.
Good luck with your boot.............
My ailment? Lackatesla!
Tesla fails smog test..no gas!
Favorite song...Tesla On My Mind....
Offline
Check this post:
dmraid problem with 2008.06 by st0nedpenguin (installation)
My ailment? Lackatesla!
Tesla fails smog test..no gas!
Favorite song...Tesla On My Mind....
Offline
Sorry about not updating the wiki, it's done now however.
I just did a fresh install and found a few new steps that were needed.
Installed on a Silicon Image Chipset and it works perfectly.
I used the Latest Overlord Install image on a USB stick.
It's dm_mod, not dm-mod btw.
Last edited by loosec (2008-06-30 21:42:55)
Offline
loosec you don't add device-mapper to kernel? you just made the steps on wiki?
in new wiki what do you mean with:
In menu.lst I had to enter (hd0,0) after root on two lines
do you mean this line?
root (hd0,1)
or this one?
kernel /boot/vmlinuz26 root=/dev/mapper/nvidia_jjcaejaj2 ro
I have also tryed to install arch on first partition. but I still can't boot it.
loosec could you post your menu.lst?
Offline
I don't know where was the problem, but today I tryed to meke a new install with core CD instead of FTP install and it works.
Thanks for your help dudes.
Offline
/boot/grub/menu.lst
title Arch Linux [/boot/vmlinuz26]
root (hd0,0)
kernel /vmlinuz26 root=/dev/mapper/nvidia_ejebcchf5 ro vga=795
initrd /kernel26.img/etc/fstab
/dev/mapper/nvidia_ejebcchf5 / ext3 defaults 0 1
/dev/mapper/nvidia_ejebcchf6 swap swap defaults 0 0
/dev/mapper/nvidia_ejebcchf1 /boot ext2 defaults 0 0
/dev/mapper/nvidia_ejebcchf8 /home ext3 defaults 0 2
/dev/mapper/nvidia_ejebcchf7 /tmp ext2 defaults 0 0
/dev/mapper/nvidia_ejebcchf9 /mnt/wst/ ntfs-3g force 0 0
/dev/mapper/nvidia_geceiece5 /mnt/wbig/ ntfs-3g force 0 0root (hd0,0) <-- this line. (hd0,0) was missing. ![]()
Offline
I'm having this problem too. Is there any solution?
Offline
juan_sck seems to have solved it by reinstalling, maybe you could be a bit more specific and post your grub menu.lst and partition table to start with?
I made a clean install with latest usb image and found no problems. Also updated the wiki then.
Offline
Why is /boot needed to be added to the GRUB lines if your boot partion is on (hd0,0). This confuses me in the wiki?
Regards
André
Offline
Why is /boot needed to be added to the GRUB lines if your boot partion is on (hd0,0)
in grub, / is the root of the partition that was set with the root command.
if you do not have a separate /boot partition, vmlinuz26 is in /boot/ (that is to say in (hd0,#)/boot/, where (hd0,#) is the root partition of your system)
if you have a separate /boot partition, vmlinuz26 is in / (that is to say in (hd0,#)/, where (hd0,#) is the /boot partition of your system)
take time to daydream, inspiration comes ...
Offline
Got it
. Many thakns my machine boots now, so I can proceed with the installation, but I get an error upon boot saying "can't parse block device" or something when it is looking at the root partition e.g. /dev/mapper/iws_baaggideei_Volume03. Then it proceeds to boot and says "going back to kernel parameters" is this something I should be worried about/fix?
Regards
André
Offline
did you put the "dmraid" hook at the end of the list in /etc/mkinitcpio.conf ?
if it is the case, try to put "dmraid" before "filesystems"
take time to daydream, inspiration comes ...
Offline
Yes, I put dmraid at the end of the HOOK line in the /etc/mkinitcpio.conf file. I'll try your suggestion when I get home from work.
Regards
André
Offline
Reinstalled and but dmraid before filesystems. Now the errors are gone, THANKS.
Regards
André
Offline
Pages: 1