How-to Install 9.10 on fakeraid

[jpichie]

Does anyone know if the GRUB2 fix has been implemented into the daily builds? or if it will be in Alpha 2 of 10.04?

[gilson585]

Not a clue but I sure am excited about it. Hope it makes it in time for release.

[cedric.driard]

The Frenchy have always a problem but this one after many installation stay the same

I think the problem is here but I didn't see any response on the forum

root@ubuntu:/# grub-install /dev/isw_diiebajfbe_Volume0
Probing devices to guess BIOS drives. This may take a long time.
/dev/isw_diiebajfbe_Volume0: Not found or not a block device.

ubuntu@ubuntu:~$ ls /dev/mapper
control.............................. isw_diiebajfbe_Volume05 ... isw_diiebajfbe_Volume08
isw_diiebajfbe_Volume0.... isw_diiebajfbe_Volume06.... isw_diiebajfbe_Volume09
isw_diiebajfbe_Volume01.. isw_diiebajfbe_Volume07

But for me I don't understand why

the full code is here if it can help

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$ sudo mkdir /mnt/root
ubuntu@ubuntu:~$ ls /dev/mapper
control                            isw_diiebajfbe_Volume05  isw_diiebajfbe_Volume08
isw_diiebajfbe_Volume0    isw_diiebajfbe_Volume06  isw_diiebajfbe_Volume09
isw_diiebajfbe_Volume01  isw_diiebajfbe_Volume07

ubuntu@ubuntu:~$ sudo mount /dev/mapper/isw_diiebajfbe_Volume07 /mnt/root
ubuntu@ubuntu:~$ sudo mount --bind /dev /mnt/root/dev
ubuntu@ubuntu:~$ sudo mount -t proc proc /mnt/root/proc
ubuntu@ubuntu:~$ sudo mount -t sysfs sys /mnt/root/sys
ubuntu@ubuntu:~$ sudo mount -t devpts devpts /mnt/root/dev/pts
ubuntu@ubuntu:~$ sudo cp /etc/resolv.conf /mnt/root/etc/resolv.conf
ubuntu@ubuntu:~$ sudo chroot /mnt/root /bin/bash
root@ubuntu:/# apt-get update
Atteint http://fr.archive.ubuntu.com karmic Release.gpg
Atteint http://fr.archive.ubuntu.com karmic/main Translation-fr                       
Atteint http://fr.archive.ubuntu.com karmic/restricted Translation-fr                  
Atteint http://fr.archive.ubuntu.com karmic/universe Translation-fr                    
Atteint http://fr.archive.ubuntu.com karmic/multiverse Translation-fr                  
Réception de : 1 http://fr.archive.ubuntu.com karmic-updates Release.gpg [189B]        
Ign http://fr.archive.ubuntu.com karmic-updates/main Translation-fr                    
Ign http://fr.archive.ubuntu.com karmic-updates/restricted Translation-fr              
Ign http://fr.archive.ubuntu.com karmic-updates/universe Translation-fr                
Ign http://fr.archive.ubuntu.com karmic-updates/multiverse Translation-fr              
Atteint http://fr.archive.ubuntu.com karmic Release                                    
Réception de : 2 http://fr.archive.ubuntu.com karmic-updates Release [44,1kB]           
Réception de : 3 http://security.ubuntu.com karmic-security Release.gpg [189B]          
Ign http://security.ubuntu.com karmic-security/main Translation-fr               
Ign http://security.ubuntu.com karmic-security/restricted Translation-fr         
Ign http://security.ubuntu.com karmic-security/universe Translation-fr           
Ign http://security.ubuntu.com karmic-security/multiverse Translation-fr         
Réception de : 4 http://security.ubuntu.com karmic-security Release [44,1kB]          
Atteint http://fr.archive.ubuntu.com karmic/main Packages                               
Atteint http://fr.archive.ubuntu.com karmic/restricted Packages
Atteint http://fr.archive.ubuntu.com karmic/main Sources
Atteint http://fr.archive.ubuntu.com karmic/restricted Sources
Atteint http://fr.archive.ubuntu.com karmic/universe Packages
Atteint http://fr.archive.ubuntu.com karmic/universe Sources
Atteint http://fr.archive.ubuntu.com karmic/multiverse Packages
Atteint http://fr.archive.ubuntu.com karmic/multiverse Sources
Réception de : 5 http://fr.archive.ubuntu.com karmic-updates/main Packages [128kB]
Réception de : 6 http://security.ubuntu.com karmic-security/main Packages [45,1kB]
Réception de : 7 http://security.ubuntu.com karmic-security/restricted Packages [14B]  
Réception de : 8 http://security.ubuntu.com karmic-security/main Sources [12,5kB]      
Réception de : 9 http://fr.archive.ubuntu.com karmic-updates/restricted Packages [14B]
Réception de : 10 http://fr.archive.ubuntu.com karmic-updates/main Sources [39,3kB]
Réception de : 11 http://security.ubuntu.com karmic-security/restricted Sources [14B]  
Réception de : 12 http://security.ubuntu.com karmic-security/universe Packages [19,3kB] 
Réception de : 13 http://fr.archive.ubuntu.com karmic-updates/restricted Sources [14B]
Réception de : 14 http://fr.archive.ubuntu.com karmic-updates/universe Packages [77,9kB]
Réception de : 15 http://fr.archive.ubuntu.com karmic-updates/universe Sources [18,8kB] 
Réception de : 16 http://fr.archive.ubuntu.com karmic-updates/multiverse Packages [6 942B]
Réception de : 17 http://fr.archive.ubuntu.com karmic-updates/multiverse Sources [3 831B]
Réception de : 18 http://security.ubuntu.com karmic-security/universe Sources [3 367B]
Réception de : 19 http://security.ubuntu.com karmic-security/multiverse Packages [1 666B]
Réception de : 20 http://security.ubuntu.com karmic-security/multiverse Sources [575B]
446ko réceptionnés en 1s (243ko/s)                 
Lecture des listes de paquets... Fait

