LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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 10-03-2007, 12:14 PM   #1
Hagoromo
LQ Newbie
 
Registered: Jul 2006
Posts: 8

Rep: Reputation: 0
[solved] Boot hangs after 'proc on /proc type proc (rw)'


Hi,

after installing an external usb disk, the server (Slack 10.0 kernel 2.6)
hangs after

INIT: version 2.84 booting
proc on /proc type proc (rw)


I have boot with the install cd, mounting the partition and changed
the entry in fstab, but the system don't boot

Any idea?

Thanks in advance

Last edited by Hagoromo; 10-05-2007 at 05:03 PM.
 
Old 10-03-2007, 03:26 PM   #2
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Rep: Reputation: 46
Can you post the full contents of your /etc/fstab?
 
Old 10-03-2007, 03:48 PM   #3
Hagoromo
LQ Newbie
 
Registered: Jul 2006
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by uselpa View Post
Can you post the full contents of your /etc/fstab?
fstab:

/dev/sda7 swap swap defaults 0 0
/dev/sda1 / ext3 defaults 1 1
/dev/sda5 /usr ext3 defaults 1 2
/dev/sda6 /var ext3 defaults 1 2
/dev/sda8 /tmp ext3 defaults 1 2
/dev/sda9 /home ext3 defaults 1 2
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0



in my laptop, after the line "proc on /proc type proc (rw)" the
boot process continues with "sysfs on /sys type sysfs (rw)" but
I cannot see this line in the pc.

Thanks again
 
Old 10-03-2007, 03:52 PM   #4
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Rep: Reputation: 46
In the messages from the kernel that you get, could it be that the external harddisk is assigned sda, instead of the internal harddisk? Or are you trying to boot from the external hd?
 
Old 10-03-2007, 03:58 PM   #5
Hagoromo
LQ Newbie
 
Registered: Jul 2006
Posts: 8

Original Poster
Rep: Reputation: 0
No, I have disconnected the external HD. These messages are
from the internal U160 SCSI harddisk (sda)
 
Old 10-03-2007, 10:40 PM   #6
ghostdancer
Member
 
Registered: Apr 2002
Distribution: Slackware
Posts: 266

Rep: Reputation: 30
This is rather weird. Did you modify anything to Slack10? This kernel (2.6) is it a recently built kernel or has been running for quite sometime? I suggest try reinstall the default kernel from Slack10, maybe this can give you back the control of the system.
 
Old 10-04-2007, 01:02 AM   #7
Hagoromo
LQ Newbie
 
Registered: Jul 2006
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ghostdancer View Post
This is rather weird. Did you modify anything to Slack10? This kernel (2.6) is it a recently built kernel or has been running for quite sometime? I suggest try reinstall the default kernel from Slack10, maybe this can give you back the control of the system.
This is a compiled kernel, but 4 years ago!

How I can reinstall the default kernel?

Thanks again
 
Old 10-04-2007, 04:34 AM   #8
ghostdancer
Member
 
Registered: Apr 2002
Distribution: Slackware
Posts: 266

Rep: Reputation: 30
Quote:
Originally Posted by Hagoromo View Post
This is a compiled kernel, but 4 years ago!
Oh? Was there any reboot since then?

Quote:
Originally Posted by Hagoromo View Post
How I can reinstall the default kernel?
Boot up from your installer CD, manually mount your filesystem at /mnt and your CD disk at /cdrom. Copy the kernel-xxx.tgz and kernel-module-xxx.tgz from your CD disk slackware/a/ (IRC) to /mnt. From here, do cd /mnt, chroot . installpkg *.tgz, edit the /etc/lilo.conf to use the default kernel and run lilo. I did this many times to recover my system when I forgot to keep an old copy of kernel, and the new kernel was not correct built, so it should work.

Last edited by ghostdancer; 10-04-2007 at 04:35 AM.
 
Old 10-04-2007, 06:09 AM   #9
Hagoromo
LQ Newbie
 
Registered: Jul 2006
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ghostdancer View Post
Oh? Was there any reboot since then?
Yes, but only fews reboots ;-)

When I make the 'chroot . installpkg *.tgz',
the command fails with:

/sbin/installpkg: line 1: basename: command not found
/sbin/installpkg: line 1: dirname: command not found
/sbin/installpkg: line 1: basename: command not found
/sbin/installpkg: line 1: dirname: command not found
Cannot install kernel ...

Any idea?

Thank you again
 
Old 10-04-2007, 06:24 AM   #10
ghostdancer
Member
 
Registered: Apr 2002
Distribution: Slackware
Posts: 266

Rep: Reputation: 30
Those commands can never be missing! I believe you may had accidentally deleted some files (or directories?) from your system. Which can be very bad. Try copy the coreutils package from your Slack10 installer and manually install them by uncompressing it: "tar zxvf coreutils-xxx.tgz" at /mnt, after that, try run the installpkg for your kernel again.
 
Old 10-04-2007, 07:38 AM   #11
ghostdancer
Member
 
Registered: Apr 2002
Distribution: Slackware
Posts: 266

Rep: Reputation: 30
Quote:
Originally Posted by Hagoromo View Post
Yes, but only fews reboots ;-)

When I make the 'chroot . installpkg *.tgz',
the command fails with:

/sbin/installpkg: line 1: basename: command not found
/sbin/installpkg: line 1: dirname: command not found
/sbin/installpkg: line 1: basename: command not found
/sbin/installpkg: line 1: dirname: command not found
Cannot install kernel ...

Any idea?

Thank you again
Sorry, my mistake. Do:

Code:
$> cd /mnt
$> chroot .
$> installpkg *.tgz
Run those command one at a time after you had copied the kernel packages to /mnt.
 
Old 10-04-2007, 02:32 PM   #12
Hagoromo
LQ Newbie
 
Registered: Jul 2006
Posts: 8

Original Poster
Rep: Reputation: 0
sorry, but same results :-(
 
Old 10-05-2007, 05:42 AM   #13
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,746

Rep: Reputation: 458Reputation: 458Reputation: 458Reputation: 458Reputation: 458
Try using this instead of chrooting:
ROOT=mnt/ installpkg *.tgz
 
Old 10-05-2007, 05:03 PM   #14
Hagoromo
LQ Newbie
 
Registered: Jul 2006
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by gnashley View Post
Try using this instead of chrooting:
ROOT=mnt/ installpkg *.tgz
That's works fine! I have recompiled the kernel and now
is all ok.

Thank you, gnashley & ghostdancer!!!
 
  


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
kernel building - proc type StargateSteve Linux - Software 2 12-07-2006 04:22 PM
problem on /proc/self/exe and /proc/num/exe snowing Programming 6 08-31-2006 01:17 AM
hidden directories under proc... what are they for? : (/proc/.23142) syssyphus Linux - General 1 04-10-2006 03:23 PM
Correlation between /proc/devices and /proc/modules ColinLadyka Linux - General 1 02-13-2006 05:25 PM
What /proc proc file do I need? GoboFraggle Programming 1 02-04-2003 11:52 PM


All times are GMT -5. The time now is 10:24 AM.

Main Menu
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