Unable to boot after flubbed install

[Old-Polack]

You could, at this time edit your /etc/fstab to replace the UUID number for the / partition with LABEL=FullMonty.

You could, at this time edit your /etc/fstab to replace the UUID number for the / partition with LABEL=FullMonty.

I assume this means what it says - delete UUID blah blah and replace it.  After doing that it shows the label and UUID in blkid.  That's not right is it?

[root@localhost ~]# blkid
/dev/sda10: LABEL="FullMonty" UUID="187311e0-2e0b-4803-90d7-b8166adac79a" TYPE="ext4"
/dev/sda2: UUID="e1da4c29-17a1-4e79-aa96-0a635a212c48" TYPE="swap" LABEL="swap320"
/dev/sda11: LABEL="Storage" UUID="1b607915-eb7c-4d9b-b4ec-c7c731274b17" TYPE="ext4"
/dev/sda1: LABEL="boot320" UUID="72ae1006-30b6-4e0a-bb2a-ef33258c3f96" TYPE="ext3"

Just want to check before I butcher the menu.lst

The blkid UUID numbers  will stay the same. Only in the /etc/fstab file, and the master menu.lst file, do you replace the UUID=<whatever number> with

/etc/fstab:

LABEL=FullMonty at the beginning of the / partition line, and;

LABEL=swap320 at the beginning of the swap partition line.

And in the master menu.lst, the changes I showed in the previous post, highlighted in blue.

Again, my blkid;

[root@fatman Documents]# blkid

Code:

/dev/sda1: LABEL="boot750" UUID="985efd35-13a4-4279-8129-0f9552d95ccb" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: LABEL="swap750" UUID="0ccd09b0-ebb4-4f78-8c73-632232adf438" TYPE="swap"
/dev/sda3: LABEL="750pclos" UUID="ace4498d-cd4b-458b-9b0c-853c0679fe70" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda5: LABEL="Documents2" UUID="d9550e51-e2e6-4b48-b382-d491ab0bc1ea" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda6: LABEL="share9" UUID="3abe7220-57d1-40c8-acb3-b8d13585577f" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: LABEL="Documents" UUID="6c984560-d3bc-4ea9-b2ad-62586c662bcf" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda10: LABEL="120backup" UUID="3dff9abc-88c0-47dc-bd2c-f3f991acab69" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda11: LABEL="storage00" UUID="f0320f20-48d5-4ddb-89ed-9da4676aefa4" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb1: LABEL="boot1000" UUID="10165aee-8b41-4c52-aa7e-c6b0d6d17eeb" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: LABEL="swap1000" UUID="8b44f813-fd45-4f94-b519-28300b4791ad" TYPE="swap"
/dev/sdb3: LABEL="TR5" UUID="6ae6cf37-7fd2-4b9c-86dc-f037141745bb" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb6: LABEL="tmpback" UUID="dcf02721-aca8-494f-8182-cc8ab1df8430" TYPE="ext3" SEC_TYPE="ext2"
/dev/sdb5: LABEL="TR5-Documents" UUID="9c1bbdf4-5f3c-4d70-b03a-983504da6c15" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb7: LABEL="TR6" UUID="36feb97d-2f61-4709-b6f5-8e8d8fee3370" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb8: LABEL="kde2011" UUID="8c17ff68-f606-4148-98ac-1e85324e7bc6" TYPE="ext4"
/dev/sdb9: LABEL="kde64-2" UUID="a8fdfcab-c52a-4de2-adce-28738e49f388" TYPE="ext4"
/dev/sdb10: LABEL="st-backup" UUID="7b1f293e-8deb-49de-adbf-db9173fd2599" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb11: LABEL="os-backups" UUID="3d1692bb-afe0-4648-b5be-d30f1eca32e7" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb12: LABEL="movies2" UUID="fad35a11-5738-401e-88b6-56b78dfeb15a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb13: LABEL="share1" UUID="9c1c0b28-b24c-40ed-8c90-e5c704021548" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb14: LABEL="minime2010" UUID="ab32e99a-5bb8-4360-b75d-e13df5412608" TYPE="ext4"
/dev/sdb15: LABEL="kde64-4" UUID="15788c3a-2767-4c9e-8ebf-a0a488c1820c" TYPE="ext4"
/dev/sdb16: LABEL="minime12" UUID="d31989a1-48f3-4875-848b-a66db2e86f09" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb17: LABEL="kde64" UUID="78e81c20-8949-487b-b685-de84a16c8802" TYPE="ext4"
/dev/sda8: LABEL="750mm" UUID="b512d57e-3c7a-4226-96ea-98ba93d5d486" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: LABEL="movies" UUID="90ae3f6a-46b2-485a-886d-e4c203491907" SEC_TYPE="ext2" TYPE="ext3"

