On 12 November 2014 15:25, Michael Chesterton <[email protected]> wrote: > On 12/11/14 15:13, DaZZa wrote: >> Has anyone come across this before? Is it something specific to >> Ubuntu, or is it the stupid "SecureBoot" crap (which was turned off, >> by the way) they put into the BIOS for these things doing *something* >> to the "disk" to make the second device not recognise it? >> >> Not really an issue, because I've fixed them so they both boot now - >> but I'm intensely curious as to *why* this happened. > > I have no idea aboot secure boot, it might be the problem, no idea. > I have seen a linux appliance that wouldn't work after being dd'd > because the mac address changed and the ethernet device > became eth1, and the appliance had hard coded eth0 in it. > > I can't see how that would matter in this scenario, but thought > I would mention it.
It didn't even get as far as loading the NIC drivers - I coulda sorted that - it just wouldn't even see the disk as a valid boot device. It's just strange - I can't understand why it would boot off the "disk' in one device but not the other when they are otherwise identical. DaZZa -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
