I’ve created separate iSCSI targets with associated mapped LUN’s for each node.
node 1 iSCSI initiator: n1bc –> iSCSI target: ttgbootn1
node 2 iSCSI initiator: n2bc –> iSCSI target: ttgbootn2
node 3 iSCSI initiator: n3bc –> iSCSI target: ttgbootn3
In the QNAP webinterface I see that the user n1bc is connected properly to the ttgbootn1 LUN.
Booting the Windows Hyper-V Server 2008R2 installer takes longer than normal, stuck at the splash screen for at least 6 mins. In which time the user n1bc disconnects from the QNAP and after a few minutes reconnects.
Wait for it…
Wait for it…
Wait for it…
Wait for it…
… and there it is. Select you favorite language and stuff, and continue.
The same waiting game happens on the Setup is starting screen. It must have something to do with installing to an iSCSI Remote Boot disk as this does not happen while installing to an internal disk.
Wait for it…
Wait for it…
Wait for it…
Wait for it…
… and here’s the next step. Acknowledge and agree to the license stuff, select the Custom install.
There’s the iSCSI Remote Boot LUN disk 🙂
At this point let the installer run its course
The installer portion will finish. Windows restarts the node and boots from the iSCSI LUN for the first time !!
Installation continues but gets stuck on the completing 
installation .. Screen just flickered, this takes a long time. Oh wait, the green progress bar is now moving.
One more restart
wh00h00 success!
Enter a new password for the administrator account
The next screen shows the server configuration sconfig which I’ll walkthrough in another post
One node done, two to go.