Grub Error 17 Raid
Contents |
RAID 1 GRUB setup General support questions Post Reply Print view Search Advanced search 7 posts • Page 1 of 1 dejanst Posts: 124 Joined: 2011/09/20 14:13:13 [SOLVED] Problems with RAID error 17 cannot mount selected partition grub 1 GRUB setup Quote Postby dejanst » 2011/09/20 14:57:32 I recently upgraded from CentOS
Error 17 Cannot Mount Selected Partition Centos
5.7 to CentOS 6 (32 bit) and I have some issues with setting up GRUB on both HDDs.The server is grub filesystem type unknown partition type 0x83 HP Proliant Microserver that is running 2 HDD's that have the same capacity. Both HDDs have the same partition layout, the partitions are properly combined in 8 RAID devices.Code: Select all
== BEGIN df
Error 17 Cannot Mount Selected Partition Redhat
-h ==
Filesystem Size Used Avail Use% Mounted on
/dev/md2 9.7G 349M 8.8G 4% /
tmpfs 440M 0 440M 0% /dev/shm
/dev/md0 291M 38M 239M 14% /boot
/dev/md7 73G 180M 69G 1% /komna
/dev/md6 grub error 17 android x86 49G 180M 46G 1% /telos
/dev/md5 2.0G 35M 1.8G 2% /tmp
/dev/md3 7.7G 883M 6.5G 12% /usr
/dev/md4 4.9G 215M 4.4G 5% /var
== BEGIN fdisk -l ==
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/md3 doesn't contain a valid partition table
Disk /dev/md4 doesn't contain a valid partition table
Disk /dev/md5 doesn't contain a valid partition table
Disk /dev/md6 doesn't contain a valid partition table
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f15fe
Device Boot Start End Blocks Id System
/dev/sda1 1 1275 10240000 fd Linux raid autodetect
/dev/sda2 1275 1530 2048000 fd Linux raid autodetect
/d
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
Grub Error 17 Fix
Gentoo Wiki Jump to: navigation, search The objective of this article is
Grub Error 17 Windows 7
to list problems and errors that may occur in certain situations when using the GRUB Legacy bootloader. All grub error 15 these solutions have been acquired through 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 http://www.centos.org/forums/viewtopic.php?t=1269 2.2 Solution 3 GRUB Error 12 3.1 Situation 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 https://wiki.gentoo.org/wiki/GRUB_Error_Reference drives. This may take a long time 8.1 Situation 8.2 Solution 9 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
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About http://serverfault.com/questions/57366/how-can-i-boot-linux-from-a-software-raid-1-array Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers error 17 are voted up and rise to the top how can I boot linux from a software raid 1 array up vote 2 down vote favorite 2 I'm trying to make a raid array on an existing linux ubuntu install. I'm following this tutorial... http://howtoforge.org/software-raid1-grub-boot-fedora-8 After going through the list of things a million times I finally understand what's going on. You make the raid device, on your grub error 17 new blank drive, copy your old / drive to it, set up the grub menu.lst, fstab, mtab initrd and grub MBR to all point to the raid device (which I have defined and is working) and then you reboot. Once you've booted, you now run in the raid device (/dev/md0) Then you merely hook your original drive up to the raid array, it syncs and voila you're done. So I set up my menu.lst to primarily load the kernel and initrd from the raid device, and failover to my original (still intact) old disk. And it always fails over when I reboot. I boot the machine, run my new grub entry and it says "error 15 file not found." Lots of stuff on the web about it, none seem to help. The only thing that's weird is when I go to setup the MBR with grub, you say "root (hd0,0)" which I finally understand what it means, and it's supposed to say Filesystem type is ext2fs, partition type 0xfd or somethingn like that. Mine says nothing. But when I run setup (hd0) and setup (hd2) it says it's doing the right thing to the right drive. So I ass