Every Moning Starts with "Error 17"

kcarun · 02-11-2007, 01:18 AM

Hi Friends,

Every Morning while booting the system My screen is as follows,

[HTML]Verifying DMI Pool Data....
Boot from ATPI CD-ROM : No Bootable Media..
Grub loading Stage 1.5.

GRUB Loading, Please wait....
Error 17[/HTML]

Then I have to press the restart button. The second time onwards there is no problem..

Why this strange Problem? Kindly advice

...Arun

FredGSanford · 02-11-2007, 02:55 AM

Assuming you're using Grub, check the grub .lst file and make sure everything looks the way it should.

kcarun · 02-18-2007, 08:47 AM

Hi FredGSanford , Sorry for the late respose, last few days i was away from home.. and just now I tried to locate the grub.lst file.. It is in which directory?

..arun

makuyl · 02-18-2007, 02:17 PM

I suppose he meant /boot/grub/menu.lst
Also have a look at /boot/grub/device.map
Might as well post contents of both files here.

kcarun · 02-18-2007, 11:13 PM

hi makuyl , Thanks for the help

Yes that file is there in mY system, and right now i am in office I will post those files today evening..

..arun

syg00 · 02-18-2007, 11:17 PM

Given that a restart fixes it, I doubt it's a software (grub) problem.
I once had a machine that had to "warm up" before I could use it - I suspected something like a "dry joint" on the motherboard. I just lived with it.

kcarun · 02-19-2007, 09:09 AM

Here is my menu.lst

PHP Code:



arun@debian:~$ cat /boot/grub/menu.lst 
# 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 options 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/hda2 ro 
 
## default grub root device 
## e.g. groot=(hd0,0) 
# groot=(hd0,1) 
 
## 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.6.8-2-386 
root            (hd0,1) 
kernel          /boot/vmlinuz-2.6.8-2-386 root=/dev/hda2 ro 
initrd          /boot/initrd.img-2.6.8-2-386 
savedefault 
boot 
 
title           Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode) 
root            (hd0,1) 
kernel          /boot/vmlinuz-2.6.8-2-386 root=/dev/hda2 ro single 
initrd          /boot/initrd.img-2.6.8-2-386 
savedefault 
boot 
 
### END DEBIAN AUTOMAGIC KERNELS LIST

and my device.map files is looks as below

PHP Code:



arun@debian:~$ cat /boot/grub/device.map 
(hd0)   /dev/hda 
(hd1)   /dev/hdb

kcarun · 02-19-2007, 09:17 AM

Hi syg00 ,

Then How can I identify this is a software or Hardware Issue?

makuyl · 02-19-2007, 09:31 AM

Can't see anything wrong with device.map or menu.lst.
On thing to try is to set the hd's on master and slave, and check their positions on the cables. Some times cable select doesn't quite agree with linux.