Home / server / Questions / 63085
Accepted
barfoon
Asked: 2009-09-08 08:50:07 +0800 CST

Why is my Fedora HD STILL coming up as 127 GB?

  • 772

After posting this question, and creating a fixed 700GB disk in Hyper-V, when I mount Fedora 11 to a CD and go to install it only shows 127GB of space to write to.

How can I use all 700GB on the VHD?????

Thanks very much,

EDIT: In response to Cristians answer, I have made a SCSI controller, pointed it at the 700GB VHD and booted, now Fedora doesnt see any drive at all:

What am I doing wrong here???



EDIT 2: If I cannot make an IDE drive thats > 127GB, and I cant boot on the 700GB SCSI, how can I use this space??? If I boot on a small IDE with the SCSI attached, Fedora has no idea that all that space is there. Will this appear after loading the operating system? How hard is it to format a large drive and use it in Hyper-V???



alt text

lspci output:

alt text

linux

2 Answers

  1. Best Answer

    Quoting from an article about Hyper-V (thanks Ryaner):

    Virtual hard disk specifications are independent of the bus type used to connect to the virtual machine. However, the bus type does impose a size limitation on virtual hard disks. Virtual hard disks connected via IDE cannot exceed 127 GB. Virtual hard disks connected via SCSI cannot exceed 2040 gigabytes.

    So it seems that you'll need to use a SCSI hard disk, instead of an IDE one. You could also try splitting the current hard disk into multiple smaller IDE hard disks.

    • 5

  2. When you say that Fedora is unable to see the SCSI harddisk, what do you mean by that? At what stage does the Fedora fail to boot?

    1. The boot-loader is unable to boot - You may see an error message saying that there are no bootable disks. You will need to somehow tell the fake Hyper-V BIOS to boot the SCSI drive.
    2. The kernel is unable to boot - You see an error message from the boot-loader (grub/lilo). This means that the boot-loader has loaded successfully. You will need to re-install the boot-loader because IDE and SCSI drive parameters may have changed.
    3. The root is unable to boot - The kernel and initrd loads but the kernel panics complaining about being unable to find root. You will need to edit the kernel parameters for the boot-loader and re-install the boot-loader. You may need to change the root from /dev/hd* to /dev/sd* instead.
    4. The system is unable to boot - You see the system starting up but it complains about problems in the midddle. This might be a problem with udev and some of the configuration.

    Have you tried re-installing Fedora after you made the switch from IDE to SCSI?

    • -1