Discussion about the possible reasons for the problem continues in that thread. Meanwhile, in the hope of shedding more light on the mystery, I have tried another approach.
After deleting, reformatting and creating a new partition table on that same USB drive, I then tried again to install MX-16 from a Live session, but this time on an old and rather slow laptop (1GB RAM, 2GHz Intel Pentium 4 CPU) which only has Windows XP on it. The Live session of MX-16 works fine on that computer. So i tried another install.
The good news is that it worked (or rather, seemed to). Root, swap and home all created OK on that drive (dev/sdb). And - yay - GRUB installed fine at sdb, and the installation progressed through to the finish.
I thought I was home and dry. BUT.....
I then tried to boot into the newly-installed MX-16 USB. Problem. The booting up seemed to take an age, even on this slow machine. I got the (kingfisher wallpaper) Grub bootloader screen with the choice of OSs (MX-16 or WinXP). Chose MX-16. It started loading.... kernel and initial ramdisk. But then the screen eventually filled with a mass of text about the booting process. I couldn't take a screenshot, obviously. So I just tried to note the key information. It was - roughly - as follows . I have marked it as code but my re-typing may not have copied all the text and spaces correctly.
Code: Select all
Scanning for Btrfs file system [ numbers...] usb 1-3: device descriptor read/64, error -62 ..... and several more similar lines.... usb 3-1 device not accepting address 2 usb3 - port 1 cannot disable (error = -32) device not accepting address 4 (error -62) device not accepting address 5 (error -62) [and there were three or four similar lines not accepting address 6 and 7] [..... numbers...] usb usb2-port2: unable to enumerate USB device [ .... numbers...] end request: I/O error, dev fd0, sector 0 Gave up waiting for root device. Common problems - Boot arguments (cat/proc/cmdline) - check root delay = (did system wait long enough?) - check root = (did system wait for right device?) - missing modules (cat/proc/modules; ls/ dev) Alert! /dev/disk/by - uuid/e5e857fg-dd3d-43b2-b252-a5531d488478 does not exist Dropping to a shell! modprobe: module ehci - orion not found in modules.dep BusyBox v 1.22.1 (Debian 1: 1.220-9+deb8u1) built in shell (ash) Enter help for a list of built-in commands /bin/sh: can't access tty; job control turned off (initramfs)
Most of that means absolutely nothing to me. But it may offer clues to the experts as to why the apparently-successful install would not boot....
Any comments (in plain English!) would be welcome.