FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 10-29-2009, 02:35 AM
 
Default boot loader not installed

>SATA RAID is set up by the BIOS so you do not need to insmod anything.<







This is not true. While it is true that SATA RAID is setup within the BIOS, you still need drivers to tell the OS how to access the physical sectors across the individual drives. After installing Ubuntu on my SATA RAID, booting failed because the kernel says that it cannot locate the root file system. The error basically says the partition table indicates the root fs drive takes more sectors than are physically present on the disk. It is a 3 disk RAID5 with 3x 150GB WD Raptors. If I shift-pgup through the kernel output, it is seeing the 3 drives as sda, sdb, and sdd but not as 1 drive. During the live cd install, it saw the SATA RAID as a single 300GB drive and could read and mount the NTFS file system, that I let it overwrite to install Ubuntu on.





The install recognized the raid5 as /dev/mapper/nvidia_fhgbbaae1. Using the tips you gave, I figured out how to mount this file system and chroot. I used this procedure as listed in the install guide:

mount -t auto /dev/mapper/nvidia_fhgbbaae1 /media/raid -o acl,user_xattr

mount --bind /dev /media/raid/dev

chroot /media/raid



One obvious problem is that the folder /dev/mapper/ does not exist on this file system and there is no device nvidia_fhgbbaae. This device should contain

/dev/mapper/nvidia_fhgbbaae1 mounted as /

/dev/mapper/nvidia_fhgbbaae5 mounted as swap

/dev/mapper/nvidia_fhgbbaae6 mounted as /tmp

/dev/mapper/nvidia_fhgbbaae7 mounted as /home



None of these mappings exist on the root fs.* Also, as you pointed out, the install for some reason decides not to install grub when it deals with a SATA RAID. This seems to be the case whenever it detects one even when it is not the install drive. I did a second install on a different drive as I pointed out. It is a single drive with space partitioned after my Vista partition. Ubuntu still did not install grub on this drive during that install either. The command you suggested:



#dpkg -l grub-pc

* output:






Desired=Unknown/Install/Remove/Purge/Hold

| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

||/ Name*********** Version******** Description

+++-===============-===============-==============================================

un* grub-pc******** <none>********* (no description available)



I did the install as you suggested.

aptitude update

aptitude install grub-pc grub-common

this worked.* the /boot/grub directory is now populated, before was empty. It has a grub.cfg I got from http://grub.enbug.org/LVMandRAID modified to look like this:

set timeout=20

set default=0

menuentry "Linux on RAID" {

insmod dmraid

set root=(nvidia_fhgbbaae1)

linux /vmlinuz root=/dev/mapper/nvidia_fhgbbaae1

initrd /initrd.img

} Then I ran:

#grub-install /dev/mapper/nvidia_fhgbbaae1

