DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to update from etch to lenny. Downloaded and burned 1st two Lenny CDs, started the installation process (had noting on the system to save so I didn't do any backups or anything, just started the Debian 5.0 install process). Install went fine until it came to installing GRUB. Then the install failed and I was bumped to a screen that had the install steps listed, at the GRUB install point (step 16 I think). Tried again, no joy. Rebooted and started over, same problem. Tried installing LILO now, also didn't work. (No info in error messages, just that it failed). Tried Super-Grub, all forms, auto, manual, install in partition, install in MBR, didn't work either. I did get an error 15: file not found. Downloaded Debian Live - boots OK but doesn't seem to have grub-install installed. Slax Live too. Maybe I am not using it right. I'm not a rank newbie but I don't know too much about LINUX outside the basics.
I think I have lenny on my harddrive (installation process seemed to be copying files from CDs and downloading from the net) but I've lost GRUB and grub-install as well. Any suggestions as to what I am doing wrong and what i should do?
Check the BIOS for protection features (like boot virus) being turned on.
Fixing grub is generally pretty straightforward, but you seemed to have covered most routes. Installing grub is a two phase process - install the software, then install the loader.
to find out where you are, go get this, and post the RESULTS.txt - run it from a liveCD is fine.
OK, here's the result.txt file. hdc is a 6Gig HD that used to have win98 on it. Hdd is an 80gig that had etch. Tried to put lenny up on both at one time or another.
------------------------
============================= Boot Info Summary: ==============================
=> No boot loader is installed in the MBR of /dev/hda
=> Syslinux is installed in the MBR of /dev/hdc
=> Lilo is installed in the MBR of /dev/hdd
aufs on / type aufs (rw)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/hda on /live/image type iso9660 (ro,noatime)
tmpfs on /live/cow type tmpfs (rw,noatime,mode=755)
tmpfs on /live type tmpfs (rw)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt' (if you have created it), or |
# | install a new kernel. The computer will most likely fail to |
# | boot if a kernel-image post-install script or you don't |
# | remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hdd1
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hdd1
# This option may be needed for some software RAID installs.
#
# raid-extra-boot=mbr-only
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
=================== hdd1: Location of files loaded by Grub: ===================
Also, just rebooted and checked BIOS. Only thing I saw regarding protections was a virus protection setting, it was disabled. I haven't changed anything since running etch.
I assume you meant in the BIOS - the only option I have there is to specify 'HardDrive' vs "CDROM". I currently have it set to boot from the CD 1st, hard drive 2nd. When I have no CD in the drive, the system tries to go to the hd but it just hangs, no messages or anything. The 6gig is the 'master' and the 80 is the slave.
I can wipe either or both drives with no problems, but I'm not sure how to do that, esp. to get the MBR. Would that help or should I rejumper the hds?
I had a similar problem with net install of Debian 5. I have Ubuntu on another partition. Debian totally ruined the grub loader. Computer would not boot from /dev/sda8. ( Ubuntu ). I got the Super Grub disk, but that wouldn't work.
Added to that, Debian would not work in GUI with the nvidia graphics card on this ASUS laptop. I finally had to a) reinstall Ubuntu b) Get the graphics card going with smxi.
Someone should tell Debian that Debian 5 has serious problems! I have it installed, but can't get on the Net. This is a ppp0 dsl with a username and password (I'm in China ) Debian doesn't seem to be able to connect.
I used to use Debian all the time. Now it just seems to have gone haywire!
Try disconnecting all hard drives except the 80 GB that you want to install Lenny on. If it is an IDE hard drive, set the jumper to master. With only 1 hard drive in the system grub should have no problem installing to the MBR. After Lenny installs you can reconnect the other drive(s) and add mount points for the other drives to your fstab.
I used the dd command to wipe both harddrives. Then Lenny installed. Currently posting from the booted system using Iceweasel. My solution probably wouldn't be too useful for most,since I am essentially starting up a new system.
Simple solution would have been to just update etch to lenny through apt.
When re-installing any OS, the boot loader will usually get wiped.
If you do not want this to happen then skip the step to install a boot loader.
This will unfortunately not allow you to boot the new system but, if you have another linux distro that is on the list boot that and update the boot loader to include the new system.
There are numerous tutorials on updating etch to lenny.
What you described is a fresh reload not an update.
I have successfully updated etch to lenny on one of my laptops and just got finished installing lenny (netinst) on my new asus laptop my only issue is bluetooth.
What you say is true, but it seems you didn't read my first message. I tried to update to lenny (from etch, with a win98 also on the small hd) using the debian 5.0 install cd, but it wouldn't successfully load grub or lilo on either of my hard drives. I tried SuperGrub and that didn't work either. While the wiping of my 80gig took some time, it seemed easiest to me as the wiping of the MBR didn't fix the problem. That's why what I did was the hard way.... But the point is that I started with a working system (etch) that lenny messed up.
Last edited by KirkShanahan; 04-06-2009 at 09:23 AM.
New problem - lenny killed my sound. With etch I had sound working fine, now it's gone. I'm a LINUX beginner, so could someone suggest what I need to do to get my sound back?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.