Gentoo Archives: gentoo-user

From: Dale <dalek1967@×××××××××.net>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Problem after 'fsck' on mounted filesystem
Date: Fri, 29 Jun 2007 14:51:21
Message-Id: 46851ADA.7030402@bellsouth.net
In Reply to: Re: [gentoo-user] Problem after 'fsck' on mounted filesystem by Xihong Yin
1 Xihong Yin wrote:
2 > Hi,
3 >
4 > I tried fsck.ext3 on the unmount partitions. It is not fixing. I still get the
5 > asking for input runlevel. No matter what runlevel you input, it always
6 > response with "no more process left on this runlevel".
7 >
8 > Xihong
9 > On Thu, 28 Jun 2007, Hans-Werner Hilse wrote:
10 >
11 >
12 >> Hi,
13 >>
14 >> On Thu, 28 Jun 2007 13:45:05 -0500 Randy Barlow
15 >> <randy@×××××××××××××××××.com> wrote:
16 >>
17 >>
18 >>> Xihong Yin wrote:
19 >>>
20 >>>> I had run "fsck" on the mounted filesystem. I think this is the
21 >>>> problem.
22 >>>>
23 >>> What were the results?
24 >>>
25 >> Irrelevant (since it was mounted) -- except if it was mounted read
26 >> only. If the OP really ran an fsck on a writable filesystem, all kinds
27 >> of errors might have occured.
28 >>
29 >> To the OP:
30 >> - was the partition mounted writable?
31 >> - what are you actually entering at the prompt (i.e. what runlevel)?
32 >> - did you try starting from a live CD and fsck'ing the -- unmounted --
33 >> partitions?
34 >>
35 >> -hwh
36 >> --
37 >> gentoo-user@g.o mailing list
38 >>
39 >>
40 >>
41 >
42 > ----------------------------------------------------------------------
43 > Find out how you can get spam free email.
44 > http://www.bluebottle.com
45 >
46 >
47
48 This may not help but you may want to check your inittab file and make
49 sure it is OK. It should look like this:
50
51 > # Default runlevel.
52 > id:3:initdefault:
53 >
54 > # System initialization, mount local filesystems, etc.
55 > si::sysinit:/sbin/rc sysinit
56 >
57 > # Further system initialization, brings up the boot runlevel.
58 > rc::bootwait:/sbin/rc boot
59 >
60 > l0:0:wait:/sbin/rc shutdown
61 > l1:S1:wait:/sbin/rc single
62 > l2:2:wait:/sbin/rc nonetwork
63 > l3:3:wait:/sbin/rc default
64 > l4:4:wait:/sbin/rc default
65 > l5:5:wait:/sbin/rc default
66 > l6:6:wait:/sbin/rc reboot
67 > #z6:6:respawn:/sbin/sulogin
68 >
69 > # TERMINALS
70 > c1:12345:respawn:/sbin/agetty 38400 tty1 linux
71 > c2:2345:respawn:/sbin/agetty 38400 tty2 linux
72 > c3:2345:respawn:/sbin/agetty 38400 tty3 linux
73 > c4:2345:respawn:/sbin/agetty 38400 tty4 linux
74 > c5:2345:respawn:/sbin/agetty 38400 tty5 linux
75 > c6:2345:respawn:/sbin/agetty 38400 tty6 linux
76 >
77 > # SERIAL CONSOLES
78 > #s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
79 > #s1:12345:respawn:/sbin/agetty 9600 ttyS1 vt100
80 >
81 > # What to do at the "Three Finger Salute".
82 > ca:12345:ctrlaltdel:/sbin/shutdown -r now
83 >
84 > # Used by /etc/init.d/xdm to control DM startup.
85 > # Read the comments in /etc/init.d/xdm for more
86 > # info. Do NOT remove, as this will start nothing
87 > # extra at boot if /etc/init.d/xdm is not added
88 > # to the "default" runlevel.
89 > x:a:once:/etc/X11/startDM.sh
90
91 I ran into this problem once and my inittab file was empty.
92
93 Hope that helps, may not but maybe it will.
94
95 Dale
96
97 :-) :-)