Hi,
I have installed Suse on my Windows Vista 64bit machine a couple of times, but the last time I did it - after a disk change - presented some unanticipated problems.
Prior to install, Windows Disk Management (whose output I was unable to paste into this question) showed that my disks were laid out as follows:
Disk Id Space Free Space Type Pri/Log Name
0
* 55M 55M Unalloc
* 15G ?G RAW Pri Recovery
C 300G 232G NTFS Pri OS
L 107G 97G NTFS Log Photos
M 48G 39G NTFS Log Music
* 468G 468G Unalloc
1
F 1397G 1000G NTFS Pri
Disk 0 is a Seagate ATA drive, while Disk 1 is a Western Digital Ext HDD Usb Device.
Looking back, I think I should have carved out a partition after M before installing Suse, but I was uncertain whether to make it a logical one or a primary, and in the
past the installation has taken the 25 or so gig it needed from the last defined
partition on disk 0. This time, however, it went after disk 1, and reformatted the
entire drive, deleting about 300 gig of user data, including my system backup. What
really suprised me is that it took up the entire drive: 2 gig for the swapfile, then a
20 gig partition, and all the rest for the third partition.
This is not what I would have expected. I especially would not have expected the
installation to re-format user data.
In any case, I did not want Suse on disk 1, so I reformatted the drive and then
used my Partition Manager to rebuild the boot Mbr. So now, I am able to boot into
windows, do not have Suse on my machine, but have lost critical data. My disks are
now back to the way they were when I started (see above), except that drive F is
now all free space, except for my latest backup.
My question is how do I ensure, when I reinstall Suse, that it will choose disk0 for the installation and will not overlay any of the data that I have on that drive.
Thanks in advance,
s660117