Grub Error 17 Fakeraid
Contents |
Notes RAID-1 RAID-5 Installation Ubuntu 10.04 (Lucid Lynx) and 10.10 (Maverick Meerkat) Ubuntu 9.10 (Karmic Koala) Ubuntu 8.0.4 LTS (Hardy Heron) Previous Releases Troubleshooting: User Contributions Introduction what is fakeraid What is fakeRAID? In the last few years, a number of
Ubuntu Fakeraid
hardware products have come onto the market claiming to be IDE or SATA RAID controllers. These have mdadm fakeraid shown up in a number of desktop/workstation motherboards and lower-end servers such as the HP DL360 G5, if ordered without the optional RAID card. Virtually none of these
Fakeraid Linux
are true hardware RAID controllers. Instead, they are simply multi-channel disk controllers combined with special BIOS configuration options and software drivers to assist the OS in performing RAID operations. This gives the appearance of a hardware RAID, because the RAID configuration is done using a BIOS setup screen, and the operating system can be booted from the ubuntu 14.04 fakeraid RAID. With the advent of Terabyte disk drives, FakeRAID is becoming a popular option for entry-level small business servers to simply mirror 2 1.5 TB drives, and dispense with an expensive hardware RAID 5 array. 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 FakeRAID support built into the ATAPI disk driver). Under Linux, which has built-in softRAID functionality that pre-dates these devices, the hardware is normally seen for what it is -- multiple hard drives and a multi-channel IDE/SATA controller. Hence, fakeRAID. Why not use a linux software raid? 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 softRAID capability." Also, it's not clear that there is any performance gain using hardware fakeRAID under Linux instead of the built-in so
#1 2011-06-13 16:10:20 snoxu Member Registered: 2010-01-24 Posts: 141 [Solved] GRUB, FakeRaid: Filesystem unknown, cannot mount partition Hello folks I've been on an Arch Linux hiatus for a while because I've had a hard time setting up GRUB
Linux Dmraid
and a FakeRaid on a Vaio laptop with a quad raid0 SSD drive.I
Intel Fakeraid
followed the begginers, Fakeraid, and chroot wiki pages to the best of my knowleged but still can not get things dmraid ubuntu setup properly. It's a bit too involved if you asked me and I only have Arch installed.As far as I know GRUB stage 1.5 starts loading, in the boot menu I select https://help.ubuntu.com/community/FakeRaidHowto Arch Linux, then I get the following error message:Booting 'Arch Linux' root (hd0,1) Filesystem type unknown, partition type 0x82 kernel /boot/vmlinux26 root=/dev/mapper/xxxxxxxxxxxxxxxx_Volume0p1 ro Error 17: Cannot mount selected partitionI can't really figure out how to fix this, so any help is apreciated.CheersFor reference this is how I have the drive partitioned/dev/mapper/xxxxxxxxxxxxxxxx_Volume0 /dev/mapper/xxxxxxxxxxxxxxxx_Volume0p1 / /dev/mapper/xxxxxxxxxxxxxxxx_Volume0p2 swap /dev/mapper/xxxxxxxxxxxxxxxx_Volume0p3 extended /dev/mapper/xxxxxxxxxxxxxxxx_Volume0p5 ntfs Last edited by snoxu (2011-06-13 17:52:21) Offline https://bbs.archlinux.org/viewtopic.php?id=120787 #2 2011-06-13 17:47:39 snoxu Member Registered: 2010-01-24 Posts: 141 Re: [Solved] GRUB, FakeRaid: Filesystem unknown, cannot mount partition Nevermind I figured it out after a few long hoursI had to chroot into the system and edit the /boot/grub/menu.lst because my root partition is in (hd0,0) and (hd0,1) points to the swap partitionToo bad the grub setup and /arch/setup for fakeraids is a bit too involved and can be prone to error. Would be great if fakeraid setup was a bit more straight foward or somewhat automatic.I never had this issue with my non raid systems.Would of saved me a lot of precious hours.Cheers Last edited by snoxu (2011-06-13 17:59:57) Offline Pages: 1 Index »Installation »[Solved] GRUB, FakeRaid: Filesystem unknown, cannot mount partition Board footer Jump to Newbie Corner Installation Kernel & Hardware Applications & Desktop Environments Laptop Issues Networking, Server, and Protection Multimedia and Games System Administration Other Architectures Announcements, Package & Security Advisories Arch Discussion Forum & Wiki discussion Pacman & Package Upgrade Issues [testing] Repo Forum Creating & Modifying Packages AUR Issues, Discussion & PKGBUILD Requests GNU/Linux Discussion Community Contributions Programming & Scripting Other Languages Artwork and Screenshots Atom topic feed Powered by FluxBB
systemHardwareSoftwareDesktopServer & SecurityProject & Community Tools What links hereRelated changesSpecial pagesPrintable versionPermanent linkPage informationBrowse properties User Create accountLog in Toggle navigation PageDiscussion View source more History GRUB Error Reference From Gentoo Wiki Jump to: https://wiki.gentoo.org/wiki/GRUB_Error_Reference navigation, search The objective of this article is to list problems and errors that may occur in certain situations when using the GRUB Legacy bootloader. All these solutions have been acquired through https://answers.launchpad.net/ubuntu/+question/111755 the cooperation of users on the Gentoo Forums. Contents 1 Starting notes 1.1 Acknowledgements 1.2 Disclaimer warning 2 GRUB loading, please wait... 2.1 Situation 2.2 Solution 3 GRUB Error 12 3.1 Situation grub error 3.2 Solution 4 GRUB error 15 4.1 Situation 4.2 Solution - Initial configuration 4.3 Solution - Booting an entry 5 GRUB error 17 5.1 Situation 5.2 Solution 6 GRUB error 18 6.1 Situation 6.2 Solution 7 GRUB GRUB GRUB GRUB GRUB ... 7.1 Situation 7.2 Solution 8 Probing devices to guess BIOS drives. This may take a long time 8.1 Situation 8.2 Solution 9 grub error 17 When installing GRUB, it just hangs 9.1 Situation 9.2 Solution 10 Uncompressing Linux... Ok, booting the kernel 10.1 Situation 10.2 Solution 11 GRUB just shows a GRUB prompt 11.1 Situation 11.2 Solution 12 Could not find device for /boot/boot: not found or not a block device 12.1 Situation 12.2 Solution 13 The system reboots after hitting return at the GRUB menu 13.1 Situation 13.2 Solution 14 After hitting the Enter (Return) key at the GRUB menu, the screen blanks out 14.1 Situation 14.2 Solution 15 Missing GRUB image 15.1 Situation 15.2 Solution 16 Failing To boot Windows from a second hard drive 16.1 Situation 16.2 Solution 17 GRUB segfaults when trying to install 17.1 Situation 17.2 Solution Starting notes Acknowledgements Many thanks to Earthwings, penetrode, loyaltonone, pilla, airhead, nephros, yamakawa and all the others for the suggestions on the original thread. Disclaimer warning The examples provided are just examples. Be sure to change partition numbers and the like according to the specific systems specs. Follow the solutions provided by this document at the readers own risk. GRUB loading, please wait... Situation GRUB loading stage 1.5 GRUB loading, please wait... After thi
use a mix of solutions from the page https://help.ubuntu.com/community/FakeRaidHowto Of course... fixing the installer so it can handle dmraid devices and partitions would be a plus ;)... as would fixing the GRUB install so that it correctly installs to the virtual device I defined..... would make all of the following headache go away. ;) In general I had to follow these instructions for the live CD installation, for my NVIDIA Raid 5 array in order to dual boot with a pre-existing windows installation. Ubuntu 10.04 The automatic installer may or may not work out of the box. When I tried it, it didn't work for a variety of reasons. The problem appears to be the installer not handling dmraid virtual disks correctly, as well as issues installing grub2 to the virtual disk. Use the LiveCD method * Boot the system with the Live CD 10.04 loads dmraid automatically so you should see a disk device via the df command, or "ls -l /dev/mapper. My NVIDIA showed up as: nvidia_ehcjahgf nvidia_ehcjahgf1 (My Windows XP Primary Partition) * Run the partitioner program gpartd (System->Gpart) ;;Gpart did not see the NVIDIA RAID at all, and the System>Administration>Disk Utility could not read the architecture of My 750G Virtual Drive until I had created the partitions from the installer. So what I had to do was: 1. Run the Live CD install until it failed attempting to format the ext4 partitions I created 2. Quit the install and load System>Administration>Disk Utility 3. Select The Disk that represented My NVIDIA RAID5 Array and format the new partitions correctly (ext4, and swap) 4. Reboot the system with the live CD and restart the installation if dmraid detected and can use a fakeraid partition * Setup your partitions (as oulined in the preceding 4 steps) using whatever space your going to allocate for Ubuntu or the entire drive. Setup a minimum of 2 partitions (logical, or primary as per your needs keeping i mind the maximum of 4 total primary+extended partitions allowed per disk), the first will be formatted ext4 and the last swap. Set the type on the swap partition to swap. Format the all of your newly created partitions for the appropriate file systems (ext4, swap). REBOOT using the Live CD before continuing to the next step. ;; My NVIDIA Array now looks like this after the reboot. ~$ ls -l /dev/mapper total 0 crw-rw---- 1 root root 10, 59 2010-05-20 05:08 control brw-rw---- 1 root disk 252, 0 2010-05-20 05:08 nvidia_ehcjahgf (The virtual disk) brw-rw---- 1 root disk 252, 1 2010-05-20 05:10 nvidia_ehcjahgf1 ( My windows Partition) brw-rw---- 1 root disk 252, 3 2010-05-20 05:08 nvidia_ehcjahgf2 (Ubuntu '/') brw-rw---- 1 root disk 25