View Single Post

   
  #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
Reply With Quote