Not
quite as simple as that, my friend
But yes, the principles are basically similar to those I was going to cover in Method 2
What I write following this begs the question of Brian:
Brian, you have said that the Windows 10 lappie has come back into your possession, and that will be on UEFI.
Is the desktop or other that you have been working on, and creating USB sticks, UEFI as well?
There is a significant difference between the environment of the writer of the TecMint article and those of any number of Users, perhaps including the OP, Brian:
At Step 3, point 7, he has the following (could only capture part of it, and the screenshot is not very clear, likewise with the original article)
SCREENSHOT 1 - WRONG FOR UEFI
He changes his Device for boot loader installation from it's default (dev/sda) to his stick (dev/sdc) and that is fine for BIOS-MBR.
However under UEFI-MBR or UEFI-GPT, the following will happen:
Linux Mint will go in search of an ESP (EFI System Partition), a FAT32 partition of perhaps 512MB or as little as 2 - 3 hundred MB, on your existing setup. It will assign that entry to /etc/fstab on your stick.
Example of an fstab under such conditions:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
#
/ was on /dev/sdb1 during installation
UUID=9dd6a7c7-e522-42cb-a14f-0be9c489e960 / ext4 errors=remount-ro 0 1
#
/boot/efi was on /dev/sda1 during installation
UUID=E9DC-B605 /boot/efi vfat umask=0077 0 1
I have highlighted the lines which reflect the circumstances.
The writer was using /dev/sdc whereas I was using /dev/sdb.
If Brian were to follow the writer's article step by step, with the stick being written on a UEFI computer, and then taken to a UEFI computer, the following would likely happen:
- Windows 10 has its own small UEFI ESP, with a unique UUID
- The laptop would not be able to find the UUID described in /etc/fstab on the stick.
- It would progress a certain way through the bootup procedure, you would see a splash screen with the Mint Logo and 5 dots turning green to white and back, then ... KAPOW, you would be dumped at a tty session (black and white) where it said something like "Welcome to emergency mode..."
- The situation CAN be fixed from there, by using nano text editor to modify the /etc/fstab on the stick OR
- The Tecmint writer's procedure will work under most conditions if you first change your Setup from UEFI to CSM (Compatibility Support Module aka Grub Legacy), boot into your computer and write the stick from there, and then use it on a computer that has the same facility OR
- At the point where the TecMint writer has Step 3 point 7. you choose actively to install the ESP onto the stick itself, either by choosing /dev/sdc1 or /dev/sdb1 as identified for your stick to install it to OR in preparation stage, carve off a small FAT32 partition on your stick of about 512MB and designate it as eg /dev/sdb2 or /dev/sdc2
Under that point 3 scenario, your stick will be taking its own ESP with it.
I cannot tell how that last one will operate under a Windows only computer, as I don't have one.
Other than that, that is a good article Capta, I have bookmarked it and thanks for sharing
Brian, if you can just confirm on UEFI or otherwise of the from and to computers, I can advise further?
Cheers
Wizard
(didn't know if it would, hadnt tried it before on Multisystem).
