Windows 2008 R2 can no longer install from DVD?

[r4pt0x]

I just ran into this problem on a server at our branch:
http://forum.proxmox.com/threads/55...r-quot-when-installing-Windows-Server-2008-R2

Weird thing though: I'm using the same original DVD from which I installed another VM just a few months ago on the very same system...

Trying to generate an iso-file with dd results in a 1.1GiB file instead of ~3GiB. This is reproducable with another DVD i have here, so i think the DVDs are made as multi-session and dd stops after the first track.

Internet connection at this server is utterly slow - download from MS has an ETA of >7h...
I won't be at the server site until next week, so downloading the iso here to an USB stick is no option.

# pveversion -v
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-72
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1

 

[tom]

installing from physical DVD and also from ISO should work. if it does not work, probably your DVD/ISO is corrupted.

 

[r4pt0x]

I know it should work - I installed Windows 2008 R2 with this very disc in october last year on this system

As I also have to install a Windows 7 VM I got somebody at the branch to change the disc at the server. Well, Win7 also refuses to install with the very same error...

Win7 has been installed into a VM 2 weeks ago on our main proxmox server from image without any problems. I just tried installing win7 from DVD on this server: same problem as on the second proxmox server...

As it's the same problem on 2 servers with identical proxmox software versions and different hardware, I doubt it's the DVD-ROM drive or disk but the passthorugh?


Update:
Both systems stop after the very same amount of bytes (1073741312 Bytes) when copying with dd from the optical drive. Googeling for this led me to the right direction:

https://bugzilla.kernel.org/show_bug.cgi?id=10116

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619757
(i don't have udftools installed!?)

 

[tom]

what do you copy with dd? Seems I do not get your issue ...

either use an ISO image (downloaded from MS) or use the physical DVD.

 

[r4pt0x]

1. Physical DVD doesn't work - setup asks for cdrom-drivers (link in first post)

2. download of the image takes >7h because of the very slow internet connection (we are still waiting for the fiberglass cable to be installed by the local ISP)

3.dd was tried to create an iso image because installing from iso seems to be the "standard workaround" for 1.

maybe the problem (#1) also traces back to the kernel bug linked in my previous post.
If i try to access the mounted disk I get tons of I/O errors for some files (maybe because they are beyond the 1073741312 byte "limit"...).

The problem can be reproduced 1:1 on the local proxmox server.

 

[tom]

1. Physical DVD doesn't work - setup asks for cdrom-drivers (link in first post)

points to a faulty CD or hardware problems.

I suggest you download a valid iso from MS.

 

[r4pt0x]

No, the DVDs are all fine - as said, I can reproduce it here on another proxmox system:
Both DVDs I tried here (Windows 7 + Windows 2008) can't install on the proxmox host
Both DVDs can't be accessed beyond 1073741312 bytes on the proxmox host (which causes dd to abort after 1073741312 bytes and most likely causes both Windows Versions to refuse to install from the disk)
Both DVDs can be fully read on my desktop system + notebook and dd also generates complete isos of ~3GiB on both systems (debian wheezy)
Both DVDs install perfectly fine from DVD within an VirtualBox VM on my desktop system (as they can be fully accessed)

I bet both DVDs at the branch are also perfectly fine as both DVDs can only be read up to 1073741312 bytes, then I get I/O errors... (plus I've already installed from both disks!)



Maybe this bug:

http://git.kernel.org/?p=linux/kern...it;h=7b3d9545f9ac8b31528dd2d6d8ec8d19922917b8

Is still present?
There is still an open bug for udftools with Kernel version 2.6.32:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619757

Is there any driver/package in proxmox (pass-trough? virtio?) opening the cdrom device in non-blocking mode, triggering this bug?

 

[WaltervdSchee]

Which looks to me like a faulty DVD-drive in the ProxMox server....
Cant' you create an ISO with your workstation and copy it to the server ?
Or place it on a thumb-drive and place it on the server that way ?

 

[r4pt0x]

I'm on an unscheduled visit at our branch today....

The drives in both servers are fine (and only a few months old) - faulty drives produce random I/O errors (already had some of them..). As on BOTH servers with ANY DVD I get I/O errors + "attempt to access beyond end of device" EXACTLY after the same ammount of bytes, the drives are definately not the problem.

To validate this, I just booted the server here at the branch into the grml rescue system and copied both DVDs with dd to an iso-image file without a single error. Back in the proxmox system: on both DVDs i can only read the first 1073741312 bytes.


Anyways - I found out how to bypass the bug (it's also mentioned here):
After running into the error, unmount (if mounted) and open/close the drive and the disc can (at least most times) be read normally:

root@R-proxmox:~# dd if=/dev/dvd of=/var/lib/vz/template/iso/w7pro_64.iso
2097151+0 Datensätze ein
2097151+0 Datensätze aus
1073741312 Bytes (1,1 GB) kopiert, 195,768 s, 5,5 MB/s
root@R-proxmox:~# eject
root@R-proxmox:~# eject -t
root@R-proxmox:~# dd if=/dev/dvd of=/var/lib/vz/template/iso/w7pro_64.iso
6383744+0 Datensätze ein
6383744+0 Datensätze aus
3268476928 Bytes (3,3 GB) kopiert, 460,87 s, 7,1 MB/s