On 2014-05-03 02:02, James Knott wrote:

The odd thing is, if I plug in the old drive, which is mounted in an external case, it will boot Windows from it. Is the drive ID stored somewhere I'm missing? Fstab has also been updated to the correct drive.

Actually, yes. Windows will detect the disk change and refuse to start, but you should see a message about that, very clearly. In that case, you simply have to clone the disk identifier with fdisk. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2014-05-03 02:31, James Knott wrote:

Carlos E. R. wrote:

...

On 2014-05-03 02:02, James Knott wrote:

Then why did it boot before I moved Linux over and set up grub?

I don't know.

Also, wouldn't the ID be the same, as I have the same partition layout as before?

No, the ID is the disk ID, not part of the partition layout. Just run "fdisk -l /dev/..." on each disk (old and new) and you will clearly see an entry labelled "disk identifier". If it is different, Windows will refuse to run. There is a menu entry in fdisk to change it, in the "extra functionality" menu. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2014-05-03 04:27, James Knott wrote:

Carlos E. R. wrote:

I changed it and no difference.

Oh, then we have to keep searching. :-( -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 05/02/2014 11:56 PM, Andrey Borzenkov wrote:

В Fri, 02 May 2014 20:02:47 -0400 James Knott пишет:

...

I recently replaced the hard drive on my Thinkpad E520 with a larger one. I have moved all the partitions over and can now boot into Linux, but I can not boot into Windows 7. After installing the Windows partition, but before installing the Linux partition, I could boot into Windows. I have checked and rechecked the grub menu and also verified that /boot/grup/menu.lst & device.map are correct, device.map is irrelevant at boot time

...

but I still cannot boot into Windows. It stops at:

map (hd0) (hd0) map (hd0) (hd0) rootnoverify (hd0,1) chainloader +1

Here is the relevant part of menu.lst:

title Windows 7 map (hd0) (hd0) map (hd0) (hd0) rootnoverify (hd0,1) chainloader +1

The odd thing is, if I plug in the old drive, which is mounted in an external case, it will boot Windows from it.

Probably you need to "activate" the Windows partition. There is a free program (Google it) that will do that. It might replace the Linux grub, but you can then put that back from a live CD (redo mbr). It doesn't seem to work if you "activate" from GParted-- don't know why. You might also be able to "activate" from the Windows install disk, but I haven't done that. It would almost surely replace the boot sector with a Windows one, and then you'd have to run redo mbr. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 03:44 (GMT+0200) Carlos E. R. composed:

James Knott wrote:

...

wouldn't the ID be the same, as I have the same partition layout as before?

No, the ID is the disk ID, not part of the partition layout. Just run "fdisk -l /dev/..." on each disk (old and new) and you will clearly see an entry labelled "disk identifier". If it is different, Windows will refuse to run. There is a menu entry in fdisk to change it, in the "extra functionality" menu.

I'm puzzled by Carlos' response. AFAIK, entries in /dev/disk/by-id/ are unique to each individual HD, not something that can be altered, but would likely be at least a component of the ID the Windows hardware identification system is using. As is normal for him, James has provided limited information about what he did, e.g. his meaning of his words "move" and "installing". It's entirely unclear whether he cloned with a true cloner, or used a partitioner to create partitions which he created filesystems on then copied to, or some mix of functions, or whether anything was done to ensure the new HD had anything in it other than what's in its last 66 bytes. I've seen no clear indication of whether his failure to boot Windows on the new HD happens while the old remains attached or not, and whether external case is USB2, USB3 or eSATA. What disk identifier did he change, and where did he make the change? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 09:07, Felix Miata wrote:

On 2014-05-03 03:44 (GMT+0200) Carlos E. R. composed:

...

James Knott wrote:

...

...

wouldn't the ID be the same, as I have the same partition layout as before?

...

No, the ID is the disk ID, not part of the partition layout. Just run "fdisk -l /dev/..." on each disk (old and new) and you will clearly see an entry labelled "disk identifier". If it is different, Windows will refuse to run. There is a menu entry in fdisk to change it, in the "extra functionality" menu.

I'm puzzled by Carlos' response. AFAIK, entries in /dev/disk/by-id/

I never talked about entries in "/dev/disk/by-id/". Go look in fdisk, in the place I said. It is also visible in Glenn's answer. Cloning full disk with dd clones this particular identifier.

As is normal for him, James has provided limited information about what he did, e.g. his meaning of his words "move" and "installing".

True :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

Felix Miata wrote:
> As is normal for him, James has provided limited information about
> what he did, e.g. his meaning of his words "move" and "installing".
> It's entirely unclear whether he cloned with a true cloner, or used a
> partitioner to create partitions which he created filesystems on then
> copied to, or some mix of functions, or whether anything was done to
> ensure the new HD had anything in it other than what's in its last 66
> bytes. I've seen no clear indication of whether his failure to boot
> Windows on the new HD happens while the old remains attached or not,
> and whether external case is USB2, USB3 or eSATA. What disk identifier
> did he change, and where did he make the change?
After installing the new drive:
1. Restored to "factory" with the restore DVDs
2. Removed Windows partition and used dd to bring over original
3. Booted Windows and used the Windows partition tool to resize to
desired size and then ran chkdsk
4. Created extended partion
5. Created new swap
6. Used GParted to copy & resize
7.  Enabled grub to enable booting into Linux.  Until I did this, I was
able to boot directly into Windows.

Incidentally, I seem to recall device by ID originally used in
configuring grub, but that no longer appears.  It just shows /dev/sda2. 
As I mentioned, I updated fstab and device.map to the new drive ID.

-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 06:59 (GMT-0400) James Knott composed:

As I mentioned, if the old drive is plugged in, via USB, the system tries to boot Windows from it. So, something is telling it to look there, rather than on the new drive. But what?

On 2014-05-03 07:40 (GMT-0400) James Knott composed: "used dd to bring over original" That is a true clone, which includes the partition identifier Windows uses (which may be a UUID). With 2 disks in the system, one of which matches the device ID, Windows is apparently choosing the partition with the matching device ID. It wouldn't be unreasonable to think another component may be sector count and/or start/end sectors may also be in the registry as some sort of backup data confirming the original as an ostensibly correct choice between the twins available. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 15:57 (GMT-0400) James Knott composed:

it only tries to boot the 2nd drive when it's connected. When there's no 2nd drive, it fails to even attempt to load Windows.

That indicates at least one of the following two things is likely wrong with the new HD: 1-MBR's first 446 bytes are either missing or invalid, or 2-MBR code points to a location that is invalid Please describe the content of and/or pastebin a dd of that first sector. It might be useful to disable boot from USB in BIOS at least temporarily. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata wrote:

...

it only tries to boot the 2nd drive when it's connected. When there's no 2nd drive, it fails to even attempt to load Windows.

Is it possible to specify the boot partition from the grub options line? That may get me around the problem, while trying to find the cause. I really have to get into Windows for some important stuff. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata wrote:

1-MBR's first 446 bytes are either missing or invalid, or

2-MBR code points to a location that is invalid

What about the MBR on the Windows partition? IIRC, there's supposed to be one. The bootmgr file is there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

Actually, yes. Windows will detect the disk change and refuse to start, but you should see a message about that, very clearly. In that case, you simply have to clone the disk identifier with fdisk.

Not really. and ... not really. It will boot if you do it right, but it may still come up and want to be re-authorized/licensed because it will notice the hard disk ID has changed which isn't affected by a clone operation (i.e. reads serial number off the driver -- it isn't the drive GUID). The main issue I found in booting Windows is making sure you have moved BOTH partitions. Since day 1 Win7 has required 2 partitions to boot -- one is usually *unmapped/unmounted* and called something like 'System Reserved' (mine reads 100MB long w/31MB used. THEN you have your main 'C' drive partition. I gave up trying to install linux's loader in front of Win's System Reserved, so don't know if just trying to boot from it will work or not. Are you trying to boot from the C drive, or the SystemReserved drive (the real boot drive that mounts 'C' as the root. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 18:13 (GMT-0400) James Knott composed:

Felix Miata wrote:

...

1-MBR's first 446 bytes are either missing or invalid, or

...

2-MBR code points to a location that is invalid

From what you had previously written in thread, it was not clear to me that you were reaching a Grub menu in the first place whenever the old HD in USB was not attached, else I would not have written the above.

What about the MBR on the Windows partition? IIRC, there's supposed to be one. The bootmgr file is there.

Partitions do not have an MBR. Maximum quantity of MBR per BIOS HD is one, the first 512 bytes of the very first disk sector. Partitions have a PBR, and logical partitions also have an EBR. M=Master E=Extended P=Partition -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/03/2014 06:16 PM, Linda Walsh wrote:

Carlos E. R. wrote:

...

Actually, yes. Windows will detect the disk change and refuse to start, but you should see a message about that, very clearly. In that case, you simply have to clone the disk identifier with fdisk.

---

Not really. and ... not really.

It will boot if you do it right, but it may still come up and want to be re-authorized/licensed because it will notice the hard disk ID has changed which isn't affected by a clone operation (i.e. reads serial number off the driver -- it isn't the drive GUID).

