From: Brendan S. <Bre...@fa...> - 2005-01-19 03:43:09
|
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. Brendan Simon. Sam Moffatt wrote: >Is it trying to mount the drive as ext2 or ext3? > >Try running fsck under real linux and see what happens - but perhaps >your linux partition might be fried given the information that coLinux >is giving you. If this is the case, you'll need a recovery disk and >work from there. > > >On Tue, 18 Jan 2005 00:15:11 +1100, Brendan Simon ><Bre...@fa...> wrote: > > >>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. >>>> >>>> >>>> >>>> >>>> >> >> |