LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 07-28-2006, 12:51 AM   #1
ryanoa
Member
 
Registered: Jan 2006
Location: Santa Cruz, CA
Distribution: Slack 10.2 and 11.0
Posts: 102

Rep: Reputation: 15
reboot from putty


Very strange problem,

I rebooted from putty on a windows machine over a local network with the "reboot" command. Now, upon going to the box I rebooted to see why it wouldn't accept another ssh session, it is in a perpetual (sp?) state of rebooting.

It gets to lilo, loads the kernel, then reboots over and over and over and over .........

????What the heck did I do????

I can boot the Slack cd and mount hda. I have no idea what to check for from there. I've been using Linux/Slack for about a year now and have been able to get myself out of most jambs but this one has me stumped.

Ideas?
 
Old 07-28-2006, 02:08 AM   #2
Daga
Member
 
Registered: Apr 2006
Location: A comfy chair...
Distribution: Slackware
Posts: 110

Rep: Reputation: 15
It sounds like something else is going on... maybe check /etc/inittab for the default runlevel? I'd also take a look at the files in /var/log. Oh, and you might look through the init scripts in /etc/rc.d also.

Sorry I can't tell you exactly what to look for, but I hope this helps.
 
Old 07-28-2006, 06:56 AM   #3
mdarby
Member
 
Registered: Nov 2004
Location: Columbus, Ohio
Distribution: Slackware-Current / Debian
Posts: 795

Rep: Reputation: 30
mis-read your post...
 
Old 07-28-2006, 09:36 AM   #4
archtoad6
Senior Member
 
Registered: Oct 2004
Location: Houston, TX (usa)
Distribution: MEPIS, Debian, Knoppix,
Posts: 4,727
Blog Entries: 15

Rep: Reputation: 231Reputation: 231Reputation: 231
2 suggestions:
  1. Power it down for a minute or 2, then restart.
  2. Look in lilo.conf for a lone "6" at the end of the kernel line or an "append=" line of the active/default stanza.

Explanation of #2

Both lilo & GRUB allow the passing of a an run level to init (see man init) from their menus (see man lilo.conf or http://www.gnu.org/software/grub/manual/grub.html). Usually we only see "1", "S", or "s" being passed, & that in the context of a failsafe or recovery mode -- all 3 indicate run level 1, single user mode.

Once I added 2 joke stanzas to a GRUB menu.lst: 1 w/ a "6", the other w/ a "0". I'm not sure which is funnier to foist on the unsuspecting.

In any case, the reboot looping you describe could be achieved this way.
 
Old 07-28-2006, 09:44 AM   #5
konsolebox
Senior Member
 
Registered: Oct 2005
Distribution: Gentoo, Slackware, LFS
Posts: 2,245
Blog Entries: 16

Rep: Reputation: 233Reputation: 233Reputation: 233
before you have had that error, did you try to recompile your kernel or modify your boot config (lilo or grub)?
 
Old 07-28-2006, 08:02 PM   #6
ryanoa
Member
 
Registered: Jan 2006
Location: Santa Cruz, CA
Distribution: Slack 10.2 and 11.0
Posts: 102

Original Poster
Rep: Reputation: 15
Thanks for all the replies,
I reinstalled lilo using the cd and it boots but I get:
Kernel Panic -not syncing: VFS: unable to mount root fs on unknown-block(3,2)

???

I've been using the 2.6.13 kernel from /testing all along without problems.
 
Old 07-28-2006, 08:03 PM   #7
ryanoa
Member
 
Registered: Jan 2006
Location: Santa Cruz, CA
Distribution: Slack 10.2 and 11.0
Posts: 102

Original Poster
Rep: Reputation: 15
kernel panic

Thanks for all the replies,
I reinstalled lilo using the cd and it boots but I get:
Kernel Panic -not syncing: VFS: unable to mount root fs on unknown-block(3,2)

???

I've been using the 2.6.13 kernel from /testing all along without problems.
 
Old 07-28-2006, 08:29 PM   #8
konsolebox
Senior Member
 
Registered: Oct 2005
Distribution: Gentoo, Slackware, LFS
Posts: 2,245
Blog Entries: 16

Rep: Reputation: 233Reputation: 233Reputation: 233
you're simply having problems with your modules. are you using a new kernel? and also are you using an initrd image? check for /boot/initrd* files.

Edit: maybe you missed including your initrd file in your lilo's config

Last edited by konsolebox; 07-28-2006 at 08:30 PM.
 
Old 07-29-2006, 12:22 PM   #9
ryanoa
Member
 
Registered: Jan 2006
Location: Santa Cruz, CA
Distribution: Slack 10.2 and 11.0
Posts: 102

Original Poster
Rep: Reputation: 15
I'm not using a new kernel or an initrd image. I have never had one and it worked just fine. I have another box with the 2.6.13 kernel and no initrd and it doesn't have any problems booting.
 
Old 07-29-2006, 12:55 PM   #10
ryanoa
Member
 
Registered: Jan 2006
Location: Santa Cruz, CA
Distribution: Slack 10.2 and 11.0
Posts: 102

Original Poster
Rep: Reputation: 15
OK,

I booted with slack cd #1 and at the boot prompt I used "test26.s root=/dev/hda2 noinitrd ro" as described in another recent post and it booted my system!!!!

Went to /boot and made an initrd using the readme file, changed lilo, ran lilo , rebooting.................

Yes! all is well.

Thanks for all the help

What I don't understand is why it worked before without an initrd and it needs one now. I have another box that is pretty much a mirror image of this one without an initrd and it works fine.
 
Old 07-29-2006, 01:09 PM   #11
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 66
Because you were using a filesystem type not included in the generic 2.6 kernel (more than likely, Reiserfs), while the other was prob using ext3 or ext2
 
Old 07-29-2006, 02:34 PM   #12
Mr_C
Member
 
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317

Rep: Reputation: 30
Quote:
Originally Posted by ryanoa
I rebooted from putty on a windows machine over a local network with the "reboot" command. Now, upon going to the box I rebooted to see why it wouldn't accept another ssh session
AS soon as you init 6, close putty immediately and it won't remember your ip and will allow the ssh when the system comes back up.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
No keyboard/mouse after reboot. Requires second reboot to work. rottie Linux - Hardware 6 01-16-2006 06:04 AM
Mandriva 10.1 fails to reboot and shows "No reboot fixup found for your hardware" ROY913 Mandriva 1 12-12-2005 03:10 AM
Re: Putty unixfreak Linux - Newbie 6 09-01-2004 12:42 PM
Need help with PUTTY unixfreak Linux - Software 2 08-30-2004 07:06 PM
Other than putty KaktusKnight Linux - General 4 05-07-2003 02:28 PM


All times are GMT -5. The time now is 04:15 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration