From: Sam M. <pa...@gm...> - 2005-01-17 22:57:00
|
Something interesting from coLinux-users; appears that we have eventual corruption on native mode ext3 drives over time. It would appear that it might be a memory issue as he notes that it takes a while for it to become apparent. ---------- Forwarded message ---------- From: Brendan Simon <Bre...@fa...> Date: Tue, 18 Jan 2005 00:15:11 +1100 Subject: Re: [coLinux-users] ext3 boot errors To: Sam Moffatt <pa...@gm...> Cc: col...@li... YIKES!!!! I just tried to launch coLinux again and got the following (BTW, I haven't rebooted my computer yet). VFS: Cannot open root device "cobd/0" or unknown-brock(0,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) colinux: kernel panic suggests that either you forget to supply a root= kernel boot parameter or the file / device mapped to the root file system is not found or inaccesible. Plesae Check your coLinux configuration I know my parameters are OK because I've launched coLinux many times in the past. This has just happened recently and all I can think of is an ext3 corruption. I will reboot my computer tomorrow and try again. I will then reboot into real linux and see if I can fix the ext3 partition. This is a serious problem and I hope we can get it fixed. Hopefully some of my reports woill be useful to track down the problem. Brendan Simon. Sam Moffatt wrote: >Since it happens after a while, I would be thinking it would be a >memory allocation thing, which would explain why coLinux doesn't want >to start up again. after colinux fails to reboot, do you restart your >computer or do you just leave it? > >also, if you could grab the error message colinux prints when it >doesn't reboot, that would be handy > > >On Mon, 17 Jan 2005 15:34:55 +1100, Brendan Simon ><Bre...@fa...> wrote: > > >>No I haven't booted into linux proper. I haven't done this for quite a >>while since I've been happy with coLinux with Samba and VNC :) >> >>I don't like booting my machine often as I have many many windows open >>and setup the way I like it. I guess I will have to bite the bullet and >>see if I can fix the issue using real linux. >> >>BTW, this problem has happended at least 3 times now. It makes me feel >>very uneasy with what coLinux is doing to my hard drive. Is there any >>known problems using ext2 and/or ext3 partitions on a hard drive >>(laptop) ??? >>If so, I would really like to see them fixed so I don't lose any data >>(or minimise the chances). >>Would I be better of with VMWare ??? (I hope not). >> >>Thanks, >>Brendan Simon. >> >> >> |
From: Dan A. <da...@co...> - 2005-01-28 10:45:12
|
On Tue, Jan 18, 2005 at 08:56:57AM +1000, Sam Moffatt wrote: > Something interesting from coLinux-users; appears that we have > eventual corruption on native mode ext3 drives over time. It would > appear that it might be a memory issue as he notes that it takes a > while for it to become apparent. > >[..] > > VFS: Cannot open root device "cobd/0" or unknown-brock(0,0) > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) > colinux: kernel panic suggests that either you forget to supply a > root= kernel boot parameter or the file / device mapped to the root > file system is not found or inaccesible. Plesae Check your > coLinux configuration >[..] That is not file system corruption, but something else. Notice the print-out of 'unknown-block(0,0)', this suggests that the kernel wasn't able to resolve the device name from a string to a proper [major, minor] tuple. cobd is major 117. Perhaps because the passed string was 'cobd/0' instead of 'cobd0'? -- Dan Aloni da...@co... |
From: Sam M. <pa...@gm...> - 2005-01-28 11:19:22
|
Still doesn't explain why Linux won't boot natively after previously working properly or for the sudden change in coLinux not operating. It was working, and then it stops working with that error. But would the device string have changed from the time when it was working? And if it has, how has it happened? It also doesn't explain this either: >I have similar behaviour. More precisely - the first time I run colinux I >get exactly the same message, but my problems go away when I re-run it. This >happens only when accessing physical partitions, not partition images. I can >repeat this on 2 totally different machines. Any clue? > >Jarek Which is common with a few others in this thread. Perhaps there are two issues here: 1) coLinux being unable to mount a partition with that error and 2) coLinux causing corruption to a partition, as is in the case of Brenden: >OK. I booted to real-linux and am currently horrified. > # fsck.ext3 -f -y -c -v /dev/hda1 > <snip> > fsck.ext3: e2fsck_read_bitmaps: illegal bitmap block(s) for /dev/hda1 > >Is my disk and/or partition stuffed? >Is it likely that coLinux is to blame? >Looks like I may have to boot to a rescue disk and try and fsck the >partition. I hope that works. 1) This appears to be solved by removing the initrd line. 2) This is either a coLinux issue or a normal disk failure issue. Until it happens again, we're not going to know. It seems his questions are worth trying to answer. On Fri, 28 Jan 2005 12:48:23 +0200, Dan Aloni <da...@co...> wrote: > On Tue, Jan 18, 2005 at 08:56:57AM +1000, Sam Moffatt wrote: > > Something interesting from coLinux-users; appears that we have > > eventual corruption on native mode ext3 drives over time. It would > > appear that it might be a memory issue as he notes that it takes a > > while for it to become apparent. > > > >[..] > > > > VFS: Cannot open root device "cobd/0" or unknown-brock(0,0) > > Please append a correct "root=" boot option > > Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) > > colinux: kernel panic suggests that either you forget to supply a > > root= kernel boot parameter or the file / device mapped to the root > > file system is not found or inaccesible. Plesae Check your > > coLinux configuration > >[..] > > That is not file system corruption, but something else. > > Notice the print-out of 'unknown-block(0,0)', this suggests that the kernel > wasn't able to resolve the device name from a string to a proper [major, minor] > tuple. cobd is major 117. Perhaps because the passed string was 'cobd/0' instead > of 'cobd0'? > > -- > Dan Aloni > da...@co... > |
From: Sam L. <sa...@li...> - 2005-01-18 15:17:14
|
Sam Moffatt wrote: > Something interesting from coLinux-users; appears that we have > eventual corruption on native mode ext3 drives over time. It would > appear that it might be a memory issue as he notes that it takes a > while for it to become apparent. This appears to be the same thign I reported with reiserfs. I could boot directly with real linux onto the partition but not from coLinux I bet if the guy downloads a root image file and boots from that, but with his old FS as a different COBD I bet he can mount it after he boots. To me it just seems to be a problem when the root fs is mounted when the initrd switches out. Sam > > > ---------- Forwarded message ---------- > From: Brendan Simon <Bre...@fa...> > Date: Tue, 18 Jan 2005 00:15:11 +1100 > Subject: Re: [coLinux-users] ext3 boot errors > To: Sam Moffatt <pa...@gm...> > Cc: col...@li... > > > YIKES!!!! > I just tried to launch coLinux again and got the following (BTW, I > haven't rebooted my computer yet). > > VFS: Cannot open root device "cobd/0" or unknown-brock(0,0) > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) > colinux: kernel panic suggests that either you forget to supply a > root= kernel boot parameter or the file / device mapped to the root > file system is not found or inaccesible. Plesae Check your > coLinux configuration > > I know my parameters are OK because I've launched coLinux many times in > the past. This has just happened recently and all I can think of is an > ext3 corruption. > > I will reboot my computer tomorrow and try again. I will then reboot > into real linux and see if I can fix the ext3 partition. This is a > serious problem and I hope we can get it fixed. Hopefully some of my > reports woill be useful to track down the problem. > > Brendan Simon. > > Sam Moffatt wrote: > > >>Since it happens after a while, I would be thinking it would be a >>memory allocation thing, which would explain why coLinux doesn't want >>to start up again. after colinux fails to reboot, do you restart your >>computer or do you just leave it? >> >>also, if you could grab the error message colinux prints when it >>doesn't reboot, that would be handy >> >> >>On Mon, 17 Jan 2005 15:34:55 +1100, Brendan Simon >><Bre...@fa...> wrote: >> >> >> >>>No I haven't booted into linux proper. I haven't done this for quite a >>>while since I've been happy with coLinux with Samba and VNC :) >>> >>>I don't like booting my machine often as I have many many windows open >>>and setup the way I like it. I guess I will have to bite the bullet and >>>see if I can fix the issue using real linux. >>> >>>BTW, this problem has happended at least 3 times now. It makes me feel >>>very uneasy with what coLinux is doing to my hard drive. Is there any >>>known problems using ext2 and/or ext3 partitions on a hard drive >>>(laptop) ??? >>>If so, I would really like to see them fixed so I don't lose any data >>>(or minimise the chances). >>>Would I be better of with VMWare ??? (I hope not). >>> >>>Thanks, >>>Brendan Simon. >>> >>> >>> > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt |
From: Jaroslaw K. <ja...@zd...> - 2005-01-19 09:49:26
|
I have similar behaviour. More precisely - the first time I run colinux I get exactly the same message, but my problems go away when I re-run it. This happens only when accessing physical partitions, not partition images. I can repeat this on 2 totally different machines. Any clue? Jarek ----- Original Message ----- From: "Sam Liddicott" <sa...@li...> To: <col...@li...> Sent: Tuesday, January 18, 2005 4:17 PM Subject: [coLinux-devel] Re: Fwd: [coLinux-users] ext3 boot errors > Sam Moffatt wrote: >> Something interesting from coLinux-users; appears that we have >> eventual corruption on native mode ext3 drives over time. It would >> appear that it might be a memory issue as he notes that it takes a >> while for it to become apparent. > > This appears to be the same thign I reported with reiserfs. > I could boot directly with real linux onto the partition but not from > coLinux > > I bet if the guy downloads a root image file and boots from that, but with > his old FS as a different COBD I bet he can mount it after he boots. > > To me it just seems to be a problem when the root fs is mounted when the > initrd switches out. > > Sam > >> >> >> ---------- Forwarded message ---------- >> From: Brendan Simon <Bre...@fa...> >> Date: Tue, 18 Jan 2005 00:15:11 +1100 >> Subject: Re: [coLinux-users] ext3 boot errors >> To: Sam Moffatt <pa...@gm...> >> Cc: col...@li... >> >> >> YIKES!!!! >> I just tried to launch coLinux again and got the following (BTW, I >> haven't rebooted my computer yet). >> >> VFS: Cannot open root device "cobd/0" or unknown-brock(0,0) >> Please append a correct "root=" boot option >> Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) >> colinux: kernel panic suggests that either you forget to supply a >> root= kernel boot parameter or the file / device mapped to the root >> file system is not found or inaccesible. Plesae Check your >> coLinux configuration >> >> I know my parameters are OK because I've launched coLinux many times in >> the past. This has just happened recently and all I can think of is an >> ext3 corruption. >> >> I will reboot my computer tomorrow and try again. I will then reboot >> into real linux and see if I can fix the ext3 partition. This is a >> serious problem and I hope we can get it fixed. Hopefully some of my >> reports woill be useful to track down the problem. >> >> Brendan Simon. >> >> Sam Moffatt wrote: >> >> >>>Since it happens after a while, I would be thinking it would be a >>>memory allocation thing, which would explain why coLinux doesn't want >>>to start up again. after colinux fails to reboot, do you restart your >>>computer or do you just leave it? >>> >>>also, if you could grab the error message colinux prints when it >>>doesn't reboot, that would be handy >>> >>> >>>On Mon, 17 Jan 2005 15:34:55 +1100, Brendan Simon >>><Bre...@fa...> wrote: >>> >>> >>> >>>>No I haven't booted into linux proper. I haven't done this for quite a >>>>while since I've been happy with coLinux with Samba and VNC :) >>>> >>>>I don't like booting my machine often as I have many many windows open >>>>and setup the way I like it. I guess I will have to bite the bullet and >>>>see if I can fix the issue using real linux. >>>> >>>>BTW, this problem has happended at least 3 times now. It makes me feel >>>>very uneasy with what coLinux is doing to my hard drive. Is there any >>>>known problems using ext2 and/or ext3 partitions on a hard drive >>>>(laptop) ??? >>>>If so, I would really like to see them fixed so I don't lose any data >>>>(or minimise the chances). >>>>Would I be better of with VMWare ??? (I hope not). >>>> >>>>Thanks, >>>>Brendan Simon. >>>> >>>> >>>> >> >> >> >> ------------------------------------------------------- >> The SF.Net email is sponsored by: Beat the post-holiday blues >> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Sam L. <sa...@li...> - 2005-01-19 10:03:38
|
Exactly the same here! It fails to run as a service on bootup. I run it by hand as a service and it fails The next time I run it it succeeds I thought it was dodgy hardware but I begin to doubt that now cos windows seems stable Sam Jaroslaw Kowalski wrote: > I have similar behaviour. More precisely - the first time I run > colinux I get exactly the same message, but my problems go away when I > re-run it. This happens only when accessing physical partitions, not > partition images. I can repeat this on 2 totally different machines. > Any clue? > > Jarek > ----- Original Message ----- From: "Sam Liddicott" <sa...@li...> > To: <col...@li...> > Sent: Tuesday, January 18, 2005 4:17 PM > Subject: [coLinux-devel] Re: Fwd: [coLinux-users] ext3 boot errors > > >> Sam Moffatt wrote: >> >>> Something interesting from coLinux-users; appears that we have >>> eventual corruption on native mode ext3 drives over time. It would >>> appear that it might be a memory issue as he notes that it takes a >>> while for it to become apparent. >> >> >> This appears to be the same thign I reported with reiserfs. >> I could boot directly with real linux onto the partition but not from >> coLinux >> >> I bet if the guy downloads a root image file and boots from that, but >> with his old FS as a different COBD I bet he can mount it after he >> boots. >> >> To me it just seems to be a problem when the root fs is mounted when >> the initrd switches out. >> >> Sam >> >>> >>> >>> ---------- Forwarded message ---------- >>> From: Brendan Simon <Bre...@fa...> >>> Date: Tue, 18 Jan 2005 00:15:11 +1100 >>> Subject: Re: [coLinux-users] ext3 boot errors >>> To: Sam Moffatt <pa...@gm...> >>> Cc: col...@li... >>> >>> >>> YIKES!!!! >>> I just tried to launch coLinux again and got the following (BTW, I >>> haven't rebooted my computer yet). >>> >>> VFS: Cannot open root device "cobd/0" or unknown-brock(0,0) >>> Please append a correct "root=" boot option >>> Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) >>> colinux: kernel panic suggests that either you forget to supply a >>> root= kernel boot parameter or the file / device mapped to the root >>> file system is not found or inaccesible. Plesae Check your >>> coLinux configuration >>> >>> I know my parameters are OK because I've launched coLinux many times in >>> the past. This has just happened recently and all I can think of is an >>> ext3 corruption. >>> >>> I will reboot my computer tomorrow and try again. I will then reboot >>> into real linux and see if I can fix the ext3 partition. This is a >>> serious problem and I hope we can get it fixed. Hopefully some of my >>> reports woill be useful to track down the problem. >>> >>> Brendan Simon. >>> >>> Sam Moffatt wrote: >>> >>> >>>> Since it happens after a while, I would be thinking it would be a >>>> memory allocation thing, which would explain why coLinux doesn't want >>>> to start up again. after colinux fails to reboot, do you restart your >>>> computer or do you just leave it? >>>> >>>> also, if you could grab the error message colinux prints when it >>>> doesn't reboot, that would be handy >>>> >>>> >>>> On Mon, 17 Jan 2005 15:34:55 +1100, Brendan Simon >>>> <Bre...@fa...> wrote: >>>> >>>> >>>> >>>>> No I haven't booted into linux proper. I haven't done this for >>>>> quite a >>>>> while since I've been happy with coLinux with Samba and VNC :) >>>>> >>>>> I don't like booting my machine often as I have many many windows >>>>> open >>>>> and setup the way I like it. I guess I will have to bite the >>>>> bullet and >>>>> see if I can fix the issue using real linux. >>>>> >>>>> BTW, this problem has happended at least 3 times now. It makes me >>>>> feel >>>>> very uneasy with what coLinux is doing to my hard drive. Is there >>>>> any >>>>> known problems using ext2 and/or ext3 partitions on a hard drive >>>>> (laptop) ??? >>>>> If so, I would really like to see them fixed so I don't lose any data >>>>> (or minimise the chances). >>>>> Would I be better of with VMWare ??? (I hope not). >>>>> >>>>> Thanks, >>>>> Brendan Simon. >>>>> >>>>> >>>>> >>> >>> >>> >>> ------------------------------------------------------- >>> The SF.Net email is sponsored by: Beat the post-holiday blues >>> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >>> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >> >> >> >> >> ------------------------------------------------------- >> The SF.Net email is sponsored by: Beat the post-holiday blues >> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >> _______________________________________________ >> coLinux-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > |