I'm using D5 to post this, but had to load it through the Graphical Rescue option on DVD #1 (running as root, using "startx"). Trying a normal boot from /dev/hda1 gives "GRUB Loading Stage 1.5; GRUB loading, please wait...; ERROR 25"
I've run into this on my main system (Klikit, a Kubuntu-based distro) when Grub by default specified hd(1,0); after editing it to hd(0,0) all was fine. My Debian 5 grub already shows hd(0,0). I tried editing it to hd(1,0) just on the off chance, and of course that didn't work... still an ERROR 25.
Any suggestions?
--werdigo49
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Debian 5: Grub Error 25 [solved]
Debian 5: Grub Error 25 [solved]
Last edited by werdigo49 on 2009-02-21 13:27, edited 1 time in total.
(hd1,0) would be the first partition on the second drive, so maybe another device was seen as /dev/sda before the hard drive?
I don't know if you tried changing /boot/grub/menu.lst, but when Debian updates a kernel or certain system configurations, it'll recreate initrd and run update-grub, which changes /boot/grub/menu.lst. If you updated one (the wrong) line and ran some system updates, the root may have been reset. Make sure you change all instances of (hd1,0) to (hd0,0) or update the groot= line in /boot/grub/menu.lst and run update-grub:
I don't know if you tried changing /boot/grub/menu.lst, but when Debian updates a kernel or certain system configurations, it'll recreate initrd and run update-grub, which changes /boot/grub/menu.lst. If you updated one (the wrong) line and ran some system updates, the root may have been reset. Make sure you change all instances of (hd1,0) to (hd0,0) or update the groot= line in /boot/grub/menu.lst and run update-grub:
should look like:## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,0)
If this doesn't work, can you paste the output of fdisk -l /dev/sda, what each partition is used for (/, /var, /boot, swap, etc), and the contents of /boot/grub/menu.lst?## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
Thanks, Logan... yes, I should have been more specific: That editing was done in the grub menu.lst. I now have everything changed back to hd(0,0). The device map shows that (hd0) is /dev/hda, and (my secondary sata drive) (hd1) is /dev/sda. (I found another post (marked "solved") with a boot problem, in which Mase recommended the OP change his menu.lst items from hda3 to hda1... but mine are already hda1.)
When I installed, I set up hda1 as /, hda3 as swap, and saved an old /home (from another distribution) as hda2. The / was formatted as reiserfs (the old /home is also).
I can't get a terminal window using this graphical rescue setup --- it gives me a "error creating the child process" message. When I get out of this graphical rescue I'll see what I can find with fdisk.
EDIT: Can't copy/paste from the text-based rescue, but here's a summary of what fdisk -l provided:
Disks: /dev/hda 30G, /dev/sda 250G
Device_____Boot_____Start_____End___.........___System
/dev/hda1____* ________1______1669__________ Linux
/dev/hda2___________ 1913_____3649__________Linux
/dev/hda3___________1670______1912__________Linux swap / Solaris
/dev/sda1____ * ________1______15298_________ Linux
/dev/sda2 ___________15299____28046_________ Linux
The boot/grub/menu.lst entries are now all back to (hd0,0). I notice that sda1 is also set with a boot flag, but there's no kernel or anything except data on it.
EDIT #2: I now have the D5 disk installed as a slave in my Klikit system and can copy and paste from it. Here is most of the menu.lst:
### 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 specific 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_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/hda1 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,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
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(single-user 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
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.6.26-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro quiet
initrd /boot/initrd.img-2.6.26-1-686
title Debian GNU/Linux, kernel 2.6.26-1-686 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.26-1-686
### END DEBIAN AUTOMAGIC KERNELS LIST
So far, I haven't noticed anything amiss... but I'm a long way from a Linux expert.
---werdigo49
When I installed, I set up hda1 as /, hda3 as swap, and saved an old /home (from another distribution) as hda2. The / was formatted as reiserfs (the old /home is also).
I can't get a terminal window using this graphical rescue setup --- it gives me a "error creating the child process" message. When I get out of this graphical rescue I'll see what I can find with fdisk.
EDIT: Can't copy/paste from the text-based rescue, but here's a summary of what fdisk -l provided:
Disks: /dev/hda 30G, /dev/sda 250G
Device_____Boot_____Start_____End___.........___System
/dev/hda1____* ________1______1669__________ Linux
/dev/hda2___________ 1913_____3649__________Linux
/dev/hda3___________1670______1912__________Linux swap / Solaris
/dev/sda1____ * ________1______15298_________ Linux
/dev/sda2 ___________15299____28046_________ Linux
The boot/grub/menu.lst entries are now all back to (hd0,0). I notice that sda1 is also set with a boot flag, but there's no kernel or anything except data on it.
EDIT #2: I now have the D5 disk installed as a slave in my Klikit system and can copy and paste from it. Here is most of the menu.lst:
### 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 specific 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_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/hda1 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,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
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(single-user 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
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.6.26-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro quiet
initrd /boot/initrd.img-2.6.26-1-686
title Debian GNU/Linux, kernel 2.6.26-1-686 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.26-1-686
### END DEBIAN AUTOMAGIC KERNELS LIST
So far, I haven't noticed anything amiss... but I'm a long way from a Linux expert.
---werdigo49
It looks alright to me, so long as /dev/hda is what grub sees for (hd0). Can you get a grub prompt and tab complete root (hd0,? Do you see the three partitions?
Were there any errors when running update-grub? Maybe try manually:
Were there any errors when running update-grub? Maybe try manually:
http://www.gnu.org/software/grub/manual ... 2e5-errors# grub --no-floppy
grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,0)/boot/grub/stage2
/boot/grub/menu.lst"... succeeded
Done.
Could there be something wrong with the disk or maybe something with the BIOS that's causing problems reading it?25 : Disk read error
This error is returned if there is a disk read error when trying to probe or read data from a particular disk.
Well, Logan, I don't know exactly what I did... but she's running this morning! I disconnected the secondary hard disk, sda (250G sata data disk), made sure the Lenny disk was set to "Master," hit the reboot button... and up it came!
Thanks again for your attention to my problem! Now I'm going to play around a little...
--werdigo49
Thanks again for your attention to my problem! Now I'm going to play around a little...
--werdigo49