And my /etc/fstab;

[root@fatman Documents]# cat /etc/fstab

Code:

# Entry for /dev/sda8 :
LABEL=kde2011           /                       ext4    defaults,noatime                1 1
LABEL=TR5-Documents     /home/polack/Documents  ext3    rw,user,noauto,exec,noatime     0 0
LABEL=Documents2        /home/polack/Documents2 ext3    rw,user,noauto,exec,noatime     0 0
# LABEL=share7          /share7                 ext3    rw,user,noauto,exec,noatime     0 0
LABEL=share1            /share1                 ext4    rw,user,auto,exec,noatime       0 0
LABEL=share9            /share9                 ext3    rw,user,auto,exec,noatime       0 0
LABEL=movies            /movies                 ext3    rw,user,auto,exec,noatime       0 0
LABEL=movies2           /movies2                ext3    rw,user,auto,exec,noatime       0 0
# LABEL=TV-1            /tv                     ext3    rw,user,noauto,exec,noatime     0 0
LABEL=storage00         /zstorage00             ext3    rw,user,noauto,exec,noatime     0 0
LABEL=120backup         /zbackup                ext3    rw,user,noauto,exec,noatime     0 0
LABEL=boot1000          /mnt/boot               ext3    rw,user,noauto,exec,noatime     0 0
#LABEL=part17           /mnt/17                 ext4    rw,user,noauto,exec,noatime     0 0
none                    /proc                   proc    defaults                        0 0
# Entry for /dev/sda2 :
#LABEL=swap200          swap                    swap    defaults                        0 0
# Entry for /dev/sda2 :
#LABEL=swap300          swap                    swap    defaults                        0 0
# Entry for /dev/sdc2 :
LABEL=swap1000          swap                    swap    defaults                        0 0
# Entry for /dev/sde2 :
LABEL=swap750           swap                    swap    defaults                        0 0
none                    /dev/pts                devpts  mode=0620                       0 0
/dev/fd0                /mnt/floppy             auto    rw,user,noauto,exec             0 0
/dev/sr0                /mnt/cdrom              auto    ro,user,noauto                  0 0
/dev/sr1                /mnt/dvd                auto    ro,user,noauto                  0 0
# none                  /dev/shm                tmpfs   defaults                        0 0

From my master menu.lst, for this OS.

title KDE 2011
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=KDE_2011 root=LABEL=kde2011 quiet nokmsboot acpi=on resume=LABEL=swap1000 splash=verbose vga=791
initrd (hd0,7)/boot/initrd.img

title KDE 2011 - BP
kernel (hd0,0)/kde2011/vmlinuz BOOT_IMAGE=KDE_2011 root=LABEL=kde2011 quiet nokmsboot acpi=on resume=LABEL=swap1000 splash=verbose vga=791
initrd (hd0,0)/kde2011/initrd.img

[MtnMan]

Sorry o-p I was editing while you typed.  You sample only the first 2 stanzas but they all have to be changed right?

[Old-Polack]

Sorry o-p I was editing while you typed.  You sample only the first 2 stanzas but they all have to be changed right?

Yes, but the changes are the same throughout.

