l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
November 4: Social gathering
Next Installfest:
TBD
Latest News:
Oct. 24: LUGOD election season has begun!
Page last updated:
2006 Aug 30 18:49

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] linux boot failed
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] linux boot failed



On Thursday 24 August 2006 00:15, Peter Jay Salzman wrote:
> On Wed 23 Aug 06,  8:58 PM, Hai Yi <yihai2004@gmail.com> said:
> > Hello,
> >
> > My debian Linux had been running fine until one day when I
> > restarted the computer, it failed to boot. The error message is as
> > follows:
> >
> > ....
> > INIT: version 2.86 booting
> > INIT: No inittab file found
> >
> > Enter runlevel:
> >
> > I didnt know what I should enter and stuck at this stage.
> >
> > Can anyone help so I dont re-install the whole thing? :-)

Unless you screwed up deleting stuff somewhere on your disk, I'd guess 
that the disk needs to be fscked, not that I expect that will actually 
fix the problem, because a missing inittab will appear in /lost+found 
with the inode number as its name, rather than reappearing 
as /etc/inittab.

Mount the disk after booting with a boot disk, see whether the disk 
needs to be fscked, and see whether /etc/inittab is there, and also see 
whether other important stuff (for 
example /etc/passwd,/etc/shadow,etc...) is missing. If there isn't lots 
of important stuff missing, let us know what distribution you're 
running. Someone here may be able to provide the 
appropriate /etc/inittab.

> Hello, Hai.
>
> Try entering "1".   What happens?

Is simply typing "1" do anything? I've never seen this situation before, 
so I didn't know that you could change runlevel by pressing a key. 
Runlevel 1 isn't "required" to be single user mode. That's runlevel "S" 
(or "s") which may have some kind of hardcoded thing to do the 
appropriate single user thing.

A good solution to get into your system without using a boot disk would 
be to reboot and give the kernel parameter init=/bin/busybox (or 
failing that init=/bin/bash).

> When the boot messages scroll, do you see any messages saying that /
> is being mounted?

If it couldn't mount /, you'd see a kernel panic.

--Ken

-- 
Ken Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu/~kbloom1/

Attachment: pgp00003.pgp
Description: PGP signature

_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.