D. R. Evans wrote on 1/24/26 2:26 PM: > Alexander V. Makartsev wrote on 1/24/26 1:48 PM: > >> It looks like these warnings appear when you try to install grub into >> disk which contains RAID array in a degraded state. [1] >> Try to boot from this disk now, if boot will be successful then you've >> done with grub and the next step is to replace missing drive and resync >> the array. >> > > OK, boot was NOT successful: > > I received the error message: disk mduuid<8d86...0aed> not found, and then it > dropped me to the "grub rescue>" prompt.
Alexander V. Makartsev wrote:
My first guess is that you are using that non-RAID disk which somehow still contains MD array metadata on it. Maybe all this time we were recovering wrong disk? Is it possible that sda and sdb devices were mixed up during boot time?
D. R. Evans wrote:
Nope, definitely not. I am very careful, each time I boot, to make sure which disk is which, because I am aware that the mapping between device name and physical drive can and does change, and one needs to be very, very careful when issuing commands that they are going to affect the correct disk.
I had just a few minutes, and thought it would be worthwhile to quickly check this by going through the entire procedure to write the MBR again, very carefully (hoping that somehow I had made a mistake the first time) -- but the result is exactly the same: the RAID disk doesn't boot, with the same error message.
I just wanted to confirm to you that the failure doesn't seem to be caused by my skipping a step or mistyping something or confusing which disk is which.
I have to go and do other stuff now for at least several hours, but will try to get back to working on the problem later today.
Doc -- Web: http://enginehousebooks.com/drevans
