Unix Technical Forum

Slackware boot problem

This is a discussion on Slackware boot problem within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> I recently installed 10.1 on my second hard drive, with hdb1 being the / partition. All partitions were formatted ...


Go Back   Unix Technical Forum > Unix Operating Systems > Slackware Linux Support

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-20-2008, 08:53 AM
lgb
 
Posts: n/a
Default Slackware boot problem

I recently installed 10.1 on my second hard drive, with hdb1 being the /
partition. All partitions were formatted and I installed everything but
Emacs automatically.

I'm using a boot manager, so I specified that LILO be installed on hdb1.
The LILO installer said it had a problem, but I could use a boot disk to
boot.

When I tried to boot, I got a message about the superblock being
clobbered. It asked me to enter the root password to enter single user
mode, but then wouldn't take the one I'd specified.

Using the installation CD, I ran e2fsck with the "-b 8193" option as the
message suggested. It appeared to find and fix several problems, but
when I rebooted I got the same error message as before.

I checked a few HOWTOs and did a Google, but could find nothing that
matched the problem.

Anyone know a solution to this? I'm going to try again with the e3fsck
and then try doing a reinstall of only the A and AP sections to see if
that works. But if this is a common problem, I'd appreciate any help
that anyone here can give.

BTW, I installed LILO on that partition before, when I installed
Minislack and it worked fine. But I wanted some things not in the
Minislack distribution so I tried the full-blown one.

--
BNSF = Build Now, Seep Forever
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-20-2008, 08:53 AM
No_One
 
Posts: n/a
Default Re: Slackware boot problem

On 2005-05-29, lgb <lblanch@fastmail.fm> wrote:
> I recently installed 10.1 on my second hard drive, with hdb1 being the /
> partition. All partitions were formatted and I installed everything but
> Emacs automatically.
>



>
> BTW, I installed LILO on that partition before, when I installed
> Minislack and it worked fine. But I wanted some things not in the
> Minislack distribution so I tried the full-blown one.
>


In the great big FWIW department, I never had the problem and can't help
directly, however, IIRC within the last month someone asked the same
question in this group. If no one answers, you might do a search google for
a post in this news group.

ken
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-20-2008, 08:54 AM
marcusm
 
Posts: n/a
Default Re: Slackware boot problem

lgb wrote:
> I recently installed 10.1 on my second hard drive, with hdb1 being the /
> partition. All partitions were formatted and I installed everything but
> Emacs automatically.
>
> I'm using a boot manager, so I specified that LILO be installed on hdb1.
> The LILO installer said it had a problem, but I could use a boot disk to
> boot.
>
> When I tried to boot, I got a message about the superblock being
> clobbered. It asked me to enter the root password to enter single user
> mode, but then wouldn't take the one I'd specified.
>
> Using the installation CD, I ran e2fsck with the "-b 8193" option as the
> message suggested. It appeared to find and fix several problems, but
> when I rebooted I got the same error message as before.
>
> I checked a few HOWTOs and did a Google, but could find nothing that
> matched the problem.
>
> Anyone know a solution to this? I'm going to try again with the e3fsck
> and then try doing a reinstall of only the A and AP sections to see if
> that works. But if this is a common problem, I'd appreciate any help
> that anyone here can give.
>
> BTW, I installed LILO on that partition before, when I installed
> Minislack and it worked fine. But I wanted some things not in the
> Minislack distribution so I tried the full-blown one.
>


I hate it when that happens but, it doesn't happen that often.
Especially if one follows the straight and narrow

Off the top..., I'd say that the partition table layout needs some work
and/or lilo was miss placed. But in order to get to the bottom of it a
little clarity is needed. Like...

What partitions, how are they formatted and what size are they?

How was liloconfig ran, simple/AUTOMATIC(no say so in the matter) or
expert(full control and not that hard at all)

Was lilo installed in the superblock of / in hdb1(which is what is
needed) or did it make its way to the MBR OF hdb1?(Not sure if this is
possible, but if it is this might be the problem right here.)