grub-probe: error: no mapping exists for `nvidia_fhgbbaae1'



This config still does not boot. The kernel cannot find the root fs. during the live cd session I can see dmraid_45 when I do lsmod. As long as this module is loaded, the kernel can see the array and can mount the fs.* I need the help of a grub expert to go further. What is missing?



John








-----Original Message-----


From: Tom H <tomh0665@gmail.com>


To: ubuntu-users@lists.ubuntu.com


Sent: Mon, Oct 26, 2009 7:33 pm


Subject: Re: boot loader not installed














>> Forgot in my last email:



>> https://wiki.ubuntu.com/Grub2



>> "Recover Grub 2 via LiveCD" is at about 75% down the page.



>> I would "sudo su -" to avoid all the sudos.



>> You will also need to run



>> aptitude update



>> aptitude install grub-pc grub-common



>> after the chroot.











> Those commands don't work from a live cd right? When I tried to install grub



> manually after the install it halted with an error. Basically refused to



> install. I don't think I can install to the installed system from the live



> cd. I it is possible, what would be the necessary steps?







> Your last email also helps. I tried a wubi install around 6 months ago and



> had a heck of a time getting the raid to work then too. Finally found dmraid



> which worked. I didn't remember the name of it so thanks. I assumed that



> since the Ubuntu install found the raid5 and partitioned and installed on it



> that it would take care of all that automatically. 4 sleepless nights later



> it's clear that was a bad assumption.







> Of course it would also be nice it the Install coders did not allow install



> on unsupported drives. Previous versions of Ubuntu never recognized software



> raid configs in the install. When I saw it fully accessible in the



> partitioning phase of the install I got all happy and couldn't resist. Of



> course the standard drive didn't work either.







> Another question: Isn't it possible to put insmod commands after



> root=/dev/xxx? Could I not instruct the kernel to install the dmraid module



> in the boot parameters?











These commands work when booted from a Live CD but only after you



chroot. Once you are chrooted, it will be as if you are booted into



your HD. You could even "su - <yourusername>" and you will have access



to your bash history. So when you run "aptitude update; aptitude



install ..." you will install Grub 2 on your HD.







I do not think that your drive is unsupported. Grub 2 is not installed



if you choose the SATA RAID option; not quite the same thing. I assume



that if you choose "no" to the SATA RAID, Grub 2 is installed.







SATA RAID is set up by the BIOS so you do not need to insmod anything.







--



ubuntu-users mailing list



ubuntu-users@lists.ubuntu.com



Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users










--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 10-29-2009, 11:25 AM
 
Default boot loader not installed

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 10-29-2009, 12:28 PM
 
Default boot loader not installed

This is very strange behavior. Why would they code the installer this way? If it detects a SATA RAID, it goes through the install normally and then it happily reboots your system knowing full well that the new install will not boot. It does not configure a boot loader at all and doesn't give you any options. Who could possibly have thought that was a good idea? The install guides tell you how to configure a software raid but that won't work because the mappings are not there. Unless anyone else has an idea how to salvage this install, I will download the release version and take another stab at it. If that doesn't work it will be time to call this OS switch over a failure.












-----Original Message-----

From: Tom H <tomh0665@gmail.com>

To: ubuntu-users@lists.ubuntu.com

Sent: Sun, Oct 25, 2009 7:54 pm

Subject: Re: boot loader not installed











On Sat, Oct 24, 2009 at 12:43 PM, <fyrbrds@netscape.net> wrote:

> I tried to install ubuntu 9.10 beta. It completes the install but does not

> install grub. I boot with other boot cds or with easy bcd and these can find

> grub no where. Why would ubuntu think it made a proper install without a

> boot loader?

> I have tried installing it 5 times on different drives and different

> partition schemes with the same result.

>

> I want a dual boot config. I have Windows Vista on a 500GB drive (hd0)

> 300GB NTFS (hd1)

> 300GB Nvidia SW RAID w/ 3x WD Raptor 150 (hd2)

>

> Tried installing on hd2 3 times. Finally read pages with information leading

> every which way.

> Tried hd0 twice. hd0 has 160G Vista partition. I set up a 40G /home, 12G

> swp, 4G /tmp, and 80G / (sda8)

>

> All attempts to boot this config after install have failed. The Vista boot

> loader remains intact.

> I tried NeoGrub and the Super grub Boot cd. No grub install found anywhere.

>

> Last question: Is there a way to boot to a command prompt with the live cd

> for repairs? The live cd gnome terminal is practically blind-mute.



You are right about Grub 2 not being installed. I have just read this

on the Ubuntu FakeRAID help page:



"Ubiquity will fail when installing grub, and will not automatically

add dmraid to the new installation. this need to be done manually.

(the Installation guide for 8.10 and 9.04 contain the step required to

manually install these items."



--

ubuntu-users mailing list

ubuntu-users@lists.ubuntu.com

Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users






--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 10-29-2009, 08:58 PM
Tom H
 
Default boot loader not installed

>> SATA RAID is set up by the BIOS so you do not need to insmod anything.

> This is not true. While it is true that SATA RAID is setup within
> the BIOS, you still need drivers to tell the OS how to access the
> physical sectors across the individual drives. After installing
> Ubuntu on my SATA RAID, booting failed because the kernel says
> that it cannot locate the root file system. The error basically
> says the partition table indicates the root fs drive takes more
> sectors than are physically present on the disk. It is a 3 disk
> RAID5 with 3x 150GB WD Raptors. If I shift-pgup through the kernel
> output, it is seeing the 3 drives as sda, sdb, and sdd but not as
> 1 drive. During the live cd install, it saw the SATA RAID as a
> single 300GB drive and could read and mount the NTFS file system,
> that I let it overwrite to install Ubuntu on.

> The install recognized the raid5 as /dev/mapper/nvidia_fhgbbaae1.
> Using the tips you gave, I figured out how to mount this file
> system and chroot. I used this procedure as listed in the install
> guide:
> mount -t auto /dev/mapper/nvidia_fhgbbaae1 /media/raid -o
> acl,user_xattr
> mount --bind /dev /media/raid/dev
> chroot /media/raid

> One obvious problem is that the folder /dev/mapper/ does not exist
> on this file system and there is no device nvidia_fhgbbaae. This
> device should contain /dev/mapper/nvidia_fhgbbaae1 mounted as /
> /dev/mapper/nvidia_fhgbbaae5 mounted as swap
> /dev/mapper/nvidia_fhgbbaae6 mounted as /tmp
> /dev/mapper/nvidia_fhgbbaae7 mounted as /home

> None of these mappings exist on the root fs. Also, as you pointed
> out, the install for some reason decides not to install grub when
> it deals with a SATA RAID. This seems to be the case whenever it
> detects one even when it is not the install drive. I did a second
> install on a different drive as I pointed out. It is a single
> drive with space partitioned after my Vista partition. Ubuntu
> still did not install grub on this drive during that install
> either. The command you suggested:

> # dpkg -l grub-pc
> ...
> un grub-pc <none> (no description available)

> I did the install as you suggested. aptitude update aptitude
> install grub-pc grub-common this worked. The /boot/grub directory
> is now populated, before was empty. It has a grub.cfg I got from
> http://grub.enbug.org/LVMandRAID modified to look like this:
> set timeout=20
> set default=0
> menuentry "Linux on RAID" {
> insmod dmraid
> set root=(nvidia_fhgbbaae1)
> linux /vmlinuz root=/dev/mapper/nvidia_fhgbbaae1
> initrd /initrd.img
> }

> Then I ran:
> # grub-install /dev/mapper/nvidia_fhgbbaae1
> grub-probe: error: no mapping exists for `nvidia_fhgbbaae1'

