Debian This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
03-29-2005, 09:16 PM
|
#1
|
LQ Newbie
Registered: Mar 2005
Distribution: Ubuntu 5.04
Posts: 5
Rep:
|
Booting up problems
Let me start I guess by explaining my situation:
Today I added a second hard drive to my PC to install debian onto to try it out. It was an older hard drive that I just had in another PC that I don't use anymore. I put it in and booted up and checked the BIOS and it saw it as the primary slave. Everything seemed to be fine so I put in my Debian netboot CD. I went with the installation and when it came to the partioning I wiped the whole HDD of the new HDD i put in and installed it to there. I wanted to keep it so I can have both 2000 and Debian so when it scanned for other OS it saw 2000 was installed and asked to install grub to select at boot. I said yes, installation was complete and it seemed like everything would be going smooth.
At this point it ejected the CD out and said the installation was complete and it was going to reboot and I would have the option to select OS.
After the reboot it seemed to be loading grub fine, but then it gave me error 21. At this point I couldn't do anything other than hit contrl alt delete to restart and come back to the same point. I didn't really know what to do so I took out the hard drive I had just put in, but it still came up with the error. I can't boot into windows or debian, it just locks up at that point with error 21.
I'm still having the error now. I had to get onto another PC and download slax (what i'm using now) to see if I could figure this out.
By reading through google I've seen some peoples problem with this was with their grub config, well this in mine in full
Code:
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5
# Pretty colours
color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hdb1 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,0)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.4.27-2-386
root (hd1,0)
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hdb1 ro
initrd /boot/initrd.img-2.4.27-2-386
savedefault
boot
title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hdb1 ro single
initrd /boot/initrd.img-2.4.27-2-386
savedefault
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows 2000 Professional
root (hd0,0)
savedefault
makeactive
chainloader +1
How can I go about fixing this?
|
|
|
03-29-2005, 09:27 PM
|
#2
|
Senior Member
Registered: Dec 2001
Location: New Zealand
Distribution: Debian
Posts: 1,046
Rep:
|
If you're not even reaching the Grub boot loader, then you'll probably have to change the boot sequence in the Bios (so that it looks to boot from your primary slave first). It's probably going straight to your other hard drive right now...
Cheers,
mj
|
|
|
03-30-2005, 01:59 PM
|
#4
|
Senior Member
Registered: Dec 2001
Location: New Zealand
Distribution: Debian
Posts: 1,046
Rep:
|
Presumably the photos were taken when the second drive was not plugged in ? It shows only an 80 Gb primary master...
Anyhoo, Grub won't find the disk if the Bios can't see it (even though linux can still read it once booted) so an error in the Bios is the most likely problem. Your Grub config file looks fine (assuming that your Debian partition is on hdb1, the first partition of your second hard disk). From a bit of googling, you could try setting the Bios Standard CMOS primary master to Type = User, Mode = LBA, and the primary slave to Type = Auto, Mode = Auto. Another option would be to try moving the Debian drive temporarily to another slot, such as secondary master/slave (obviously you'd have to change your Grub conf if you wanted to actually load it). Also, double-check the cables and jumper settings (cable select is not completely reliable).
Just in case you haven't seen it, error 21 corresponds to "Selected disk does not exist. This error is returned if the device part of a device - or full file name refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system." ( http://www.gnu.org/software/grub/man...ge1.5%20errors).
Cheers,
mj
|
|
|
03-30-2005, 04:21 PM
|
#5
|
LQ Newbie
Registered: Mar 2005
Distribution: Ubuntu 5.04
Posts: 5
Original Poster
Rep:
|
Thanks - I actually found a website with that same info just before I saw your response. I ended up last night being able to get back to windows using fixmbr, then I formatted the other drive, edited the BIOS for auto/auto and re-installed debian and put grub on a floppy now, rather than the MBR. Everything is now working fine, posting this on it now 
|
|
|
03-30-2005, 05:18 PM
|
#6
|
Senior Member
Registered: Dec 2001
Location: New Zealand
Distribution: Debian
Posts: 1,046
Rep:
|
Great to hear
I would definitely recommend putting Grub (or Lilo) on the MBR of one of your hard drives at some stage however - once it's set up you shouldn't have any problems.
Cheers,
mj
|
|
|
All times are GMT -5. The time now is 12:31 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|