Thanks for your continued support. We need to set aside SMAP and Iso-Hybrid approach for a moment because now we have a real non-booting case. Recall that the partition in the HDD caddy was corrupted, and that my ultimate goal was to replace the SSD with a larger one. So I did, and moved the smaller SSD to the HDD caddy. Now I have two cloned Windows partitions to boot from, the larger one in the main HDD slot, and the smaller one in the HDD caddy. Unfortunately, BSOD.
This is the larger SSD that replaced the smaller one:
/dev/sda1: UUID="2496E29E96E2702A" TYPE="ntfs" PARTUUID="051396f8-01"
/dev/sda2: LABEL="System Reserved" UUID="8E500369500356FD" TYPE="ntfs" PARTUUID="051396f8-02"
/dev/sda4: LABEL="WIN-P" UUID="000352A9000F2D09" TYPE="ntfs" PARTUUID="051396f8-04"
/dev/sda5: LABEL="BOOT" UUID="1676-EF88" TYPE="vfat" PARTUUID="051396f8-05"
/dev/sda6: LABEL="OS" UUID="b109ad1f-eef8-4623-a1f2-e86da390b290" TYPE="ext4" PARTUUID="051396f8-06"
unallocated space follows.
This is the smaller SSD that got replaced and moved to the HDD caddy located in the CD-drive slot, see my first post for physical interface info:
/dev/sdb1: UUID="3496E29E96E2702A" TYPE="ntfs" PARTUUID="051396f8-01"
/dev/sdb2: LABEL="System Reserved" UUID="9E500369500356FD" TYPE="ntfs" PARTUUID="051396f8-02"
/dev/sdb4: LABEL="WIN-P" UUID="100352A9000F2D09" TYPE="ntfs" PARTUUID="051396f8-04"
/dev/sdb5: LABEL="BOOTX" UUID="2676-EF88" TYPE="vfat" PARTUUID="051396f8-05"
/dev/sdb6: LABEL="OSx" UUID="c109ad1f-eef8-4623-a1f2-e86da390b290" TYPE="ext4" PARTUUID="051396f8-06"
I cloned the smaller SDD to the larger one using clonezilla with default parameters. Then I used methods  and  to change the UUIDs of all partitions on the smaller disk. Notice that each UUID in /dev/sdb is the same as the corresponding UUID of /dev/sda with the first hex digit augmented by 1. I also used gparted to change the labels of sdb5 and sdb6. This concerns my Linux bootloader entries, and I think it shouldn't matter for Windows.
A glitch is that PARTUUIDs are the same between the two disks. I don't know how to change them, and I don't know if it matters, because I've never seen PARTUUIDs referenced in grub4dos. But maybe Windows and other bootloaders use them?
sda3 is the extended partition that holds sda5 and sda6. Similarly for sdb3.
sda2 and sdb2 are bootable. sda5 and sdb5 are hidden.
Windows grub4dos boot entry sda1:menu.lst (and sdb1:menu.lst). This entry used to work just fine when the smaller SSD (sdb) was in sda's place, and a Toshiba HDD was in the caddy (without booting it):
title Windows 7 (sda2:PBS)
Now that entry works to boot Win7 to a blue screen:
STOP 0x0000007B 0xFFFFF880009A9928
My intention is to boot off the larger SSD entirely, but I think that the boot process follows the smaller SSD, because file BOOT/BCD.LOG1 in sdb2 is newer than the corresponding file in the larger SSD.
I didn't change BCD - not sure how to do it. I booted Hirens and opened sda2/Boot/BCD with BootICE in edit mode but I don't see any partition UUID or PARTUUID to guide me. One thing I noticed is that the OS Title entry was changed from "Windows" to "Windows (recovered)". Possibly Windows attempted a repair on the first boot? The OS Title entry of sdb3/Boot/BCD is still "Windows".
So, I'm stuck.
Out of curiosity, are the devices both the exact same size?
The grub4dos screenshot you posted shows for both 14594/255/63 and 234452610 sectors, i.e. 120,039,736,320, around 120 GB.
Yes, they are. I noticed the coincidence too, a Samsung SSD and a much older TOSHIBA HDD exactly the same. But the TOSHIBA is gone now.
Edited by stepdown, 11 December 2017 - 09:09 AM.