Trying to Install Win 7 Template on OVH SSD VPS  

  RSS
chocolateTHUNDA
(@chocolatethunda)
Active Member

Template Name: 7.ENT.EVAL.64.VIRTIO-SCSI.gz
Vendor: OVH
Vendor Service Package: VPS 2017 Discovery SSD 2
Physical or Virtual: SSD VPS
Motherboard: -
Processor: -
RAM: 2 G
Network Interface: 
Location: Sydney (SYD) - Australia
Error Information

Hello,

I'm trying to install 7.ENT.EVAL.64.VIRTIO-SCSI.gz on a OVH SSD VPS.
Your instructions say wget -O- http://mirror.whatuptime.com/cer5w2637/7.ENT.EVAL.64.VIRTIO-SCSI.gz | gunzip | dd of=/dev/sdb

However, there is no sdb volume on my VPS when I login via Rescue. Here is the list of volumes I have:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
└─vdb1 254:17 0 40G 0 part /mnt/vdb1

What should I be putting in the command line for dd of=

Thanks.

 

ReplyQuote
Posted : April 27, 2018 5:16 am
SysAdmin
(@sysadmin)
Member Admin

Unfortunately it appears your VPS is using regular VirtIO (as opposed to VirtIO-ISCSI) which is why you are seeing VDA & VDB.

Inside your OVH client area, try performing a OS reinstall to CentOS 7 x64. Once completed there is about a 99% chance your VPS will be using VirtIO-SCSI as opposed to the regular VirtIO.

Good luck!

ReplyQuote
Posted : April 27, 2018 11:42 am
chocolateTHUNDA
(@chocolatethunda)
Active Member

Thanks for the reply.

Maybe I should try installing the VirtIO Win 10 template. I just need a non server version of Windows.

Cheers.

 

 

ReplyQuote
Posted : April 27, 2018 12:11 pm
SysAdmin
(@sysadmin)
Member Admin
Posted by: chocolateTHUNDA

Thanks for the reply.

Maybe I should try installing the VirtIO Win 10 template. I just need a non server version of Windows.

Cheers.

 

 

I would advise reinstalling to CentOS ad advise earlier to see if your can get the VirtIO-SCSI driver working for both nic and disk as there are reports that when you reboot it may swap on you (VirtIO --> VirtIO-ISCSI) which would cause Windows to fail to boot up.

ReplyQuote
Posted : April 27, 2018 12:36 pm
chocolateTHUNDA
(@chocolatethunda)
Active Member

I reinstalled VPS with Centos 7. However, it's still showing vda and vdb in recovery.

[email protected]:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
└─vdb1 254:17 0 40G 0 part /mnt/vdb1

ReplyQuote
Posted : April 27, 2018 11:55 pm
SysAdmin
(@sysadmin)
Member Admin
Posted by: chocolateTHUNDA

I reinstalled VPS with Centos 7. However, it's still showing vda and vdb in recovery.

[email protected]:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
└─vdb1 254:17 0 40G 0 part /mnt/vdb1

hmm...so you can either proceed with the VirtIO template or contact their support 🙁

ReplyQuote
Posted : April 27, 2018 11:57 pm
chocolateTHUNDA
(@chocolatethunda)
Active Member

I will try the VirtIO templates first to check if it works.

Thanks for the help mate.

ReplyQuote
Posted : April 28, 2018 12:01 am
chocolateTHUNDA
(@chocolatethunda)
Active Member

ok... this is strange.

when I log into CentOS via ssh I get sda:

