On Thu 29 Jan 2026 at 22:17:21 (+0500), Alexander V. Makartsev wrote: > On 1/29/26 21:31, David Wright wrote: > > ... > > Before moving on from the "ls" step, the OP needs to see some > > output that ends in /grub, at least resembling: > > > > Grub> ls (hdX,msdosY)/boot/ > > … … … … … … grub/ … … … … … > > Grub> ls (hdX,msdosY)/boot/grub/ > > … a list of Grub directories Grub> … … grub.cfg … … > > > > at which point, these commands should work: > > > > Grub> set prefix=(hdX,msdosY)/boot/grub > > Grub> set root=hdX,msdosY > > Grub> insmod normal > > Grub> normal > > > > giving access to all of Grub's commands. > His prefix "/boot/grub" and "/" is inside md array, so <TAB>-asking > existing device (hdX,msdosY) will return nothing.
(hdX,msdosY) was a placeholder; the OP needs to try them all. I would have left the other drive(s) in the machine, in case Grub could find some modules on a different partition from the target. What I was trying to point out was that if insmod normal was the first instruction after booting, as you posted, Grub would have done that for itself. > Instead, (md/0) <TAB> should show "/boot" If completion is working, Grub will add the / anyway. But using <Return>, it should show the partition type, if it is capable. (<Tab> might show that too, in passing; I don't remember.) > I'm confident those commands (some of them are redundant) I typed will > boot OS with his storage configuration from a grub command line. > There is even no apparent reason for boot process to go through grub > rescue in a first place. I was unaware that you could decide whether to "go through grub rescue"; I thought it was a choice made by Grub, depending on how much of itself it succeeds in finding. It's tricky for me to copy what the OP is doing: how much am I willing to wreck my system to avoid Grub getting beyond the rescue prompt. That's why I don't know, for example, whether completion works. There may be a lot else that doesn't work. Cheers, David.
