From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing 2.13 under Hyper-V
Date: Thu, 29 Nov 2012 09:18:51 +0000
Message-ID: <97822795629dd97cd251d09ef5e08e77@mail01.ipfire.org>
In-Reply-To: <50B61F17.4030906@jlpaonline.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0532245054608099169=="
List-Id: <development.lists.ipfire.org>

--===============0532245054608099169==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Wed, 28 Nov 2012 08:26:31 -0600, Jeffrey Lanham
<bluezone(a)jlpaonline.com> wrote:
> I tried installing under Windows Hyper-V 2008 R2. Installation
> seemed flawless and it found the synthetic drivers and everything, so
> that was good. Problem is, it installs to a 127gb sized hard drive
> regardless of the size of the virtual hard drive installed on the
> virtual machine, it seems to create this partition and shows the
> actual hard drive as sdb. Then the web interface becomes unresponsive
> and all commands entered on the command line show an I/O error. I
> haven't gone through the logs to try to determine what exactly is
> going on, but, it doesn't seem to like the result of installing on a
> virtual hard drive. Very odd.

Is sda you source device or a complete wrong device? Are you able to
extract the output from the second console and the dmesg.
Also the files in /sys/block/sda , /sys/block/sda/device and the same
for the correct sdb are intresting.


--===============0532245054608099169==--