Ok, I understand now what your previous question meant.
Yes, I believe the os-prober completed normally (returned to the command prompt) with the output as in the previously attached os-prober.log. I ran it with 2>&1, so both stdout and stderr would be included in that file, and I didn't notice any obvious error messages. I will re-run the process tonight to make sure I didn't miss anything we've discussed here.
If os-prober did complete properly (even in the auto install), do you have a guess as to what else might be the hang-up? I'll do the ps aux as you suggested to see what else is going on at that point in the process.
Ok, I understand now what your previous question meant.
Yes, I believe the os-prober completed normally (returned to the command prompt) with the output as in the previously attached os-prober.log. I ran it with 2>&1, so both stdout and stderr would be included in that file, and I didn't notice any obvious error messages. I will re-run the process tonight to make sure I didn't miss anything we've discussed here.
If os-prober did complete properly (even in the auto install), do you have a guess as to what else might be the hang-up? I'll do the ps aux as you suggested to see what else is going on at that point in the process.
thanks for the diagnostic help