[gentoo-user] Problem after 'fsck' on mounted filesystem

[gentoo-user] Problem after 'fsck' on mounted filesystem

[Xihong Yin]

My Gentoo can not initialize. It first asks for runlevel. After type in a  runlevel, it says "no more processes left on this level" and then hangs. I had run "fsck" on the mounted filesystem. I think this is the problem. So how do I fix it? Should I reinstall the system?

thanks,
Xihong

----------------------------------------------------------------------
Get a free email account with anti spam protection.
http://www.bluebottle.com

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem after 'fsck' on mounted filesystem

[Randy Barlow]

Xihong Yin wrote:
> I had run "fsck" on the mounted filesystem. I think this is the 
> problem.

What were the results?

-- 
Randy Barlow
http://electronsweatshop.com

But you are a chosen race, a royal priesthood, a holy nation, a people 
for his own possession, that you may proclaim the excellencies of him 
who called you out of darkness into his marvelous light. Once you were 
not a people, but now you are God's people; once you had not received 
mercy, but now you have received mercy. ~1 Peter 2:9-10

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem after 'fsck' on mounted filesystem

[Hans-Werner Hilse]

Hi,

On Thu, 28 Jun 2007 13:45:05 -0500 Randy Barlow
<randy@electronsweatshop.com> wrote:

> Xihong Yin wrote:
> > I had run "fsck" on the mounted filesystem. I think this is the 
> > problem.
> 
> What were the results?

Irrelevant (since it was mounted) -- except if it was mounted read
only. If the OP really ran an fsck on a writable filesystem, all kinds
of errors might have occured.

To the OP:
- was the partition mounted writable?
- what are you actually entering at the prompt (i.e. what runlevel)?
- did you try starting from a live CD and fsck'ing the -- unmounted --
  partitions?

-hwh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem after 'fsck' on mounted filesystem

[Xihong Yin]

Hi,

I tried fsck.ext3 on the unmount partitions. It is not fixing. I still get the
asking for input runlevel. No matter what runlevel you input, it always
response with "no more process left on this runlevel".

Xihong
On Thu, 28 Jun 2007, Hans-Werner Hilse wrote:

> Hi,
>
> On Thu, 28 Jun 2007 13:45:05 -0500 Randy Barlow
> <randy@electronsweatshop.com> wrote:
>
> > Xihong Yin wrote:
> > > I had run "fsck" on the mounted filesystem. I think this is the
> > > problem.
> >
> > What were the results?
>
> Irrelevant (since it was mounted) -- except if it was mounted read
> only. If the OP really ran an fsck on a writable filesystem, all kinds
> of errors might have occured.
>
> To the OP:
> - was the partition mounted writable?
> - what are you actually entering at the prompt (i.e. what runlevel)?
> - did you try starting from a live CD and fsck'ing the -- unmounted --
>   partitions?
>
> -hwh
> --
> gentoo-user@gentoo.org mailing list
>
>

----------------------------------------------------------------------
Find out how you can get spam free email.
http://www.bluebottle.com

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem after 'fsck' on mounted filesystem

[Hans-Werner Hilse]

Hi,

On Fri, 29 Jun 2007 10:27:55 -0400 (EDT) Xihong Yin
<xyin@bluebottle.com> wrote:

> I tried fsck.ext3 on the unmount partitions. It is not fixing. I
> still get the asking for input runlevel. No matter what runlevel you
> input, it always response with "no more process left on this
> runlevel".

_What_ are you entering? "boot"? "default"? Or old style rc levels
(which portage does _not_ use)? Maybe you could also send your
current /etc/inittab...

-hwh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem after 'fsck' on mounted filesystem

[Xihong Yin]

Hi hwh,

I've entered number 0 - 6, none of them works. Should I use 'boot'? or
'default' instead of numbers?

I could not find the /etc directory now. Maybe I lost it after 'fsck'.

Thanks,
Xihong


On Fri, 29 Jun 2007, Hans-Werner Hilse wrote:

> Hi,
>
> On Fri, 29 Jun 2007 10:27:55 -0400 (EDT) Xihong Yin
> <xyin@bluebottle.com> wrote:
>
> > I tried fsck.ext3 on the unmount partitions. It is not fixing. I
> > still get the asking for input runlevel. No matter what runlevel you
> > input, it always response with "no more process left on this
> > runlevel".
>
> _What_ are you entering? "boot"? "default"? Or old style rc levels
> (which portage does _not_ use)? Maybe you could also send your
> current /etc/inittab...
>
> -hwh
> --
> gentoo-user@gentoo.org mailing list
>
>

