LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 04-04-2009, 01:28 PM   #1
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Rep: Reputation: 0
Lenny killed GRUB!


Hi all,

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?

Kirk S.
 
Old 04-04-2009, 07:02 PM   #2
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 17,525

Rep: Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744
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.
 
Old 04-04-2009, 08:32 PM   #3
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Original Poster
Rep: Reputation: 0
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

hdc1: _________________________________________________________________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /etc/fstab

hdc2: _________________________________________________________________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

hdc5: _________________________________________________________________________

File system: swap
Boot sector type: -
Boot sector info:

hdd1: _________________________________________________________________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Debian GNU/Linux 5.0
Boot files/dirs: /etc/fstab /etc/lilo.conf

hdd2: _________________________________________________________________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

hdd5: _________________________________________________________________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

hdd6: _________________________________________________________________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

hdd7: _________________________________________________________________________

File system: swap
Boot sector type: -
Boot sector info:

hdd8: _________________________________________________________________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

hdd9: _________________________________________________________________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:

=========================== Drive/Partition Info: =============================

Drive: hda ___________________ _____________________________________________________
Note: sector size is 2048 (not 512)

Disk /dev/hda: 724 MB, 724105216 bytes
255 heads, 63 sectors/track, 22 cylinders, total 353567 sectors
Units = sectors of 1 * 2048 = 2048 bytes

Partition Boot Start End Size Id System

Invalid MBR Signature found


Drive: hdc ___________________ _____________________________________________________

Disk /dev/hdc: 6448 MB, 6448619520 bytes
255 heads, 63 sectors/track, 784 cylinders, total 12594960 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x000b8131

Partition Boot Start End Size Id System

/dev/hdc1 * 63 11,936,294 11,936,232 83 Linux
/dev/hdc2 11,936,295 12,594,959 658,665 5 Extended
/dev/hdc5 11,936,358 12,594,959 658,602 82 Linux swap / Solaris


Drive: hdd ___________________ _____________________________________________________

Disk /dev/hdd: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x0009e2fa

Partition Boot Start End Size Id System

/dev/hdd1 * 63 690,794 690,732 83 Linux
/dev/hdd2 690,795 156,296,384 155,605,590 5 Extended
/dev/hdd5 690,858 10,458,314 9,767,457 83 Linux
/dev/hdd6 10,458,378 16,322,039 5,863,662 83 Linux
/dev/hdd7 16,322,103 21,623,489 5,301,387 82 Linux swap / Solaris
/dev/hdd8 21,623,553 22,410,674 787,122 83 Linux
/dev/hdd9 22,410,738 156,296,384 133,885,647 83 Linux


blkid -c /dev/null: ____________________________________________________________

/dev/hdc1: UUID="8a673619-975a-42f4-b1a8-184bec0c240c" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdc5: TYPE="swap"
/dev/hdd1: UUID="2ba7fa66-eb4e-43fc-b39f-5cb8d80c1c26" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdd5: UUID="aa90abe2-9a52-41a3-908b-5d7430c6c079" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdd6: UUID="2d23cfbd-f04f-44d1-8f63-4feb9523f853" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdd7: TYPE="swap"
/dev/hdd8: UUID="cc7656be-04f2-4eb7-99df-ebf2877ea7f6" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdd9: UUID="2e8e72eb-c56a-4a69-a899-9322dbaa506b" SEC_TYPE="ext2" TYPE="ext3"
/dev/loop0: TYPE="squashfs"

=============================== "mount" output: ===============================

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)


=============================== hdc1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hdc1 / ext3 errors=remount-ro 0 1
/dev/hdc5 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0

=============================== hdd1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hdd1 / ext3 errors=remount-ro 0 1
/dev/hdd9 /home ext3 defaults 0 2
/dev/hdd8 /tmp ext3 defaults 0 2
/dev/hdd5 /usr ext3 defaults 0 2
/dev/hdd6 /var ext3 defaults 0 2
/dev/hdd7 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0