[MtnMan]

Sorry o-p I was editing while you typed.  You sample only the first 2 stanzas but they all have to be changed right?

Yes, but the changes are the same throughout.

Thanks - the day is burnt for me.  I will have to review and be back tomorrow.

[MtnMan]

o-p> This is my master menu.lst and I can't imagine what it will look like with several installations.  Can I comment out some, and if I need to boot into (for example) failsafe , un-comment from a live CD - or just not worry that my boot options will stretch from here to Chile?  I think you said you only add the first 2 but the I wonder how you would boot to failsafe in that case.  It may be more obvious when I add another OS which I am pretty nervous about right now.

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,9)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320 splash=silent vga=788
initrd (hd0,9)/boot/initrd.img

title PCLinuxOS_FullMonty - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320 splash=silent vga=788
initrd (hd0,0)/FM/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320
initrd (hd0,9)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320
initrd (hd0,0)/FM/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=LABEL=FullMonty quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,9)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe) - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=LABEL=FullMonty quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,0)/FM/initrd.img

title memtest-4.20 - BP
kernel (hd0,0)/FM/memtest-4.20 BOOT_IMAGE=memtest-4.20

title memtest-4.20
kernel (hd0,9)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20

[Old-Polack]

o-p> This is my master menu.lst and I can't imagine what it will look like with several installations.  Can I comment out some, and if I need to boot into (for example) failsafe , un-comment from a live CD - or just not worry that my boot options will stretch from here to Chile?  I think you said you only add the first 2 but the I wonder how you would boot to failsafe in that case.  It may be more obvious when I add another OS which I am pretty nervous about right now.

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,9)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320 splash=silent vga=788
initrd (hd0,9)/boot/initrd.img

title PCLinuxOS_FullMonty - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320 splash=silent vga=788
initrd (hd0,0)/FM/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320
initrd (hd0,9)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320
initrd (hd0,0)/FM/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=LABEL=FullMonty quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,9)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe) - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=LABEL=FullMonty quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,0)/FM/initrd.img

title memtest-4.20 - BP
kernel (hd0,0)/FM/memtest-4.20 BOOT_IMAGE=memtest-4.20

title memtest-4.20
kernel (hd0,9)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20

Certainly! 

As I stated before, when I add new installations I only copy the first boot stanza from the  new installation, then copy and modify it to make a - BP stanza. I don't bother with the failsafe and non-fb stanzas. With multiple installations, unless the hard drive itself fails, one or the other of the full installations will boot, giving a full compliment of tools and a comfortable GUI to work from. I still do the actual fixing from a terminal, but I have full use of my browsers for Google of forum searches on the net.

I only had you modify the failsafe and non-fb stanzas in case you have problems before adding any additional installations. You can comment them out at any time, to reduce the entries shown in the initial boot menu. As you said, if needed, they can easily be uncommented from a liveCD.

I just checked, and my master menu.lst has a total of 209 lines. I'd go nuts too, if I didn't have all but the most used stanzas commented out. They are there when I need them, they just don't show most of the time.

[MtnMan]

As I stated before, when I add new installations I only copy the first boot stanza from the  new installation, then copy and modify it to make a - BP stanza. I don't bother with the failsafe and non-fb stanzas. With multiple installations, unless the hard drive itself fails, one or the other of the full installations will boot, giving a full compliment of tools and a comfortable GUI to work from. I still do the actual fixing from a terminal, but I have full use of my browsers for Google of forum searches on the net.

Thanks - now I think I am ready to add another (LXDE) - normally I let the installer find and add other installs but in this case (if my understanding is correct) it doesn't matter.  It won't touch the menu list on the boot partition and I can copy from the boot menu list to the master boot as before or is it going to be different now that the boot partition is mountable.  Sorry if it seems to be low level noobness but that's where I am at.  This is the part that I am really nervous about.

[Old-Polack]

