Меню Рубрики

Установка ubuntu на fakeraid

Ubuntu Documentation

Unsupported Version
This article applies to an unsupported version of Ubuntu. More info.

Needs Updating
This article needs updating to include the latest versions of Ubuntu. More info.

Introduction

What is fakeRA >

In the last few years, a number of hardware products have come onto the market claiming to be >

Older Windows versions required a driver loaded during the Windows install process for these cards, but that is changing as it has already changed in FreeBSD (which has FakeRA >

Why not use a linux software RA >

If you have arrived here after researching this topic on the Internet, you know that a common response to this question is, «I don’t know if you can actually do that, but why bother — Linux has built-in softRA >

That sa >

This wiki describes how to get Linux to see the RA >

Grub2 contains the dm_nv.mod module that allows it to read Grub files from your boot partition on nV >

  • nV >
  • with appropriate manual ‘fixes’ your pre-boot environment (initramfs) will also support activating the array and all its partitions.
  • Other cards may have less support. For example, the RocketRa >

    So Grub can boot nv >

    You have to add GRUB_PRELOAD_MODULES=»diskfilter dm_nv» to /etc/default/grub and install Grub with grub-install --modules="diskfilter dm_nv" and it will load your menu and boot from it just fine! (Tested on 16.04.3).

    What about the pre-boot environment?

    You must copy the script to /etc and append it:

    Make sure your dmra >

    Now regenerate your initramfs:

    And make sure to check that your Grub config contains the systems available on your ra >

    And install on your required device as sa >

    If this doesn’t work, copy /usr/share/initramfs-tools/scripts/local-top/lvm2 as above and add «dmra >

    Currently writing this on a 16.04.3 system booted from nV >

    Notes

    General Notes

    Ubiquity will fail when installing grub, and will not automatically add dmra >

    ‘Alternate CD’ is different to the standard Ubuntu iso download. Trying to install a fakeRA >

    The Live CD is not present in any server install ISOs. Use the desktop ISO.

    It’s critical to have dmra >

    You should be aware that dmra >

    So it secures the system from data loss, but the system can nonetheless crash. There exists patches for the 2.6.17 kernel series which enables a higher read speed and error handling in failure case, but until now they are not incorporated.

    Installation

    Always when installing something of this magnitude make sure that you back up anything of importance.

    Ubuntu 10.04 (Luc >

    The installer will recognize the dmra >

    Ubuntu 9.10 (Karmic Koala)

    The automatic installer may or may not work out of the box. When I tried it, it d > the first time and I had to manually install dmra > same machine, (with disks that had been wiped) The problem appears to be installing grub2

    * Boot the system with the Live CD

    * Run the partitioner program gparted (System->Administration->GParted)

    /dev/mapper/pdc_feddabdf or some suchlike

    * Setup an extended partition using whatever space your going to allocate for Ubuntu or the entire drive. Setup a minimum of 2 logical partitions in the extended partition, the first will be formatted ext4 and the last swap. Set the type on the swap partition to swap. Format the first partition. Exit gparted

    * Run the installer. When it gets to it's partitioner, change the mount point on the first partition to / DO NOT format it! Do NOT make any partition changes! The installer partitioner does not understand dmra >

    * In the installer summary screen right before the copy process starts, click the Advanced button. Change the boot partition (this is the MSDOS-style "parent" partition not the Linux partitions) to /dev/mapper/pdc_feddabdf (or whatever dmra >

    * When the installer finishes DO NOT REBOOT, the new system will be mounted on /target. If you rebooted then run the terminal screen and mount the /dev/mapper/pdc_feddabddf4 (root) partition (this is the target the installer put the root on) on some convenient directory (/tmp/tmp or some such) chroot that directory (/target or whatever it's mounted on)

    * Run the command "apt-get install dmra >

    * When the system comes back up login and verify that /dev/mapper/pdc_feddabdf (or whatever dmra > fakera >

    Ubuntu 8.0.4 LTS (Hardy Heron)

    Open a terminal and type: There should be a listing for the ra >

  • Manually partition using cfdisk, create at least two partitions, swap and root.
    • Start the GUI installer and complete the install.
    • Make sure you only use partitions you created yourself in case partitions are listed doubly.
    • The installer fails to install Grub and you must do it from the command line.
    • There was apparently a bug in 8.04 where the initrd d >

    Previous Releases

    Documentation for older, unsupported releases has been moved to /Historical.

    Troubleshooting: User Contributions

    One possible source of error is that if you have several kernels installed, only one initrd gets updated, and that you therefore might boot with an old initrd where the dmraid modules and hooks are missing; To avoid this, run update-initramfs -u -k where would be the kernel version you would like to boot with, in the format given by uname -r.

    1. 18 June 2006:

    Another user reported this same problem. dpkg-reconfigure d >

    1. 08 June 2007:

    I've followed this tutorial but used a knoppix 5.1.1 CD and installed Debian lenny. I encountered one more problem that seems to be a bug in GRUB and is described here: "ALERT! does not exist" at boot with ICH7. I've used the stage files from the feisty+mem_lower.tgz to overwrite my Debian lenny files, because the Ubuntu debian package had some unresolvable dependencies.

    1. 22 June 2007:

    The File Not Found error from Grub when the savedefault option is used in menu.lst is because the file /boot/grub/default does not exist. I manually created this file by executing 'sudo grub-set-default 0' from within the installed system. This should also work when initially setting up Grub, as described above. Adding this file eliminates the need to remove the savedefault option from the menu.lst each time you run update-grub (eg, after a kernel upgrade).

    1. 21 Oct 2007

    Gutsy uses linux-generic as the kernel which loads optimizations at runtime. Instead of "apt-get install linux-386 # or k7, k8, k8-smp, etc" simply use "apt-get install linux-generic".

    1. 30 Nov 2008

    I followed this instructions to the letter, but I got grub error 15 (File not found) during boot, although all the file were on place. However, grub d >

    This solved my error 15 issue.

    1. 15 Jan 2009

    I've just managed to make work a Gigabyte MA78GPM-DS2H motherboard RA > This is a pdc controller. I configured RA >

    dmra > More strangely, after reboot, BIOS launched an alarm that one of the disks is nonfunctional. The alarm gone after hard reset.

    Now the solution: go to BIOS, delete your configuration and create it again. But this time change two options:

    • - "Gigabyte bonduary" to "NO" - "Fast Init" to "NO"

    I am now waiting until Ubuntu is installed, hopefully grub part will be easy. Regards.

    1. 26 Jan 2009

    I followed these instructions - Method 2 in long - and they worked perfectly EXCEPT for booting Windows.

    Windows was an XP installation on a single ATA drive that wasn't part of the (new) RA >

    The section is "Chainloading Windows on a non-first hard disk". The problem lies with Windows - it expects to be on the first drive. In the Windows section of Menu.lst, I now have:

    hd0 is my (booting) RA > hd1 is my (non-booting) ATA drive with windows in the first partition (hd1,0). The two map commands fool Windows into thinking it is on the first drive. This works.

    This is a GREAT tutorial! I have learned much about my hardware and Ubuntu.

    I have an Asus A8V motherboard and had Gutsy running on it for some time. The moment I activated SATA ra >

    Possibly because of the above issue (or not?) I could not set the ra >

    I am using the six partition method with boot ( >

    I have found that gparted does not work correctly (for me). I used fdisk and mkfs.

    Another strange situation is, during Live CD installation, the partition section shows multiple lines for each of the ra >

    Also, if you are using a Live CD install, ""do not"" deselect grub install. It could wreck any previous grub instalaltion.

    1. A Striping with Fake Root (9.04 ubuntu)

    Since I skipped the step installing raid 4-5 (modprobe dm-raid4-5), I later skipped installing the module (echo dm-raid4-5 >> /etc/initramfs-tools/modules). Since I don't need the dm-ra > rmra > I then had to run the following command from above (as noted in the modules file): update-initramfs -u

    The last thing I had to do was edit my /boot/grub/menu.lst It had placed root=/dev/hda1, which needed to be replaced by my root=/dev/mapper/Mapper_Device_ >

    I also poured salt in my wound, if you'd like to see how, reed my forum post: http://ubuntuforums.org/showthread.php?p=7281944#post7281944

    Would it be possible for someone to update for ubuntu 9.10 - the partitioning section in particular is confusing.

    Added something about Alternate CD at the top - hope people don't mind, but if you're new to Ubuntu, you don't know what this is and don't realise that it's an official thing which you need to download.

    My windows boot drive has 139gb free space according to Windows' 'Computer Management' app, but only 27mb according to the ubuntu installer's partitioning app - hence I can't install it. After 2 tries to get started on linux and each time discovering it'll likely be thrice as hard as I thought it would be the time before (an example. Also saw the number of times partitions appear in the Ubuntu problems fixlist), I'm now asking myself (/the ubuntu braintrust) "should I persevere with Ubuntu, given that it's clearly not going to be the the ant >

    1. 9.10 How-To

    I have prov >

    1. 10.04 Installation on isw fakera >

    Had to work around the installer. Q&A'ed it in question 108677 in launchpad. Trick was using chmod on the disc's root partition! Just mount the root partition into the /media folder. Then sudo chmod 755 /media/fake

    1. 10.04 Addition for the Live CD installation (Ubiquity Graphical installer)

    (Own experience with an intel RA >

    5.a. alternatively you could test you ra >

    6. Partitioning and formatting with ubiquity installer d >

    6.b. After creating new partition on the ra >

    • Output should show the activation of the new partition(s).

    6.c. Format the new partition(s) with the file system you want

      Z is the number of the new partition.

      Example: $ mkfs.ext4 /dev/mapper/isw_beeaakeeaa_five5

    8.a. Do not format nor partition using the ubiquity installer. in manual mode, choose the "/" mounting point on the partition you want and make sure "format" checkbox is unchecked. As you already format the partition in the step 6.c. it should allow you to attach "/" without formatting.

    9.l.ii The command find /boot/grub/stage1 resulted in an error for me I had to do the following command to make Grub recognize my ra >

    • Replace C H S (Cylinders, Heads and Sectors) above with the proper numbers. You can find them using cfdisk at the top of the main screen (be aware: they are not displayed in the same order).
      • Example: 18079 255 63 for a RA >

    9.l.iii

    • Replace Y with the drive number. Usually 0 as specified in the step 9.l.i.
    • Replace X with the partition number from the previous step.

      9.p. Make sure the device.map file is correct. This file is used to map the dmra >

      • Edit the file:
      • and add the following line:

      Make sure there is no other line beginning by (hd0).

    If you have multiple dmra >

    11. Dual-Boot configuration.

    In case of a dual boot with Win7, grub may have some problem to launch windows. An easy solution is to install grub on the linux partition (not the MBR). Cf. step 9.l.iv, grub> setup (hd0,4) Then, use the Win7 boot manager to choose between windows and linux. To add a new entry into the win7 boot manager, you can use the official "bcdedit" command or the unofficial graphical utility named "EasyBCD 2.0 beta".

    15. 10.10 Addition for the Live CD installation (Ubiquity Graphical installer) (Own experience with an nv >

    The built in installer nearly works. There is just some issue about a restricted hard-drive area used by some motherboards, which is ignored by default in Ubuntu. Ignoring this area interferes with fakera >

    16. 12.04 LTS 04 January 2014:

    Setting up a dual-boot system 12.04 LTS/Win7

    As stated above, the reason to use fakera >

    16.a Disable EFI-Settings - Disabling EFI and choosing "legacy only" avo >

    16.b Boot the Ubuntu Live-CD, for the system this gu >

    16.c Choose "Try Ubuntu" - Once the Live Environment is booted start "gparted"

    16.d Using gparted set up the partitons you want Ubuntu to use. (eg. ROOT and SWAP)

    16.e Once this is finished reboot the System with a Windows-Installation Medium. Be mindful to have the RA >

    16.f Once the installation of Windows is finished, boot the ubuntu live-CD again and this time choose "install ubuntu".

    16.g Click through the installation screens and configure everything to your liking UNTIL you reach the point, where Ubuntu asks you for the partition layout. Here you must choose manual partitioning and tell Ubuntu to use the partions you set up during step 16.d. DO NOT FORMAT these partitions, just install onto them. Otherwise the Installer messes up the partition setting and you have to start from the beginning.

    16.h Also of importance is that you choose the whole RA >

    16.i Once this is done continue the installation as normal and reboot the system when told to do so.

    16.j If everything went well you are presented with a GRUB bootscreen, that allows you to boot into ubuntu or Windows.

    16.k Now finish the setup of ubuntu and Windows (drivers software etc.) I recommend this as the very last step, since the time you invest here will be lost, if something does not go according to plan.

    Please contribute your lessons learned here.

    The material on this wiki is available under a free license, see Copyright / License for details
    You can contribute to this wiki, see Wiki Guide for details

    источник

    Intel fake raid and linux

    Есть ли какая нибудь возможность подключить intel fake raid в linux? Нашел на этом форуме одну тему, однако не смог туда добавить сообщение. кто-то юзает Intel Fakeraid? Судя по этой теме, Pavval (www.linux.org.ru/people/Pavval/profile) как то это делал. Хотелось бы с ним связаться, но нигде нет контактов. Буду благодарен за любую помощь.

    А чем mdadm не устраивает?

    Есть ли какая нибудь возможность подключить intel fake raid в linux?

    Есть, подключай. apt-get install dmraid.

    Для загрузки с него нужно иметь dmraid в initrd, нормальные дистры это делают.

    насколько я понял mdadm поддерживает только software raid. Мне нужен линукс и винда на одном рэйде. В принципе до mdadm я пока просто не добрался, начал копать с dmraid.

    Все это дело ставится на мини-линукс, в котором нет менеджеров пакетов. Сегодня смог собрать dmraid из исходников, и удалось примонтировать fake-raid. И при этом даже ничего не сломалось. Однако, покопался я с ним немножко, и понял, что dmraid не подойдет мне. Утилитка img (которая из zenworks), и даже fdisk отказались его видеть. В связи с этим вопрос, нет ли где-нибудь в ядре поддержки fake-raid, чтобы он виделся как обычный диск?

    Утилитка img (которая из zenworks), и даже fdisk отказались его видеть. В связи с этим вопрос, нет ли где-нибудь в ядре поддержки fake-raid, чтобы он виделся как обычный диск?

    Он отлично видется как диск - ищите проблему у себя. Обычно после активации создаются устройства в /dev/mapper/. Они прекрасно понимаются тем же fdisk. У меня были проблемы с тулзами, которые пытались как-то получить список дисков в системе (тот же gparted видел /dev/sda и /dev/sdb вместо состоящего из них /dev/mapper/isw_*). К kde partition manager я даже сделал патч, который это чинил, но разработчик не откликнулся. Может симлинки в /dev/sd* исправят это.

    fdisk -l выдает как раз /dev/sda и /dev/sdb и ни слова об /dev/mapper/. но это не так важно. Главное img не видит. А поподробнее про симлинки можно? Предлагаете сделать симлинк типа /dev/sdc -> /dev/mapper/isw_xxxxxxxxxxx? И еще прочитал что его grub не понимает. А grub2 или lilo мне не подходят. Так что же насчет ядра?

    источник

    fakeraid

    Мать Socket АМ2 GIGABYTE GA-M55PLUS-S3G nForce 4, в описании говорится что она имеет интегрированный raid контроллер. Я почитал инфу про интегрированные raid контроллеры, и как выяснилось это fakeraid 🙂

    В связи с этим у меня есть несколько вопросов:
    1. Какие-то функции исполнены аппаратно, или всё-таки все функции реализованы програмно?
    2. Если в raid 0 закинуть более 2-х винтов, то производительность будет расти?
    3. Если контроллер программный, то чем завести raid? mdadm?

    Re: fakeraid

    Здравствуйте, 1. - Все функции реализованы программно. 2. - Да, будет. Только RAID0 - этог вообще не RAID (redundant array of independent disks). Использовать его можно только под /tmp. 3. - Да, mdadm.

    Re: fakeraid

    > Использовать его можно только под /tmp

    И ещё один вопрос:
    Есть утилита dmraid, она предназначена для поднятия raid массива, созданного другой утилитой или она предназначена для поднятия fakeraid настроенного в bios?

    Re: fakeraid

    напрягитесь и поищите в google описание RAID0, который вообще не имеет права называться raid'ом.

    Re: fakeraid

    > Есть утилита dmraid, она предназначена для поднятия raid массива, созданного другой утилитой или она предназначена для поднятия fakeraid настроенного в bios?

    Да, модуль dmraid используется для поднятия сконфигурированного в Bios массива на совтовых контроллерах. По всем параметрам (скорость, надежность) уступает mdadm. Практически, бывает нужен только в одном случае - при совместной установке Windows и Linux на один массив.

    Конечно, можно подобрать и другие ситуации, где RAID0 уместен. Вроде /var/spool/squid. Да и то, проблемы с диском даже в этом случае приведут к простою сервера. Выше я приводил расшифровку аббревиатуры RAID. Ключевым здесь является слово redundant - избыточный. Нормальный RAID (1, 3, 5, 10, 50, 1+0) выдерживает гибель одного из дисков без потери данных и остановки машины. Особо надежные уровни (6, 1ee) выдерживают вылет даже 2-х дисков. В случае же RAID0 сбой любого из дисков приведет к потере всей информации. На самом деле, ситуация еще хуже - развал массива и гибель данных может произойти из-за случайного логического сбоя контроллера или диска, вызванных, например, скачком напряжения в дешевых блоках питания. Таким образом, приходим к выводу, что RAID0 можно использовать только для хранения временных данных, не имеющих существенной ценности и только в машинах, не критичных к времени простоя.

    Re: fakeraid

    PS. На счёт ненадёжности RAID0 я в курсе(просто сначала не понял прикол с /tmp). Но всё-таки я буду его использовать, поскольку у меня дисковая система самое узкое место, и информация на нём будет только для зчитывания. Если случится какая-то трабла, то в будущем вы увидите пост: как востановить инфу с raid0 🙂

    Re: fakeraid

    > Если случится какая-то трабла, то в будущем вы увидите пост: как востановить инфу с raid0 🙂

    Дабы не плодить темы, сразу пишу ответ - никак.

    источник

    Читайте также:  Установки индикаторов для mt4

    Добавить комментарий