From: Andreas G. <ag...@gm...> - 2009-11-25 12:40:27
|
Hello, I never tried the provided ArchLinux image, but the problem seems to be that the image is accessed via /dev/hda1. It should be /dev/cobd0 or similar. Please check the "root=" line in your LA.conf file for the correct device name and make sure that there is a corresponding line cobd0="c:\path\to\your\root_fs" that points to the image file. Best regards, Andreas Göb Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb ger...@og...: > Hello > > New to coLinux > > New installation > Host: windows 2000 service pack 4 > coLinux: 0.7.5 > selected distro (from installation dialog): arch linux > because it is the smallest one. > extracted the 7z file > selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs > (renamed to "root_fs") > > On windows: > Start -> Run -> cmd > cd to coLinux installation > copy example.conf to LA.conf > adjust the path from c:\coLinux to c:\Programme\coLinux > type: colinux-daemon.exe @LA.conf > boot looks nice > mount of /dev/hda1 -> / looks like working > but fsck failes with: > FILESYSTEM CHECK FAILED (Possibly not existent or swap device?) > > going to maintenance console works > > cat /etc/issue > tells me that I work on "Arch Linux (Core Dump)" > > mount shows: > /dev/hda1 on / type ext2 (rw,noatime) > > fsck ends up with: > fsck.ext3: No such device or address while trying to open /dev/hda1 > Possibly not existent or swap device? > > continuing with CTRL-D does a reboot ending up with the same failure > > Do I something wrong or is the provided arch-linux fs realy corrupt? > > thanks > gerhard |
From: <ger...@og...> - 2009-11-25 14:21:51
|
Here my config (all not commented lines) kernel=vmlinux cobd0="c:\Programme\coLinux\root_fs" root=/dev/cobd0 ro initrd=initrd.gz So everything looks fine? ro seams to be ignored? Whats the location of the initrd file? It is not part of the c:\Programme\coLinux\ directory Full output of mount: /dev/hda1 on / type ext2 (rw,noatime) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/shm type tmpfs (rw) Looks fine for me. yours gerhard Andreas Göb schrieb: > Hello, > > I never tried the provided ArchLinux image, but the problem seems to be > that the image is accessed via /dev/hda1. It should be /dev/cobd0 or > similar. Please check the "root=" line in your LA.conf file for the > correct > device name and make sure that there is a corresponding line > cobd0="c:\path\to\your\root_fs" that points to the image file. > > Best regards, > Andreas Göb > > > Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb > ger...@og...: >> Hello >> >> New to coLinux >> >> New installation >> Host: windows 2000 service pack 4 >> coLinux: 0.7.5 >> selected distro (from installation dialog): arch linux >> because it is the smallest one. >> extracted the 7z file >> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs >> (renamed to "root_fs") >> >> On windows: >> Start -> Run -> cmd >> cd to coLinux installation >> copy example.conf to LA.conf >> adjust the path from c:\coLinux to c:\Programme\coLinux >> type: colinux-daemon.exe @LA.conf >> boot looks nice >> mount of /dev/hda1 -> / looks like working >> but fsck failes with: >> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?) >> >> going to maintenance console works >> >> cat /etc/issue >> tells me that I work on "Arch Linux (Core Dump)" >> >> mount shows: >> /dev/hda1 on / type ext2 (rw,noatime) >> >> fsck ends up with: >> fsck.ext3: No such device or address while trying to open /dev/hda1 >> Possibly not existent or swap device? >> >> continuing with CTRL-D does a reboot ending up with the same failure >> >> Do I something wrong or is the provided arch-linux fs realy corrupt? >> >> thanks >> gerhard > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > |
From: Peter K. <pet...@ma...> - 2009-11-25 17:35:32
|
Please, try to add: hda1=:cobd0 after line cobd0="c:\Programme\coLinux\root_fs" Peter. > Here my config (all not commented lines) > > kernel=vmlinux > ??cobd0="c:\Programme\coLinux\root_fs" > ??root=/dev/cobd0 > ??ro > ??initrd=initrd.gz > > So everything looks fine? > > ro seams to be ignored? > > Whats the location of the initrd file? It is not part of the > c:\Programme\coLinux\ directory > > > Full output of mount: > /dev/hda1 on / type ext2 (rw,noatime) > none on /proc type proc (rw) > none on /sys type sysfs (rw) > none on /dev/shm type tmpfs (rw) > > Looks fine for me. > > > yours > gerhard > > > Andreas Göb schrieb: > > Hello, > > > > I never tried the provided ArchLinux image, but the problem seems to be > > that the image is accessed via /dev/hda1. It should be /dev/cobd0 or > > similar. Please check the "root=" line in your LA.conf file for the > > correct > > device name and make sure that there is a corresponding line > > cobd0="c:\path\to\your\root_fs" that points to the image file. > > > > Best regards, > > Andreas Göb > > > > > > Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb > > ger...@og...: > >> Hello > >> > >> New to coLinux > >> > >> New installation > >> Host: windows 2000 service pack 4 > >> coLinux: 0.7.5 > >> selected distro (from installation dialog): arch linux > >> because it is the smallest one. > >> extracted the 7z file > >> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs > >> (renamed to "root_fs") > >> > >> On windows: > >> Start -> Run -> cmd > >> cd to coLinux installation > >> copy example.conf to LA.conf > >> adjust the path from c:\coLinux to c:\Programme\coLinux > >> type: colinux-daemon.exe @LA.conf > >> boot looks nice > >> mount of /dev/hda1 -> / looks like working > >> but fsck failes with: > >> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?) > >> > >> going to maintenance console works > >> > >> cat /etc/issue > >> tells me that I work on "Arch Linux (Core Dump)" > >> > >> mount shows: > >> /dev/hda1 on / type ext2 (rw,noatime) > >> > >> fsck ends up with: > >> fsck.ext3: No such device or address while trying to open /dev/hda1 > >> Possibly not existent or swap device? > >> > >> continuing with CTRL-D does a reboot ending up with the same failure > >> > >> Do I something wrong or is the provided arch-linux fs realy corrupt? > >> > >> thanks > >> gerhard > > > > ------------------------------------------------------------------------------ > > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > > trial. Simplify your report design, integration and deployment - and focus on > > what you do best, core application coding. Discover what's new with > > Crystal Reports now. ?http://p.sf.net/sfu/bobj-july > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. ?http://p.sf.net/sfu/bobj-july > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > |
From: Henry N. <hen...@ar...> - 2009-11-25 23:25:07
|
Hello Andreas, if you have hda1 in the file "/etc/fstab", then please use this config: hda1="c:\Programme\coLinux\root_fs root=/dev/hda1 Please don't use initrd.gz, if you have trobble with fsck, because this initrd.gz tries to mount your filesystem "rw" to inject the modules. Later (after fsck success), you can enable initrd for one boot. And more later you never needs initrd again, as long you not upgraded coLinux version. Of curse "ro" is not ignored. That's why you see such mysterious output. Mount will read some times from /etc/mtab, so that fails on read only mounted filesystems. Please ask the kernel directly with "cat /proc/mounts". Henry Am 25.11.2009 18:35, schrieb Peter Kuznetsov: > Please, try to add: > hda1=:cobd0 > after line > cobd0="c:\Programme\coLinux\root_fs" > > Peter. > > > > >> Here my config (all not commented lines) >> >> kernel=vmlinux >> ??cobd0="c:\Programme\coLinux\root_fs" >> ??root=/dev/cobd0 >> ??ro >> ??initrd=initrd.gz >> >> So everything looks fine? >> >> ro seams to be ignored? >> >> Whats the location of the initrd file? It is not part of the >> c:\Programme\coLinux\ directory >> >> >> Full output of mount: >> /dev/hda1 on / type ext2 (rw,noatime) >> none on /proc type proc (rw) >> none on /sys type sysfs (rw) >> none on /dev/shm type tmpfs (rw) >> >> Looks fine for me. >> >> >> yours >> gerhard >> >> >> Andreas Göb schrieb: >> >>> Hello, >>> >>> I never tried the provided ArchLinux image, but the problem seems to be >>> that the image is accessed via /dev/hda1. It should be /dev/cobd0 or >>> similar. Please check the "root=" line in your LA.conf file for the >>> correct >>> device name and make sure that there is a corresponding line >>> cobd0="c:\path\to\your\root_fs" that points to the image file. >>> >>> Best regards, >>> Andreas Göb >>> >>> >>> Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb >>> ger...@og...: >>> >>>> Hello >>>> >>>> New to coLinux >>>> >>>> New installation >>>> Host: windows 2000 service pack 4 >>>> coLinux: 0.7.5 >>>> selected distro (from installation dialog): arch linux >>>> because it is the smallest one. >>>> extracted the 7z file >>>> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs >>>> (renamed to "root_fs") >>>> >>>> On windows: >>>> Start -> Run -> cmd >>>> cd to coLinux installation >>>> copy example.conf to LA.conf >>>> adjust the path from c:\coLinux to c:\Programme\coLinux >>>> type: colinux-daemon.exe @LA.conf >>>> boot looks nice >>>> mount of /dev/hda1 -> / looks like working >>>> but fsck failes with: >>>> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?) >>>> >>>> going to maintenance console works >>>> >>>> cat /etc/issue >>>> tells me that I work on "Arch Linux (Core Dump)" >>>> >>>> mount shows: >>>> /dev/hda1 on / type ext2 (rw,noatime) >>>> >>>> fsck ends up with: >>>> fsck.ext3: No such device or address while trying to open /dev/hda1 >>>> Possibly not existent or swap device? >>>> >>>> continuing with CTRL-D does a reboot ending up with the same failure >>>> >>>> Do I something wrong or is the provided arch-linux fs realy corrupt? >>>> >>>> thanks >>>> gerhard >>>> >>> |
From: <ger...@og...> - 2009-11-30 11:07:54
|
Henry Nestler schrieb: > Hello Andreas, > > if you have hda1 in the file "/etc/fstab", then please use this config: > > hda1="c:\Programme\coLinux\root_fs > root=/dev/hda1 YES this did the trick. yours gerhard > > Please don't use initrd.gz, if you have trobble with fsck, because this > initrd.gz tries to mount your filesystem "rw" to inject the modules. > Later (after fsck success), you can enable initrd for one boot. And more > later you never needs initrd again, as long you not upgraded coLinux > version. > > Of curse "ro" is not ignored. That's why you see such mysterious output. > Mount will read some times from /etc/mtab, so that fails on read only > mounted filesystems. Please ask the kernel directly with "cat /proc/mounts". > > Henry > > > Am 25.11.2009 18:35, schrieb Peter Kuznetsov: >> Please, try to add: >> hda1=:cobd0 >> after line >> cobd0="c:\Programme\coLinux\root_fs" >> >> Peter. >> >> >> >> >>> Here my config (all not commented lines) >>> >>> kernel=vmlinux >>> ??cobd0="c:\Programme\coLinux\root_fs" >>> ??root=/dev/cobd0 >>> ??ro >>> ??initrd=initrd.gz >>> >>> So everything looks fine? >>> >>> ro seams to be ignored? >>> >>> Whats the location of the initrd file? It is not part of the >>> c:\Programme\coLinux\ directory >>> >>> >>> Full output of mount: >>> /dev/hda1 on / type ext2 (rw,noatime) >>> none on /proc type proc (rw) >>> none on /sys type sysfs (rw) >>> none on /dev/shm type tmpfs (rw) >>> >>> Looks fine for me. >>> >>> >>> yours >>> gerhard >>> >>> >>> Andreas Göb schrieb: >>> >>>> Hello, >>>> >>>> I never tried the provided ArchLinux image, but the problem seems to be >>>> that the image is accessed via /dev/hda1. It should be /dev/cobd0 or >>>> similar. Please check the "root=" line in your LA.conf file for the >>>> correct >>>> device name and make sure that there is a corresponding line >>>> cobd0="c:\path\to\your\root_fs" that points to the image file. >>>> >>>> Best regards, >>>> Andreas Göb >>>> >>>> >>>> Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb >>>> ger...@og...: >>>> >>>>> Hello >>>>> >>>>> New to coLinux >>>>> >>>>> New installation >>>>> Host: windows 2000 service pack 4 >>>>> coLinux: 0.7.5 >>>>> selected distro (from installation dialog): arch linux >>>>> because it is the smallest one. >>>>> extracted the 7z file >>>>> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs >>>>> (renamed to "root_fs") >>>>> >>>>> On windows: >>>>> Start -> Run -> cmd >>>>> cd to coLinux installation >>>>> copy example.conf to LA.conf >>>>> adjust the path from c:\coLinux to c:\Programme\coLinux >>>>> type: colinux-daemon.exe @LA.conf >>>>> boot looks nice >>>>> mount of /dev/hda1 -> / looks like working >>>>> but fsck failes with: >>>>> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?) >>>>> >>>>> going to maintenance console works >>>>> >>>>> cat /etc/issue >>>>> tells me that I work on "Arch Linux (Core Dump)" >>>>> >>>>> mount shows: >>>>> /dev/hda1 on / type ext2 (rw,noatime) >>>>> >>>>> fsck ends up with: >>>>> fsck.ext3: No such device or address while trying to open /dev/hda1 >>>>> Possibly not existent or swap device? >>>>> >>>>> continuing with CTRL-D does a reboot ending up with the same failure >>>>> >>>>> Do I something wrong or is the provided arch-linux fs realy corrupt? >>>>> >>>>> thanks >>>>> gerhard >>>>> > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > |
From: <ger...@og...> - 2009-11-30 11:06:52
|
Peter Kuznetsov schrieb: > Please, try to add: > hda1=:cobd0 > after line > cobd0="c:\Programme\coLinux\root_fs" According to the docu this should solve the problem, but did not. It is solved anyway (see ohter mail). thanks gerhard > >> Here my config (all not commented lines) >> >> kernel=vmlinux >> ??cobd0="c:\Programme\coLinux\root_fs" >> ??root=/dev/cobd0 >> ??ro >> ??initrd=initrd.gz >> >> So everything looks fine? >> >> ro seams to be ignored? >> >> Whats the location of the initrd file? It is not part of the >> c:\Programme\coLinux\ directory >> >> >> Full output of mount: >> /dev/hda1 on / type ext2 (rw,noatime) >> none on /proc type proc (rw) >> none on /sys type sysfs (rw) >> none on /dev/shm type tmpfs (rw) >> >> Looks fine for me. >> >> >> yours >> gerhard >> >> >> Andreas Göb schrieb: >>> Hello, >>> >>> I never tried the provided ArchLinux image, but the problem seems to be >>> that the image is accessed via /dev/hda1. It should be /dev/cobd0 or >>> similar. Please check the "root=" line in your LA.conf file for the >>> correct >>> device name and make sure that there is a corresponding line >>> cobd0="c:\path\to\your\root_fs" that points to the image file. >>> >>> Best regards, >>> Andreas Göb >>> >>> >>> Am Mittwoch, den 25.11.2009, 12:01 +0100 schrieb >>> ger...@og...: >>>> Hello >>>> >>>> New to coLinux >>>> >>>> New installation >>>> Host: windows 2000 service pack 4 >>>> coLinux: 0.7.5 >>>> selected distro (from installation dialog): arch linux >>>> because it is the smallest one. >>>> extracted the 7z file >>>> selcted root file system: ArchLinux-2007.08-2-ext3-256m.fs >>>> (renamed to "root_fs") >>>> >>>> On windows: >>>> Start -> Run -> cmd >>>> cd to coLinux installation >>>> copy example.conf to LA.conf >>>> adjust the path from c:\coLinux to c:\Programme\coLinux >>>> type: colinux-daemon.exe @LA.conf >>>> boot looks nice >>>> mount of /dev/hda1 -> / looks like working >>>> but fsck failes with: >>>> FILESYSTEM CHECK FAILED (Possibly not existent or swap device?) >>>> >>>> going to maintenance console works >>>> >>>> cat /etc/issue >>>> tells me that I work on "Arch Linux (Core Dump)" >>>> >>>> mount shows: >>>> /dev/hda1 on / type ext2 (rw,noatime) >>>> >>>> fsck ends up with: >>>> fsck.ext3: No such device or address while trying to open /dev/hda1 >>>> Possibly not existent or swap device? >>>> >>>> continuing with CTRL-D does a reboot ending up with the same failure >>>> >>>> Do I something wrong or is the provided arch-linux fs realy corrupt? >>>> >>>> thanks >>>> gerhard >>> ------------------------------------------------------------------------------ >>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >>> trial. Simplify your report design, integration and deployment - and focus on >>> what you do best, core application coding. Discover what's new with >>> Crystal Reports now. ?http://p.sf.net/sfu/bobj-july >>> _______________________________________________ >>> coLinux-users mailing list >>> coL...@li... >>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>> >>> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. ?http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> > > |