Any way, you get the idea? I would just rip out these partitions and
start over(practice makes perfect, eventually.) If you want fast and
easy(maybe the way to go for now,) then one partition for / (6GB or 7GB
will do nicely for a full install,) and that it move on.

This link will come in handy.

http://www.justlinux.com/nhf/Install...on_System.html

Here's what I do. (/dev/hdb6 is the one lilo needs to know about)
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdb6 2.0G 465M 1.6G 24% /
/dev/hdb7 5.9G 525M 5.4G 9% /home
/dev/hdb8 5.9G 1.5G 4.4G 26% /usr
/dev/hdb9 5.9G 3.0G 3.0G 50% /usr/local
/dev/hdb10 1004M 60M 945M 6% /tmp
/dev/hdb11 1004M 65M 940M 7% /var
Ironblue:$

$ mount
/dev/hdb6 on / type reiserfs (rw)
/dev/hdb7 on /home type reiserfs (rw)
/dev/hdb8 on /usr type reiserfs (rw)
/dev/hdb9 on /usr/local type reiserfs (rw)
/dev/hdb10 on /tmp type reiserfs (rw)
/dev/hdb11 on /var type reiserfs (rw)


Hope this is of some help to you, let us know how it works out.

PS. Unless you must have it, (please no jumping on the bone.) I would
leave Gnome and TeX off as well. Make sure your doing a full install
except for Emacs, Gnome and maybe Tex. There are some libraries that
are gnome specific that kde will need. Doing the full install will take
care of it.

This may be handy as well.
http://www.bitbenderforums.com/vb22/...?postid=311808
http://www.linuxquestions.org/questi...hreadid=174447
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-20-2008, 08:55 AM
lgb
 
Posts: n/a
Default Re: Slackware boot problem

In article <pIydnak8ktGyBgffRVn-qg@comcast.com>, "marcusm
<\"marcusm7\"@" <"comcast.netWork> says...
> lgb wrote:
> >
> > When I tried to boot, I got a message about the superblock being
> > clobbered. It asked me to enter the root password to enter single user
> > mode, but then wouldn't take the one I'd specified.
> >

>
> How was liloconfig ran, simple/AUTOMATIC(no say so in the matter) or
> expert(full control and not that hard at all)
>

I ran liloconfig in expert mode and installed to the superblock of hdb1.

>
> Any way, you get the idea? I would just rip out these partitions and
> start over(practice makes perfect, eventually.


I did it over, installing only A and AP to save time, and it worked
fine. Either I screwed up the first time, or it was just a glitch.
Then I added the other sets and it still worked, so I'm happy. Now I
just have to get X and dialup working and I'll be set to go.

BTW, I tried KDE and it was extremely slow in my old equipment (233mhz).
I thought I'd try Gnome just to see how slow it was. You don't seem to
like it. Any reasons?

P.S. I'm not a Linux novice, I tried it first when Slackware was at
0.97 (or 0.79, who remembers). I used it for several years to develop
and test programs for a customer running SCO Unix. But I stopped using
it about 10 years ago and am amazed at how much I've forgotten. Of
course, at my age, I'm amazed at how much I've forgotten about
everything :-).

Thanks for the advice.

--
BNSF = Build Now, Seep Forever
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-20-2008, 08:55 AM
marcusm
 
Posts: n/a
Default Re: Slackware boot problem

lgb wrote:
> In article <pIydnak8ktGyBgffRVn-qg@comcast.com>, "marcusm
> <\"marcusm7\"@" <"comcast.netWork> says...
>
>
> Now I just have to get X and dialup working and I'll be set to go.
>

In case you haven't heard; X has on many distributions has gone from
XFree86 to Xorg and so the commands are a little different: # xorgconfig
Will do the trick to setup a starting xorg.conf file. The location is
/etc/X11/xorg.conf.
>
> BTW, I tried KDE and it was extremely slow in my old equipment (233mhz).
> I thought I'd try Gnome just to see how slow it was. You don't seem to
> like it. Any reasons?
>

