grub error 17 Cannot mount selected partition for second MD RAID disk
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
grub error 17 Cannot mount selected partition for second MD RAID disk
Hi,
I have a physical linux system running Centos 6.7 kernel 2.6.32-573.12.1.el6.x86_64. It has 4 SATA disks configured into 3 MD RAID 1 mirrors, md0 for /boot, md1 for the OS and md2 for my data.
Recently I found issues with /dev/sda causing high iowait due to journalling. I checked SMART and it found issue with sda which was then failed in md0 and md1.
I rebooted to boot from sdb and got a GRUB error:
grub error 17 Cannot mount selected partition
Now, everything I have read about this error points to incorrect grub devices for the partitions. However, I have checked these thoroughly and they appear correct.
I set up md0 as metadata version 0.90 for grub compatibility so that rules out that. The remaining devices are md1 version 1.0 and md2 version 1.1.
The system was booted using BIOS not UEFI. Currently /dev/sdb is set as the first boot disk since sda failed.
Can anyone suggest anything? Until I get the system booted from /dev/sdb I cannot replace the failed disk.
Now, everything I have read about this error points to incorrect grub devices for the partitions. However, I have checked these thoroughly and they appear correct.
I generally believe the software (author).
Most likely you setup grub on the second drive whilst booted from the "first" drive. And didn't make any allowances for it by, for example, adjusting the map file.
Grub knows which drive is which - 0x80 for the first, 0x81 second ... This info gets written into the stage 1 (and 1.5) - hence the message I would guess. From the grub screen the following should re-write the stage 1/1.5 to allow you to boot
I generally believe the software (author).
Most likely you setup grub on the second drive whilst booted from the "first" drive. And didn't make any allowances for it by, for example, adjusting the map file.
Grub knows which drive is which - 0x80 for the first, 0x81 second ... This info gets written into the stage 1 (and 1.5) - hence the message I would guess. From the grub screen the following should re-write the stage 1/1.5 to allow you to boot
Code:
root (hd0,0)
setup (hd0)
I am booting from the first drive, and then running grub followed by:
root (hd0,0)
setup (hd0)
root (hd1,0)
setup (1,0)
What am I missing out? Can you provide me an example of a map file change appropriate to what I am doing please?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.