Yes, I found that this occurs for the specific condition when the 'init' script (in the initrd) was unable to find 'vmlinuz' on the first pass, so repeats the search of the drives one-level deeper. This second pass is a precaution, a fall-back, and generally should be avoided -- only because it slows bootup a tiny bit. The first pass looks 2-deep in the directory hierarchy, the second looks 3-deep.
Anyway, I have fixed the problem. As it is in the 'init' script, which is in file initrd.gz, the fix cannot be provided as a PET for Wary 5.1 and you will have to wait for Wary 5.1.1 -- coming very soon.
No comments posted yet.