Grub Loading Error 17 Centos
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 1 GRUB setup Quote Postby dejanst » 2011/09/20 14:57:32 I recently upgraded from CentOS 5.7 to CentOS 6 (32 error 17 cannot mount selected partition grub bit) and I have some issues with setting up GRUB on both HDDs.The server is HP Proliant error 17 cannot mount selected partition centos 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
Error 17 Cannot Mount Selected Partition Redhat
devices.Code: Select all
== BEGIN df -h ==
Filesystem Size Used Avail Use% Mounted on
/dev/md2 9.7G 349M 8.8G 4% /
tmpfs 440M
Grub Filesystem Type Unknown Partition Type 0x83
0 440M 0% /dev/shm
/dev/md0 291M 38M 239M 14% /boot
/dev/md7 73G 180M 69G 1% /komna
/dev/md6 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 grub error 15 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
/dev/sda3 * 1530 1569 307200 fd Linux raid autodetect
/dev/sda4 1569 19458 143693824 5 Extended
/dev/sda5 1569 7943 51200000 fd Linux raid autodetect
/dev/sda6 7943 8963 8192000 fd Linux raid autodetect
/dev/sda7 8963 9600 5120000 fd Linux raid autodetect
/dev/sda8 9601 9856 2048000 fd Linux raid autodetect
/dev/sda9 9856 19458 7712870
Unanswered Index »Help & Support (Crunchbang 11 "Waldorf") »[SOLVED] Grub error 17 -Menu.1st =nothing working, but data isthere Pages: 1 #1
Grub Error 17
2010-10-27 18:18:06 CheekyBangBang Member Registered: 2009-08-15 Posts: 46 [SOLVED] Grub error 17 grub commands -Menu.1st =nothing working, but data isthere Hi.I recently shut off my laptop (dual boot, winxp then installed #!, been grub rescue working for months) and turned it back on WITH A USB hard drive plugged in.BAM!Grub is somehow messed up (error 17)...1) I've spent about 48 hours trying things I've read http://www.centos.org/forums/viewtopic.php?t=1269 about- nothing so far is working2) The data is ALL THERE (hard drive is mechanically fine, data is all accessible if mounted or viewed)3) Initially I could NOT mount the linux partitions (ext3, etc) as they were locked (I hard shut the system off I think). I booted live with gparted and also with my #! 9.04 cd's to check the http://crunchbang.org/forums/viewtopic.php?id=10056 partition tables and edit stuff4) I've saved menu.1st to a back up usb flash (I've actually saved the whole grub folder too) so I can post that too...5) Partition table is in order and, again, everything CAN be mounted and viewed (not sure about the swap).6) Everything appears normal to me-(DUH, pebkac error) but I still get this *GRUB Loading stage1.5., GRUB loading, please wait... Error 17* -then nothing.7) I added the *root (hd0,6)* lines (three of them, below) as nothing appeared for root for these. I also edited the titles (and make a backup before I did all this). #! is installed on my hd0,6 (partition #7/sda7).9) I changed the default to default 1 (to boot to windowsXP first for now) ----------------------------------------------------------------------------------------------------Here is the end part of menu.1st and below my partition table...## End Default Options ## title CrunchBang 9.04, 2.6.28-13 root (hd0,6) uuid 3a5544ef-df3d-439e-8873-ffae92bcc878 kernel /boot/vmlinuz-2.6.28-13-generic root=UUID=3a5544ef-df3d-439e-8873-ffae92bcc878 ro quiet splash initrd /boot/initrd.img-2.6.28-13-generic quiet title CrunchBang 9.04, 2.6.28-13 (recovery mode) root (hd0,6) uuid 3a5544ef-df3d-439e-8873-ffae92bcc878 kernel /boot/vmlinuz-2.6.28-13-generic root=UUID=3a5544ef-df3d-439e-8873-ffae92bcc878 ro single initrd /boot/initrd.img-2.6.28-13-generic[/color] title CrunchBang [b]9.04[/b], memtest86+ root (hd0,6) uuid 3a5544ef-df3d-439e-8873-ffae92bcc878 kernel /boot/m
Home Linux distributions Linux tutorials News Frequently Asked Questions Opensource Unix Ask/unixmen Home Linux tutorials Fixing a few common grub errors | Broken Bootloader and error 17/15 Fixing a https://www.unixmen.com/fixing-a-few-common-grub-errors-broken-bootloader-and-error-1715/ few common grub errors | Broken Bootloader and error 17/15 By M.el Khamlichi Share on Facebook Tweet on Twitter tweet Grub is short for GNU GRand Unified Bootloader. To be simply put, it’s a boot loader package from the GNU Linux project. It’s the common and reference implementation of a multiboot Linux system. It allows you to choose error 17 which operating system or specific kernel to boot into.In this article, we’ll be looking into figuring out some common grub errors and hopefully, work out a fix for them. Repairing a broken Grub 2 bootloader: There are tons of us here who broke their grub thanks to autoupdates through apt or similar. Hopefully, this will allow them an error 17 cannot way to fix their system without reinstall.Grub now features an advanced rescue mode, truly a godsend for people who somehow messed their MBR tables up.You want to trigger that and get into grub. Then execute the commands below to get back into an working desktop first.lsset prefix=(hdX,Y)/boot/grubset root=(hdX,Y)setls /bootinsmod /boot/grub/linux.modlinux /vmlinuz root=/dev/sdXY roinitrd /initrd.imgboot The X and Ys are to be filled in with your own HDD information. If you only have one HDD, it’ll be X=0, Y=1 and so on. At this point, you should atleast be able to boot up normally. You’re almost done. sudo update-grub sudo grub-install /dev/sdX Execute those two commands, replacing X with the partition your linux is installed on. For me, it was ‘a’. Voila! You’ve fixed your broken ‘auto-updated’ MBR records. Fixing grub error 17/15 Grub error 17 is one of the most common error messages that you’re likely to encounter using the Grub bootloader. The root cause behind it is a messed up partition table disk order.To fix this, grab a live cd