[[email protected] ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 40G 0 disk
└─sda1 8:1 0 40G 0 part /

but when I login to recovery via ssh I get vda:

[email protected]:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
└─vdb1 254:17 0 40G 0 part /mnt/vdb1

Do I have to install the templates via Recovery mode or can I just do it through normal ssh to CentOS?

ReplyQuote
Posted : April 28, 2018 1:23 am
SysAdmin
(@sysadmin)
Member Admin
Posted by: chocolateTHUNDA

ok... this is strange.

when I log into CentOS via ssh I get sda:

[[email protected] ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 40G 0 disk
└─sda1 8:1 0 40G 0 part /

but when I login to recovery via ssh I get vda:

[email protected]:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
└─vdb1 254:17 0 40G 0 part /mnt/vdb1

Do I have to install the templates via Recovery mode or can I just do it through normal ssh to CentOS?

It needs to be installed from the rescue mode.

ReplyQuote
Posted : April 29, 2018 8:59 am
chocolateTHUNDA
(@chocolatethunda)
Active Member

Update:

So I installed 7.ENT.EVAL.64.VIRTIO-SCSI.gz on a CentOS VPS. It booted properly and even ran well for a couple of days. I created a new volume to make use of the unallocated 30G space that's left over after the template install. I did this through Windows Storage Management.

After I did this, at the next reboot, the VPS automatically went into Windows Recovery mode stating that a boot device couldn't be found.

In OVH Rescue mode I see the following now:

[email protected]:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
├─vdb1 254:17 0 100M 0 part /mnt/vdb1
├─vdb2 254:18 0 8.9G 0 part /mnt/vdb2
└─vdb3 254:19 0 31G 0 part /mnt/vdb3

Do you think this has something to do with the way I created a new volume through Windows to use the unallocated Space after the template install?

 

ReplyQuote
Posted : April 30, 2018 10:39 am
chocolateTHUNDA
(@chocolatethunda)
Active Member

Any ideas @sysadmin?

ReplyQuote
Posted : May 13, 2018 11:46 am
SysAdmin
(@sysadmin)
Member Admin
Posted by: chocolateTHUNDA

Update:

So I installed 7.ENT.EVAL.64.VIRTIO-SCSI.gz on a CentOS VPS. It booted properly and even ran well for a couple of days. I created a new volume to make use of the unallocated 30G space that's left over after the template install. I did this through Windows Storage Management.

After I did this, at the next reboot, the VPS automatically went into Windows Recovery mode stating that a boot device couldn't be found.

In OVH Rescue mode I see the following now:

[email protected]:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
├─vdb1 254:17 0 100M 0 part /mnt/vdb1
├─vdb2 254:18 0 8.9G 0 part /mnt/vdb2
└─vdb3 254:19 0 31G 0 part /mnt/vdb3

Do you think this has something to do with the way I created a new volume through Windows to use the unallocated Space after the template install?

 

It's more likely that the disk driver swapped from VirtIO to VirtIO-SCSI unfortunately.

Why did you create a new volume?

ReplyQuote
Posted : May 14, 2018 12:16 am
chocolateTHUNDA
(@chocolatethunda)
Active Member

When restoring the template, it only uses about 8.9 gig of the total partition. This leaves nearly 30 gig of unallocated space. I created a new parturition (via Windows storage manager) to use that space. 

ReplyQuote
Posted : May 15, 2018 1:57 am
call2sun
(@call2sun)
New Member

hi 

 

how do you installed it while it show vdb1?

as i have the same problem could you advise please?

 

regards

ReplyQuote
Posted : May 31, 2018 7:30 am
chocolateTHUNDA
(@chocolatethunda)
Active Member

i replaced 

dd of=/dev/sdb

with 

dd of=/dev/vdb

but i still get the issue where after a couple of days windows doesn't boot anymore and goes in to recovery mode.

 

 

ReplyQuote
Posted : June 7, 2018 6:10 am
call2sun
(@call2sun)
New Member

Sysadmin could you help please as it is known issue with new ovh ssd  vps

 

Regards

ReplyQuote
Posted : June 7, 2018 8:34 am
SysAdmin
(@sysadmin)
Member Admin
Posted by: call2sun

Sysadmin could you help please as it is known issue with new ovh ssd  vps

 

Regards

I would highly recommend reaching out to OVH for assistance with the VirtIO vs VirtIO-SCSI as we do not have any control over that portion of their system.

Sorry 🙁

ReplyQuote
Posted : June 9, 2018 12:18 am
SysAdmin
(@sysadmin)
Member Admin
Posted by: chocolateTHUNDA

When restoring the template, it only uses about 8.9 gig of the total partition. This leaves nearly 30 gig of unallocated space. I created a new parturition (via Windows storage manager) to use that space. 

While you are welcome to create a new partition, I would highly recommend you expand the default partition instead otherwise Windows will almost certainly run out of disk space when running updates, etc.

ReplyQuote
Posted : June 9, 2018 12:19 am
tiencpvn
(@tiencpvn)
New Member
Posted by: chocolateTHUNDA

Update:

So I installed 7.ENT.EVAL.64.VIRTIO-SCSI.gz on a CentOS VPS. It booted properly and even ran well for a couple of days. I created a new volume to make use of the unallocated 30G space that's left over after the template install. I did this through Windows Storage Management.

After I did this, at the next reboot, the VPS automatically went into Windows Recovery mode stating that a boot device couldn't be found.

In OVH Rescue mode I see the following now:

[email protected]:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 3G 0 disk
└─vda1 254:1 0 3G 0 part /
vdb 254:16 0 40G 0 disk
├─vdb1 254:17 0 100M 0 part /mnt/vdb1
├─vdb2 254:18 0 8.9G 0 part /mnt/vdb2
└─vdb3 254:19 0 31G 0 part /mnt/vdb3

Do you think this has something to do with the way I created a new volume through Windows to use the unallocated Space after the template install?

 

hi, did you resolved it, chocolateTHUNDA?
i got same problem, and dont know how to fix it 🙁

ReplyQuote
Posted : July 11, 2018 4:04 am
Share:
  
Working

Please Login or Register