When installing grub, setup with a wrong device didn't produce any output. Later I tried again, fixing the error, and then I got a succeeded message. It would be better to tell users that the succeeded message is necessary, this avoids confusion when grub doesn't do a thing. Reproducible: Always Steps to Reproduce: 1.I'm not exactly sure how I did it, but I think I pointed my /boot to the wrong directory. (I can't test for the moment sorry folks) Actual Results: I got no error message from grub, but it didn't appear on boot time either. Expected Results: We should warn users to wait for a succeeded message. Confusion with grubs partition naming can produce this error, and it is very difficult and frustrating to debug.
Normally grub should give an error if it doesn't succeed...
It didn't at my system, and it took some time to find out the real source. The problem is the disk naming schema grub uses, I made a little mistake there. Anyway I think telling users to get the succeeded message is not unnecessary, but if I'm the only one who's ever had this problem this bug can be closed. (I just thought I'd give my experience with a reinstall to the community, improving to docs is always necessary)
I'll let this one linger here until someone tests (and gives some output if appropriate) grub commands. I'm currently limited to a single system and don't want to try anything on it (too important :)
I've just tried making many errors during the grub installation (wrong device, invalid kernel image, even pointing to a file that isn't a kernel) and it always resulted in an error. Perhaps it was an error in grub itself that is fixed now? I'm marking this one as WORKSFORME...