root@ubuntu:/# apt-get purge grub2 grub-pc
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Le paquet grub2 n'est pas installé, et ne peut donc être supprimé
Le paquet grub-pc n'est pas installé, et ne peut donc être supprimé
0 mis à jour, 0 nouvellement installés, 0 à enlever et 170 non mis à jour.

root@ubuntu:/# rm -r /boot/grub
root@ubuntu:/# apt-get install grub
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
grub est déjà la plus récente version disponible.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 170 non mis à jour.

root@ubuntu:/# grub-install /dev/isw_diiebajfbe_Volume0
Probing devices to guess BIOS drives. This may take a long time.
/dev/isw_diiebajfbe_Volume0: Not found or not a block device.

root@ubuntu:/# chmod 777 /boot/grub/device.map
root@ubuntu:/# nano /boot/grub/device.map
root@ubuntu:/# chmod 744 /boot/grub/device.map
root@ubuntu:/# grub --no-curses
Probing devices to guess BIOS drives. This may take a long time.

       [ Minimal BASH-like line editing is supported.   For
         the   first   word,  TAB  lists  possible  command
         completions.  Anywhere else TAB lists the possible
         completions of a device/filename. ]

grub> grub> device (hd0) /dev/mapper/isw_diiebajfbe_Volume0
grub> device (hd0) /dev/mapper/isw_diiebajfbe_Volume0

Error 27: Unrecognized command

my device.map before and after change if someone can confirm if it's ok to

