From: Jim & A. H. <JimHenderson@Sydney.dialix.com.au> - 2004-11-22 17:40:11
|
Greetings, I got the May version of coLinux to work, and then decided to try the latest snapshot, because I want to use cofs to write to the NTFS file system. I installed coLinux-0.6.1-20041024.exe and fetched what I thought was the most recent Gentoo file system, gentoo-i586-ext3-2g-deluxe.bz2 and unpacked it in place of the previous one, but the kernel is unable to check the file system. Here are the console messages: modprobe: Safe mode has more than one parameter modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter fsck.ext3: No such file or directory while trying to open /dev/cobd0 /dev/cobd0: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> * Filesystem couldn't be fixed :( [ !! ] Give root password for maintenance (or type Control-D for normal startup): error copying: "/dev/initctl" to "/lib/d ev-state/initctl" I have tried e2fsck on /dev/cobd0, but it complains about the boot block: e2fsck 1.34 (25-Jul-2003) modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter modprobe: QM_MODULES: Function not implemented modprobe: Safe mode has more than one parameter e2fsck: No such file or directory while trying to open /dev/codb0 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> bash-2.05b# I've tried with the -b 8193 option as well. Did I perhaps get the wrong file system? Can any of you help? I ran the program with this command: colinux-daemon -c colinux.xml -t nt and colinux.xml contains: <?xml version="1.0" encoding="UTF-8"?> <colinux> <!-- This line needs to point to your root file system. For example change "root_fs" to the name of the Debian image. Inside coLinux it will be /dev/cobd0 Block Device Aliasing: You can now handle most dual-boot issues by adding an alias="devname" to block_device. i.e. alias="hda", alias="hda1" You can do this for SCSI as well as IDE. You need to be aware that if you add an alias, you need to change your bootparams root="devname" appropriately (you may need to use devfs naming in some situations). --> <block_device index="0" path="\DosDevices\c:\coLinux\gentoo-i586-ext3-2g-deluxe" enabled="true" /> <!-- This line can specify a swap file if you wish, or an additional image file, it will /dev/cobd1. Additional block_devices can be specified in the same manner by increasing the index --> <block_device index="1" path="\DosDevices\c:\coLinux\swap_device.swp" enabled="false" /> <!-- bootparams allows you to pass kernel boot parameters --> <bootparams>root=/dev/cobd0</bootparams> <!-- Initial RamDISK (initrd) support --> <initrd path="initrd.gz" /> <!-- image allows you to specify the kernel to boot --> <image path="vmlinux" /> <!-- this line allows you to specify the amount of memory available to coLinux --> <memory size="64" /> <!-- This allows you to modify networking parameters, see the README or website or wiki for more information --> <network index="0" type="tap" /> </colinux> I get the same kind of result with this command line: colinux-daemon kernel=vmlinux hda1=gentoo-i586-ext3-2g-deluxe root=/dev/hda1 \ initrd=initrd.gz mem=64 Any help appreciated, Jim Henderson -- JimHenderson@Sydney.dialix.com.au |
From: Ringer <rin...@gm...> - 2004-11-22 23:02:17
|
Go to the colinux wiki site: http://www.colinux.org/wiki/ Find the section "Getting Gentoo to work nicely with 2.6.x colinux", follow the instructions and good luck. On Sun, 21 Nov 2004 23:46:59 -0500, Jim & Anne Henderson <jim...@sy...> wrote: > Greetings, > > I got the May version of coLinux to work, and then decided to try the latest > snapshot, because I want to use cofs to write to the NTFS file system. > > I installed coLinux-0.6.1-20041024.exe and fetched what I thought was the > most recent Gentoo file system, gentoo-i586-ext3-2g-deluxe.bz2 and unpacked > it in place of the previous one, but the kernel is unable to check the file > system. Here are the console messages: > > modprobe: Safe mode has more than one parameter > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > fsck.ext3: No such file or directory while trying to open /dev/cobd0 > /dev/cobd0: > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 <device> > > * Filesystem couldn't be fixed :( > [ !! ] > > Give root password for maintenance > (or type Control-D for normal startup): error copying: "/dev/initctl" to > "/lib/d > ev-state/initctl" > > I have tried e2fsck on /dev/cobd0, but it complains about the boot block: > > e2fsck 1.34 (25-Jul-2003) > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > modprobe: QM_MODULES: Function not implemented > > modprobe: Safe mode has more than one parameter > e2fsck: No such file or directory while trying to open /dev/codb0 > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 <device> > > bash-2.05b# > > I've tried with the -b 8193 option as well. > > Did I perhaps get the wrong file system? Can any of you help? > > I ran the program with this command: > colinux-daemon -c colinux.xml -t nt > > and colinux.xml contains: > > <?xml version="1.0" encoding="UTF-8"?> > <colinux> > <!-- This line needs to point to your root file system. > For example change "root_fs" to the name of the Debian image. > Inside coLinux it will be /dev/cobd0 > > Block Device Aliasing: You can now handle most dual-boot issues > by adding an alias="devname" to block_device. i.e. alias="hda", > alias="hda1" You can do this for SCSI as well as IDE. You need > to be aware that if you add an alias, you need to change your > bootparams root="devname" appropriately (you may need to use > devfs naming in some situations). --> > <block_device index="0" > path="\DosDevices\c:\coLinux\gentoo-i586-ext3-2g-deluxe" > enabled="true" /> > > <!-- This line can specify a swap file if you wish, or an additional > image file, it will /dev/cobd1. Additional block_devices can > be specified in the same manner by increasing the index --> > > <block_device index="1" path="\DosDevices\c:\coLinux\swap_device.swp" > enabled="false" /> > > <!-- bootparams allows you to pass kernel boot parameters --> > <bootparams>root=/dev/cobd0</bootparams> > > <!-- Initial RamDISK (initrd) support --> > <initrd path="initrd.gz" /> > > <!-- image allows you to specify the kernel to boot --> > <image path="vmlinux" /> > > <!-- this line allows you to specify the amount of memory available > to coLinux --> > <memory size="64" /> > > <!-- This allows you to modify networking parameters, see the README > or website or wiki for more information --> > <network index="0" type="tap" /> > </colinux> > > I get the same kind of result with this command line: > colinux-daemon kernel=vmlinux hda1=gentoo-i586-ext3-2g-deluxe root=/dev/hda1 > \ > initrd=initrd.gz mem=64 > > Any help appreciated, > Jim Henderson > -- > JimHenderson@Sydney.dialix.com.au > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Ringer <rin...@gm...> - 2004-11-23 19:29:36
|
http://www.colinux.org/?section=downloads On Mon, 22 Nov 2004 21:40:19 -0500, Jim Henderson <jim...@sy...> wrote: > Dear Ringer, > > Thanks for pointing me to that page in the Wiki. I already have the latest > snapshot, but the link to get the filesystem: > http://www.gentoo.org.tw/benny/distfiles/gentoo_2.6.8.1-co-0.6.2-pre6.zip.tgz > is broken. > > Do you know another place I can get one? > > Jim > > > ----- Original Message ----- > From: "Ringer" <rin...@gm...> > To: "Jim & Anne Henderson" <jim...@sy...> > Cc: <col...@li...> > Sent: Monday, November 22, 2004 6:02 PM > Subject: Re: [coLinux-users] Wrong file system with Oct 24 snapshot? > > > Go to the colinux wiki site: > > > > http://www.colinux.org/wiki/ > > > > Find the section "Getting Gentoo to work nicely with 2.6.x colinux", > > follow the instructions and good luck. > > > > On Sun, 21 Nov 2004 23:46:59 -0500, Jim & Anne Henderson > > <jim...@sy...> wrote: > >> Greetings, > >> > >> I got the May version of coLinux to work, and then decided to try the > >> latest > >> snapshot, because I want to use cofs to write to the NTFS file system. > >> > >> I installed coLinux-0.6.1-20041024.exe and fetched what I thought was the > >> most recent Gentoo file system, gentoo-i586-ext3-2g-deluxe.bz2 and > >> unpacked > >> it in place of the previous one, but the kernel is unable to check the > >> file > >> system. Here are the console messages: > >> > <<snip>> > > |