On Tuesday 10 February 2004 03:11 am, Chris wrote:
> On Tuesday 10 February 2004 02:34 am, LoneStar wrote:
> > Chris wrote:
> > >I emerged kernel 2.6.2 dev-gentoo last night and proceeded to get it up
> > > and running this evening. When I tried to boot it I ended up with the
> > > following problems.
> > >
> > >Step 4: Determining root device
> > >Root block device unspecified or not detected.
> > >Please specify a device to boot, or "shell" for a shell.
> > >
> > >:   (i input /dev/hdb3 and it continued)
> > >
> > >then it did the next
> > >
> > >Remounting root filesystem read-only (if necesarry)...   [!!]
> > >Filesystem is NOT cleanly unmounted.
> > >Partition /dev/hdb3 is mounted with write permissions, cannot check it
> > >*Filesystem couldn't be fixed :(              [!!]
> > >Give root password for maintenance
> > >
> > >What could I have done wrong and how do I fix it?
> >
> > Boot to a working kernel or the live CD and comment out the initrd line.
> > I've had this problem with every kernel I've built with the genkernel
> > betas and this is how I work around it.
> >
> > >the snip from my lilo.conf in case it helps.
> > >
> > >#
> > >image = /boot/kernel-2.6.2-gentoo
> > >        root = /dev/hdb3
> > >        #root = /devices/discs/disc0/part3
> > >        label = Gentoo3
> > >   initrd=/boot/initrd-2.6.2-gentoo
> > >   append="root=/dev/ram0 init=/linuxrc"
> > >        read-only # read-only for checking
> > >#
> > >
> > >thanks in advance for any help
>
> ok i did as you suggested then it gave me the following error...
>
> UDF-fs: No partition found (1)
> XFS-bad magic number
> XFS-SB validate failed
> kernel panic: VFS: Unable to mount root fs on ram0
>
> so I rebooted with my old kernel and changed ram0 to hdb3 in lilo.conf and
> tried again this time everything went fine to the following point
>
> Remounting root filesystem read-only (if necessary)...    [!!]
>
> Filesystem is cleanly unmounted
>
> Remounting root filestem read/write...
> Root filesystem could not be mounted read/write :(   [!!]

what setting in the kernel could cause the above problem if it was not turned 
on?
-- 

Chris P. Carter
<--------------------------------------->
 The smallest and even the dumbest of questions can lead to enlightenment.
 
 True wisdom is knowing when to listen, when to speak, when act and when to 
but out.
<--------------------------------------->
Gentoo Linux - KDE 3.2 (and proud of it)


--
[EMAIL PROTECTED] mailing list

Reply via email to