(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/sdb

(fd0) /dev/fd0
(hd0) /dev/isw_diiebajfbe_Volume0

other informations
- motherbord : asus P5QPRO
- raid : fakeraid 1 (miror)
- southbridge controller : ICH10R
- HD : 2HD 500Go SATA
- OS : WXP SP3 / maybe Ubuntu in the futur

If someone have any idea !
thanks

[gilson585]

I've read somewhere that the ICH10R chipset and its built-in raid is somewhat flaky in linux. Not sure why it had worked in 9.04 but not 9.10 in your case. I'm gonna take a wild guess here but I would like to believe dmraid can't make sense out of the metadata defining your array. The only way to prove that would be start the array from scratch. I'm sure you dont want to backup all your data and try that just to get linux, I don't blame you. Maybe wait a lil while longer for 10.04 and see if that works for you. It may also be that the command used for device is not english on your sys try typing help at the GRUB CMD line.

[cedric.driard]

I tried to install ubuntu since now 2 years (with others problems at starting ), and I really want to use linux

So I would like to try a other method

- at the install with the live CD after partitionning HD there is a advance menu where I can choose

"install boot" on dev/isw_diie..... my raid controleur is detected
"install boot" on dev/sda
"install boot" on dev/sdb

- if someone have an other idea with no scratch
- with the tuto https://help.ubuntu.com/community/FakeRaidHowto as like 9.04

If there is no solution with that, I will be happy to contribute to Linux community (and not only ask questions), I will be ok to scratch all my data (the weather will no be good this week end so I will just have to play snow with my soon), my backup is nearly ok and since I maked a new installation of WXP 2 weeks ago and I didn't take time to install all programs

But to do this, I would like someone say me what to do precisely in simply english word because I speak well in Windows but not in Linux neither in english however I will better after


Trying is the better way to learn

[[Neurotic]]

cedric - if you see my previous replies, you can see that I've run into a similar issue, as grub-install didn't work with my system either. With an update-grub, and some copying of default grub files, it worked perfectly. I didn't have to bother messing around with the device.map. Check out my previous responss for more details.

(This should probably be added to the walkthrough if grub-install fails).

[gilson585]

Before you go and remove everything I want you to look at this http://grub.enbug.org/MirroringRAID?...ght=%28raid%29 now after following my instructions up to step 8 you should try to follow whats in that link. It just may be that me and eveyone else here using raid 0 are fine but raid 1 requires a diff way to do things. Don't leave out step 13 though. Lemme know what happens.

[cedric.driard]

First test
- at the install with the live CD after partitionning HD there is a advance menu where I can choose :

"install boot" on dev/isw_diiebajfbe_Volume0 # this is my raid controleur
"install boot" on dev/sda
"install boot" on dev/sdb

With this installation on dev/isw_diiebajfbe_Volume0 ubuntu can boot with a menu list but without a Windows choice

In Ubuntu I can see (I put many things, because I don't now what can I put to be sure the system is ok in raid1) :

1. Grub2 is not install but grub 0.97 is install instead
2. In the files navigator program, I see only 1 HDD
3. cedric@cedric-desktop:~$ ls /dev/mapper

control isw_diiebajfbe_Volume05 isw_diiebajfbe_Volume08
isw_diiebajfbe_Volume0 isw_diiebajfbe_Volume06 isw_diiebajfbe_Volume09
isw_diiebajfbe_Volume01 isw_diiebajfbe_Volume07

4. cedric@cedric-desktop:~$ sudo dmraid -s

*** Group superset isw_diiebajfbe
--> Active Subset
name : isw_diiebajfbe_Volume0
size : 976767232
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0

5. cedric@cedric-desktop:~$ sudo dmraid -r

/dev/sdb: isw, "isw_diiebajfbe", GROUP, ok, 976773166 sectors, data@ 0
/dev/sda: isw, "isw_diiebajfbe", GROUP, ok, 976773166 sectors, data@ 0

6. grub> find /boot/grub/stage1

(hd0,6)
(hd1,6)

7. cedric@cedric-desktop:~$ sudo gedit /boot/grub/device.map

(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/sdb

Do you think a can make a test after this installation (for example do this how to, or test if /dev/isw_diiebajfbe_Volume0: Not found or not a block device. is already down or disconnect 1HD to see if the system is ready to boot and the other)

Second test Gilson585

I would like to be sure before testing this method, You want I do this ?

install ubuntu
execute the step 1 to the step 8 of your How to
execute the how to http://grub.enbug.org/MirroringRAID?...ght=%28raid%29
execute the step 13 to the step 14 of your How to (here I'm not sure)

Third test Neurotic

I'm not good enough in english and in linux language to try to make a similar test than you (for example I don't understand very well what is the command mount) for the moment

[gilson585]

Are you saying you got it to work? There are ways to add windows to the grub menu it's not that big of a deal. So i'm going to ask how you got to this point. Did you just choose /dev/sda for install rather than the /dev/mapper device? Being that it's Raid 1 that kinda makes sense. My suggestion is from an older set of instructions and may not be required in 9.10 if you could just test each disk individually to assure they both work as planned in a mirrored setup that would be great. If they don't we can work on this. I'd like to add the results of this to my how-to so that other users with a mirrored setup don't run into issues. Thanks for your time and effort.

[cedric.driard]

for your first question : I have just do what is writen on my previous post

But I don't like to wait, so I try a other installation with this tuto https://help.ubuntu.com/community/FakeRaidHowto and your tuto to see differences and I think this installation work well (I have a boot with the menu.lst and windows and ubuntu work)

I will post tomorrow what I do exactly and maybe do some test if you want
rapidely, I installed with the live CD without boot sequence (as write at § 3.1.2) and I changed "/target/" to "/mnt/root/" (with a mkdir /mnt/root/ before) and changed "x86_64-pc" to "i386-pc" that all

My full install with this tuto https://help.ubuntu.com/community/Fa...20installer%29

MAKE SURE YOU BACK UP ANYTHING OF IMPORTANCE!!!
This Section shows you how to install Ubuntu using the Ubiquity graphical installer found on the Live CD.

1. Modify the bios to boot on the Live CD
2. Begin the install process
   
   • creat the raid partition for ubuntu.
   • On the last step before installing, click the Advanced options and uncheck the install boot loader option. We will install grub (the boot loader later).
   • After installer finishes, close ubiquity installer and reboot the machine.
   
   
3. Start on the Live CD where you choose use Ubuntu without any change
4. Open a terminal
5. Now check that you can view the partitions in the raid array with this command
   
   1. $ ls -l /dev/mapper/
      
      • OUTPUT: control isw_beeaakeeaa_fivewe will be using the array /dev/mapper/isw_beeaakeeaa_five in this example.
      • We used /dev/mapper/isw_beeaakeeaa_five5 partition as Ubuntu root partition in this example.
      
      
   
   
6. Install dmraid and grub in your new Ubuntu installation:
   
   1. $ sudo mkdir /mnt/root
   2. $ sudo mount /dev/mapper/isw_beeaakeeaa_five5 /mnt/root/
      
      • if this fails maybe the /target directory is already mounted if not then some debuging will be required.
      
      
   3. $ sudo mount --bind /dev /mnt/root/dev/
   4. $ sudo mount -t proc proc /mnt/root/proc/
   5. $ sudo mount -t sysfs sys /mnt/root/sys/
   6. $ sudo cp /etc/resolv.conf /mnt/root/etc/resolv.conf
   7. $ sudo chroot /mnt/root/
   8. # apt-get update
   9. # apt-get install -y dmraid
   10. # apt-get install -y grub
   11. # mkdir /boot/grub
   12. # cp /usr/lib/grub/i386-pc/* /boot/grub/
   13. # grub --no-curses you will now be at the grub prompt grub>
       
       1. grub> device (hd0) /dev/mapper/isw_beeaakeeaa_five
       2. grub> find /boot/grub/stage1
          
          • OUTPUT: find /boot/grub/stage1
            (hd0,4)
          
          
          
          • make a note of the output from this command it will be needed later. in my case I have my linux partition as the first extended partition you most likely will have different results (remember that grub starts partition numbers in zero, so partition 5 for linux is partition 4 for grub).
          
          
       3. grub> root (hd'x','x')
          
          • replace 'x' with the partition number from the previous step
          
          
       4. Install grub on your disk (or partition if you prefer boot your computer with another boot manager)
          
          1. grub> setup (hd'x')
             
             • replace 'x' with the values gathered in the previous step
             
             or
             
             • grub> setup (hd'x','x') to install grub on the partition.
               YOU WILL NEED ANOTHER BOOT MANAGER TO START YOUR COMPUTER
             
             
          
          
       5. grub> quit
       
       
   14. # update-grub
       
       • say yes to creating a menu.lst
       
       
   15. now open the newly created menu list and make the following changes. Any editor can be used it is not required that you use nano # nano /boot/grub/menu.lst
       
       1. Change
          
          • # groot=(hd0,0) TO # groot=(hd0,'x')
            root option in the boot entries to root (hd0,'x') Replace the 'x' with the partition that was found earlier
          
          
       2. Add the Windows boot entry if need be.
          title Windows
          rootnoverify (hd0,0) # use the correct partition for Windows, of course
          makeactive
          chainloader +1
       3. For all Ubuntu-related boot entries, such as
          title Ubuntu ...
          root (hd0,0)
          ...change (hd0,0) to (hd'x','x') (in my case, Linux partition was not the first one, and without these changes I would get grub "Error 17" after reboot). You can use the uuid of the mapped raid partition in a grub menu.lst uuid field instead of the root (hd'x','x') field; look in /dev/disk/by-uuid with 'ls -l'.
       4. Save and exit nano. or what ever text editor you are using.
       
       
   16. # update-grub
   
   
7. make sure the new install of Ubuntu loads the raid module kernel
   
   1. # echo dm-raid4-5 >> /etc/initramfs-tools/modules
   2. # update-initramfs -u
   3. # nano /etc/modules
      
      • and add 'dm-raid4-5' if not exists
      
      
   
   
8. Reboot
9. Modify the bios to boot on your HDD
10. Start and verify both Ubuntu and the existing Windows partition boot if Windows is installed.