Linux-Noob Forums

OK, So I'm very new to linux and I have to use fedora for one of my university modules.

 

Here's the scenario

 

I am using virtual box to install(or try to install) fedora core 2. when I get to disk partitioning it tells me something like : input/output error cannot write to dev/hda.... which is where I get stuck, any help on this.. I have set aside 8gb of fixed disk space for the virtual machine.

Quote:OK, So I'm very new to linux and I have to use fedora for one of my university modules.

 

Here's the scenario

 

I am using virtual box to install(or try to install) fedora core 2. when I get to disk partitioning it tells me something like : input/output error cannot write to dev/hda.... which is where I get stuck, any help on this.. I have set aside 8gb of fixed disk space for the virtual machine.

 

Instead of install you could first try to boot from the live cd and go to the terminal and and type "fdisk -l" to see if fedora actually sees your virtual hardisk?

Could you show us the settings you are using for your VirtualBox VM for Fedora Core 2? I have got a custom derivative of Fedora Core 3 working great in VirtualBox, but I did have some issues with hard drives. I had to manually select an IDE controller for that VM for that OS to be happy installing.

 

Do you have an IDE controller listed in your VM settings for this VM? I have a suspicion that older versions of Fedora Core might have issues with the SCSI/SATA controllers VirtualBox could be using.

ok under storage settings



SATA controller(virtual hdd)




type : AHCI



port count : 1



Use host I/O cache : is unchecked



IDE controller(cd/dvd) type : PIIX 4





Use host I/O cache : is checked







 

What else can I show you??

I think you might have more luck if you attach the virtual hard disk image to the IDE controller, so you will have both the virtual HDD and the virtual CD/DVD on the IDE controller, and no SATA controller at all. VirtualBox's defaults work great on more recent versions of Linux as guest operating systems, but older releases, like FC2, probably want legacy settings, i.e. using an IDE controller instead of a SATA controller.

 

To do this:

 

1.

 

Right click on the VM in the list of VMs and choose Settings.

 

<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-65688600-1313683490.png" data-fileid="1315">[img]<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-65688600-1313683490.png[/img]</a>

 

2.

 

On the Storage tab, click on the SATA Controller and then click the contoller minus button to remove the SATA Controller (this will not delete your virtual disk file).

 

<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-37921400-1313683572.png" data-fileid="1316">[img]<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-37921400-1313683572.png[/img]</a>

 

3.

 

Click on the IDE Controller that remains and click the Add Attachment button. Choose to add a hard disk to the IDE Controller from the menu that appears.

 

<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-99398100-1313683638.png" data-fileid="1317">[img]<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-99398100-1313683638.png[/img]</a>

 

4.

 

Click Choose existing disk and locate the virtual hard disk image for the VM, which should be just in the folder for the VM. For me, the correct file to choose came up right away.

 

(Or, if you prefer, just make a new disk image at this point, if there is nothing on the old one)

 

<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-75803000-1313683720.png" data-fileid="1318">[img]<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-75803000-1313683720.png[/img]</a>

 

5.

 

Verify that the hard disk is now attached to the IDE Controller.

 

<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-93455400-1313683807.png" data-fileid="1319">[img]<fileStore.core_Attachment>/monthly_08_2011/post-1019-0-93455400-1313683807.png[/img]</a>

 

6.

 

Boot the VM, and try the installer again.

 

----------------------------------------------------------------------------

 

Let us know how you get on and if this helps the installer!