Once upon a time Reid Mumford wrote @ Wed, 12 Mar 2003 13:09:50 -0500 (EST)
> I have a problem that has brought my laptop down.
>
> I recently installed KDE 3.1 and everything seemed to be working pretty
> well. I was messing around with the file browser in kde and suddenly
> started to get some
On Wed, Mar 12, 2003 at 10:19:35PM +0100, Johannes Rohr wrote:
> Reid Mumford <[EMAIL PROTECTED]> writes:
>
> > On Wed, 12 Mar 2003, sean finney wrote:
> >
> > > On Wed, Mar 12, 2003 at 01:09:50PM -0500, Reid Mumford wrote:
> > > > EXT2-fs warning: checktime reached, running e2fsck is recommended
On Wed, 12 Mar 2003 13:09:50 -0500 (EST)
Reid Mumford <[EMAIL PROTECTED]> wrote:
> I have a problem that has brought my laptop down.
>
> Any ideas on how to save this system without having to reinstall?
Your filesystem was corrupted and you've lost some files (or pieces of files).
You may be a
On Wed, Mar 12, 2003 at 01:09:50PM -0500, Reid Mumford wrote:
> linux root=/dev/hda2
>
> this results in the following error messages on boot:
>
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> VFS: Mounted root (ext2 filesystem) readonl
Reid Mumford <[EMAIL PROTECTED]> writes:
> On Wed, 12 Mar 2003, sean finney wrote:
>
> > On Wed, Mar 12, 2003 at 01:09:50PM -0500, Reid Mumford wrote:
> > > EXT2-fs warning: checktime reached, running e2fsck is recommended
> > > VFS: Mounted root (ext2 filesystem).
> > > VFS: Mounted root (ext2 f
Am Mit, 2003-03-12 um 19.57 schrieb Reid Mumford:
> On Wed, 12 Mar 2003, sean finney wrote:
>
> > On Wed, Mar 12, 2003 at 01:09:50PM -0500, Reid Mumford wrote:
> > > EXT2-fs warning: checktime reached, running e2fsck is recommended
> > > VFS: Mounted root (ext2 filesystem).
> > > VFS: Mounted root
Warwick Brown wrote:
tbh it looks like you have lost some vital system binaries, your best bet is
to boot off the rescue disk, back up yer data files and reinstall, but make
sure u bad block check the disks when u reformat them, coz lappies do get
bounced around a fair bit, so disk damage shoul
On Wed, 12 Mar 2003, sean finney wrote:
> On Wed, Mar 12, 2003 at 01:09:50PM -0500, Reid Mumford wrote:
> > EXT2-fs warning: checktime reached, running e2fsck is recommended
> > VFS: Mounted root (ext2 filesystem).
> > VFS: Mounted root (ext2 filesystem) readonly.
> > change_root: old root has d
On Wed, Mar 12, 2003 at 01:09:50PM -0500, Reid Mumford wrote:
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> VFS: Mounted root (ext2 filesystem) readonly.
> change_root: old root has d_count=1
> Trying to unmount old root ... okay
> Free
tbh it looks like you have lost some vital system binaries, your best bet is
to boot off the rescue disk, back up yer data files and reinstall, but make
sure u bad block check the disks when u reformat them, coz lappies do get
bounced around a fair bit, so disk damage shouldnt be ruled out
rega
On Mon, Apr 22, 2002 at 11:54:18PM -0500, dman wrote:
> On Mon, Apr 22, 2002 at 11:29:25PM -0400, Jerome Acks Jr wrote:
> | On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
> | > Hi!
> | >
> | > Thank you for your answer. I have tried passing to the boot prompt
> | >
> | > linux
On Wed, Apr 24, 2002 at 01:59:00AM -0500, Gary Turner wrote:
...
| In re using links, would you also use full file name for the kernel
| image rather than an alias? And, is a magical transformation very
| likely? If so, what would do it?
Yes, I use the full file name for both kernel and initrd
#include
Alessandro Ghigi wrote on Mon Apr 22, 2002 um 03:08:40AM:
> partition on the hard disk: /sbin/init is there and is ok (I have
> replaced it with a copy from another system), and also inittab looks
> ok. But the original root partition still does not work and gives the
> same message.
On Tue, 23 Apr 2002 23:47:11 -0500, dman wrote:
>On Tue, Apr 23, 2002 at 03:22:56AM -0500, Gary Turner wrote:
>| On Tue, 23 Apr 2002 00:16:01 -0400, Andy Saxena wrote:
>| >On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
>| >> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote
On Tue, Apr 23, 2002 at 03:22:56AM -0500, Gary Turner wrote:
| On Tue, 23 Apr 2002 00:16:01 -0400, Andy Saxena wrote:
| >On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
| >> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
| >> | On Mon, 2002-04-22 at 15:08, Alessandro Ghig
On Tue, Apr 23, 2002 at 12:16:01AM -0400, Andy Saxena wrote:
| On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
| > On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
| > | On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
| >
| > | > Kernel panic: no init found. Try passi
On Tue, 23 Apr 2002 00:16:01 -0400, Andy Saxena wrote:
>On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
>> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
>> | On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
>>
snip
>> Something or other like that. After upgrading
On Mon, Apr 22, 2002 at 11:33:18PM -0400, Andy Saxena wrote:
| On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
| > Thank you for your answer. I have tried passing to the boot prompt
| >
| > linux root=/dev/hda9 init=/sbin/init,
| >
| > but the result is the same as before. Actu
On Mon, Apr 22, 2002 at 11:29:25PM -0400, Jerome Acks Jr wrote:
| On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
| > Hi!
| >
| > Thank you for your answer. I have tried passing to the boot prompt
| >
| > linux root=/dev/hda9 init=/sbin/init,
| >
| > but the result is the same
On Mon, Apr 22, 2002 at 08:08:41PM -0500, dman wrote:
> On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
> | On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
>
> | > Kernel panic: no init found. Try passing init= option to kernel.
>
> Hey, cool (sorta) -- someone else has t
On Tue, 2002-04-23 at 04:24, Alessandro Ghigi wrote:
> Hi!
>
> Thank you for your answer. I have tried passing to the boot prompt
>
> linux root=/dev/hda9 init=/sbin/init,
>
> but the result is the same as before. Actually /sbin is on the root
> partition.
>
> I guess the reason why my system h
On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
>
>
> Hi!
>
> Thank you for your answer. I have tried passing to the boot prompt
>
> linux root=/dev/hda9 init=/sbin/init,
>
> but the result is the same as before. Actually /sbin is on the root
> partition.
>
> I guess the rea
On Mon, Apr 22, 2002 at 04:24:54PM -0400, Alessandro Ghigi wrote:
>
>
> Hi!
>
> Thank you for your answer. I have tried passing to the boot prompt
>
> linux root=/dev/hda9 init=/sbin/init,
>
> but the result is the same as before. Actually /sbin is on the root
> partition.
>
> I guess the rea
On Mon, Apr 22, 2002 at 05:21:23PM +0800, Crispin Wellington wrote:
| On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
| > Kernel panic: no init found. Try passing init= option to kernel.
Hey, cool (sorta) -- someone else has this problem too. I've got a
kernel that does this too. I will lo
Hi!
Thank you for your answer. I have tried passing to the boot prompt
linux root=/dev/hda9 init=/sbin/init,
but the result is the same as before. Actually /sbin is on the root
partition.
I guess the reason why my system hanged, was that I tried suspending to
disk while my ethernet card was w
On Mon, 2002-04-22 at 15:08, Alessandro Ghigi wrote:
>
>
> Hi.
>
> My laptop hanged, and I shut it down. Afterwards it cannot boot.
> After loading linux, it stops saying roughly
>
>
> Partition check
> hda: hda1
> apm: Bios version ...
> VFS: Mounted root (ext2 filesyustem) readonly.
>
Rory O'Connor wrote:
welp, i'm not sure if linux will ever boot from my hard disk again! before
I was having a problem with LILO hanging at "LI", and i deemed it a problem
with my SCSI drive. I unplugged the SCSI drive, rebooted, and the MBR was
found and the boot process began...only to end i
replace the scsi disk, boot from the floppy, check dmesg to see what
hardware or anything else is or isn't there, and configure a new kernel
based on what you find.
Rory O'Connor wrote:
>
> welp, i'm not sure if linux will ever boot from my hard disk again! before
> I was having a problem wit
on Sat, Nov 17, 2001 at 01:46:15AM -0600, Rory O'Connor ([EMAIL PROTECTED])
wrote:
> welp, i'm not sure if linux will ever boot from my hard disk again!
> before I was having a problem with LILO hanging at "LI", and i deemed
> it a problem with my SCSI drive. I unplugged the SCSI drive,
> reboote
** On Apr 02, Bob Nielsen scribbled:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing init= option to kernel.
You compiled the kernel with wrong root partition, it happens sometimes. The
best bet is to use
On Sun, Apr 02, 2000 at 09:30:07PM -0400, Mike Werner wrote:
> On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> > I have had the same problem as Bob N. and ext2 is IN the kernel, not
> > a module and I have a Pentium III. Is there some bug either in kpkg
> > or latest kernel vers
On Sun, Apr 02, 2000 at 09:15:34PM -0500, eric k. wolven wrote:
> I have had the same problem as Bob N. and ext2 is IN the kernel, not
> a module and I have a Pentium III. Is there some bug either in kpkg
> or latest kernel version of 2.2.14?
For what it's worth, I'm running 2.2.14 on two of my m
-BEGIN PGP SIGNED MESSAGE-
Dear Debians:
I have had the same problem as Bob N. and ext2 is IN the kernel, not a module
and I have a Pentium III. Is there some bug either in kpkg or latest kernel
version of 2.2.14?
"Dpkg -i the kernel-image" doesn't run through its usual routine. It ju
One thing to check: Make sure that you have ext2 support compiled in the
kernel, and not as a module.
Paul
On 02-Apr-2000 Bob Nielsen wrote:
> I just compiled a new 2.2.14 kernel after doing a new potato install and got
> the message:
>
> Kernel panic: No init found. Try passing init= option t
Nope, it is an Intel CPU.
On Sat, Apr 01, 2000 at 09:58:58PM -0800, Bill Alexander wrote:
> > "Bob" == Bob Nielsen <[EMAIL PROTECTED]> writes:
>
> Bob> --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii
>
> Bob> I just compiled a new 2.2.14 kernel after doing a new potato
> "Bob" == Bob Nielsen <[EMAIL PROTECTED]> writes:
Bob> --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii
Bob> I just compiled a new 2.2.14 kernel after doing a new potato
Bob> install and got the message:
Bob> Kernel panic: No init found. Try passing init= optio
Jianming YOU wrote:
>
> Hi, Paul,
>
> Thank you very much.
>
> I followed your suggestion. Here is what I did and what I got:
>
> Boot from a floppy, with kernel 2.0.35
> login as root
>
> > mount /dev/hda2 /mnt
> > cd mnt
> > rm vmlinuz
> > ln -s boot/vmlinuz-2.0.34 vmlinuz
> > ls -l sbin/lil
Hi, Paul,
Thank you very much.
I followed your suggestion. Here is what I did and what I got:
Boot from a floppy, with kernel 2.0.35
login as root
> mount /dev/hda2 /mnt
> cd mnt
> rm vmlinuz
> ln -s boot/vmlinuz-2.0.34 vmlinuz
> ls -l sbin/lilo
-rwxr-xr-x 1 root root 50708 Feb 2 17:31
Jianming YOU wrote:
>
> Hi, Experts,
>
> I just upgraded my box from 2.0.34 to 2.2.1 and I got
> "kernel panic, no init found..." when I tried to boot with the new
> kernel. The problem have been reported by several people. However, I
> still don't know how to recover the system after reading tho
39 matches
Mail list logo