The main issue I found in booting Windows is making sure you have moved BOTH partitions.

Since day 1 Win7 has required 2 partitions to boot -- one is usually *unmapped/unmounted* and called something like 'System Reserved' (mine reads 100MB long w/31MB used.

THEN you have your main 'C' drive partition. I gave up trying to install linux's loader in front of Win's System Reserved, so don't know if just trying to boot from it will work or not.

Are you trying to boot from the C drive, or the SystemReserved drive (the real boot drive that mounts 'C' as the root.

I have 3 computers with Windows on--two Win 7 Pro, and one Win 8.1 Pro, and nono of them have more than one partition. I think MS gets manufacturers to fill up the drives with primary partitions so that you can't install Linux! But I installed two Windows systems myself, and I believe I deleted an extra partition on my Dell laptop, leaving just one for Windows. (Dell is weird: it insisted on making an extra partition for Linux, and Linux (PCLOS) will not work without it! The extra partition seems to contain some or all of the "real" / directory.) So I don't know how I'd run two Linux distros on the laptop, since the one Linux fills up the drive! (And it's not a weird file system.) --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 15:16 (GMT-0700) Linda Walsh composed:

Since day 1 Win7 has required 2 partitions to boot -- one is usually *unmapped/unmounted* and called something like 'System Reserved' (mine reads 100MB long w/31MB used.

THEN you have your main 'C' drive partition. I gave up trying to install linux's loader in front of Win's System Reserved, so don't know if just trying to boot from it will work or not.

Based upon my very limited partition experience with Windows post-XP, I don't believe the above to be entirely accurate in the sense that standing alone it could mislead as to what W7 requires. I've only ever installed such an animal on one system, a (free) Win8beta. http://fm.no-ip.com/Tmp/Dfsee/vizioL05.txt shows the partitioning used. Both XP and 8 booted from sda1, which both called C:. XP's "system" was installed to sda6, which it called D:. W8's (bloated) "system" was installed to sda7. Whether it called sda7 D:, E: or something else I don't remember, and since it's now history I can't check, but it was not C:. DOS (still) is on sda2. Grub Legacy (still) is on sda3. Traditional WinDOS-friendly code is in the MBR, which directs boot via Grub on the "active" sda3 primary, from which Windows could be reached via a chainloader stanza pointing to sda1. In summary, both Windows versions started/initialized/booted from the same primary (C:) partition, while each ran from individual logical partitions, and stored or used nothing on any other primary partition. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-02 20:02 (GMT-0400) James Knott composed:

I recently replaced the hard drive on my Thinkpad E520 with a larger one. I have moved all the partitions over and can now boot into Linux, but I can not boot into Windows 7. After installing the Windows partition, but before installing the Linux partition, I could boot into Windows. I have checked and rechecked the grub menu and also verified that /boot/grup/menu.lst & device.map are correct, but I still cannot boot into Windows. It stops at:

map (hd0) (hd0) map (hd0) (hd0) rootnoverify (hd0,1) chainloader +1

Here is the relevant part of menu.lst:

title Windows 7 map (hd0) (hd0) map (hd0) (hd0) rootnoverify (hd0,1) chainloader +1

The odd thing is, if I plug in the old drive, which is mounted in an external case, it will boot Windows from it. Is the drive ID stored somewhere I'm missing? Fstab has also been updated to the correct drive.

On revisiting this OP, something bothers me. I cannot find fdisk output from either old or new HD anywhere in the thread. Please provide so that I can try to make the bother go away, and maybe provide the solution. One other question, to clarify, your use of the word Grub in this thread has only one meaning, Grub Legacy, right? IOW, you did not install 13.1 fresh on the new HD and leave the default Grub2 selected as bootloader, right? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata wrote:

On revisiting this OP, something bothers me. I cannot find fdisk output from either old or new HD anywhere in the thread. Please provide so that I can try to make the bother go away, and maybe provide the solution.

New drive Disk /dev/sda: 750.2 GB, 750156374016 bytes, 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: dos Disk identifier: 0x694d7503 Device Boot Start End Blocks Id System /dev/sda1 2048 2457599 1227776 7 HPFS/NTFS/exFAT /dev/sda2 * 2457600 702959615 350251008 7 HPFS/NTFS/exFAT /dev/sda3 1440571392 1465145343 12286976 7 HPFS/NTFS/exFAT /dev/sda4 702959616 1440571391 368805888 f W95 Ext'd (LBA) /dev/sda5 702961664 713201663 5120000 82 Linux swap / Solaris /dev/sda6 713203712 796106751 41451520 83 Linux /dev/sda7 796108800 1440571391 322231296 0 Empty Partition table entries are not in disk order Command (m for help): Old drive Disk /dev/sdb: 320.1 GB, 320072933376 bytes, 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x694d7503 Device Boot Start End Blocks Id System /dev/sdb1 2048 2459647 1228800 7 HPFS/NTFS/exFAT /dev/sdb2 2459648 293361663 145451008 7 HPFS/NTFS/exFAT /dev/sdb3 600563712 625139711 12288000 7 HPFS/NTFS/exFAT /dev/sdb4 * 293363712 600563711 153600000 f W95 Ext'd (LBA) /dev/sdb5 293365760 297574399 2104320 82 Linux swap / Solaris /dev/sdb6 297576448 339519487 20971520 83 Linux /dev/sdb7 339521536 600563711 130521088 83 Linux Partition table entries are not in disk order

One other question, to clarify, your use of the word Grub in this thread has only one meaning, Grub Legacy, right? IOW, you did not install 13.1 fresh on the new HD and leave the default Grub2 selected as bootloader, right?

No, it was an upgrade from a previous system with the original "legacy" grub. I have grub 2 on another computer and prefer legacy. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 20:34 (GMT-0400) James Knott composed:

New drive Disk /dev/sda: 750.2 GB, 750156374016 bytes, 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: dos Disk identifier: 0x694d7503

Device Boot Start End Blocks Id System /dev/sda1 2048 2457599 1227776 7 HPFS/NTFS/exFAT /dev/sda2 * 2457600 702959615 350251008 7 HPFS/NTFS/exFAT /dev/sda3 1440571392 1465145343 12286976 7 HPFS/NTFS/exFAT /dev/sda4 702959616 1440571391 368805888 f W95 Ext'd (LBA) /dev/sda5 702961664 713201663 5120000 82 Linux swap / Solaris /dev/sda6 713203712 796106751 41451520 83 Linux /dev/sda7 796108800 1440571391 322231296 0 Empty

Partition table entries are not in disk order

Old drive

Disk /dev/sdb: 320.1 GB, 320072933376 bytes, 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x694d7503

Device Boot Start End Blocks Id System /dev/sdb1 2048 2459647 1228800 7 HPFS/NTFS/exFAT /dev/sdb2 2459648 293361663 145451008 7 HPFS/NTFS/exFAT /dev/sdb3 600563712 625139711 12288000 7 HPFS/NTFS/exFAT /dev/sdb4 * 293363712 600563711 153600000 f W95 Ext'd (LBA) /dev/sdb5 293365760 297574399 2104320 82 Linux swap / Solaris /dev/sdb6 297576448 339519487 20971520 83 Linux /dev/sdb7 339521536 600563711 130521088 83 Linux

Partition table entries are not in disk order

Redone in logical order one can see the new first partition sda1 is smaller than sdb1, and last physical partition sda3 is smaller than sdb3: Sec Hd Sec SPC Bytes MiB 512 64 32 2048 1048576 1 NEW HD Old HD Position Name Type Sectors Start End Blocks MiB Delta 2048 0 2047 1024 0.00097656 0 1 sda1 Win???? 2455552 2048 2457599 1227776 1.17089844 -1024 2 sda2 Win7 700502016 2457600 702959615 350251008 334.025391 204800000 empty 2048 702959616 702961663 1024 0.00097656 -1024 3 sda5 swap 10240000 702961664 713201663 5120000 4.8828125 3015680 empty 2048 713201664 713203711 1024 0.00097656 0 4 sda6 openSUSE 82903040 713203712 796106751 41451520 39.53125 20480000 empty 2048 796106752 796108799 1024 0.00097656 0 5 sda7 /home 644462592 796108800 1440571391 322231296 307.303711 191710208 6 sda3 ntfs???? 24573952 1440571392 1465145343 12286976 11.7177734 -1024 Totals 1465145344 732572672 698.635742 420002816 actual 1465149168 unused 3824 OLD HD Position Name Type Sectors Start End Blocks MiB 2048 0 2047 1024 0.00097656 1 sdb1 Win???? 2457600 2048 2459647 1228800 1.171875 2 sdb2 Win7 290902016 2459648 293361663 145451008 138.712891 empty 4096 293361664 293365759 2048 0.00195313 3 sdb5 swap 4208640 293365760 297574399 2104320 2.00683594 empty 2048 297574400 297576447 1024 0.00097656 4 sdb6 openSUSE 41943040 297576448 339519487 20971520 20 empty 2048 339519488 339521535 1024 0.00097656 5 sdb7 /home 261042176 339521536 600563711 130521088 124.474609 6 sdb3 ntfs???? 24576000 600563712 625139711 12288000 11.71875 Totals 625139712 312569856 298.089844 actual 625142448 unused 2736 Depending on your create methodology, something of importance on the two old partitions may have disappeared in the copy process that only mattered after installing Grub. Did you shrink them on purpose? If so, how? Otherwise, they look to have been truncated and may need chkdsk run on them, and still may have been destroyed. Unrelated to the truncations, with Grub on MBR I would expect the following to not matter, but who knows? Old disk has boot flag on extended, while new has it on NTFS. Maybe Windows 7 doesn't like that and its loader goes into an endless loop? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 22:12 (GMT-0400) James Knott composed:

I didn't shrink anything. I moved to a larger drive and expanded the partitions. I used the Windows partition tool to enlarge the Windows partition and GParted, the Linux ones. The extended and swap partitions were created fresh, rather than move and expand.

Two new HD partitions are smaller: /dev/sda1 2048 2457599 1227776 7 HPFS/NTFS/exFAT /dev/sdb1 2048 2459647 1228800 7 HPFS/NTFS/exFAT new #1 1024 blocks smaller /dev/sda3 1440571392 1465145343 12286976 7 HPFS/NTFS/exFAT /dev/sdb3 600563712 625139711 12288000 7 HPFS/NTFS/exFAT new #3 1024 blocks smaller

Grub works fine for booting into Linux. It's just Window that I can't get to work.

Two Windows partitions on the new HD are smaller than before. Do you know that the difference does not matter? I expect it very well could, and based on your experience, does. BTW, in my previous post where it said MiB it should have been GiB. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Two new HD partitions are smaller: /dev/sda1 2048 2457599 1227776 7 HPFS/NTFS/exFAT /dev/sdb1 2048 2459647 1228800 7 HPFS/NTFS/exFAT new #1 1024 blocks smaller /dev/sda3 1440571392 1465145343 12286976 7 HPFS/NTFS/exFAT /dev/sdb3 600563712 625139711 12288000 7 HPFS/NTFS/exFAT new #3 1024 blocks smaller

...

Grub works fine for booting into Linux. It's just Window that I can't get to work.

Two Windows partitions on the new HD are smaller than before. Do you know that the difference does not matter? I expect it very well could, and based on your experience, does. I don't know why the different sizes. Those are the SYSTEM_DRV and Lenovo_Recovery partitions and were installed by the restore DVDs on the new drive and as from the factory on the old one. The restore DVDs were created by the utility that came with Windows 7, though I also have original Lenovo DVDs here. I didn't copy over either of those

Felix Miata wrote: partitions. Windows 7 is on sda2, which is much larger on the new drive. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-05-03 22:11 (GMT-0700) Linda Walsh composed:

I was NOT able to install Win7 all in 1 partition.

With no description of how you tried to install, that doesn't say anything useful. Did you do as most do and present it with an empty HD, or tell it to discard whatever is there and start as if empty? In such cases it's only natural to expect it to do entirely as it pleases. It's my HD, so I control it by always partitioning in advance, usually filling the MBR table with entries, filling the MBR code block with code it's finds no need to diddle with, and leaving no freespace, so that the only option for the Windows installer is putting boot files on the only partition native to it, and using an existing (empty) type 0x07 partition among a bunch of non-natives for its bulk. XP, prior, and 8beta all had no problem accepting and proceeding to use the partitions I offered, once their installers initialized at all. On occasions I never fully understood, the XP installer would sometimes object to something or other and proceed without putting anything on the screen, necessitating CAD to try again. I can't recall ever installing XP anywhere but to a D: logical on HD0, or not first creating a small primary intended for its boot files, before booting its installer. As yet I've never needed to deal with any vendor's recovery media and the problems they foster for multibooters. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Fri, 02 May 2014 20:31:36 -0400 James Knott пишет:

Carlos E. R. wrote:

...

On 2014-05-03 02:02, James Knott wrote:

...

The odd thing is, if I plug in the old drive, which is mounted in an external case, it will boot Windows from it. Is the drive ID stored somewhere I'm missing? Fstab has also been updated to the correct drive. Actually, yes. Windows will detect the disk change and refuse to start, but you should see a message about that, very clearly. In that case, you simply have to clone the disk identifier with fdisk.

Then why did it boot before I moved Linux over and set up grub?

According to your other post, you could boot before you "resized and moved" and that is *VERY* different from simply installing Linux. At least you never said that you could still boot *after* "resize and move" but *before* installing Linux. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov wrote:

At least you never said that you could still boot *after* "resize and move" but *before* installing Linux.

From an earlier message

After installing the new drive: 1. Restored to "factory" with the restore DVDs 2. Removed Windows partition and used dd to bring over original 3. Booted Windows and used the Windows partition tool to resize to desired size and then ran chkdsk 4. Created extended partion 5. Created new swap 6. Used GParted to copy & resize 7. Enabled grub to enable booting into Linux. Until I did this, I was able to boot directly into Windows. Booting into Windows failed after I enabled grub. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov wrote:

On Sun, May 4, 2014 at 3:30 PM, James Knott wrote:

...

Andrey Borzenkov wrote:

...

Please upload somewhere partition boot block (the very first block of partition that is expected to be Windows boot partition). I have attached the first block of the Windows partition. The file sda2 is from the new drive and sdb2, the old. I do not see any attachments, sorry.

My mistake. I've attached them now.

Andrey Borzenkov wrote:

At this point the only clean way to fix it is to boot from Windows media and perform boot recovery.

The recovery disks provide 2 options, recover the entire disk or just the C: partition. I suppose I may be able to do just C:. save the first block and then restore the backup and copy the first block in. Other than that, I only have an XP install disc that I could boot from. Is that capable of restoring that first block? Also, with that issue, why was it bootable before I enabled grub? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

arvidjaar@gmail.com wrote:

...

Also, with that issue, why

...

was it bootable before I enabled grub? It was not. I already explained it.

It was bootable. I was able to boot into Window, resize the partition with the Windows partition utility and run chkdsk to verify the disk. It was only after I enabled grub that I could no longer boot into Windows. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/04/2014 01:11 AM, Linda Walsh wrote: /snip/

I was NOT able to install Win7 all in 1 partition.

/snip Here is my disk. Notice that there is only ONE partition for Windows 7, and it runs perfectly. There are several Linux distros installed. [doug@localhost ~]$ sudo fdisk -l Password: Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xe271ee17 Device Boot Start End Blocks Id System /dev/sda1 * 63 928699063 464349500+ 7 HPFS/NTFS/exFAT /dev/sda2 928704510 1591304191 331299841 5 Extended /dev/sda5 928704512 1031217151 51256320 83 Linux /dev/sda6 1031219200 1134862335 51821568 83 Linux /dev/sda7 1134863793 1167636329 16386268+ 82 Linux swap / Solaris /dev/sda8 1167638528 1229703167 31032320 83 Linux /dev/sda9 1229705216 1320906751 45600768 83 Linux /dev/sda10 1320908800 1404413951 41752576 83 Linux /dev/sda11 1404416000 1487880191 41732096 83 Linux /dev/sda12 1487882240 1539082239 25600000 83 Linux /dev/sda13 1539084288 1591304191 26109952 83 Linux --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov wrote:

Why you insist that it was the last step of these 4 and not the first?

Because right up until I enabled grub, I could boot into Windows. I know when it failed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, May 4, 2014 at 9:05 PM, James Knott wrote:

...

arvidjaar@gmail.com wrote:

...

...

Also, with that issue, why

...

was it bootable before I enabled grub? It was not. I already explained it. It was bootable. I was able to boot into Window, resize the partition with the Windows partition utility and run chkdsk to verify the disk. It was only after I enabled grub that I could no longer boot into Windows. Please read once more what I wrote. You verified that you could boot Windows, then made 4 (four) steps, then found that you cannot boot Windows anymore. Why you insist that it was the last step of these 4 and not the first?

With data that you provided so far the most obvious conclusion is that failure was caused by "resizing and moving" partitions with GParted. Don't know about the situation you refer to, but you CAN resize a Windows partition using GParted, so long as work from the END of it and leave the beginning where it was when it worked. And of course, you can't make the new partition smaller than the actual in-use

On 05/04/2014 04:30 PM, Andrey Borzenkov wrote: portion of the original, but you can certainly make it smaller if it was taking up the whole disk, originally. Yes, I have done that, a number of times. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata wrote:

On 2014-05-03 22:12 (GMT-0400) James Knott composed:

...

I didn't shrink anything. I moved to a larger drive and expanded the partitions. I used the Windows partition tool to enlarge the Windows partition and GParted, the Linux ones. The extended and swap partitions were created fresh, rather than move and expand.

Two new HD partitions are smaller: /dev/sda1 2048 2457599 1227776 7 HPFS/NTFS/exFAT /dev/sdb1 2048 2459647 1228800 7 HPFS/NTFS/exFAT new #1 1024 blocks smaller /dev/sda3 1440571392 1465145343 12286976 7 HPFS/NTFS/exFAT /dev/sdb3 600563712 625139711 12288000 7 HPFS/NTFS/exFAT new #3 1024 blocks smaller

---- Have you looked at the contents of that small drive??? (I.e. mounted it ?) to check to see what's on it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Doug wrote:

Don't know about the situation you refer to, but you CAN resize a Windows partition using GParted, so long as work from the END of it and leave the beginning where it was when it worked

Yes, I know that, but I've long been in the habit, going back to the OS/2 days, of using the tools for the environment. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/04/2014 10:56 PM, James Knott pecked at the keyboard and wrote:

James Knott wrote:

Earlier today, I tried re-installing the Windows partition from the recovery disks. That worked and could be booted. I used that working Windows to create a system repair CD and saved the boot sector from that partition.

I then put the original Windows back and tried running the repair CD, but nothing in it, including commands to repair boot sector helped.

I then copied over the saved boot sector. It would now boot, but failed to properly load. The problems also prevented Linux from running, as it couldn't find things needed on the Windows partition.

I tried rebuilding everything from scratch, starting with a complete restore from the recovery discs, as follows

Restored entire system from DVDs - boots OK Shrunk Windows partition - boots OK Created extended & swap partitions, copied & resized partitions 6 & 7 - boots OK Copied Windows 7 partition - boots, but start up repair runs. Didn't happen before but Windows runs fine after. Resized Windows 7 partition using Windows utility - boots OK Enabled grub, edited fstab, device.map & menu.lst - can boot into Linux, but not Windows Replaced sda2 boot sector with one saved earlier. Windows boots, but fails. Linux also fails. Replaced sda2 boot sector with the one saved prior to enabling grub. Can now boot into Linux, but Windows won't boot.

Bottom line, there's something about that boot sector that grub doesn't like. The one from the fresh Windows install works with grub, but can't load the original system.

I guess my next step is to reload the Windows partition from the restore discs and then restore as much as I can from the old Windows partition, unless someone has a better idea.

Run Windows in a VM and get rid of the headaches or run linux in a VM in your windows install. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/05/2014 01:08 PM, John Andersen pecked at the keyboard and wrote:

On 5/5/2014 6:47 AM, Ken Schneider - openSUSE wrote:

...

Run Windows in a VM and get rid of the headaches or run linux in a VM in your windows install.

A LOT to be said for this approach, I haven't found dual booting to be a satisfactory solution for over 10 years.

Still there is a problem if you want a linux machine on which you occasionally need windows. Your existing Certificate of Authenticity will probably NOT work when you install windows in a Virtual machine.

I have never had this issue with running M$W in a VM. I always used the COA that was on the machine. As far as I am concerned if windows is running in a VM on the metal it came on it is legal.

Especially true of OEM installed Windows. So you are probably stuck with Linux guest in a Windows Virtual machine. Which works well with Vmware, but not so well with Microsoft's Virtual Machine package.

My day job gives me access to MSDN subscription from which I can get legitimate (paid for) licenses of windows to install in VMs running on top of Linux, which is the best solution if you still have to run windows.

-- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 5/5/2014 3:14 PM, Doug wrote:

On 05/05/2014 04:48 PM, Ken Schneider - openSUSE wrote:

...

On 05/05/2014 01:08 PM, John Andersen pecked at the keyboard and wrote:

...

On 5/5/2014 6:47 AM, Ken Schneider - openSUSE wrote:

...

Run Windows in a VM and get rid of the headaches or run linux in a VM in your windows install.

A LOT to be said for this approach, I haven't found dual booting to be a satisfactory solution for over 10 years.

Still there is a problem if you want a linux machine on which you occasionally need windows. Your existing Certificate of Authenticity will probably NOT work when you install windows in a Virtual machine.

I have never had this issue with running M$W in a VM. I always used the COA that was on the machine. As far as I am concerned if windows is running in a VM on the metal it came on it is legal. /snip/

I'm almost certain that you can legally run ONE copy of Windows (that you obtained legally) on any machine, whether it came on that machine or not. You just can't copy it and run it on an additional machine. You are not licensing a machine, you are licensing a copy of Windows. IF you don't have a real install disk, I'm not sure how you would do this, but so long as the software only runs on one machine, it's legal. (If it is not possible to install the software on a machine because you are trying to run it in a VM, that would be too bad, but I wouldn't count on MS to help you do it!)

I'm no lawyer, but that's the way I've always understood the license.

--doug

Guys, this isn't a legal issue I'm addressing here. When you buy a laptop with windows pre-installed, you don't even get installation media these days. (You get a recovery partition at best). So when you want to move that windows OS into a virtual machine, you have to special order a disk from the hardware vendor to install in your VM. Then you try to install that disk using your original COA, only to find out that the disk is further trapped out so as not to work if the hardware doesn't look pretty close to the original. In a VM, it won't look the same. So you run out and borrow someone's installation disk who bought a commercial boxed set, only to find out that your COA won't work on that version either. I've been through this several times with lap tops. I've take to just using a MSDN key and installing an MSDN version of Windows in the virtual machine after I install linux. Also... when buying laptops, I just put the original hard drive on the shelf. (I always buy the smallest they offer). Then I pop in the size I really wanted from commercial sources, and install Linux on that. Because if any warranty issue crops up and they find you had Linux installed you've just about got to threaten legal action to get them to honor the warranty. Easier jut to pop in the original disk and send the machine in for repair. When the warranty expires, you have a spare hard drive to do with what you want. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 5/7/2014 1:24 PM, Linda Walsh wrote:

I have re-installed with a retail onto my dell box, but to get it to 'license' correctly, I need to copy over the BIOS authentication mechanisms from a dell-install disk. Once those are on the disk Windows will use those to check for activation & authenticity.

That process (copy over the bios authentication mechanisms) would bear fleshing out a little bit for the Google Spiders if nothing else. All often, you don't get a disk at all anymore. Where are these mechanisms actually found, what do they look like, where do you have to have them in order to get the COA to be accepted? -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On May 8, 2014 7:56:23 AM EDT, Linda Walsh wrote:

John Andersen wrote:

...

On 5/7/2014 1:24 PM, Linda Walsh wrote:

...

I have re-installed with a retail onto my dell box, but to get it to 'license' correctly, I need to copy over the BIOS

authentication

...

mechanisms from a dell-install disk. Once those are on the disk Windows will use those to check for activation & authenticity.

That process (copy over the bios authentication mechanisms) would bear fleshing out a little bit for the Google Spiders if nothing else.

All often, you don't get a disk at all anymore. Where are these mechanisms actually found, what do they look like, where do you have to have them in order to get the COA to be accepted?

---- The COA *isn't* accepted -- unless you resort to the phone. When the phone people hear the COA, they'll check to see if it's a stolen/too many uses license that's been suspended, but if not, they'd give you a validation code.

If you have a Professional or Ultimate (maybe just ultimate, I forget), then they should support you running Win7 in a VM. If it's a home version, then it's not supported/not licensed.

I went and looked. For ultimate you can run the OS on a physical machine or a single VM, but not both. I did not check pro. There are enterprise win 7 licenses that are more flexible, but I don't have access to anything like that. Also it seems you can migrate a single XP machine to a VM and run it under win 7 and be legal. I need to research that more unless someone knows. Ie. I have an old XP machine with a demo on it and I need to keep the demo demo-able. Once migrated the physical computer will be retired. Is there a way to migrate a physical XP machine to a VM that runs under opensuse? Is xp still activated/licensed? Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/08/2014 09:17 AM, Greg Freemyer wrote: /snip/

I went and looked. For ultimate you can run the OS on a physical machine or a single VM, but not both. I did not check pro. There are enterprise win 7 licenses that are more flexible, but I don't have access to anything like that.

Also it seems you can migrate a single XP machine to a VM and run it under win 7 and be legal. I need to research that more unless someone knows. Ie. I have an old XP machine with a demo on it and I need to keep the demo demo-able. Once migrated the physical computer will be retired.

Is there a way to migrate a physical XP machine to a VM that runs under opensuse? Is xp still activated/licensed?

Greg

You don't have to "migrate" XP to a Windows 7 Pro--it has a built-in emulator. Looks and acts exactly like XP. Even 32-bit progs run on it. And you don't need any MS special license or code, if you are running a legal Win 7 Pro. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, May 8, 2014 at 11:15 AM, Linda Walsh wrote:

Greg Freemyer wrote:

...

Is there a way to migrate a physical XP machine to a VM that runs under opensuse? Is xp still activated/licensed?

---- You get a free XP virtual machine when you buy ultimate.

I think it came w/SP1 and was a download before that.

I think it's still a download, but it is installed and in the process of configuring now. fyi: It is always 32-bit which is exactly what I wanted, so I'm looking good. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Greg Freemyer wrote:

...

...

I think it came w/SP1 and was a download before that. I think it's still a download, but it is installed and in the process of configuring now.

fyi: It is always 32-bit which is exactly what I wanted, so I'm looking good.

Windows XP Mode is a horrible VM. It may work for me, but it is extremely slow and it hasn't been able to run more than a few hours at a time without crashing.

And all I'm doing so far is trying to get the security patches installed.

That is unfortunate. The few times I tried it I had no problems, but I didn't try to install all of the cumulative security patches that were issued for XP after SP3 came out. Given how some of those same patches entirely hosed Win7, I suppose I shouldn't be surprised that XP wouldn't come through unscathed. The worst "restore"[sic], I had to do was after a Win7 update last August that left my machine unbootable. No sys restore, and no backups working at the time and couldn't run update because that only runs from a working system. System restore failed twice in a row, but after 2nd restore, system booted but with no aero desktop. Then system upgrade failed near the end, and rolled back the upgrade. So I upgraded it again and prevented the upgrade ... bunch more steps tto get back to working... so .. MS updates... a mixed blessing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org