From what I read a lot of people are very fond of Gnome and I'm sure
for good reasons. Myself, I tried it a few times and never got the hang
of it. I'm mush better at using kde. I don't install it because even
not using it, it has a mind of its own. It has interactions with the
kde install that I don't care for and then its help database was also
being updated regularly. From what I hear its also going in to pastures
in Slackware 11. Xfce is the light wight champ on the block, so you may
want to give it a go.
>
> P.S. I'm not a Linux novice, I tried it first when Slackware was at
> 0.97 (or 0.79, who remembers). I used it for several years to develop
> and test programs for a customer running SCO Unix. But I stopped using
> it about 10 years ago and am amazed at how much I've forgotten. Of
> course, at my age, I'm amazed at how much I've forgotten about
> everything :-).
>
> Thanks for the advice.
>


So I'm definitely trying to learn what you may have forgotten
Glad to hear you got it all ironed out.


Just in case:

/usr/doc/Linux-HOWTOs/Security-Quickstart-HOWTO
http://members.cox.net/laitcg/new/intro.html
http://www.giac.org/certified_profes.../gcux/0177.php
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 02-20-2008, 08:55 AM
Grant Coady
 
Posts: n/a
Default Re: Slackware boot problem

On Mon, 30 May 2005 09:15:51 -0700, lgb <lblanch@fastmail.fm> wrote:
>
>I did it over, installing only A and AP to save time, and it worked
>fine. Either I screwed up the first time, or it was just a glitch.


I was getting about 50/50 success rate with lilo on new slack installs,
I check the /etc/lilo.conf before reboot now, fix if required. So
me surprised now when it looks sane.

>.... Of
>course, at my age, I'm amazed at how much I've forgotten about
>everything :-).


"Older I get, better I was"

--Grant.

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 02-20-2008, 08:55 AM
notbob
 
Posts: n/a
Default Re: Slackware boot problem

On 2005-05-30, marcusm <"marcusm7"@ <"comcast.netWork>> wrote:


> being updated regularly. From what I hear its also going in to pastures
> in Slackware 11.


Unlikely. Pat is a fan and KDE user.

nb
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old 02-20-2008, 08:56 AM
marcusm
 
Posts: n/a
Default Re: Slackware boot problem

notbob wrote:
>
>>being updated regularly. From what I hear its also going in to pastures
>>in Slackware 11.

>
>
> Unlikely. Pat is a fan and KDE user.
>
> nb


He is, well that grate. I know I am; it must be my English, I should
have finished school. I was referring to Gnome.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #9 (permalink)  
Old 02-20-2008, 09:19 AM
Faux_Pseudo
 
Posts: n/a
Default Re: Slackware boot problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

_.-In alt.os.linux.slackware, lgb wrote the following -._
> P.S. I'm not a Linux novice, I tried it first when Slackware was at
> 0.97 (or 0.79, who remembers).


Memo
AOLS Policy Change
Effective: June 16 2005
Since we are now on version 10 of Slackware it is no loger needed to
specify "I started with 0.xx". In its place you can now say "I
started before 1.00". We may all be computer geeks but there is no
need to split hairs over about .20 worth of revison history that is
is now over a decade old.
Thank you in advance for your support of this new policy.

Love The Managment

- --
.-')) fauxascii.com ('-. | It's a damn poor mind that
' ..- .:" ) ( ":. -.. ' | can only think of one way to
((,,_;'.;' UIN=66618055 ';. ';_,,)) | spell a word.
((_.YIM=Faux_Pseudo :._)) | - Andrew Jackson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCsazRSJec2PH9pbURAnVxAJ0bZILzYldw51C138XuSb BxxZNmAwCfYJAu
RF4JUlMaxf0CgfSFnoZI0Pg=
=Sx4T
-----END PGP SIGNATURE-----
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

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

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 06:35 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
www.UnixAdminTalk.com