----------------------------------------------------------------------
Free pop3 email with a spam filter.
http://www.bluebottle.com

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem after 'fsck' on mounted filesystem

[Hemmann, Volker Armin]

On Freitag, 29. Juni 2007, Xihong Yin wrote:
> Hi hwh,
>
> I've entered number 0 - 6, none of them works. Should I use 'boot'? or
> 'default' instead of numbers?

yes. but you should use something like 'single' to repair the system.
>
> I could not find the /etc directory now. Maybe I lost it after 'fsck'.

In that case you should find it in 'lost+found'.

If you are missing stuff - search in /var/db/pkg/  for packages which 
installed something in /etc.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem after 'fsck' on mounted filesystem

[Dale]

[-- Attachment #1: Type: text/plain, Size: 2694 bytes --]

Xihong Yin wrote:
> Hi,
>
> I tried fsck.ext3 on the unmount partitions. It is not fixing. I still get the
> asking for input runlevel. No matter what runlevel you input, it always
> response with "no more process left on this runlevel".
>
> Xihong
> On Thu, 28 Jun 2007, Hans-Werner Hilse wrote:
>
>   
>> Hi,
>>
>> On Thu, 28 Jun 2007 13:45:05 -0500 Randy Barlow
>> <randy@electronsweatshop.com> wrote:
>>
>>     
>>> Xihong Yin wrote:
>>>       
>>>> I had run "fsck" on the mounted filesystem. I think this is the
>>>> problem.
>>>>         
>>> What were the results?
>>>       
>> Irrelevant (since it was mounted) -- except if it was mounted read
>> only. If the OP really ran an fsck on a writable filesystem, all kinds
>> of errors might have occured.
>>
>> To the OP:
>> - was the partition mounted writable?
>> - what are you actually entering at the prompt (i.e. what runlevel)?
>> - did you try starting from a live CD and fsck'ing the -- unmounted --
>>   partitions?
>>
>> -hwh
>> --
>> gentoo-user@gentoo.org mailing list
>>
>>
>>     
>
> ----------------------------------------------------------------------
> Find out how you can get spam free email.
> http://www.bluebottle.com
>
>   

This may not help but you may want to check your inittab file and make
sure it is OK.  It should look like this:

> # Default runlevel.
> id:3:initdefault:
>
> # System initialization, mount local filesystems, etc.
> si::sysinit:/sbin/rc sysinit
>
> # Further system initialization, brings up the boot runlevel.
> rc::bootwait:/sbin/rc boot
>
> l0:0:wait:/sbin/rc shutdown
> l1:S1:wait:/sbin/rc single
> l2:2:wait:/sbin/rc nonetwork
> l3:3:wait:/sbin/rc default
> l4:4:wait:/sbin/rc default
> l5:5:wait:/sbin/rc default
> l6:6:wait:/sbin/rc reboot
> #z6:6:respawn:/sbin/sulogin
>
> # TERMINALS
> c1:12345:respawn:/sbin/agetty 38400 tty1 linux
> c2:2345:respawn:/sbin/agetty 38400 tty2 linux
> c3:2345:respawn:/sbin/agetty 38400 tty3 linux
> c4:2345:respawn:/sbin/agetty 38400 tty4 linux
> c5:2345:respawn:/sbin/agetty 38400 tty5 linux
> c6:2345:respawn:/sbin/agetty 38400 tty6 linux
>
> # SERIAL CONSOLES
> #s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
> #s1:12345:respawn:/sbin/agetty 9600 ttyS1 vt100
>
> # What to do at the "Three Finger Salute".
> ca:12345:ctrlaltdel:/sbin/shutdown -r now
>
> # Used by /etc/init.d/xdm to control DM startup.
> # Read the comments in /etc/init.d/xdm for more
> # info. Do NOT remove, as this will start nothing
> # extra at boot if /etc/init.d/xdm is not added
> # to the "default" runlevel.
> x:a:once:/etc/X11/startDM.sh

I ran into this problem once and my inittab file was empty. 

Hope that helps, may not but maybe it will.

Dale

:-)  :-)


[-- Attachment #2: Type: text/html, Size: 3663 bytes --]