AndLinux: Difference between revisions

From miki
Jump to navigation Jump to search
Line 8: Line 8:
To mount an existing drive or partition, add to your '''<tt>settings.txt</tt>''':
To mount an existing drive or partition, add to your '''<tt>settings.txt</tt>''':
hda=\Device\HarddiskVolume0 # To mount the whole drive
hda=\Device\HarddiskVolume0 # To mount the whole drive
hda2=\Device\Harddisk0\Partition2 # To mount a single partition (listed Partition 3 by diskpart.exe)
hda2=\Device\Harddisk0\Partition2 # To mount a single partition


Be '''careful''' with the way Windows numbers the partition. Use '''<code>diskpart.exe</code>''' to get the number and then '''{{red|subtract 1 from displayed number}}''':
Use '''<code>diskpart.exe</code>''' to get the number (other alternatives are ''dd'' and ''dmdiag'', see [http://colinux.wikia.com/wiki/Partitions]).<br/>
'''{{red|Caution!}}''' To get things even more confusing it seems that the partition number sometimes start from 0 or 1. So you might have to substract 1 from the given number or not.
<pre>
<pre>
DISKPART> list disk
DISKPART> list disk
Line 18: Line 19:
...
...
Partition 4 Extended 125 GB 24 GB
Partition 4 Extended 125 GB 24 GB
Partition 5 Logical 3814 MB 24 GB <-- to select this partition, use \Device\Harddisk0\Partition4
Partition 5 Logical 3814 MB 24 GB <-- try \Device\Harddisk0\Partition4 or \Device\Harddisk0\Partition5
...
...



Revision as of 10:19, 24 November 2010

Mount

Mounting a .dvi drive file

Say you have a file D:\andlinux\drives\base.vdi. To mount it in AndLinux, add to your settings.txt:

cobd0=D:\andlinux\drives\base.vdi

Mounting a physical drive/partition/cdrom/usb

Reference: [1], [2] To mount an existing drive or partition, add to your settings.txt:

hda=\Device\HarddiskVolume0                    # To mount the whole drive
hda2=\Device\Harddisk0\Partition2              # To mount a single partition

Use diskpart.exe to get the number (other alternatives are dd and dmdiag, see [3]).
Caution! To get things even more confusing it seems that the partition number sometimes start from 0 or 1. So you might have to substract 1 from the given number or not.

DISKPART> list disk
DISKPART> select disk 0
DISKPART> list partition

  ...
  Partition 4    Extended           125 GB    24 GB
  Partition 5    Logical           3814 MB    24 GB  <-- try \Device\Harddisk0\Partition4 or \Device\Harddisk0\Partition5
  ...

DISKPART> exit

The above notation is actually the shorthand notation for:

codb3=\Device\Harddisk0\Partition2
hda2=:cobd3

One can also mount a floppy, cd, usb:

fd0=\Device\Floppy0 
cdrom0=\Device\Cdrom0 
sda1=\Device\Harddisk1\Partition1              # Assuming usb is the 2nd hard disk

In AndLinux the partition can be mounted as usual:

mount -t ext3 /dev/hda2 /mnt/hda2

Troubleshooting

Startup delays

  • Interaction with Anti-Virus software - AV software may interact with the startup of AndLinux, typically by maintaining a lock on the 4GB disk image file base.drv while it is scanned.
    • Solution: To prevent this, one can exclude the andlinux directory from the AV on-access scanner. In McAfee, this is done by opening the VirusScan consoledouble-ckick On-Access Scanner → then select All Processes → open the pane Detection and click the button Exclusions... → click Add... to add a new exclusion → Browse to AndLinux directory and select Also exclude subfolders.
  • Stalling when mounting / - You experience a huge delay during the startup process, and when launching the FLTK console, you observe that andlinux is stalling on the message below.
ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on cobd0
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Modules already installed.
Closing /
kjournald starting.  Commit interval 5 seconds
  • Solution: The fix proposed in this post is to actually change the extension of the disk image file from .drv to something like .drive (ie. change ./Drives/base.drv to ./Drives/base.drive and ./Drives/swap.drv to ./Drives/swap.drive) and adapt the configuration files ./settings.txt accordingly.

Network issues

  • TAP Interfaces - Reference coLinux page. Some forum posts: [4], [5].
  • Message Network cable unplugged for TAP interface even when AndLinux started.
  • Open your settings file settings.txt, and check the configuration line for the tuntap interface
eth1=tuntap,"TAP-Colinux",00:11:22:33:44:55
  • Go to Network Connections window. Check that the connection for device named TAP-Win32 Adapter V8 (coLinux) is indeed called TAP-Colinux, as specified above. If not (for instance it is called Local Area Connection or Local Area Connection 2), then rename it!
  • Another solution (not tried) from [6]:
    • Control-PanelNetwork Connectionsright click on the TAP-Win32 connection → PropertiesConfigureAdvancedMedia Status = Always connected.