Re: [ilugd] kernel panic

2005-11-06 Thread Shiv


--- Mithun Bhattacharya [EMAIL PROTECTED] wrote:

 
 --- Sharad Birmiwal [EMAIL PROTECTED]
 wrote:
 
  if you are trying to boot the machine without any
 ram and getting
  that
  error, please correct me if i am wrong, it could
 be because 2.4
  kernels try
  to load initrd onto a ram-drive first.
 
  On 11/2/05, Manish Popli [EMAIL PROTECTED]
 wrote:
  
   I m using 2.4.21-4.Elsmp kernel.it
 http://kernel.it
  http://kernel.it
   went down suddenly and
   when i reboot, it was not able to found the boot
 record..
   after that i plughed out a slot of 512mb ram
 from it and tryed to
  boot
   it..M/c got start but i was facing the error...
   *Kernel* *panic*: *no* *init* *found*. Try
 passing *init*= option
 
 Firstly a PC can not boot without RAM. Since the PC
 seems to have
 powered up and the boot loader also got loaded I am
 assuming there is
 some sort of damage to the hard disk. I would
 recommed a backup disk be
 created and then you should start looking at what
 you can retrieve from
 the damaged hard disk.
 
 The other reason the boot loader would be confused
 are:
 
 1. Extensive filesystem damage - you are better off
 with the backup
 disk in any case then
 2. Power went off before lilo could write to the
 boot sector - only
 valid if you were playing with lilo and only if lilo
 couldnt write
 before power went off.
 3. If you use grub then /boot/grub folder or
 /boot/grub/grub.conf or
 /boot/grub/menu.1st on Debian got corrupt.
 
 Do note if power wasnt the culprit then either the
 kernel was non
 standard or the motherboard is dying on you.
 
 
 
 Mithun
 
 
   
 __ 
 Start your day with Yahoo! - Make it your home page!
 
 http://www.yahoo.com/r/hs
 
 ___
 ilugd mailinglist -- ilugd@lists.linux-delhi.org
 http://frodo.hserus.net/mailman/listinfo/ilugd
 Archives at:
 http://news.gmane.org/gmane.user-groups.linux.delhi

http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
 
 
Hi,
If all you want to do is recover data from the hard
disk, boot off knoppix and mount the hard disk
partition and copy it elsewhere.


catch ya later (Ive gotta UnWire Life!!!)
  shiv



__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

___
ilugd mailinglist -- ilugd@lists.linux-delhi.org
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/ilugd@lists.linux-delhi.org/



Re: [ilugd] kernel panic

2005-11-02 Thread Sharad Birmiwal
if you are trying to boot the machine without any ram and getting that
error, please correct me if i am wrong, it could be because 2.4 kernels try
to load initrd onto a ram-drive first.
what does the exact error message say when you try to boot the system with
ram?
one thing you can do is get a live disc (or use the first disc of whichever
distro you are using), get a shell from that (they all provide different
ways of getting there. some need to be passed rescue on the boot loader
prompt of the cd etc) and try mounting your fs there. see if everything
seems to be intact.
you can try chrooting into the root (/) fs on the hdd and exploring. if you
use lilo, try running lilo from the chroot-ed environment.
did you swap hard-drives recently? did the computer reboot by itself/power
failure? could it be that you use ext2 filesystem?


sharad birmiwal


On 11/2/05, Manish Popli [EMAIL PROTECTED] wrote:

 I m using 2.4.21-4.Elsmp kernel.it http://kernel.it http://kernel.it
 went down suddenly and
 when i reboot, it was not able to found the boot record..
 after that i plughed out a slot of 512mb ram from it and tryed to boot
 it..M/c got start but i was facing the error...
 *Kernel* *panic*: *no* *init* *found*. Try passing *init*= option to
 *kernel
 *.
 any one solve my problem there is critical data in this HDD..
 --
 Manish Popli
 ___
 ilugd mailinglist -- ilugd@lists.linux-delhi.org
 http://frodo.hserus.net/mailman/listinfo/ilugd
 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi
 http://www.mail-archive.com/ilugd@lists.linux-delhi.org/


___
ilugd mailinglist -- ilugd@lists.linux-delhi.org
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/ilugd@lists.linux-delhi.org/



Re: [ilugd] kernel panic

2005-11-02 Thread Mithun Bhattacharya

--- Sharad Birmiwal [EMAIL PROTECTED] wrote:

 if you are trying to boot the machine without any ram and getting
 that
 error, please correct me if i am wrong, it could be because 2.4
 kernels try
 to load initrd onto a ram-drive first.

 On 11/2/05, Manish Popli [EMAIL PROTECTED] wrote:
 
  I m using 2.4.21-4.Elsmp kernel.it http://kernel.it
 http://kernel.it
  went down suddenly and
  when i reboot, it was not able to found the boot record..
  after that i plughed out a slot of 512mb ram from it and tryed to
 boot
  it..M/c got start but i was facing the error...
  *Kernel* *panic*: *no* *init* *found*. Try passing *init*= option

Firstly a PC can not boot without RAM. Since the PC seems to have
powered up and the boot loader also got loaded I am assuming there is
some sort of damage to the hard disk. I would recommed a backup disk be
created and then you should start looking at what you can retrieve from
the damaged hard disk.

The other reason the boot loader would be confused are:

1. Extensive filesystem damage - you are better off with the backup
disk in any case then
2. Power went off before lilo could write to the boot sector - only
valid if you were playing with lilo and only if lilo couldnt write
before power went off.
3. If you use grub then /boot/grub folder or /boot/grub/grub.conf or
/boot/grub/menu.1st on Debian got corrupt.

Do note if power wasnt the culprit then either the kernel was non
standard or the motherboard is dying on you.



Mithun



__ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs

___
ilugd mailinglist -- ilugd@lists.linux-delhi.org
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/ilugd@lists.linux-delhi.org/



Re: [ilugd] Kernel Panic

2004-02-21 Thread Avinesh Bangar
can't bootup even by using Bootable Floppies.
#tell me whats the problem?what should i do?
Some times it ask for root password  run fsck witout -a  -p switch.
#HOW should i run fsck to recover ext3 file system?

Sounds like garbage collection didn't get called by a particular
application.

Run, the following to determine which partitions are active: 'mount -l'
You will see a list such as:
/dev/hda5 on / type ext3 (rw) [/]
/dev/hda3 on / type ext3 (rw) [/home]
...
etc.

Now, you will need to run the following:
$ fsck.ext3 /dev/hda5
$ fsck.ext3 /dev/hda3

HTH.

Regards,
 Avinesh



___
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd


Re: [ilugd] Kernel Panic

2004-02-21 Thread Avinesh Bangar
 Run, the following to determine which partitions are active: 'mount -l'
 You will see a list such as:
 /dev/hda5 on / type ext3 (rw) [/]
 /dev/hda3 on / type ext3 (rw) [/home]

On a side note, it's a bad idea running fsck on a mounted filesystem (can
lead to further corruption), so ensure that the filesystem is unmounted
before continuing:
'umount /home'.  The root partition (/) will usually be mounted in read-only
(ro) mode during such recovery operations though.

Regards,
 Avinesh



___
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd


Re: [ilugd] Kernel Panic

2004-02-21 Thread Sudev Barar
On Sat, 2004-02-21 at 15:44, Navneet Choudhary wrote:
 Some times it ask for root password  run fsck witout -a  -p switch.
 #HOW should i run fsck to recover ext3 file system?
Next time it asks for this give root password and then fsck -y
Reboot after this finishes.
-- 
Sudev Barar

Learning Linux



___
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd