From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey Lanham To: development@lists.ipfire.org Subject: Re: Testing 2.13 under Hyper-V Date: Thu, 29 Nov 2012 07:51:30 -0600 Message-ID: <50B76862.1050202@jlpaonline.com> In-Reply-To: <97822795629dd97cd251d09ef5e08e77@mail01.ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4485316098658875661==" List-Id: --===============4485316098658875661== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I don't know if SDA or SDB is the correct device or not. It shows both during boot, but once it completely boots up after install, I can't do anything else because any command line access fails with an I/O error, so I can't cat dmesg or the messages logs after reboot. Jeff On 11/29/2012 3:18 AM, Arne Fitzenreiter wrote: > On Wed, 28 Nov 2012 08:26:31 -0600, Jeffrey Lanham > 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. > --===============4485316098658875661==--