> This config still does not boot. The kernel cannot find the root
> fs. during the live cd session I can see dmraid_45 when I do
> lsmod. As long as this module is loaded, the kernel can see the
> array and can mount the fs. I need the help of a grub expert to go
> further. What is missing?

The insmod commands in grub.cfg are loading grub 2 modules not kernel
modules, afaik. The grub 2 modules are listed in /boot/grub and there
is no dmraid.mod module there (so your "insmod dmraid" must not be
doing much). There are kernel modules for dmraid. In my config:
CONFIG_BLK_DEV_DM=y
CONFIG_DM_MIRROR=y
CONFIG_DM_RAID45=m
CONFIG_DM_ZERO=m

SATA RAID is called fake/software/bios/... raid because unlike real
hardware raid is not actually activated by the hardware,
pre-bootloader, independently of the os; afaik, because I have never
had the pleasure/headache of getting my hands on a dmraid box.

So the installer is seeing your dmraid disk because dmraid is
installed on the Live CD and activates the raid volumes.

grub-install calls grub-mkdevicemap and then grub-probe early on so
your "no mapping exists..." error must mean that grub-mkdevicemap is
not creating a "(hd0) /dev/mapper/..." entry and grub-probe cannot map
"/dev/mapper/..." to a grub device.

Are your "nvidia_" entries listed when you chroot to
"/dev/mapper/nvidia_" and run "ls -l /dev/mapper"? (They should since
you are running "mount -o bind /dev..." before chrooting.)

Are your "nvidia_" entries listed and ok when you chroot to
"/dev/mapper/nvidia_" and run "dmraid -r"?

Are your "nvidia_" entries listed when you chroot to
"/dev/mapper/nvidia_" and run "cat fstab"?

I have just looked at the procedure whose url I had emailed you and,
had I written it, I would have run "mount -o bind /dev
/media/raid/proc" and "mount -o bind /sys /media/raid/sys" as well as
"mount -o bind /dev /media/raid/dev" before chrooting.

Assuming that you are able to run "grub-install" successfully, I would replace
insmod dmraid
by
insmod raid
insmod mdraid
insmod lvm
insmod ext2
in grub.cfg before trying to boot from your dmraid set but I would
have the insmods both before and within the "menuentry" stanza in the
same way way the grub.cfg that is generated by grub-mkconfig has
"insmod ext2" at both these stages, even if it is probably overkill.

You could at a later stage reduce the insmod(s) to the one or those
that actually enable dmraid in grub.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 

Thread Tools




All times are GMT. The time now is 05:26 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org