============================= hdd1/etc/lilo.conf: =============================

# /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=

#
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
append="quiet"
initrd=/initrd.img

image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
append="quiet"
initrd=/initrd.img.old


# 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: ===================


.1GB: boot/initrd.img-2.6.26-1-686
.0GB: boot/vmlinuz-2.6.26-1-686
.1GB: initrd.img
.0GB: vmlinuz
=============================== StdErr Messages: ===============================

sed: can't read hdc1/etc/issue: No such file or directory
 
Old 04-04-2009, 08:41 PM   #4
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Original Poster
Rep: Reputation: 0
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.

P.S. Thanks for the help!
 
Old 04-04-2009, 09:15 PM   #5
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 17,525

Rep: Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744
Check that you have the 80Gig as the first (hard-disk) boot device; I'd suspect that syslinux on the small disk is getting in the way.
 
Old 04-04-2009, 09:47 PM   #6
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Original Poster
Rep: Reputation: 0
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?
 
Old 04-04-2009, 10:11 PM   #7
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 17,525

Rep: Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744Reputation: 2744
Personally I'd wipe the loader code in the MBR of the smaller disk to get rid of syslinux, and let the BIOS find the 80 Gig
Code:
dd if=/dev/zero of=/dev/hdc count=440 bs=1
(as root).
Try a reboot, and if that still doesn't work either scrub hdd MBR likewise, or just try re-install grub or lilo.

Last edited by syg00; 04-04-2009 at 10:12 PM.
 
Old 04-05-2009, 10:14 AM   #8
Pedroski
Senior Member
 
Registered: Jan 2002
Location: Nanjing, China
Distribution: Ubuntu 18.04
Posts: 1,687

Rep: Reputation: 55
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!
 
Old 04-05-2009, 02:48 PM   #9
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Original Poster
Rep: Reputation: 0
So Pedroski, did you ever get Debian 5 to work?
 
Old 04-05-2009, 04:58 PM   #10
tommcd
Senior Member
 
Registered: Jun 2006
Location: Philadelphia PA USA
Distribution: Lubuntu, Slackware
Posts: 2,230

Rep: Reputation: 291Reputation: 291Reputation: 291
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.
 
Old 04-05-2009, 09:46 PM   #11
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Original Poster
Rep: Reputation: 0
Success - the hard way!

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.

Thanks to all who helped, but esp. syg00.
 
Old 04-05-2009, 10:16 PM   #12
kschulen
LQ Newbie
 
Registered: Sep 2005
Location: OH
Distribution: Debian Sarge / Lenny
Posts: 14

Rep: Reputation: 0
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.
 
Old 04-05-2009, 10:19 PM   #13
kschulen
LQ Newbie
 
Registered: Sep 2005
Location: OH
Distribution: Debian Sarge / Lenny
Posts: 14

Rep: Reputation: 0
Also, Debian 5 (lenny) has some issues but nothing major that I can see. Also, keep in mind that ubuntu and most other distros are based off of debian
 
Old 04-06-2009, 09:29 AM   #14
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Original Poster
Rep: Reputation: 0
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 10:23 AM.
 
Old 04-06-2009, 09:30 AM   #15
KirkShanahan
LQ Newbie
 
Registered: Dec 2008
Posts: 20

Original Poster
Rep: Reputation: 0
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?
 
  


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
Lenny Update Killed Wine dkpw Debian 6 01-23-2008 01:43 PM
XP has Killed Grub nOmArch Linux - Newbie 4 01-12-2008 08:35 PM
linspire killed grub...now no fc3... cyanide_2 Fedora 3 02-22-2005 10:22 AM
removing GRUB killed my XP HDD?!? (help!) CuriousGeorge Linux - Newbie 5 02-06-2004 06:03 AM
Grub killed my kernel! I think... =P SmackMyBishop Linux - General 2 08-03-2002 11:38 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 10:05 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration