Code:
[17179594.964000] SCSI device sdb: 114688035 512-byte hdwr sectors (58720 MB)
[17179594.964000] sdb: Write Protect is off
[17179594.964000] sdb: Mode Sense: 27 00 00 00
[17179594.964000] sdb: assuming drive cache: write through
[17179594.964000] SCSI device sdb: 114688035 512-byte hdwr sectors (58720 MB)
[17179594.964000] sdb: Write Protect is off
[17179594.964000] sdb: Mode Sense: 27 00 00 00
[17179594.964000] sdb: assuming drive cache: write through
[17179594.964000] sdb:<5> Vendor: Maxtor Model: 3200 Rev: 0341
[17179594.996000] Type: Direct-Access ANSI SCSI revisio
Here is a SATA volume it looks called sdb, and it is about 60 gigs in size, would this be the vista install?
Code:
[17179595.628000] SCSI device sdc: 398297088 512-byte hdwr sectors (203928 MB)
[17179595.628000] sdc: Write Protect is off
[17179595.628000] sdc: Mode Sense: 17 00 00 00
[17179595.628000] sdc: assuming drive cache: write through
[17179595.628000] sdc: sdc1
Here is another serial ata volume that would be like 200gig in size, would this be it?
Once you know what it is you can edit the /boot/grub/menu.lst file and add the installation as a boot option. This is one reason why I like YaST2 manager in SuSe linux, it gives you a gui for these config files.
so if you vista install is on your sdc1 volume you could add this line in the menu.lst file:
Code:
title Windows Vista
root (sdc,1)
makeactive
chainloader +1
If you made a swap partition it most likely would have the volume label of sda after looking at your output.