On Mon, 16 Dec 2013 21:50:28 -0800 King Beowulf <[email protected]> dijo: la any attempt to boot to SDB would >>> just hang. However, on the Ubuntu forums I found a suggestion to >>> use: >>> >>> sudo grub-install /dev/sdb >>> >>> And afterward it no longer hangs when I select SDB to boot to. >>> Unfortunately, the boot proceeds on SDA, not SDB. It would be >>> interesting to see what would happen if I physically removed SDA >>> from the computer, but I haven't tried that yet. >>> >>> I think the problem is somehow conglomerated with the UUID >>> numbers, /etc/fstab, and /boot/grub/grub.cfg, but I'm not sure how >>> to fix it. I do know that I can use tune2fs to generate a new >>> random UUID for a device. But I don't know if that is the solution, >>> or which device to give a new UUID to, or what changes to make to >>> grub.cfg and fstab after doing so.
>UUIDs need to be unique. Its kinda the point of using them. You should >also check your BIOS settings to make sure that booting from mSATA is >(1) possible (2) Selected (3) at the top of the boot order. Often >there is a fuction key, F12 on some laptops, that will pop up a BIOS >boot menu to pick your divice (hard drive, DVD/CDROM, USB etc.). > >https://wiki.debian.org/Part-UUID >https://help.ubuntu.com/community/UsingUUID > >I haven't used grub much yet as my distro of choice hasn't switched to >it yet. They will pry LILO from my cold, dead keyboard!! I should have mentioned something about the BIOS. There is no way to set the boot order in the BIOS as is customary. It always boots to the optical drive first and then to the hard drive *unless* you press F7 at the BIOS splash screen. Thoughtfully, there is a menu item on the splash screen that says "Press F7 th change boot order." When you press F7 it becomes highlighted so you know it "took" - you don't have to keep pressing whatever the magic key is to get into the BIOS. Then a list of devices pops up and you can select which one you want to boot to. However, I don't know yet how the BIOS decides which is the hard drive that it should boot to. As for booting from the mSATA, Sager / Clevo (the US distributor / Chinese manufacturer) offers to sell the computer with an mSATA as the operating system drive, so it certainly must be possible. While reading about tune2fs I noted that you can give the partition a label, e.g., "this_is_the_boot_partition," and then you can use the label in both grub.cfg and fstab instead of the UUIID. I'll probably use tune2fs to give SDB1 and SDB2 random new UUIDs and enter the UUIDs into the appropriate places in grub.cfg and fstab instead of trying a label. The problem is editing grub.cfg, because reading it and figuring what is the boot line is not trivial. I have never had to edit a grub 2 config file; I only understand the old grub, and that not terribly well. I looked at the grub.cfg file on SDB1 and sorting out what is a menu line and what is not is confusing as heck. I see UUIDs scattered all through it. It will take a lot of study to figure it out. :( _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