Thanks - now I think I am ready to add another (LXDE) - normally I let the installer find and add other installs but in this case (if my understanding is correct) it doesn't matter.  It won't touch the menu list on the boot partition and I can copy from the boot menu list to the master boot as before or is it going to be different now that the boot partition is mountable.  Sorry if it seems to be low level noobness but that's where I am at.  This is the part that I am really nervous about.

When installing a new OS none of the hard drives partitions will be mounted. When you get to the grub install stage, pick the new / partition as the place to install grub. When done, there will be no new boot stanza in the master menu.lst, only in the new installation's menu.lst. Before you can boot to the new installation you will need to boot to the original installation, mount the new / partition, then copy the first stanza from the new menu.lst to the master menu.lst. Save the master menu.lst and reboot. The new boot menu option you just created will then allow booting to the new installation.

Once you have the new installation set up, with a root password and normal user, have logged in as the normal user and set up your desktop and such, you can then, as root, use the mkdir command to create a /mnt/boot mount point directory, and mount the boot partition on /mnt/boot.

[root@localhost ~]# mkdir -p /mnt/boot               <Enter>

[root@localhost ~]# mount LABEL=boot320 /mnt/boot              <Enter>


Then, as a repeat of what you did with the original installation, copy the new /boot directory to /mnt/boot, only this time, rename it LXDE.

Open /mnt/boot/grub/menu.lst (the master menu.lst) copy/paste the newly added LXDE stanza directly below the original, (leaving a blank line between) and modify the new copy to create a - BP stanza using;

title LXDE - BP
kernel (hd0,0)/LXDE/vmlinuz <yada-yada>
initrd (hd0,0)/LXDE/initrd.img

If you LABEL the new / partition LXDE, you can then also do the changes from the UUID numbers to root=LABEL=LXDE and resume=LABEL=swap320 in both LXDE stanzas, before saving the file.

At which point you are ready to reboot and test both LXDE stanzas.

[MtnMan]

HALP!  I think I may have done something wrong.  After installing LXDE it rebooted into LXDE - was I supposed to pick sda1 as default maybe?  I had deleted all the other boot options.   
Sorry it took awhile but I got swamped with work before I could do this.

When you get to the grub install stage, pick the new / partition as the place to install grub. When done, there will be no new boot stanza in the master menu.lst, only in the new installation's menu.lst. Before you can boot to the new installation you will need to boot to the original installation, mount the new / partition, then copy the first stanza from the new menu.lst to the master menu.lst.

I did look at the master menu.lst and it is the same. 

[Old-Polack]

HALP!  I think I may have done something wrong.  After installing LXDE it rebooted into LXDE - was I supposed to pick sda1 as default maybe?  I had deleted all the other boot options.  
Sorry it took awhile but I got swamped with work before I could do this.

When you get to the grub install stage, pick the new / partition as the place to install grub. When done, there will be no new boot stanza in the master menu.lst, only in the new installation's menu.lst. Before you can boot to the new installation you will need to boot to the original installation, mount the new / partition, then copy the first stanza from the new menu.lst to the master menu.lst.

I did look at the master menu.lst and it is the same.  

Yup!

As long as you are there, go ahead and to what was posted in my last reply, and when done, do this again, choosing;

root (hd0,0)

setup (hd0)

http://www.pclinuxos.com/forum/index.php/topic,62786.msg508062.html#msg508062

Then:

root (hd0,n)

setup (hd0,n)

Where n is the / partition of LXDE, at which point all will be as it should be. Grub is easy to fix.  

By the by, (hd0,1) is your swap partition.

[MtnMan]

HALP!  I think I may have done something wrong.  After installing LXDE it rebooted into LXDE - was I supposed to pick sda1 as default maybe?  I had deleted all the other boot options.   
Sorry it took awhile but I got swamped with work before I could do this.

When you get to the grub install stage, pick the new / partition as the place to install grub. When done, there will be no new boot stanza in the master menu.lst, only in the new installation's menu.lst. Before you can boot to the new installation you will need to boot to the original installation, mount the new / partition, then copy the first stanza from the new menu.lst to the master menu.lst.

I did look at the master menu.lst and it is the same. 

Yup!

Making mistakes is just part of the learning process.  I went back and reinstalled to get a feel for the right way.

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,9)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320 splash=silent vga=788
initrd (hd0,9)/boot/initrd.img

title PCLinuxOS_FullMonty - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320 splash=silent vga=788
initrd (hd0,0)/FM/initrd.img

#title PCLinuxOS_FullMonty-nonfb
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320
initrd (hd0,9)/boot/initrd.img

#title PCLinuxOS_FullMonty-nonfb - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=LABEL=FullMonty quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320
initrd (hd0,0)/FM/initrd.img

#title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,9)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=LABEL=FullMonty quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,9)/boot/initrd.img

#title PCLinuxOS_FullMonty(failsafe) - BP
kernel (hd0,0)/FM/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=LABEL=FullMonty quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd0,0)/FM/initrd.img

#title memtest-4.20 - BP
kernel (hd0,0)/FM/memtest-4.20 BOOT_IMAGE=memtest-4.20

#title memtest-4.20
kernel (hd0,9)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20

title PCLinuxOS_LXDE
kernel (hd0,8)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=LXDE  quiet nokmsboot vmalloc=256M acpi=on resume=UUID=e1da4c29-17a1-4e79-aa96-0a635a212c48 splash=silent vga=788
initrd (hd0,8)/boot/initrd.img

title PCLinuxOS_LXDE - BP
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=LXDE  quiet nokmsboot vmalloc=256M acpi=on resume=UUID=e1da4c29-17a1-4e79-aa96-0a635a212c48 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

Now when I boot there is the LXDE boot screen (with sda1 as default) then the Master boot screen.  I can go to boot options in LXDE and make the timer 0 but I am wondering if this is expected.  I probably missed a step and suspect you're going to color this line.

Have to go back to work now.  Stink.

[Old-Polack]

Now when I boot there is the LXDE boot screen (with sda1 as default) then the Master boot screen.  I can go to boot options in LXDE and make the timer 0 but I am wondering if this is expected.  I probably missed a step and suspect you're going to color this line.

Have to go back to work now.  Stink.

That would indicate that you again installed the LXDE grub in the MBR, and it has a chainload stanza to (hd0,0) as default. To reestablish (hd0,0) as the true "master", you still need to do the grub native install using;

root (hd0,0)

setup (hd0)

title PCLinuxOS_LXDE - BP
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=LXDE  quiet nokmsboot vmalloc=256M acpi=on resume=UUID=e1da4c29-17a1-4e79-aa96-0a635a212c48 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

should be;

title PCLinuxOS_LXDE - BP
kernel (hd0,0)/LXDE/vmlinuz BOOT_IMAGE=linux root=LABEL=LXDE  quiet nokmsboot vmalloc=256M acpi=on resume=LABEL=swap320 splash=silent vga=788
initrd (hd0,0)/LXDE/initrd.img

[MtnMan]

old-polack> After fixing the labels and MBR repair, we have been booting from the boot partition without any problem.  I was not able to get to my computer much lately so haven't added anything else yet.   Having your precise and clearly detailed instructions at hand, I will be doing this many times and expect it will feel more comfortable after that.  In fact, I plan to print it all out.  You are a good and patient teacher.  Thank you much.

[Old-Polack]

old-polack> After fixing the labels and MBR repair, we have been booting from the boot partition without any problem.  I was not able to get to my computer much lately so haven't added anything else yet.   Having your precise and clearly detailed instructions at hand, I will be doing this many times and expect it will feel more comfortable after that.  In fact, I plan to print it all out.  You are a good and patient teacher.  Thank you much.

It seems complicated, and a bit of an extra hassle at first, but I've been doing this for years, and the whole extra process now takes me less than two minutes for each installation. Repetition definitely causes the process to become second nature.

You are most welcome.