Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

error while starting CoLinux

Help
Abhishek
2006-09-18
2013-05-09
  • Abhishek
    Abhishek
    2006-09-18

    My config file looks like this -

    <?xml version="1.0" encoding="UTF-8"?>
    <colinux>
        <block_device index="0" path="\DosDevices\C:\coLinux\Debian-3.0r0.ext3.1gb" enabled="true"/>
        <block_device index="1" path="\DosDevices\c:\coLinux\swap_564Mb" enabled="true"/>
        <bootparams>root=/dev/cobd0</bootparams>
        <image path="vmlinux"/>
        <memory size="128"/>
        <network index="0" type="tap" name="TAP"/>
    </colinux>

    But, when I start the colinux, I get the following error -
    EXT2-fs warning: checktime reached, running e2fsck is recommended
    VFS: Mounted root (ext2 filesystem).
    end_request: I/O error, dev cobd0, sector 16
    ReiserFS: cobd0: warning: sh-2006: read_super_block: bread failed (dev cobd0, bl
    ock 2, size 4096)
    end_request: I/O error, dev cobd0, sector 128
    ReiserFS: cobd0: warning: sh-2006: read_super_block: bread failed (dev cobd0, bl
    ock 16, size 4096)
    ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
    cobd0
    end_request: I/O error, dev cobd0, sector 2
    EXT3-fs: unable to read superblock
    end_request: I/O error, dev cobd0, sector 2
    EXT2-fs: unable to read superblock
    end_request: I/O error, dev cobd0, sector 64
    isofs_fill_super: bread failed, dev=cobd0, iso_blknum=16, block=32
    end_request: I/O error, dev cobd0, sector 16
    ReiserFS: cobd0: warning: sh-2006: read_super_block: bread failed (dev cobd0, bl
    ock 2, size 4096)
    end_request: I/O error, dev cobd0, sector 128
    ReiserFS: cobd0: warning: sh-2006: read_super_block: bread failed (dev cobd0, bl
    ock 16, size 4096)
    end_request: I/O error, dev cobd0, sector 2
    end_request: I/O error, dev cobd0, sector 64
    isofs_fill_super: bread failed, dev=cobd0, iso_blknum=16, block=32
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(117,0)

    I am sure this has to do with my config file and specially the bootparam. Just don't know what the value there should be and how to resolve the error.

    Any help would be appreciated.
    Thanks,
    Abhi

     
    • Henry N.
      Henry N.
      2006-10-02

      I think, your file Debian-3.0r0.ext3.1gb is corrupted.  Is this your first start of coLinux? Than are you shure, that you have extracted it in right way with bunzip2.exe?  Some other windows unzipper make a wrong outputfile.  The file size should be exactly 1GB (1024*1024*1024 bytes).

      Here is the tool:
      http://www.henrynestler.com/colinux/tools/bzip2-102-x86-win32.zip

       
      • Nate
        Nate
        2007-01-25

        I encountered this problem and solved it by going into cmd

        colinux-daemon.exe --remove-driver
        colinux-daemon.exe --install-driver

        Make sure that you're in your root directory C:\coLinux\ for me

        This solves that problem if you uninstall [or move] coLinux from one location and install it to another.

        -Nate