Re: Grub Problem
On 06/25/2022 09:37 AM, Stephen P. Molnar wrote: I have four hard drives ion my Bullseye platform; Three SSD's and one HDD. My current copy of Bullseye is on /dev/sdd1. I have installed a pristine copy of Bullsye on /dev/sda. The installer found the copy of Bullseye on /dev/ssd1 and I installed grub on /dev/sda1. At the end of the installation process I removed the installationm media from the cdrom drive, rebooted the computer and selected /dev/sda1. I got an error message that /dev/sda couldn't be found. The good news is that if I hit the reset button on the platform the old grub menu comes up and the system boots into the version on sdd1. Now, this ROF (retired old fool, althought other terms might be aplicable) from the long gone days of punched cards and tape drives has been using computers sine the early 1960's, google was not my frient in trying to find a solution to the problem. Assistanc will be mucn appeciated. Thanks in advance. -- Stephen P. Molnar, Ph.D. Molecular Modeling 614.312.7528 (c) Skype: smolnar1 After much trepidation, sudo update-grub solved the problem Thanks to those who answered my request. -- Stephen P. Molnar, Ph.D. Molecular-Modeling 614.312.7528 (c) Skype: smolnar1
Re: Grub Problem
"Stephen P. Molnar" writes: > Assistanc will be mucn appeciated. You didn't really specify what you want assistance with but I guess you want to boot the new Bullseye too? I don't really see the point of having two copies of the same OS installed though. Assuming a BIOS system and os-prober package installed, it could be as simple as running update-grub in your old Bullseye. Which would create a new grub config file with entries for the old and the new Bullseyes.
Re: Grub Problem
On Sat 25 Jun 2022 at 09:37:32 (-0400), Stephen P. Molnar wrote: > > I have four hard drives ion my Bullseye platform; Three SSD's and one > HDD. My current copy of Bullseye is on /dev/sdd1. I have installed a > pristine copy of Bullsye on /dev/sda. > > The installer found the copy of Bullseye on /dev/ssd1 and I installed > grub on /dev/sda1. At the end of the installation process I removed > the installationm media from the cdrom drive, rebooted the computer > and selected /dev/sda1. I got an error message that /dev/sda couldn't > be found. The good news is that if I hit the reset button on the > platform the old grub menu comes up and the system boots into the > version > on sdd1. > > Now, this ROF (retired old fool, althought other terms might be > aplicable) from the long gone days of punched cards and tape drives > has been using computers sine the early 1960's, google was not my > frient in trying to find a solution to the problem. > > Assistanc will be mucn appeciated. > > Thanks in advance. It looks as if you asked a question very like this in February, to which there were two followups, but nothing back from you about how you're booting this machine, UEFI or legacy BIOS, and how the disks are partitioned, MBR or GPT. This may make people reluctant to help, as they may feel they are wasting their breath. My only advice at this time would be to find a better method to identify your disk partitions than their kernel names, /dev/sd[abcd]: so LABELs, PARTLABELs or UUIDs. Cheers, David.
Re: Grub Problem
On 25/06/2022 14:37, Stephen P. Molnar wrote: The installer found the copy of Bullseye on /dev/ssd1 and I installed grub on /dev/sda1. You supposed to install GRUB in a disk, not in a partition. So, /dev/sda, not /dev/sda1. You select /dev/sda during installation. At the end of the installation process I removed the installationm media from the cdrom drive, rebooted the computer and selected /dev/sda1. I am not surprised here, if you really installed GRUB in a partition. Computer is trying to boot from /dev/sda, and GRUB is not there, its somewhere further down in the disk on sda1 partition. I don't think BIOS is looking for it there. I got an error message that /dev/sda couldn't be found. The good news is that if I hit the reset button on the platform the old grub menu comes up and the system boots into the version on sdd1. You can change boot priority by pressing button (usually F9), or entering BIOS and selecting drive you want to boot from. But in current state, most likely you will not be able to boot to new Bullseye on /dev/sda, because GRUB is not correctly installed. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: Grub Problem
before any action ... comes diagnosis: please fill in missing pieces: - SDD's, HDD are formatted GPT? or is the dinosaur using MBR? - is your computer configured to boot UEFI-style? Or are you still using BIOS-style/compatibility-mode? - can you show (and comment) the output from lsblk and (sudo) blkid? - did you look at all the grub.cfg files (in different systems)? Anything particular? - Are you able to use grub command line in case you would need it? My first guess would be, that sticking to /dev/sd?? device names confused yourself, the OS and maybe even grub. i recommend (mid-term) to switch to some other ID, like PARTUUID, or such in order to prevent confusion. But first things first: I did not really understand the problem, you are running into, which certainly has an easy fix, once it reveals itself fully. DdB
Re: GRUB problem after clone
On Sat, Sep 29, 2012 at 7:50 PM, Brian a...@cityscape.co.uk wrote: On Sat 29 Sep 2012 at 18:56:43 +0200, Artifex Maximus wrote: On Sat, Sep 29, 2012 at 12:24 PM, Brian a...@cityscape.co.uk wrote: At the GRUB prompt press the 'e' key. Please post what you see. There will probably be a long UUID. To save some typing put 123 for it. Thanks. Might I was not clean. This is not grub prompt just a GRUB line on the screen. Keys even ctrl-alt-del don't work. I assume this is the output of loader in the boot sector of sda2. No, you clearly described your situation. It was me who mangled it. I think what I wanted to say was the UUID of the partition in grub.cfg would not be the same as before the cloning, so the file needs editing. blkid would be used to get the new UUID. Alternatively, deleting the search line and having the linux line as linux /vmlinuz root=/dev/sda2 might work. Just for the record. I download the latest Wheezy DVD and try to recover GRUB under rescue mode. No success still only displaying GRUB at boot and nothing else. Then do some more search and found the following page: https://help.ubuntu.com/community/Boot-Repair As Ubuntu is based on Debian I choose as the recommended way to go. Then I turn to this page: https://help.ubuntu.com/community/UbuntuSecureRemix Downloaded and use boot repair application to reinstall(?) GRUB on sda2 and finally my GRUB is working and I was able to load Debian. Then upgrade my Debian system and because there was GRUB upgrade as well the upgrade asked me what is the boot system as my device.map is changed. I select sda2 and upgrade do the rest. So now I am happy Debian user again on a bigger drive. Thanks for all of your help. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPkuXvGd-6MEtMQBz_3x3FMrpdhYKgXyX2bPLNsXWtb6=n6...@mail.gmail.com
Re: GRUB problem after clone
On Sat, Sep 29, 2012 at 7:50 PM, Brian a...@cityscape.co.uk wrote:
On Sat 29 Sep 2012 at 18:56:43 +0200, Artifex Maximus wrote:
On Sat, Sep 29, 2012 at 12:24 PM, Brian a...@cityscape.co.uk wrote:
At the GRUB prompt press the 'e' key. Please post what you see. There
will probably be a long UUID. To save some typing put 123 for it.
Thanks. Might I was not clean. This is not grub prompt just a GRUB
line on the screen. Keys even ctrl-alt-del don't work. I assume this
is the output of loader in the boot sector of sda2.
No, you clearly described your situation. It was me who mangled it. I
think what I wanted to say was the UUID of the partition in grub.cfg
would not be the same as before the cloning, so the file needs editing.
blkid would be used to get the new UUID. Alternatively, deleting the
search line and having the linux line as
linux /vmlinuz root=/dev/sda2
might work.
Thanks for your answer but the problem is the loader stops before
loading GRUB itself so I cannot do anything within GRUB. The GRUB
text was displayed by boot sector of partition. This means that GRUB
loader in boot sector of partition does not find the next stage of
GRUB. I do not know why. I do not know how to reinstall GRUB to my
Debian partition. The UUID of swap partition lost in clone but I think
there is a myriad of tutorial how to change UUID of partition.
Here is the blkid output:
/dev/sda1: UUID=01CBD00909925860 TYPE=ntfs
/dev/sda2: LABEL=rootfs UUID=6fcb6e1c-92a2-4ac5-beac-e997ab08491f
SEC_TYPE=ext2 TYPE=ext3
/dev/sda3: TYPE=swap
Here is the grub.cfg part:
menuentry 'Debian GNU/Linux, with Linux 3.2.0-3-amd64' --class debian
--class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)'
search --no-floppy --fs-uuid --set=root
6fcb6e1c-92a2-4ac5-beac-e997ab08491f
echo'Loading Linux 3.2.0-3-amd64 ...'
linux /boot/vmlinuz-3.2.0-3-amd64
root=UUID=6fcb6e1c-92a2-4ac5-beac-e997ab08491f ro quiet acpi=force
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-3-amd64
}
And here is the fstab:
# / was on /dev/sda2 during installation
UUID=6fcb6e1c-92a2-4ac5-beac-e997ab08491f / ext3
errors=remount-ro 0 1
# swap was on /dev/sda3 during installation
UUID=d76a59a5-e778-41c6-8d2d-e10a52bd739f noneswapsw
0 0
Bye,
a
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAPkuXvHPBVntCs7DA5Zbp8SOMZUeG7xa=bnbm7xk1xa5bbc...@mail.gmail.com
Re: GRUB problem after clone
On Fri 28 Sep 2012 at 22:24:16 +0200, Artifex Maximus wrote: I would like to move from old 320GB HDD to a new 1TB HDD. I have the following partition structure: sda1 - XP sda2 - Debian 7 x86_64 (boot partition) sda3 - swap The GRUB is on the sda2 partition not in the MBR. That's why sda2 is the boot partition. If I set sda1 as boot partition XP runs. I just do not want to disturb original MBR loader code. I clone my system to a new bigger HDD using Clonezilla 2 for Linux. At start GRUB loader only writes GRUB on the screen and nothing else happen. If I set sda1 as boot XP load and works fine. I've tried to reinstall grub under RIPLinux x86_64 with mount sda2 and chroot but no success. update-grub displays no error but no success. The Linux filesystem including /boot folder and grub is there. Most likely there is some missing piece which is not part of filesystem therefore clonezilla misses that part. My question is what is the recommended way of reinstall GRUB after cloning in such situation? Why update-grub does not works? Might try to copy with dd and resize later? At the GRUB prompt press the 'e' key. Please post what you see. There will probably be a long UUID. To save some typing put 123 for it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120929102417.GD22368@desktop
Re: GRUB problem after clone
On Sat, Sep 29, 2012 at 12:24 PM, Brian a...@cityscape.co.uk wrote: On Fri 28 Sep 2012 at 22:24:16 +0200, Artifex Maximus wrote: I would like to move from old 320GB HDD to a new 1TB HDD. I have the following partition structure: sda1 - XP sda2 - Debian 7 x86_64 (boot partition) sda3 - swap The GRUB is on the sda2 partition not in the MBR. That's why sda2 is the boot partition. If I set sda1 as boot partition XP runs. I just do not want to disturb original MBR loader code. I clone my system to a new bigger HDD using Clonezilla 2 for Linux. At start GRUB loader only writes GRUB on the screen and nothing else happen. If I set sda1 as boot XP load and works fine. I've tried to reinstall grub under RIPLinux x86_64 with mount sda2 and chroot but no success. update-grub displays no error but no success. The Linux filesystem including /boot folder and grub is there. Most likely there is some missing piece which is not part of filesystem therefore clonezilla misses that part. My question is what is the recommended way of reinstall GRUB after cloning in such situation? Why update-grub does not works? Might try to copy with dd and resize later? At the GRUB prompt press the 'e' key. Please post what you see. There will probably be a long UUID. To save some typing put 123 for it. Thanks. Might I was not clean. This is not grub prompt just a GRUB line on the screen. Keys even ctrl-alt-del don't work. I assume this is the output of loader in the boot sector of sda2. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPkuXvGexBQvvBetNfPLHOPvoXgGiqU=SciNmdZ0=jetdzp...@mail.gmail.com
Re: GRUB problem after clone
On Sat 29 Sep 2012 at 18:56:43 +0200, Artifex Maximus wrote: On Sat, Sep 29, 2012 at 12:24 PM, Brian a...@cityscape.co.uk wrote: At the GRUB prompt press the 'e' key. Please post what you see. There will probably be a long UUID. To save some typing put 123 for it. Thanks. Might I was not clean. This is not grub prompt just a GRUB line on the screen. Keys even ctrl-alt-del don't work. I assume this is the output of loader in the boot sector of sda2. No, you clearly described your situation. It was me who mangled it. I think what I wanted to say was the UUID of the partition in grub.cfg would not be the same as before the cloning, so the file needs editing. blkid would be used to get the new UUID. Alternatively, deleting the search line and having the linux line as linux /vmlinuz root=/dev/sda2 might work. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120929175057.GJ22368@desktop
Re: Grub problem
On Saturday 08 November 2008 21:22:15 Bela Balazs wrote: Hello all. I installed Debian, but the installer failed to install grub. Did it fail or dint propose? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub problem
Op Sat, 8 Nov 2008 22:22:15 +0200 Bela Balazs wrote: The two menu.lst entries: title Debian GNU/Linux, kernel 2.6.24-1-686 root(hd0,1) kernel /boot/vmlinuz-2.6.24-1-686 root=UUID=5dd1a349-c311-40ca-82f4-a7a39ca134a3 ro initrd /boot/initrd.img-2.6.24-1-686 [...] I tried changing the UUID to /dev/sda2 but still no luck. I'm sure that Debian is installed on that partition (I know from fdisk -l in Ubuntu). I believe 'root (hd0,1)' should be 'root (sd0,1)'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub problem
On Sat, Nov 08, 2008 at 10:22:15PM +0200, Bela Balazs wrote: Hello all. I installed Debian, but the installer failed to install grub. I have that problem whenever I install Etch: the installer says its installing Etch but it doesn't. I end up rebooting the installer in rescue mode and doing it from the menus again. I also have Ubuntu, so I installed grub manually by chrooting to the Debian partition.The two systems are installed on separate disks. Debian is installed on a SATA disk.I didn't have a Sata controller on the motherboard so I had used a PCI SATA card.My bios can't boot on that disk (not sure why). I don't know if your bios can boot a kernel on a drive from which it can't boot, even if it can load grub. You may need to put a 64 MB partition on the Ubuntu disk and use that for Debian's /boot. My only option to boot Debian is trough Ubuntu's grub. Remember that you'll have to manually update the boot loader every time you update debian's kernel. So I copied the two entries from Debian's menu.lst to Ubuntu's,but when I select Debian in the menu I get an error: Could not mount selected partition (or something similar).I've also tried reinstalling grub from Rescue mode on the Debian DVD, but no luck. See above re booting from a disk that the bios can't boot. Is the Could not mount error coming from grub (e.g. couldn't find the kernel) or from the kernel (e.g. couldn't find the root partition). The two menu.lst entries: title Debian GNU/Linux, kernel 2.6.24-1-686 root(hd0,1) kernel /boot/vmlinuz-2.6.24-1-686 root=UUID=5dd1a349-c311-40ca-82f4-a7a39ca134a3 ro initrd /boot/initrd.img-2.6.24-1-686 title Debian GNU/Linux, kernel 2.6.24-1-686 (single-user mode) root(hd0,1) kernel /boot/vmlinuz-2.6.24-1-686 root=UUID=5dd1a349-c311-40ca-82f4-a7a39ca134a3 ro single initrd /boot/initrd.img-2.6.24-1-686 I'd go to the grub command promt and try entering things manually, using grub's tab-completion to ensure that devices are correct. For example, should root be (sd0,1)? I tried changing the UUID to /dev/sda2 but still no luck. I'm sure that Debian is installed on that partition (I know from fdisk -l in Ubuntu). Ubuntu is installed on (hd0,2). Booting issues are where a serial console (or logging the output directly to a printer on lp0) is very helpful. You can see the serial-console HOWTO for how to set that up, as well as the grub manual for how to have grub talk to a serial console. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub problem
On Sat, Nov 08, 2008 at 11:03:48PM +0100, Sjoerd Hiemstra wrote: Op Sat, 8 Nov 2008 22:22:15 +0200 Bela Balazs wrote: The two menu.lst entries: title Debian GNU/Linux, kernel 2.6.24-1-686 root(hd0,1) kernel /boot/vmlinuz-2.6.24-1-686 root=UUID=5dd1a349-c311-40ca-82f4-a7a39ca134a3 ro initrd /boot/initrd.img-2.6.24-1-686 [...] I tried changing the UUID to /dev/sda2 but still no luck. I'm sure that Debian is installed on that partition (I know from fdisk -l in Ubuntu). I believe 'root (hd0,1)' should be 'root (sd0,1)'. No. Grub only calls disks hd. It has not heard of soft-disk :-) -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub problem
On Saturday 08 November 2008 16:03, Sjoerd Hiemstra wrote: Op Sat, 8 Nov 2008 22:22:15 +0200 Bela Balazs wrote: The two menu.lst entries: title Debian GNU/Linux, kernel 2.6.24-1-686 root(hd0,1) kernel /boot/vmlinuz-2.6.24-1-686 root=UUID=5dd1a349-c311-40ca-82f4-a7a39ca134a3 ro initrd /boot/initrd.img-2.6.24-1-686 [...] I tried changing the UUID to /dev/sda2 but still no luck. I'm sure that Debian is installed on that partition (I know from fdisk -l in Ubuntu). I believe 'root (hd0,1)' should be 'root (sd0,1)'. ALL GRUB hard drives are (hd?) and ALL GRUB partitions are (hd?,?). (sd0,1) is simply a filename to grub, and therefore not a valid argument to the root command. Do you have a separate partition for /boot or not? That looks valid for /boot stored on the same partition as /, but you may need to change it if your /boot is a separate partition. If your BIOS can't boot from the disk, grub might have problems as well. I tought grub could only see BIOS devices. What devices does grub see? Try (hdTABTAB at the grub prompt from the grub boot menu. Can grub find your kernel on any device? Try find /vmlinuz-2.6.24-1-686 and find /boot/vmlinuz-2.6.24-1-686 from that same prompt. -- Boyd Stephen Smith Jr. ,= ,-_-. =. [EMAIL PROTECTED] ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/ pgppPm9YuIbNb.pgp Description: PGP signature
Re: grub problem with primary partition
On Sat,19.Jul.08, 10:36:44, Peibol wrote: [...] As you can see hda3 is the last primary partition and it is beyond the last logical partition. Debian + grub is on hda6 and it boots ok. But I have other Linux distribution (Suse) installed on hda3 and when I tried to boot it, it fails. [...] I think that is some problem with the fact that it is a primary partition after the logical ones. Rather that the partition is beyond some limit (32 GB?). If you only want to boot it then it should be enough to copy the kernel and initrd to ex. debian's /boot (but do keep the correct root=/dev/hda3 parameter). Disclaimer: I have never used Fedora and I can't guarantee this will even work on Debian. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: grub problem with primary partition
On Sat,19.Jul.08, 11:50:10, Andrei Popescu wrote: On Sat,19.Jul.08, 10:36:44, Peibol wrote: [...] As you can see hda3 is the last primary partition and it is beyond the last logical partition. Debian + grub is on hda6 and it boots ok. But I have other Linux distribution (Suse) installed on hda3 and when I tried to boot it, it fails. [...] I think that is some problem with the fact that it is a primary partition after the logical ones. Rather that the partition is beyond some limit (32 GB?). If you only want to boot it then it should be enough to copy the kernel and initrd to ex. debian's /boot (but do keep the correct root=/dev/hda3 parameter). Disclaimer: I have never used Fedora and I can't guarantee this will even work on Debian. s/Fedora/Suse/ Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: GRUB problem?
Keith Willis schreef: Hi, Here's a weird one... I've noticed that as soon as the GRUB boot-loader runs, I lose my DVD-RW drive. It functions normally if I jump into the BIOS setup at boot time, then ceases to respond the moment GRUB runs, so that even if I boot into WinXP, the drive does not show up. Restoring the MBR makes the problem go away, so it is definitely not a drive problem. I can't see anything specifically about this at the GNU GRUB home page. Anyone have any ideas, please? Thx, klw -- http://www.bytebrothers.co.uk (not currently working) PGP key ID 0xEB7180EC I had a problem with GRUB last week, it seemed that 'timeout' didn't work. I also noted that I had the same problem with LILO and even when starting a live-cd. When I unplugged the keyboard I had no problem! As you can imagine the problem disappeared when I bought a new keyboard. The strange fact was that the only way in which I found the problem was when booting. After the boot process the keyboard worked fine. Maybe your problem is somehow similar? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub problem
}}Hello,Hi.}} But how can I reinstall GRUB from the Debian CD without}}passing through the partitioner?Probably booting with a live-cd (Knoppix) and chroot-ing!!Hope it help you!Bye
Re: grub problem
On Wed, Jun 07, 2006 at 12:27:34PM -0300, Marcelo Chiapparini wrote: Hello, I have a machine with Windows XP and Debian (sarge) installed. The boot manager is GRUB. The machine was working fine, but suddently GRUB doesn't boot the system any more. At boot time I get the following: GRUB loading stage 1.5 GRUB loading, please wait... and the system freezes. I wonder if reinstalling GRUB from the Debian CD will fix things. But how can I reinstall GRUB from the Debian CD without passing through the partitioner? I want to keep all the information present in the disk, and each time I want to jump directly to install GRUB, I am faced with the partitioner. (and no, I don't have a rescue disk...) you could switch to a virtual terminal (ctrl-alt-f2) from the installer and run what you need from there maybe A signature.asc Description: Digital signature
Re: Grub-Problem nach Partitionierung mit cfdisk
Am Mittwoch, 2. November 2005 10:58 schrieb Ruediger Noack: Moin, Auch Moin, ich bin noch dabei, mein Notebook einzurichten. Installiert sind Ubuntu, SuSE und XP. Hier der funktionsfähige Ausgangszustand: Wo ist denn Debian? ;-) Device Boot Start End Blocks Id System /dev/hda1 * 1 2437512284968+ 7 HPFS/NTFS /dev/hda2 24376 34778 5243112 83 Linux /dev/hda3 39988 11628038451577+ f W95 Ext'd (LBA) /dev/hda5 40001 44160 2096608+ 7 HPFS/NTFS /dev/hda6 44161 54315 5118088+ b W95 FAT32 /dev/hda7 114001 116280 1149120 82 Linux swap / Solaris /dev/hda8 54316 62061 3903763+ 83 Linux /dev/hda8 ist die root-Partition von Ubuntu. Von hier wird auch grub konfiguriert. Wieso ist diese Partition hda8? Sollte sich die Numerierung nicht der Anordnung der Partionen auf der Platte folgen? D.h. dein ubuntu sollte auf hda7 liegen? Schmeiß' doch probeweise mal die swap 'raus, dann hast du wieder eine logische Folge von Partitionsbezeichnungen, die der Reihenfolge auf der HD entspricht. Ubuntu müßte dann auf hda7 wandern, dann kannst du die swap (hda8) und die LVM (hda9) wieder anlegen. Ich habe keine Ahnung ob das so geht, würde es aber versuchen. Dein Notebook hat hoffentlich genug RAM, daß es auch mal kurz ohne swap auskommt... Ähnlichen Ärger hatte ich auch mal als ich eine Partition ganz ans Ende gelegt hatte mit free space dazwischen, seither mach' ich das nicht mehr. Ich habe nun ab Zylinder 62062 eine 10G große LVM-Partition mit cfdisk eingerichtet. Diese wurde hda7. Die bisherigen hda7 und hda8 verschoben sich also nach hinten. Ich passte dementsprechend noch die menu.lst an. Nun das Problem, grub grummelt: GRUB loading, please wait... Error 17 Hier hängt die Kiste. Keine Eingabe ist möglich, nur auf Strg Alt Entf reagiert die Kiste noch. Was ist hier passiert? Wie muss ich unter diesen Voraussetzungen die Partitionen anlegen und grub konfigurieren? Danke für erleuchtende Tipps. Rüdiger Tschüss dirk
Re: Grub-Problem nach Partitionierung mit cfdisk
Sorry Dirk, sollte natürlich an die Liste gehen. Bin webmailen nicht mehr gewöhnt. ;-) --- Dirk Wernien [EMAIL PROTECTED] schrieb: Am Mittwoch, 2. November 2005 10:58 schrieb Ruediger Noack: Installiert sind Ubuntu, SuSE und XP. Wo ist denn Debian? ;-) $ cat /etc/debian_version testing/unstable Wieso ist diese Partition hda8? Sollte sich die Numerierung nicht der Anordnung der Partionen auf der Platte folgen? D.h. dein ubuntu sollte auf hda7 liegen? Schmeiß' doch probeweise mal die swap 'raus, dann hast Klang nach einer gute Idee und habe deshalb die swap-Partition entfernt. Hat mich Stunden gekostet, bis ich wieder einen bootfähigen MBR hatte. Booten von HD brachte besagten Hänger, als Rescue-CD hatte ich nur eine SuSE zu Hand, dort brachte grub-install auf die Ubuntu-Partition merkwürdige Fehler, aber ich kann jetzt wieder alle System booten. Eine Ursache für die Problemchen war wohl, dass mir cfdisk beim Löschen der swap-Partition auch die komplette erweiterte Partition verkleinert hat. /dev/hda3 39988 6206111125012+ f W95 Ext'd (LBA) Wie bekomme ich die denn jetzt wieder bis ans Ende der HD (Cylinder 116280) vergrößert? Gruß Rüdiger PS. Sitze heute Abend wohl wieder internetfrei im Hotel, kann also evtl. erst morgen mailtechnisch auf Hinweise reagieren. -- ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Grub-Problem nach Partitionierung mit cfdisk
Am Mittwoch, 2. November 2005 17:51 schrieb Ruediger Noack: Wieso ist diese Partition hda8? Sollte sich die Numerierung nicht der Anordnung der Partionen auf der Platte folgen? D.h. dein ubuntu sollte auf hda7 liegen? Schmeiß' doch probeweise mal die swap 'raus, dann hast Klang nach einer gute Idee und habe deshalb die swap-Partition entfernt. Hat mich Stunden gekostet, bis ich wieder einen bootfähigen MBR hatte. Booten von HD brachte besagten Hänger, als Rescue-CD hatte ich nur eine SuSE zu Hand, dort brachte grub-install auf die Ubuntu-Partition merkwürdige Fehler, aber ich kann jetzt wieder alle System booten. PUH! Diese Spiele mit fdisk + Consorten können einem graue Haare wachsen lassen... Und ubuntu ist jetzt hda7? Eine Ursache für die Problemchen war wohl, dass mir cfdisk beim Löschen der swap-Partition auch die komplette erweiterte Partition verkleinert hat. Scheißding - hat ihm keiner gesagt, daß er das tun soll. (Vielleicht liegt das daran, daß Du noch eine primäre Partition 'übrig' hast.) Ich glaube mit fdisk wäre das nicht passiert. Das ist nicht so modern und denkt (hier unerwünschterweise) mit. /dev/hda3 39988 6206111125012+ f W95 Ext'd (LBA) Wie bekomme ich die denn jetzt wieder bis ans Ende der HD (Cylinder 116280) vergrößert? Ich würde sagen, daß cfdisk das dann auch automatisch macht, wenn Du eine logische Partition in dem Bereich anlegst. Kann das nicht das Partitionier-Modul von yast2? Gruß Rüdiger Tschüss dirk
Ant: Re: Grub-Problem nach Partitionierung mit cfdisk
--- Dirk Wernien [EMAIL PROTECTED] schrieb: Am Mittwoch, 2. November 2005 17:51 schrieb Ruediger Noack: Und ubuntu ist jetzt hda7? Ja. Eine Ursache für die Problemchen war wohl, dass mir cfdisk beim Löschen der swap-Partition auch die komplette erweiterte Partition verkleinert hat. Scheißding - hat ihm keiner gesagt, daß er das tun soll. (Vielleicht liegt das daran, daß Du noch eine primäre Partition 'übrig' hast.) Ich glaube mit fdisk wäre das nicht passiert. Das ist nicht so modern und denkt (hier unerwünschterweise) mit. Ich habe bisher immer fdisk benutzt, aber da die man page davor lautstark warnt, habe ich es mal mit cfdisk versucht. Ich würde sagen, daß cfdisk das dann auch automatisch macht, wenn Du eine logische Partition in dem Bereich anlegst. War leider nicht möglich, falls ich da nichts übersehen habe. Kann das nicht das Partitionier-Modul von yast2? Ich kenne mich mit yast nicht aus. Ich habe erst seit einigen Tagen zusätzlich SuSE auf der Kiste, weil der hier beim Kunden auch als Client benutzt wird. Meine Klickversuche durch yast endeten immer mit dem Hinweis, dass er eine erweitete Partition nicht anrühren wollte. Ist aber jetzt erledigt. Ich habe mich gestern im Hotelzimmer an parted, was ich bisher nie benutzt hatte, erinnert. Dessen resize-Funktion hat seinen Job zwar mit erhobenem Zeigefinger, aber klaglos und korrekt ausgeführt. ~# fdisk -l /dev/hda Disk /dev/hda: 60.0 GB, 60011642880 bytes 16 heads, 63 sectors/track, 116280 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2437512284968+ 7 HPFS/NTFS /dev/hda2 24376 34778 5243112 83 Linux /dev/hda3 39988 11628038451672f W95 Ext'd (LBA) /dev/hda5 40001 44160 2096608+ 7 HPFS/NTFS /dev/hda6 44161 54315 5118088+ b W95 FAT32 /dev/hda7 54316 62061 3903763+ 83 Linux /dev/hda8 62061 9112514648224+ 8e Linux LVM Ich habe jetzt meine LVM-Partition und genügend Reserven. :-) Danke fürs Mitdenken. Rüdiger -- ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
bios - Re: GRUB problem (long, description of BOOT)
hi ya mike On Tue, 27 Sep 2005, Mike McCarty wrote: the tracking info is dependant on the filesystem It is not. i beg to differ ... different fs has different disk structure to tune itself for various things to make it better or worst than other fs It is used by the uController on the disc itself to servo. the disk controller on the disk does its magic too but that is 1 level lower than the track info needed by the fs the disk controller also does all the bad-block remapping so that the fs thinks it has a clean 100GB of disks even if its using 110GB of actual physical space A FS format should not disturb the low level format. no it doesne't, but it uses that info in conjunction with what it needs to be faster/better Anyone who redoes the low level format is taking his figurative life into his own hands. those are the folks that insist on using dd semi proof: a) partition and format with xfs your test disk ( /dev/hdc ) with your favorite too let's say test disk is all xfs and 8 partitions b) use dd if=/dev/MasterDisk of=/dev/hdc lets say MasterDisk is reiserfs after the dd, you have lost all info about /dev/hdc and the test disk is now a clone of MasterDisk ( the test disk is now 1 partition and reiserfs ) c) mark some blocks as bad with badblock command and see what dd does to those sectors when you copy one disk to another some intermingle track info ( aka servo data ) with data Not without changing the ROM contained on the disc. maybe there is a difference in what you call track info and what i'm calling track info .. servo data vs meta-data vs ??-data servo data is on one platter as yu say, OR interspersed amongst each track ( not on one platter ) meta-data is for the ext3, xfs, jfs, dos, etc I'm afraid that dd cannot see that information, nor can it destroy it. sure it can ... try it ... the servo data is gone that track-1234 head-6 sector-47 is not longer marked as bad block because dd overwrote it if the bad block is marked at the disk controller, than yes, dd cannot change those badblocks and servo info bad blocks is part of servo data ?? and is managed in various wys fdformat or superformat ( low level formatting ) is done separately from the filesystem formatting Yes, fdformat does the first two levels, but not the third. yup mkdos, format a:, mkfs.vfat, ... Which does the third level. (Though not the fourth.) yup There is only one MBR per physical disc. Each partition has a BR, not an MBR. okay ... i'll bite with the mbr vs br not 100% sure but we all know any of these are bootable, each having enough info to make it bootable ( maybe a difference in terminology ) /dev/hda1 windoze /dev/hda2 debian /dev/hda3 redhat each partition has its own MBR allowing it to be bootable I'm afraid you have some misconceptions yourself. just a difference of vocabulary of mbr or br per your correction important to note that its active, but is NOT required to boot Depends on what boot program one is using. Since the current context is Windows, that is the context I used. yup... i'm using lilo/grub context... nto sure if loadlin needs the active boot flag the boot sequence is configurable in the BIOS setting It may or may not be configurable in the ROM boot program settings. sure it is ... always have been since 1979 ... bootsequence: floppy cdrom hda hdc usb-stick network - mix and match as you need and change it - it is also stored in nvram or flash portion of the bios rom - you know that once you change the boot sequence it always uses that boot sequence .. and you do NTO have to tell it again to boot from usb-stick or whatever you list first 512 bytes 2 bytes for boot flag 64 4 partitons of 16 bytes each 446 is the actual mbr As I said, some consider the PT to be separate from the MBR, some consider it to be part of the MBR. yup... c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tuesday 27 September 2005 07:05 pm, Jeremy Merritt wrote: I have been having a problem getting my GRUB bootloader to return on boot. No matter what I do, it keeps going to XP. I consulted with other people on this list and got some good input. But have run into a dead end again. Can someone analyze these steps and tell me what I'm doing wrong, or what I need to do to get the GRUB menu to return the way it was when I first installed Debian: Steps so far: 1. Boot up with live CD (Knoppix) 2. Activate shell and go root 3. Mount /dev/hda5 as /mnt/hda5 4. chroot /mnt/hda5 /bin/bash 5. grub-install /dev/hda5 -- Reports successful install but no results on bootup i can't recall exactly what but i've had problems doing exactly what you described. and since, i've adopted a habit of keeping a GRUB boot disk around. (it's fairly trivial to create a bootable floppy. only slightly tougher to create a bootable CD.) i then use grub shell, to do a 'setup' of the drive. actually, it's easier to do this (i actually have a DHCP/network boot setup to launch grub should i not find my GRUB disk): 1) boot using the floppy/CD so that you have a GRUB screen. 2) type 'c' (i think) to get to the grub command line. 3) type 'root(hdX)' 4) type 'menu /boot/grub/menu.lst' 5) and boot like normal. once you get to your shell prompt, do a grub-install there. i wrote the instructions from memory so it might be a little our of wack. like i said, i can't remember the decisions that made me arrive at this solution but what i described above has bailed me out consistantly. hope it helps, anoop. [EMAIL PROTECTED] fdisk -l information (hda5=Mandrake, hdb2=Debian, system is booting from hda1=XP): Disk /dev/hda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS /dev/hda2 2434 4865 19535040 5 Extended /dev/hda5 2434 3197 6136798+ 83 Linux /dev/hda6 3198 3337 1124518+ 82 Linux swap /dev/hda7 3338 4865 12273628+ 83 Linux Disk /dev/hdb: 61.4 GB, 61492838400 bytes 255 heads, 63 sectors/track, 7476 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA) /dev/hdb2 * 3189 7298 33013575 83 Linux /dev/hdb3 7299 7476 1429785 5 Extended /dev/hdb5 7299 7476 1429753+ 82 Linux swap Disk /dev/hdd: 30.0 GB, 30020272128 bytes 255 heads, 63 sectors/track, 3649 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 3649 29310561 83 Linux __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bios - Re: GRUB problem (long, description of BOOT)
Alvin Oga wrote: hi ya mike Hi yourself. Glad to meet you. I hope this message doesn't seem pugnacious. It isn't intended to be. But your response seems to me to contain some factual and comprehensional errors. Since this is a technical forum, I don't feel comfortable allowing what I percieve to be the technical failings to go unnoted. No personal criticism is intended in any way. I appreciate your attempt to clarify my message. You are obviously smart and intelligent, but you weren't THERE. I was. On Tue, 27 Sep 2005, Mike McCarty wrote: the tracking info is dependant on the filesystem It is not. i beg to differ ... different fs has different disk structure to tune itself for various things to make it better or worst than other fs It is used by the uController on the disc itself to servo. the disk controller on the disk does its magic too but that is 1 level lower than the track info needed by the fs Precisely my point. I guess I didn't make myself clear enough. I was talking about a low-level format, not a file system thing. the disk controller also does all the bad-block remapping so that the fs thinks it has a clean 100GB of disks even if its using 110GB of actual physical space No longer done by the disc controller. With the advent of Advanced Technology attachment (ATA) (incorrectly referred to by many as Integrated Drive Electronics [IDE]) drives, the intelligence is no longer on the controller board, but rather on the disc itself. Modern controller boards are just I/O expansion ports. The controller logic is now on the disc itself. A FS format should not disturb the low level format. no it doesne't, but it uses that info in conjunction with what it needs to be faster/better Anyone who redoes the low level format is taking his figurative life into his own hands. those are the folks that insist on using dd No, dd cannot disturb the low-level format. That requires talking to the uC on the disc itself (usually), using proprietary commands. [snip due to talking at cross-purposes] maybe there is a difference in what you call track info and what i'm calling track info .. servo data vs meta-data vs ??-data servo data is on one platter as yu say, OR interspersed amongst each track ( not on one platter ) Yes, I'm talking about servo data, which cannot be seen by dd or any other normal (or even driver level) accesses. meta-data is for the ext3, xfs, jfs, dos, etc I'm afraid that dd cannot see that information, nor can it destroy it. sure it can ... try it ... the servo data is gone that track-1234 head-6 sector-47 is not longer marked as bad block because dd overwrote it Certainly it can write to the reserved areas of the disc (I mean reserved by the file system). But it cannot write to the servo area (which is used by the uC on the disc to ensure proper head alignment). if the bad block is marked at the disk controller, than yes, dd cannot change those badblocks and servo info bad blocks is part of servo data ?? and is managed in various wys Bad blocks and bad track info are used by different levels of the system. The bad blocks are a file level thing, and can be modified or obliterated by dd, as you note. The bad track info and sector remapping is a low level construct, and cannot be modified by dd. The bad block information stored in the File Allocation Table (FAT) was/is separate from the low-level bad track marking used by a low-level format. You may be confusing this information (not stored in a FAT for for non-FAT FS, naturally) used by the file system with the low-level bad track remapping. You are using the word servo in a way I don't recognize. I quote from Funk Wagnalls New Comprehensive [QUOTE MODE ON] servo- /combining form/ In technical use, auxiliary: servomechanism [L servus a slave]. servomechanism n. Any of various relay devices which can be actuated by comparatively weak force in the automatic control of a complex machine, instrument, operation, or process, as artillery fire, the course of an airplane or ship, etc. [QUOTE MODE OFF] The servo tracks are used to supply the weak force used in automatic control of the head movement mechanism. The older MFM and RLL drives used stepper motors and a wound band of steel to move the heads. This resulted in gradual creep of the tracks as formatted on the disc with temperature. We used to have to warm up the discs to operating temperature before low-level formatting them (laying down tracks and sectors). Over time, the tracks would also creep due to various changes in the movement mechanism, requiring periodic (like every few months) redoing of the low level format. Eventually, the head movement mechanism would develop hysteresis, leading to an unusable disc. (I have a few of those around :-) When the newer voice coil technology came out, we all regretted the loss of one entire disc surface, but we all heaved a great sigh of relief at not
Re: GRUB problem
anoop aryal wrote:
On Tuesday 27 September 2005 07:05 pm, Jeremy Merritt wrote:
I have been having a problem getting my GRUB
bootloader to return on boot. No matter what I do, it
keeps going to XP. I consulted with other people on
this list and got some good input. But have run into a
dead end again. Can someone analyze these steps and
tell me what I'm doing wrong, or what I need to do to
get the GRUB menu to return the way it was when I
first installed Debian:
Steps so far:
1. Boot up with live CD (Knoppix)
2. Activate shell and go root
3. Mount /dev/hda5 as /mnt/hda5
4. chroot /mnt/hda5 /bin/bash
5. grub-install /dev/hda5 -- Reports successful
install but no results on bootup
i can't recall exactly what but i've had problems doing exactly what you
described. and since, i've adopted a habit of keeping a GRUB boot disk
around. (it's fairly trivial to create a bootable floppy. only slightly
tougher to create a bootable CD.) i then use grub shell, to do a 'setup' of
[snip]
This is excellent advice, and I keep one around, too.
Rather than post from memory,
http://www.gnu.org/software/grub/manual/html_node/Creating-a-GRUB-boot-floppy.html
It's also a good idea to have a hard copy of how to boot from
the GRUB floppy. I keep one of those around, too. :-)
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bios - Re: GRUB problem (long, description of BOOT)
hi ya On Wed, 28 Sep 2005, Mike McCarty wrote: You are obviously smart and intelligent, but you weren't THERE. I was. i been playing with them removable 14 disk platters and stripping um and reassemble um and stick it back into the dg/dec/si washing machines the disk controller on the disk does its magic too but that is 1 level lower than the track info needed by the fs Precisely my point. I guess I didn't make myself clear enough. I was talking about a low-level format, not a file system thing. same here .. but never mind, not important ... we both saying the same thingie ma jiggie No longer done by the disc controller. With the advent of Advanced Technology attachment (ATA) (incorrectly referred to by many as Integrated Drive Electronics [IDE]) drives, the intelligence is no longer on the controller board, but rather on the disc itself. Modern controller boards are just I/O expansion ports. The controller logic is now on the disc itself. there's the disk controllers on the disk drive .. there's the disk controllers on the motherboard ( ide card ) both can do the same work ... or some of the work .. No, dd cannot disturb the low-level format i say it does ... simple experiment to see bad blocks and track info go bonkers... when overwritten by dd ... - dd and gohost et.al. is low level format and copying That requires talking to the uC on the disc itself (usually), using proprietary commands. unless you're refrring to disk controller firmware stuff is yet even loower than low level format servo data is on one platter as yu say, OR interspersed amongst each track ( not on one platter ) Yes, I'm talking about servo data, which cannot be seen by dd or any other normal (or even driver level) accesses. i think we;re talking about the different kidns of servo data ... created/maintained at different levels and i'm not talking about file system junk either but it doesnt matter ... my point is different apps plays with different data and is NOT jst the factory ( wd, maxtor, seagate ) that can create these servo data sure it can ... try it ... the servo data is gone that track-1234 head-6 sector-47 is not longer marked as bad block because dd overwrote it Certainly it can write to the reserved areas of the disc (I mean reserved by the file system). you keep going to filesytem there is reserved space for servo dta too as you noted and that data can be over written by dd depending on its purpose and where and when it is written But it cannot write to the servo area (which is used by the uC on the disc to ensure proper head alignment). am not talking about the head alignment and gaps or anything Bad blocks and bad track info are used by different levels of the system. bingo !!!... and written by different programs and firmware and apps The bad blocks are a file level thing no... bad blaocks can also be marked as bad by the disk firmware with whatever code it wants touse to indicate a bad sector or bad track and which one is its replacement and can be modified or obliterated by dd, as you note. The bad track info and sector remapping is a low level construct, and cannot be modified by dd. sure it can ... and that is my point ... but that's where we disagree ... not a biggie .. The bad block information stored in the File Allocation Table (FAT) don't care about that ... that is a file system issue ... now low level servo data used by a low-level format. You may be confusing this information (not stored in a FAT for for non-FAT FS, naturally) used by the file system with the low-level bad track remapping. nope ... not confusing fs related junk vs servo data.. The servo tracks are used to supply the weak force used in automatic control of the head movement mechanism. there are other things that is part of servo data ... like gaps ... and other whacky stuff The older MFM and RLL drives used stepper motors and a wound band of steel to move the heads. nobody uses mfs/rll anymore .. non-issue for dd just a difference of vocabulary of mbr or br per your correction I've been formatting hard discs since 1984 when each level was hee heee ... i been doing that since 1973... or sooner ... gotcha including writing and debugging them silly disk controllers on decs and dg ... and few other assorted junk ... long before PCs came alone The boot record (aka boot sector) is contained on each volume. It contains the BIOS Parameter Block (BPB). we been over all this .. and i agreed w/ ya about the difference between with br vs mbr There has been in past some confusion of the terms BR, BPB, MBR, and PT. yup... and 99.99% of the folks don't worry about the differences Well, I repeatedly used in my message the word traditionally, which was *supposed* to be a hint that there are other ways of doing things. yup... BUT, this guy has a problem with a Windows MBR on his disc not recognizing/using the
Re: GRUB problem
On Wed, Sep 28, 2005 at 10:34:43AM -0500, Mike McCarty wrote: described. and since, i've adopted a habit of keeping a GRUB boot disk around. (it's fairly trivial to create a bootable floppy. only slightly tougher to create a bootable CD.) i then use grub shell, to do a 'setup' of [snip] This is excellent advice, and I keep one around, too. Rather than post from memory, http://www.gnu.org/software/grub/manual/html_node/Creating-a-GRUB-boot-floppy.html I remember a while ago the instructions to create a grub floppy weren't good, don't know if this is the case here for this link, I would have to try it. There was some modification that had to be made somewhere. Any way, there was some issue with it ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bios - Re: GRUB problem (long, description of BOOT)
Alvin Oga wrote:
hi ya
On Wed, 28 Sep 2005, Mike McCarty wrote:
[snip]
Yes, I'm talking about servo data, which cannot be seen
by dd or any other normal (or even driver level) accesses.
i think we;re talking about the different kidns of servo
data ... created/maintained at different levels
and i'm not talking about file system junk either
but it doesnt matter ... my point is different
apps plays with different data and is NOT
jst the factory ( wd, maxtor, seagate ) that can
create these servo data
sure it can ... try it ... the servo data is gone
that track-1234 head-6 sector-47 is not longer
marked as bad block because dd overwrote it
Certainly it can write to the reserved areas of the
disc (I mean reserved by the file system).
you keep going to filesytem
No, you do.
there is reserved space for servo dta too as you noted
and that data can be over written by dd depending
on its purpose and where and when it is written
But it cannot
write to the servo area (which is used by the uC on the
disc to ensure proper head alignment).
am not talking about the head alignment and gaps or anything
But I am, and was, and have been, and have been trying
(unsuccessfully) to point that out. The head alignment
(servo) information cannot be diddled by dd. The low-level
format information is not accessible to high-level programs
(like dd). It requires special interface. One cannot clobber
the sector formatting by using dd, which sits on top of
that.
[snip]
This is probably as far as we can (profitably) go.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bios - Re: GRUB problem (long, description of BOOT)
hi ya On Wed, 28 Sep 2005, Mike McCarty wrote: :-) you keep going to filesytem No, you do. i see we're assumign too many stuff .. i never once said aything but servo info being the same as fs info .. etc..etc am not talking about the head alignment and gaps or anything But I am, and was, and have been, and have been trying (unsuccessfully) to point that out. The head alignment (servo) information cannot be diddled by dd. The low-level format information is not accessible to high-level programs (like dd). again, if you think it cannot be done ... that's your option i'm saying i can trivially wipe out your partitions and some of the servo info especially badblock data with dd ... i think the badblock is what the confusion is.. - it can be part of the servo and/or part of the formatting/partitioning .. i consider badblock info part of servo data since it can be done by the controller on the disk itself ... It requires special interface. nope ... you concurred earlier that fdformat and superformat is low level formatt ... it doesn't need any special interface One cannot clobber the sector formatting by using dd, which sits on top of that. simple case is to convert a 512byte/sector to 2Kbyte/sector on the disk - ie .. not to be confused with fs block size This is probably as far as we can (profitably) go. yup.. have fun ... thanx for the vocubulary lessons :-0 c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
Antonio Rodriguez wrote:
On Wed, Sep 28, 2005 at 10:34:43AM -0500, Mike McCarty wrote:
described. and since, i've adopted a habit of keeping a GRUB boot disk
around. (it's fairly trivial to create a bootable floppy. only slightly
tougher to create a bootable CD.) i then use grub shell, to do a 'setup'
of
[snip]
This is excellent advice, and I keep one around, too.
Rather than post from memory,
http://www.gnu.org/software/grub/manual/html_node/Creating-a-GRUB-boot-floppy.html
I remember a while ago the instructions to create a grub floppy
weren't good, don't know if this is the case here for this link, I
would have to try it. There was some modification that had to be made
somewhere. Any way, there was some issue with it ...
Maybe this is more reliable?
http://www.gnu.org/software/grub/grub-legacy-faq.en.html
I know I created a GRUB floppy some time back. I'd have to find
some old notes to remember the exact steps.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Wed, Sep 28, 2005 at 03:11:18PM -0500, Mike McCarty wrote: I know I created a GRUB floppy some time back. I'd have to find some old notes to remember the exact steps. Mike This way from /usr/share/doc/grub/README.Debian.gz cat /boot/grub/stage1 /boot/grub/stage2 /dev/fd0 works fine, I just tried it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
Antonio Rodriguez wrote:
On Wed, Sep 28, 2005 at 03:11:18PM -0500, Mike McCarty wrote:
I know I created a GRUB floppy some time back. I'd have to find
some old notes to remember the exact steps.
Mike
This way from /usr/share/doc/grub/README.Debian.gz
cat /boot/grub/stage1 /boot/grub/stage2 /dev/fd0
works fine, I just tried it.
That should have the same effect as the instructions in the URL
I posted, which gives
# dd if=stage1 of=/dev/fd0 bs=512 count=1
# dd if=stage2 of=/dev/fd0 bs=512 seek=1
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
Jeremy Merritt wrote: I have been having a problem getting my GRUB bootloader to return on boot. No matter what I do, it keeps going to XP. I consulted with other people on this list and got some good input. But have run into a dead end again. Can someone analyze these steps and tell me what I'm doing wrong, or what I need to do to get the GRUB menu to return the way it was when I first installed Debian: Steps so far: 1. Boot up with live CD (Knoppix) 2. Activate shell and go root 3. Mount /dev/hda5 as /mnt/hda5 4. chroot /mnt/hda5 /bin/bash 5. grub-install /dev/hda5 -- Reports successful install but no results on bootup fdisk -l information (hda5=Mandrake, hdb2=Debian, system is booting from hda1=XP): Disk /dev/hda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS /dev/hda2 2434 4865 19535040 5 Extended /dev/hda5 2434 3197 6136798+ 83 Linux /dev/hda6 3198 3337 1124518+ 82 Linux swap /dev/hda7 3338 4865 12273628+ 83 Linux Disk /dev/hdb: 61.4 GB, 61492838400 bytes 255 heads, 63 sectors/track, 7476 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA) /dev/hdb2 * 3189 7298 33013575 83 Linux /dev/hdb3 7299 7476 1429785 5 Extended /dev/hdb5 7299 7476 1429753+ 82 Linux swap Disk /dev/hdd: 30.0 GB, 30020272128 bytes 255 heads, 63 sectors/track, 3649 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 3649 29310561 83 Linux __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com From your listing, it seems that you have multiple bootable partitions. You should only have one. On hda, it seems that you are booting from the windoze partition, in which case, unless you have configured the XP boot-loader for linux, it will always boot into XP. If hda2 is / for the first linux system, I would make that bootable and run grub from there. I think you can also overwrite the MBR. I have a dual boot laptop with XP and debian. I overwrote the MBR and boot everything from GRUB. Art Edwards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
If having multiple partitions is the problem or part of the problem, how do I make /dev/hda2 bootable and make the others not bootable? Is that the only thing that needs to be done in addition to the other steps? --- Art Edwards [EMAIL PROTECTED] wrote: Jeremy Merritt wrote: I have been having a problem getting my GRUB bootloader to return on boot. No matter what I do, it keeps going to XP. I consulted with other people on this list and got some good input. But have run into a dead end again. Can someone analyze these steps and tell me what I'm doing wrong, or what I need to do to get the GRUB menu to return the way it was when I first installed Debian: Steps so far: 1. Boot up with live CD (Knoppix) 2. Activate shell and go root 3. Mount /dev/hda5 as /mnt/hda5 4. chroot /mnt/hda5 /bin/bash 5. grub-install /dev/hda5 -- Reports successful install but no results on bootup fdisk -l information (hda5=Mandrake, hdb2=Debian, system is booting from hda1=XP): Disk /dev/hda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS /dev/hda2 2434 4865 19535040 5 Extended /dev/hda5 2434 3197 6136798+ 83 Linux /dev/hda6 3198 3337 1124518+ 82 Linux swap /dev/hda7 3338 4865 12273628+ 83 Linux Disk /dev/hdb: 61.4 GB, 61492838400 bytes 255 heads, 63 sectors/track, 7476 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA) /dev/hdb2 * 3189 7298 33013575 83 Linux /dev/hdb3 7299 7476 1429785 5 Extended /dev/hdb5 7299 7476 1429753+ 82 Linux swap Disk /dev/hdd: 30.0 GB, 30020272128 bytes 255 heads, 63 sectors/track, 3649 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 3649 29310561 83 Linux __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com From your listing, it seems that you have multiple bootable partitions. You should only have one. On hda, it seems that you are booting from the windoze partition, in which case, unless you have configured the XP boot-loader for linux, it will always boot into XP. If hda2 is / for the first linux system, I would make that bootable and run grub from there. I think you can also overwrite the MBR. I have a dual boot laptop with XP and debian. I overwrote the MBR and boot everything from GRUB. Art Edwards __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, 27 Sep 2005, Jeremy Merritt wrote: If having multiple partitions is the problem or part of the problem, NOT the problem how do I make /dev/hda2 bootable and make the others not bootable? take it out with the bios so that it doesn't check it or # delete the MBR on the whole disk dd if=/dev/zero of=/dev/hda bs=446 count=1 # delete the MBR on partition1 dd if=/dev/zero of=/dev/hda1 bs=446 count=1 # delete the MBR on partition2 dd if=/dev/zero of=/dev/hda2 bs=446 count=1 but do NOT do dd if you donno what you're doing and the consequence ( you WILL lose data ) Is that the only thing that needs to be done in addition to the other steps? a partition or disk is bootable when: a) you explicitly tell lilo or grub boot=/dev/hda2 - the mbr of just this partition or boot=/dev/hda - the mbr of the whole thingie b) you do tell the bios with: fdisk a 2 - set the bootable flag on partition2 you can check bytes 511 and 512 of track-0, head-0, sector-0 ( aka the MBR of the disk ) same for the mbr of the partition... but starting at whever you started the partition at nowdays, the bios and bootloaders try to be smarter and doesn't care if the bootable flag is set or not if you tell it it's bootable and there's nothing to boot and you only have 1 bootable media ( anything you can boot from ), you will get no operating sysstem found c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
If you can boot from cdrom, use cfdisk to toggle the boot properties of the partitions (as root, of course). Art Edwards Jeremy Merritt wrote: If having multiple partitions is the problem or part of the problem, how do I make /dev/hda2 bootable and make the others not bootable? Is that the only thing that needs to be done in addition to the other steps? --- Art Edwards [EMAIL PROTECTED] wrote: Jeremy Merritt wrote: I have been having a problem getting my GRUB bootloader to return on boot. No matter what I do, it keeps going to XP. I consulted with other people on this list and got some good input. But have run into a dead end again. Can someone analyze these steps and tell me what I'm doing wrong, or what I need to do to get the GRUB menu to return the way it was when I first installed Debian: Steps so far: 1. Boot up with live CD (Knoppix) 2. Activate shell and go root 3. Mount /dev/hda5 as /mnt/hda5 4. chroot /mnt/hda5 /bin/bash 5. grub-install /dev/hda5 -- Reports successful install but no results on bootup fdisk -l information (hda5=Mandrake, hdb2=Debian, system is booting from hda1=XP): Disk /dev/hda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS /dev/hda2 2434 4865 19535040 5 Extended /dev/hda5 2434 3197 6136798+ 83 Linux /dev/hda6 3198 3337 1124518+ 82 Linux swap /dev/hda7 3338 4865 12273628+ 83 Linux Disk /dev/hdb: 61.4 GB, 61492838400 bytes 255 heads, 63 sectors/track, 7476 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA) /dev/hdb2 * 3189 7298 33013575 83 Linux /dev/hdb3 7299 7476 1429785 5 Extended /dev/hdb5 7299 7476 1429753+ 82 Linux swap Disk /dev/hdd: 30.0 GB, 30020272128 bytes 255 heads, 63 sectors/track, 3649 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 3649 29310561 83 Linux __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com From your listing, it seems that you have multiple bootable partitions. You should only have one. On hda, it seems that you are booting from the windoze partition, in which case, unless you have configured the XP boot-loader for linux, it will always boot into XP. If hda2 is / for the first linux system, I would make that bootable and run grub from there. I think you can also overwrite the MBR. I have a dual boot laptop with XP and debian. I overwrote the MBR and boot everything from GRUB. Art Edwards __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Re: GRUB problem (long, description of BOOT)
Jeremy Merritt wrote: I have been having a problem getting my GRUB bootloader to return on boot. No matter what I do, it keeps going to XP. I consulted with other people on this list and got some good input. But have run into a dead end again. Can someone analyze these steps and tell me what I'm doing wrong, or what I need to do to get the GRUB menu to return the way it was when I first installed Debian: Steps so far: 1. Boot up with live CD (Knoppix) 2. Activate shell and go root 3. Mount /dev/hda5 as /mnt/hda5 4. chroot /mnt/hda5 /bin/bash 5. grub-install /dev/hda5 -- Reports successful install but no results on bootup You installed GRUB as the boot record (BR) of one of your partitions (/dev/hda5). This will work fine, but it is not what the BIOS will load. I think you need a little more information about how boot is accomplished on IBM PC style computers. If you get that, then I think things will be much more clear. So, here is a brief tutorial on disc partitioning and how boot proceeds. Those who are familiar with this may either skip the rest of this message, or use it as a review, or criticize it for errors or omissions. Discs, to be used, must be formatted. The formatting takes place in levels. The lowest level (sometimes called low-level format) places tracks and sectors on each surface usable on the disc. Modern hard discs reserve one surface to hold tracking information alone, no data. Low-level formatting should not be done on modern hard discs except at the factory. Those of us who used to use MFM and RLL discs are glad for that. (Floppy discs have all three levels done at once by a single program, usually. This causes some confusion. The levels of formatting are actually done in passes even for floppies.) At the second level of formatting, the surface is divided into partitions (floppy discs have only one partition, so they have no partitioning to be done). Traditionally, the first record on the disc, the Master Boot Record (MBR) contains two parts: a small bootstrap program and a Partition Table (PT). Some consider the PT to be separate from the MBR. Also, traditionally, there may only be four (4) partitions defined. However, as time went by discs grew larger, and a percieved need for more partitions grew as well. So the concept of a Primary Partition and an Extended Partition was developed. There could be only four (4) Primary Partitions, but only one (1) Extended Partition. If an Extended Partition existed, it used up one of the entries, so only up to three (3) Primary Partitions could then be defined. The PT uses physical addresses (head, track [or cylinder], and sector). Within the Extended Partition, Logical Partitions (also called Logical Discs or Volumes) could be created. Primary Partitions also contain Volumes, but only one per partition. Each Partition has a type (OS, more or less) and a status. The status could be either Bootable (also called Active) or non-bootable (Inactive). Only up to one (1) partition may be in an Active state, and if so, it must be a Primary Partition. A floppy disc is a single Volume, hard discs may have up to one Volume per Primary Partition, and any number of Volumes (logical partitions or logical discs) in an extended partition. Each Volume has a Boot Record (BR) also called BIOS Parameter Block (BPB). Technically, the BPB is actually a part of the BR, in somewhat the same way the PT is part of the MBR. The BR contains a description of the logical layout of the Volume, like how many reserved sectors there are before the data area, how many logical sectors there are, etc. The BR uses logical disc addressing (logical sector number). The top level of format is the File System (FS). The file system uses allocatable units for addressing. Exactly what an allocatable unit is depends on what FS is being used. Usually the FS presents an Application Programming Interface (API) which uses File Addressing (directories, files, and records within file). fdisk -l information (hda5=Mandrake, hdb2=Debian, system is booting from hda1=XP): Disk /dev/hda: 40.0 GB, 40020664320 bytes This is your first disc. 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS Here is your primary partition which is active. /dev/hda2 2434 4865 19535040 5 Extended This is your extended partition. /dev/hda5 2434 3197 6136798+ 83 Linux /dev/hda6 3198 3337 1124518+ 82 Linux swap /dev/hda7 3338 4865 12273628+ 83 Linux These are volumes inside your extended partition. Each of them may be treated as a partition. Disk /dev/hdb: 61.4 GB, 61492838400 bytes This is your second disc. 255 heads, 63 sectors/track, 7476 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA) This is a primary partition, not bootable. (LBA = Linear Block Addressing, which means
Re: GRUB problem (long, description of BOOT)
Mike McCarty wrote:
[some stuff about formatting discs and boot]
I forgot one more layer of format: OS install.
A volume may have a file system without an OS
on it.
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem (long, description of BOOT)
Wow, what a great explanation. I have read through it, but am going to do another to make sure it's all taken in. Thanks. --- Mike McCarty [EMAIL PROTECTED] wrote: Jeremy Merritt wrote: I have been having a problem getting my GRUB bootloader to return on boot. No matter what I do, it keeps going to XP. I consulted with other people on this list and got some good input. But have run into a dead end again. Can someone analyze these steps and tell me what I'm doing wrong, or what I need to do to get the GRUB menu to return the way it was when I first installed Debian: Steps so far: 1. Boot up with live CD (Knoppix) 2. Activate shell and go root 3. Mount /dev/hda5 as /mnt/hda5 4. chroot /mnt/hda5 /bin/bash 5. grub-install /dev/hda5 -- Reports successful install but no results on bootup You installed GRUB as the boot record (BR) of one of your partitions (/dev/hda5). This will work fine, but it is not what the BIOS will load. I think you need a little more information about how boot is accomplished on IBM PC style computers. If you get that, then I think things will be much more clear. So, here is a brief tutorial on disc partitioning and how boot proceeds. Those who are familiar with this may either skip the rest of this message, or use it as a review, or criticize it for errors or omissions. Discs, to be used, must be formatted. The formatting takes place in levels. The lowest level (sometimes called low-level format) places tracks and sectors on each surface usable on the disc. Modern hard discs reserve one surface to hold tracking information alone, no data. Low-level formatting should not be done on modern hard discs except at the factory. Those of us who used to use MFM and RLL discs are glad for that. (Floppy discs have all three levels done at once by a single program, usually. This causes some confusion. The levels of formatting are actually done in passes even for floppies.) At the second level of formatting, the surface is divided into partitions (floppy discs have only one partition, so they have no partitioning to be done). Traditionally, the first record on the disc, the Master Boot Record (MBR) contains two parts: a small bootstrap program and a Partition Table (PT). Some consider the PT to be separate from the MBR. Also, traditionally, there may only be four (4) partitions defined. However, as time went by discs grew larger, and a percieved need for more partitions grew as well. So the concept of a Primary Partition and an Extended Partition was developed. There could be only four (4) Primary Partitions, but only one (1) Extended Partition. If an Extended Partition existed, it used up one of the entries, so only up to three (3) Primary Partitions could then be defined. The PT uses physical addresses (head, track [or cylinder], and sector). Within the Extended Partition, Logical Partitions (also called Logical Discs or Volumes) could be created. Primary Partitions also contain Volumes, but only one per partition. Each Partition has a type (OS, more or less) and a status. The status could be either Bootable (also called Active) or non-bootable (Inactive). Only up to one (1) partition may be in an Active state, and if so, it must be a Primary Partition. A floppy disc is a single Volume, hard discs may have up to one Volume per Primary Partition, and any number of Volumes (logical partitions or logical discs) in an extended partition. Each Volume has a Boot Record (BR) also called BIOS Parameter Block (BPB). Technically, the BPB is actually a part of the BR, in somewhat the same way the PT is part of the MBR. The BR contains a description of the logical layout of the Volume, like how many reserved sectors there are before the data area, how many logical sectors there are, etc. The BR uses logical disc addressing (logical sector number). The top level of format is the File System (FS). The file system uses allocatable units for addressing. Exactly what an allocatable unit is depends on what FS is being used. Usually the FS presents an Application Programming Interface (API) which uses File Addressing (directories, files, and records within file). fdisk -l information (hda5=Mandrake, hdb2=Debian, system is booting from hda1=XP): Disk /dev/hda: 40.0 GB, 40020664320 bytes This is your first disc. 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS Here is your primary partition which is active. /dev/hda2 2434 4865 19535040 5 Extended This is your extended partition. /dev/hda5 2434 3197 6136798+ 83 Linux /dev/hda6 3198 3337 1124518+ 82 Linux swap /dev/hda7 3338 4865 12273628+ 83 Linux These are volumes inside your extended partition. Each of them may be treated as a
Re: GRUB problem (long, description of BOOT)
hi ya mike :-) i'm even more sleepy now :-) but, some comments On Tue, 27 Sep 2005, Mike McCarty wrote: I think you need a little more information about how boot is accomplished on IBM PC style computers. if a user can't get the machine to boot .. this much detail is probably more than they need ?? a simple post of their config is enough that shows root= and boot= along with the output fdisk -l but .. Discs, to be used, must be formatted. The formatting takes place in levels. The lowest level (sometimes called low-level format) places tracks and sectors on each surface usable on the disc. Modern hard discs reserve one surface to hold tracking information alone, no data. the tracking info is dependant on the filesystem some intermingle track info ( aka servo data ) with data Low-level formatting should not be done on modern hard discs except at the factory. and then there's the joe-blow-me-too-factories that wipe out the low level formatting with dd or equivalent includhing windoze ghost low level format is wiped out when the partition that used exists before is gone and was overwritten by dd dd is a very bad thing to use for multiple reasons .. especially bad blocks but a you say, with todays disks, the platter is relatively defect free that dd'ing will usually work except for those that have too many disk problems - if you did dd, that's bad - if you bought-at-el-cheapo-webstore, that's bad - if you did not put a cooling fan on it, that bad - endless list of why disks are bad, go bad there are other low level format tools .. ( too lazy to go looking for it, since dd is good enough ) (Floppy discs have all three levels done at once by a single program, usually. fdformat or superformat ( low level formatting ) is done separately from the filesystem formatting mkdos, format a:, mkfs.vfat, ... if your floppy doesn't boot, its probably because you didn't do fdformat/superformat or you didn't use rawrite in dos-land or dd in *nix-land Each Partition has a type (OS, more or less) and a status. and an MBR The status could be either Bootable (also called Active) or non-bootable (Inactive). Only up to one (1) partition may be in an Active state, and if so, it must be a Primary Partition. not 100% sure but we all know any of these are bootable, each having enough info to make it bootable ( maybe a difference in terminology ) /dev/hda1 windoze /dev/hda2 debian /dev/hda3 redhat each partition has its own MBR allowing it to be bootable pretty pics http://linux-boot.net/MBR/ 255 heads, 63 sectors/track, 4865 cylinders you forgot to describe the cyliner/head/sector mapping :-) it's sorta hard to have 255 heads on that itty bitty thingie that flies over the disk platter :-) /dev/hda1 * 1 2433 19543041 7 HPFS/NTFS Here is your primary partition which is active. important to note that its active, but is NOT required to boot set that boot flag with a 1 in fdisk Device Boot Start End Blocks Id System /dev/hdb1 1 3188 25607578+ c W95 FAT32 (LBA) This is a primary partition, not bootable. it is not flagged .. but it can still be bootable if lilo has boot=/dev/hdb1 or boot=/dev/hdb Now, how does BOOT take place? more of the gory details ... http://linux-boot.net/Boot.Stage/ After POST, the boot program starts looking for boot devices. Using BIOS settings (technically, these are not BIOS settings, they are boot program settings, but hardly anyone makes that distinction) the devices are searched in order. I am not familiar with the details of boot from USB, SCSI, or CDROM devices, so I do not deal with them here. Look elsewhere if you want that information. the boot sequence is configurable in the BIOS setting scsi cdrom floppy hd0 ( hda ) hd1 ( hdb) usb-hdd usb-fdd network(lan) - you tell it what to check first outside of any partition). It then looks for a Boot Marker (0x55, 0xAA) as the last two bytes of the first sector. the important thing to remember ... as part of the MBR and the 4 disk partitions 512 bytes 2 bytes for boot flag 64 4 partitons of 16 bytes each 446 is the actual mbr If the marker is found, the sector is loaded to a fixed location in memory (I forget the exact address, but I believe it may be 07C0:). Then it is given control. that is the right addy all that is stage_0 booting Otherwise, the OS gets loaded, and hopefully completes the bootstrap. the os loading is stage-1 booting which is where oyu see loading vmlinuz.. Now, you may install GRUB as the MBR boot program, or as a BR boot program. If it is installed into the MBR, then it manages the boot. If not, then it can be installed as the first sector of the partition you are using as /boot.
Re: GRUB problem (long, description of BOOT)
Alvin Oga wrote:
hi ya mike
:-) i'm even more sleepy now :-)
HEY! I SAID it was long!
:-)
but, some comments
On Tue, 27 Sep 2005, Mike McCarty wrote:
I think you need a little more information about how
boot is accomplished on IBM PC style computers.
if a user can't get the machine to boot .. this much
detail is probably more than they need ??
a simple post of their config is enough that shows
root= and boot=
along with the output fdisk -l
but ..
Discs, to be used, must be formatted. The formatting
takes place in levels. The lowest level (sometimes
called low-level format) places tracks and sectors on
each surface usable on the disc. Modern hard discs reserve
one surface to hold tracking information alone, no
data.
the tracking info is dependant on the filesystem
It is not. It is used by the uController on the disc itself
to servo. A FS format should not disturb the low level
format. Anyone who redoes the low level format is taking
his figurative life into his own hands.
some intermingle track info ( aka servo data ) with data
Not without changing the ROM contained on the disc.
Low-level formatting should not be done on modern
hard discs except at the factory.
and then there's the joe-blow-me-too-factories that wipe
out the low level formatting with dd or equivalent
includhing windoze ghost
I'm afraid that dd cannot see that information, nor
can it destroy it.
[snip]
(Floppy discs have all three levels done at once
by a single program, usually.
I should have qualified this with under DOS/Windows
environments.
fdformat or superformat ( low level formatting ) is done
separately from the filesystem formatting
Yes, fdformat does the first two levels, but not the third.
mkdos, format a:, mkfs.vfat, ...
Which does the third level. (Though not the fourth.)
[snip]
Each Partition has a type (OS, more or less) and a status.
and an MBR
There is only one MBR per physical disc. Each partition has
a BR, not an MBR.
The status could be either Bootable (also called Active) or
non-bootable (Inactive). Only up to one (1) partition may be in
an Active state, and if so, it must be a Primary Partition.
not 100% sure but we all know any of these are bootable, each having
enough info to make it bootable
( maybe a difference in terminology )
/dev/hda1 windoze
/dev/hda2 debian
/dev/hda3 redhat
each partition has its own MBR allowing it to be bootable
I'm afraid you have some misconceptions yourself.
pretty pics
http://linux-boot.net/MBR/
255 heads, 63 sectors/track, 4865 cylinders
you forgot to describe the cyliner/head/sector mapping :-)
Well, I didn't want to get into the details of LBA. But, since
you mention it
The original BIOS interface (INT 13) had reserved bit fields in
various registers to request reads and writes. As discs got bigger,
it turned out that the bit fields were not large enough to contain
the maximum number of cylinders (equiv. tracks). So some more unused
bits were co-opted. But eventually even those extra bits ran out.
So, some BIOS allowed one to use a logical/physical interface, called
LBA (Linear Block Addressing) which fiddled the actual number of
heads (usually less than 10) into something huge, while reducing the
actual number of cylinders (equiv. tracks) by the same factor.
In this manner, one could use larger discs while maintaining a
sort of compatible interface.
it's sorta hard to have 255 heads on that itty bitty thingie
that flies over the disk platter :-)
/dev/hda1 * 1 2433 19543041 7 HPFS/NTFS
Here is your primary partition which is active.
important to note that its active, but is NOT required to boot
Depends on what boot program one is using. Since the current
context is Windows, that is the context I used.
[snip]
This is a primary partition, not bootable.
it is not flagged .. but it can still be bootable
if lilo has boot=/dev/hdb1 or boot=/dev/hdb
It is not bootable by the standard MBR Windows installs, which
is the current context.
[snip]
the boot sequence is configurable in the BIOS setting
It may or may not be configurable in the ROM boot program
settings.
[snip]
outside of any partition). It then looks for a Boot Marker
(0x55, 0xAA) as the last two bytes of the first sector.
the important thing to remember ... as part of the MBR
and the 4 disk partitions
512 bytes
2 bytes for boot flag
64 4 partitons of 16 bytes each
446 is the actual mbr
As I said, some consider the PT to be separate from the MBR,
some consider it to be part of the MBR.
[snip]
How many times did you quote that? :-)
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in
Re: GRUB problem (long, description of BOOT)
Jeremy Merritt wrote:
Wow, what a great explanation. I have read through it,
but am going to do another to make sure it's all taken
in. Thanks.
Thank you. I realize that it is very condensed and long. But even
so, it glosses over quite a bit of detail (e.g. LBA and the fact
that one can actually boot from partitions marked
not active, depending on the boot program contained
in the MBR, etc.).
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem (long, description of BOOT)
Mike McCarty wrote: [...] So, here is a brief tutorial on disc partitioning and how boot proceeds. [...] Thanks for the explanation, it was very useful. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub problem
On Tue, 12 Jul 2005, Eugen Wintersberger wrote: (I'm not sure if this was the exact error message). If I do the same installation procedure but install LILO the machine reboots as expected (means that the bootloader works). if lilo works ( boots properly ), than there is nothing wrong with the hardware - i assume you have a boot floppy or boot-cd in case grub wipes out the working lilo MBR what is your /etc/grub.conf and /boot/grub/menu.lst and /boot/grub/devices.map root# grub-install /dev/hdaor whatever is your disk - if grub doesn't work, download the latest CVS version for gnu.org c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB-Problem
Stephan Kulka wrote: Hallo Habe leider den Fehler gemacht Windows XP neu installieren zu müssen ohne den Bootsector zu sichern. Jetzt habe ich wie vor kurzem auf der Liste besprochen, Knoppix gestartet, chroot in mein / Verzeichnis gemacht und grub aufgerufen und wieder in den MBR installiert. Das hat auch prima funktioniert und das alte Startmenü ist wieder da. Doch sobald ich aber einen Linux-Eintrag starten will, wird /boot/vmlinuz nicht gefunden und GRUB gibt den Fehler 15 aus. WO ist mein Denkfehler bzw. was kann ich machen? Gab es da nicht mal lustige Effekte, daß Windows die Partitionen renummeriert hat? -- Bye, Patrick Cornelissen http://www.p-c-software.de ICQ:15885533 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: GRUB-Problem
Stephan Kulka wrote: Jetzt habe ich wie vor kurzem auf der Liste besprochen, Knoppix gestartet, chroot in mein / Verzeichnis gemacht und grub aufgerufen und wieder in den MBR installiert. Das hat auch prima funktioniert und das alte Startmenü ist wieder da. Doch sobald ich aber einen Linux-Eintrag starten will, wird /boot/vmlinuz nicht gefunden und GRUB gibt den Fehler 15 aus. WO ist mein Denkfehler bzw. was kann ich machen? Du kannst in der GRUB-Shell die Pfade zum Kernel ändern. Also booten bis das GRUB-Menü kommt, dann auf e = EDIT drücken Nun änderst du die Angaben für root kernel und initrd (weiss die genauen Namen nicht auswendig) GRUB nummeriert deine Platten einfach durch hd0, hd1, hd2, auch die Partitionen starten bei NULL! Hinweis zur Tastaturbelegung: Die Klammern sind eins nach rechts verschoben, also Shift-9 gibt ne Klammer auf, ... Der Schrägstrich ist auf der Taste _ (Unterstrich). Zum Ändern mit den Cursortasten an den Anfang der Zeile scrollen und dann das Laufwerk wie folgt anpassen (hier auf /dev/hda6): kernel (hd0,5)/boot/vmlinuz ... Thomas -- SDG - System Design Group GmbH= Tel. +49 89 54 828 979 Dachauer Strasse 38 = Fax. +49 89 55 028 719 80335 Muenchen, Germany = E-Mail: [EMAIL PROTECTED] -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: GRUB-Problem
Hallo, Stephan Kulka [EMAIL PROTECTED] writes: Habe leider den Fehler gemacht Windows XP neu installieren zu müssen ohne den Bootsector zu sichern. Jetzt habe ich wie vor kurzem auf der Liste besprochen, Knoppix gestartet, chroot in mein / Verzeichnis gemacht und grub aufgerufen und wieder in den MBR installiert. Das hat auch prima funktioniert und das alte Startmenü ist wieder da. Doch sobald ich aber einen Linux-Eintrag starten will, wird /boot/vmlinuz nicht gefunden und GRUB gibt den Fehler 15 aus. WO ist mein Denkfehler bzw. was kann ich machen? hatte das selbe Prolem, habe aber kein chroot gemacht, sonder Knoppix gebootet und dann: mount Linux-Partition grub-install --root-directory=/mnt/Linux-Partition/ '(hd0)' MfG Silvio -- Silvio Vogt E-Mail: [EMAIL PROTECTED] - Outside of a dog, a book is man's best friend. Inside of a dog, it is too dark to read.
Re: GRUB-Problem
Thomas Rösch schrieb: Du kannst in der GRUB-Shell die Pfade zum Kernel ändern. Also booten bis das GRUB-Menü kommt, dann auf e = EDIT drücken Nun änderst du die Angaben für root kernel und initrd (weiss die genauen Namen nicht auswendig) Muss man auch nicht wissen. GRUB hilft. Auf der Kommandozeile gibt man einfach ein, was bekannt ist und er ergänzt oder zeigt eine Auswahl an. Beginnen kann man z.B. mit: kernel ( und haut dann auf die TAB-Taste. Wenn man dann Platte und Partition weiss und da z.B. kernel (hd0,2) / steht, haut man wieder mit einem Körperteil seiner Wahl auf die TAB-Taste et voilà, da ist der Inhalt von /. Ciao Walter -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Grub problem?
sure.That depends on your own choice On Wed, 10 Nov 2004 09:38:16 -0500 Christian Convey [EMAIL PROTECTED] wrote: Hi guys, (Debian newbie) I just burned a Debian testing net-inst disk. I think that makes it Sarge. I tried installing Debian on my home server, which has two IDE harddrives and a SCSI harddrive. I set up the SCSI drive as the / partition, and the two IDE drives as /mnt/spare1 and /mnt/spare2. Is there some way I can force the Debian installer to put Grub into the SCSI disk's MBR rather than hda's MBR? I'm trying to avoid having anything in my system's boot process rely on those IDE drives being present and operational. Thanks, Christian -- Christian Convey Computer Scientist, Naval Undersea Warfare Center Newport, RI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Whatever you do will be insignificant,but the important is you do it! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub problem?
Hi Christian, I have not experience for net-inst disk. But I think you can install GRUB to SCSI disk's MBR after installation. The config. file of GRUB is /boot/grub/menu.lst. This file tells GRUB where is the files for bootup your machine and the related options. After confirm the contain of this file has not problem. Issue this command grub-install /dev/sd? sd? is the harddisk which you want to boot from. Then you can reboot your machine to check if success. If fail you have to use the grub shell to bootup your machine. And then modify the config file or install GRUB to other MBR or Change the boot sequence at BIOS. So DON'T do it on a production machine. Regrads, Ming On Wed, Nov 10, 2004 at 09:38:16AM -0500, Christian Convey wrote: Hi guys, (Debian newbie) I just burned a Debian testing net-inst disk. I think that makes it Sarge. I tried installing Debian on my home server, which has two IDE harddrives and a SCSI harddrive. I set up the SCSI drive as the / partition, and the two IDE drives as /mnt/spare1 and /mnt/spare2. Is there some way I can force the Debian installer to put Grub into the SCSI disk's MBR rather than hda's MBR? I'm trying to avoid having anything in my system's boot process rely on those IDE drives being present and operational. Thanks, Christian -- Christian Convey Computer Scientist, Naval Undersea Warfare Center Newport, RI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub problem
[EMAIL PROTECTED] wrote: I am trying to implement a fallback full backup method for this great proxy-filter for the library. I used ghost to back it up, just as I used to do with redhat. Of course, ghost screws up grub. With Redhat, I'd stick the install cd in and at boot type in Linux Rescue chroot /mnt/sysimage grub-install Since I used the sarge netinst, I seem to have no rescue cd. :( Would someone mind giving me a simply way, on this system, to get grub back? If you have a floppy drive, make a grub boot floppy. Google around for GRUB boot floppy. They work wonders and are very flexible. BTW, in the future, if I'm not dual booting, do I need a boot loader? Yes you always need some sort of boot loader. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub problem
I attempted a repair floppy last night. It didn't work out real well. Ahhh, for a command like sys a::) Novel idea... Anyway here's what I did for future google searches. Maybe it'll help someone someday. How to Repair Grub boot loader after debian ghost restore I booted with mepis (Any live-cd would probably do) Open a terminal window Mounted the drive (don't use the mepis icon as it mounts read only) mount -rw /dev/hda1 /mnt/hda1 chroot /dev/hda1 grub-install /dev/hda Worked like a charm.. Am a bit confused what the drive is hda1 till I get to the install part, but I'm guessing I'm mounting partition one on hda, but the grub wants the drive to install to. Not the partition. Patrick Ouellette wrote: [EMAIL PROTECTED] wrote: I am trying to implement a fallback full backup method for this great proxy-filter for the library. I used ghost to back it up, just as I used to do with redhat. Of course, ghost screws up grub. With Redhat, I'd stick the install cd in and at boot type in Linux Rescue chroot /mnt/sysimage grub-install Since I used the sarge netinst, I seem to have no rescue cd. :( Would someone mind giving me a simply way, on this system, to get grub back? If you have a floppy drive, make a grub boot floppy. Google around for GRUB boot floppy. They work wonders and are very flexible. BTW, in the future, if I'm not dual booting, do I need a boot loader? Yes you always need some sort of boot loader. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub problem
On Thu, 2004-07-08 at 16:27, Rodney Richison wrote: I attempted a repair floppy last night. It didn't work out real well. Ahhh, for a command like sys a::) Novel idea... Anyway here's what I did for future google searches. Maybe it'll help someone someday. How to Repair Grub boot loader after debian ghost restore I booted with mepis (Any live-cd would probably do) Open a terminal window Mounted the drive (don't use the mepis icon as it mounts read only) mount -rw /dev/hda1 /mnt/hda1 chroot /dev/hda1 grub-install /dev/hda Worked like a charm.. Am a bit confused what the drive is hda1 till I get to the install part, but I'm guessing I'm mounting partition one on hda, but the grub wants the drive to install to. Not the partition. Hi Rodney, The standard procedure for booting on the PC architecture is that the BIOS is configured with a list of boot devices and the order to scan them. It checks the MBR (master boot record, aka boot sector) of each device in turn until it finds some executable code. Note: the BIOS does not care at all about the partitions on the drive, it only looks at the boot sector for the device. What grub-install does is write a small amount of code (512 bytes) into the MBR on a device, called the stage1 code. This code is just smart enough to be able to read a sequence of hard-wired disk blocks (the stage1.5 or stage2 executable) into memory and jump to the loaded code. This data resides as a standard file in some kind of filesystem. Note that no filesystem knowledge is required - but the file being loaded had better not move on disk (eg defragmentation is a really bad idea) as the physical location of the blocks is wired into the MBR. That is why grub-install takes a device (hence /dev/hda) as a target, not a partition; it is installing the stage1 code into the MBR. And it needs to figure out the physical disk blocks which contain the executable which is the next stage of grub. So you can either mount the filesystem that will contain these files as the root partition (which you effectively did), or mount it elsewhere and pass the --root-directory option to grub-install. Of course here you are dealing with *filesystems* which reside on *partitions* (hence /dev/hda1). I hope this helps. I learnt much of this the hard way after having to fix unbootable systems just like you are doing now :-) The grub docs at http://www.gnu.org/software/grub/manual/grub.html are of course the ultimate source of info. NB: To confuse issues, each partition also has a boot sector. The BIOS never looks at these, but a bootloader stored in the MBR of the device can be set up to delegate to the boot code in a partition's boot sector. BTW, there may be errors in the above - anyone who knows better is welcome to correct these. Regards, Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Thursday 03 July 2003 05:51, Vineet Kumar wrote: * cr ([EMAIL PROTECTED]) [030629 19:28]: Yes, I did that. It produced a floppy which, when booted off, just says 'GRUB' and hangs. Does it hang, or is that a grub prompt you're seeing? It won't go to a menu. You'll have to type commands manually. From the looks of this thread, it seems like you're getting familiar enough with grub to be able to do that by now =) This is the boot floppy produced by using grub-install to fd0. (I can't remember the exact sequence of commands now). It says 'GRUB' (in capital letters) and hangs. Typing has no effect. (But see below for a 'good' boot floppy - ) Basically you need to type just what you would in a stanza of menu.lst right into the grub prompt, something like this: root (hd0,0) kernel /vmlinuz-2.2.20-idepci ro root=/dev/hda5 initrd /initrd.img-2.2.20-idepci boot good times, Vineet I do have another Grub floppy, produced IIRC by following 'Creating a Grub Boot Floppy' from the Grub manual, using dd to copy stage1 and stage2 to a floppy.That one boots into Grub successfully. I booted off the 'good' Grub floppy, and got the following: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub kernel /vmlinuz-2.2.20-idepci ro root=/dev/hda5 Error 13Invalid or unsupported executable format And - I'm too stupid to own a computer!!! I just fixed the whole thing. The answer, when found, will be obvious. This is where something that had been niggling at me for days finally dawned on me.Not expecting it to make any difference, I went to the BIOS and changed the drive setting from 'Normal' (16/63/4092, which is what the drive label says) to 'LBA' 64/63/1023. I bever bothered before because I think Linux takes no notice of BIOS settings and I imagined Grub didn't either, besides which the root (hd0,0) command had always shown the filesystem correctly. Anyway, I got grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83(exactly the same as before) grub kernel /vmlinuz-2.2.20-idepci ro root=/dev/hda5 [Linux-bzimage, setup=0x1000, size=0x15a5] ... and it boots! And it *also* now boots fine off the hard drive. Problem solved! I feel like an idiot, missing something so obvious! Thanks, everyone who helped with advice. My apologies for taking up so much of your time. Regards Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
* Kevin McKinley ([EMAIL PROTECTED]) [030701 13:33]: On Tue, 1 Jul 2003 19:54:51 +1200 cr [EMAIL PROTECTED] wrote: Errrm, *I* didn't produce that line kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro - grub-install did. In fact, if I read GRUB terminology aright, it's looking for (hd0,0)/vmlinuz-2.2.20-idepci. Or, as Linux sees it, /dev/hda/vmlinuz-2.2.20-idepci aka /boot/vmlinuz-2.2.20-idepci. And it's there, and also in /boot/boot/vmlinuz-2.2.20-idepci (because I copied it there just to make sure). In the kernel line of menu.lst (or at the grub command prompt), /something means something in the root directory of the filesystem, not in /boot. If you want the latter, specify it either as /boot/something or as (hd0,0)/something. You're using contradicting terms. /something does indeed mean something in the root directory of _a_ filesystem. Which filesystem? (hd0,0) (a.k.a. /dev/hda1, a.k.a. /boot). cr is correct in saying that that (hd0,0)/vmlinux-2.2.20-idepci is the same as what Linux calls /boot/vmlinux-2.2.20-idepci . Grub's root is specified as (hd0,0), so all filenames are relative to that filesystem. Grub doesn't mount a tree of filesystems like linux does; it just mounts one, known as it's root (or groot, in the nomenclature used by debian's default menu.lst) and all filenames are relative to that. good times, Vineet -- http://www.doorstop.net/ -- Those who desire to give up freedom in order to gain security will not have, nor do they deserve, either one. --President Thomas Jefferson signature.asc Description: Digital signature
Re: GRUB problem
* cr ([EMAIL PROTECTED]) [030629 19:28]: Yes, I did that. It produced a floppy which, when booted off, just says 'GRUB' and hangs. Does it hang, or is that a grub prompt you're seeing? It won't go to a menu. You'll have to type commands manually. From the looks of this thread, it seems like you're getting familiar enough with grub to be able to do that by now =) Basically you need to type just what you would in a stanza of menu.lst right into the grub prompt, something like this: root (hd0,0) kernel /vmlinuz-2.2.20-idepci ro root=/dev/hda5 initrd /initrd.img-2.2.20-idepci boot good times, Vineet -- http://www.doorstop.net/ -- http://www.eff.org/ Defeinding freedom in the digital world signature.asc Description: Digital signature
Re: GRUB problem
On Monday 30 June 2003 14:40, Kevin McKinley wrote: On Sun, 29 Jun 2003 14:44:46 +1200 cr [EMAIL PROTECTED] wrote: Well, in my system, /vmlinuz is a symlink thus: lrwxrwxrwx1 root root 26 Jun 12 08:25 vmlinuz - boot/vmlinuz-2.2.20-idepci and /boot/vmlinuz is: -rw-r--r--1 root root 665509 Jun 21 23:05 vmlinuz-2.2.20-idepci As I read it, my menu.lst which is as follows: title Debian GNU/Linux, kernel 2.2.20-idepci root (hd0,0) kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault first sets root to (hd0,0) (i.e. /dev/hda1 or /boot) then tries to load vmlinuz-2.2.20-idepci , passing it the parameters of root=/dev/hda1 That's not the case. You can refer to your kernel either by the symlink name of /vmlinuz or by its actual name which is /boot/vmlinuz-2.2.20-idepci. You're trying to mix the two together, and it won't work. Kevin Errrm, *I* didn't produce that line kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro - grub-install did. In fact, if I read GRUB terminology aright, it's looking for (hd0,0)/vmlinuz-2.2.20-idepci. Or, as Linux sees it, /dev/hda/vmlinuz-2.2.20-idepci aka /boot/vmlinuz-2.2.20-idepci. And it's there, and also in /boot/boot/vmlinuz-2.2.20-idepci (because I copied it there just to make sure). cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, 1 Jul 2003 19:54:51 +1200 cr [EMAIL PROTECTED] wrote: Errrm, *I* didn't produce that line kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro - grub-install did. In fact, if I read GRUB terminology aright, it's looking for (hd0,0)/vmlinuz-2.2.20-idepci. Or, as Linux sees it, /dev/hda/vmlinuz-2.2.20-idepci aka /boot/vmlinuz-2.2.20-idepci. And it's there, and also in /boot/boot/vmlinuz-2.2.20-idepci (because I copied it there just to make sure). In the kernel line of menu.lst (or at the grub command prompt), /something means something in the root directory of the filesystem, not in /boot. If you want the latter, specify it either as /boot/something or as (hd0,0)/something. Since I can't see your system I've given up on figuring out what's wrong here. Perhaps one way to fix it would be to purge and reinstall grub: dpkg -P grub delete any remnants of grub you find in the filesystem apt-get install grub grub-install /dev/hda update-grub edit menu.lst update-grub I've resorted to that in the past when I couldn't get grub to work. I had a different problem that I never did figure out, but I finally fixed. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Sun, 29 Jun 2003 14:44:46 +1200 cr [EMAIL PROTECTED] wrote: Well, in my system, /vmlinuz is a symlink thus: lrwxrwxrwx1 root root 26 Jun 12 08:25 vmlinuz - boot/vmlinuz-2.2.20-idepci and /boot/vmlinuz is: -rw-r--r--1 root root 665509 Jun 21 23:05 vmlinuz-2.2.20-idepci As I read it, my menu.lst which is as follows: title Debian GNU/Linux, kernel 2.2.20-idepci root (hd0,0) kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault first sets root to (hd0,0) (i.e. /dev/hda1 or /boot) then tries to load vmlinuz-2.2.20-idepci , passing it the parameters of root=/dev/hda1 That's not the case. You can refer to your kernel either by the symlink name of /vmlinuz or by its actual name which is /boot/vmlinuz-2.2.20-idepci. You're trying to mix the two together, and it won't work. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Saturday 28 June 2003 23:37, [EMAIL PROTECTED] wrote: In linux.debian.user, you wrote: I have /boot on /dev/hda1 and root on /dev/hda5 Grub when installed and booted gives the following: GRUB Loading Stage 1.5 GRUB Loading, please wait... Error 2(and that's as far as it gets) Error 2 means Bad file or directory type This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO. Does anyone have any ideas? [The details - I installed GRUB in accordance with /usr/share/doc/grub/README.Debian - 1. grub-install --root-directory=boot /dev/hda 2. Ran update-grub 3. Checked /boot/boot/grub/menu.lst and didn't need to change a thing - the significant lines (leaving out all the comments) are: title Debian GNU/Linux, kernel 2.2.20-idepci root(hd0,0) kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault In /boot I have (amongst other files left over from lilo) -rw-r--r--1 root root 224124 Jun 21 23:05 System.map-2.2.20-idepci -rw-r--r--1 root root 3888 Jun 21 23:05 config-2.2.20-idepci -rw---1 root root17408 Jun 21 23:50 map -rw-r--r--1 root root 665509 Jun 21 23:05 vmlinuz-2.2.20-idepci In /boot/boot/grub I have (put there by grub-install) *all* the stage1_5 flavours, including -rw-r--r--1 root root 60 Jun 21 23:06 device.map -rw-r--r--1 root root 7904 Jun 22 00:10 e2fs_stage1_5 -rw-r--r--1 root root 2392 Jun 22 00:10 menu.lst -rw-r--r--1 root root 512 Jun 22 00:10 stage1 -rw-r--r--1 root root95712 Jun 22 00:10 stage2 None of those look like symlinks to me. Have I got root set right in menu.lst, as /dev/hda1? Should it be /dev/hda5? Seems unlikely to be the cause since the boot menu or 'booting in 5 seconds' message never comes up and I wouldn't expect that root setting to take effect until after the menu.. Chris I tried using grub at home this morning and see that I was wrong in what I posted about using /boot/vmlinuz-xx. So I'm going to post what I have here that is working. I have a separate /boot partition. I have the same files that you have above and they are the same size except my device.map is a tad smaller. These files are, however, all in /boot/grub and not in /boot/boot/grub. I already had them installed and can't tell you how I did it for sure. I was playing with grub a long time ago when I was trying out the HURD. Anyway, I think the person who suggested moving the files to /boot/grub was correct. Here are the sections of menu.lst and fstab that pertain: ---menu.lst title Win4Lin root (hd0,1) kernel/vmlinuz-win4lin-2.4.20 root=/dev/hdb5 ro savedefault ### END DEBIAN AUTOMAGIC KERNELS LIST ---etc/fstab # /etc/fstab: static file system information. /dev/hdb5 /ext2 defaults01 /dev/hda2 /bootext2 defaults0 0 I put a floppy in and ran 'grub-install /dev/fd0' and the floppy then booted me into linux. Now there's my problem. What works for everybody else doesn't seem to work for me grin So as far as I can tell, the changes to be made on this initial posting should be 1. put the grub stuff in /boot/grub 2. change the kernel line so that it says root=/dev/hda5 And my guess is that you have already tried this. I guess I would try installing it on a floppy after making sure those two things are in place. Also be sure that the kernel line does not have the /boot in front of the kernel. I've tried it both ways, in fact. i.e. with the stuff in /boot/grub *and* in /boot/boot/grub. I looked at 'info grub' and there was next to no information on Troubleshooting Stage 1.5. There were error messages for Stages 1 and 2. According to the Grub manual, stage 1.5 errors are the same as for stage 2. (I found the manual by Googling, probably on the Gnu site but I'm afraid I didn't make a note of it). I apologize for the wrong information earlier. Anita Not at all. All information gives a clue as to where to look. Anyway, thanks all for the information. Obviously there's something very odd about my setup which doesn't respond as it ought. For now I can live with boot floppies and I'll find the Grub list, maybe they can suggest something. cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Thu, 26 Jun 2003 12:28:11 -0400 (EDT) Anita Lewis [EMAIL PROTECTED] wrote: The other thing to check is in your menu.lst It says: kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro Is that where that kernel is or is it /boot/vmlinuz-2... ? Yes, that's right. I'm embarrassed I missed that. Sheesh. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Friday 27 June 2003 05:47, Vineet Kumar wrote: I just tried it on this setup and got: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) Careful mixing 's' and 'S'; this is a case-sensitive filesystem! I believe the filenames grub uses are all lowercase. I guess that error message above was something you wrote down and typed into the email, since it's difficult to copy and paste from your boot loader =). But make sure that grub indicates that it's looking for stage1 (lowercase) and that the file you have is also called stage1 (lowercase). good times, Vineet You're quite correct, all Grub's names are lowercase. And I did type it into the mail, as you guessed. Whatever the reason GRUB can't see the files that Linux says are there, it isn't because of wrong case.Besides, I'm sure Grub's error messages have the correct case, Grub ought to know what case to look for. ;) cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Friday 27 June 2003 05:42, Vineet Kumar wrote: * cr ([EMAIL PROTECTED]) [030625 01:44]: I think grub-install actually looks for the files in /usr/lib/grub/i386pc/ and copies them to /boot/grub in root dir on /dev/hdaOR, if you specify (as I do) grub-install --root-directory=/boot /dev/hda then it copies them to the /boot partition i.e. /boot/boot/grub/ in Linux terms. Grub itself when booted from floppy looks for files in both /boot/grub and /grub, going by the error messages: root (hd0,0) setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 2: Bad file or directory type Just to avoid confusion, I'll reiterate what you have already so clearly pointed out earlier in this thread. The above messages indicte that grub is looking for (hd0,0)/boot/grub/Stage1 (which Linux calls /boot/boot/grub/Stage1) and then, when that's not found, (hd0,0)/grub/Stage1 (which Linux calls /boot/grub/Stage1). Okay, so maybe I increased the confusion! good times, Vineet You haven't increased my confusion. :) And what you say there is quite correct. As you pointed out earlier, all those 'Stage1' mentions should be 'stage1', I was typing it in from a scribbled note I made. But anyway, Linux can see those files on the drive and grub apparently can't. They're there right now, in both directories (since grub-install copied them from /usr/lib/grub/i386-pc to /boot/boot/grub, and I copied them to /boot/grub just to make sure), and they're real files, not symlinks.Very odd. Thanks cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
In linux.debian.user, you wrote: I have /boot on /dev/hda1 and root on /dev/hda5 Grub when installed and booted gives the following: GRUB Loading Stage 1.5 GRUB Loading, please wait... Error 2(and that's as far as it gets) Error 2 means Bad file or directory type This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO. Does anyone have any ideas? [The details - I installed GRUB in accordance with /usr/share/doc/grub/README.Debian - 1. grub-install --root-directory=boot /dev/hda 2. Ran update-grub 3. Checked /boot/boot/grub/menu.lst and didn't need to change a thing - the significant lines (leaving out all the comments) are: title Debian GNU/Linux, kernel 2.2.20-idepci root (hd0,0) kernel/vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault In /boot I have (amongst other files left over from lilo) -rw-r--r--1 root root 224124 Jun 21 23:05 System.map-2.2.20-idepci -rw-r--r--1 root root 3888 Jun 21 23:05 config-2.2.20-idepci -rw---1 root root17408 Jun 21 23:50 map -rw-r--r--1 root root 665509 Jun 21 23:05 vmlinuz-2.2.20-idepci In /boot/boot/grub I have (put there by grub-install) *all* the stage1_5 flavours, including -rw-r--r--1 root root 60 Jun 21 23:06 device.map -rw-r--r--1 root root 7904 Jun 22 00:10 e2fs_stage1_5 -rw-r--r--1 root root 2392 Jun 22 00:10 menu.lst -rw-r--r--1 root root 512 Jun 22 00:10 stage1 -rw-r--r--1 root root95712 Jun 22 00:10 stage2 None of those look like symlinks to me. Have I got root set right in menu.lst, as /dev/hda1? Should it be /dev/hda5? Seems unlikely to be the cause since the boot menu or 'booting in 5 seconds' message never comes up and I wouldn't expect that root setting to take effect until after the menu.. Chris I tried using grub at home this morning and see that I was wrong in what I posted about using /boot/vmlinuz-xx. So I'm going to post what I have here that is working. I have a separate /boot partition. I have the same files that you have above and they are the same size except my device.map is a tad smaller. These files are, however, all in /boot/grub and not in /boot/boot/grub. I already had them installed and can't tell you how I did it for sure. I was playing with grub a long time ago when I was trying out the HURD. Anyway, I think the person who suggested moving the files to /boot/grub was correct. Here are the sections of menu.lst and fstab that pertain: ---menu.lst title Win4Lin root(hd0,1) kernel /vmlinuz-win4lin-2.4.20 root=/dev/hdb5 ro savedefault ### END DEBIAN AUTOMAGIC KERNELS LIST ---etc/fstab # /etc/fstab: static file system information. /dev/hdb5 /ext2 defaults01 /dev/hda2 /bootext2 defaults00 I put a floppy in and ran 'grub-install /dev/fd0' and the floppy then booted me into linux. So as far as I can tell, the changes to be made on this initial posting should be 1. put the grub stuff in /boot/grub 2. change the kernel line so that it says root=/dev/hda5 And my guess is that you have already tried this. I guess I would try installing it on a floppy after making sure those two things are in place. Also be sure that the kernel line does not have the /boot in front of the kernel. I looked at 'info grub' and there was next to no information on Troubleshooting Stage 1.5. There were error messages for Stages 1 and 2. I apologize for the wrong information earlier. Anita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Friday 27 June 2003 04:28, Anita Lewis wrote: cr, it looks like /boot is available from both /etc/fstab and from your df listing. I am assuming that you ran 'update-grub' first to produce menu.lst, but even if you hadn't done that, by now you have rerun grub-install enough. I notice that 1. has --root-directory=boot. That should be --root-directory=/boot according to the README.Debian file. So it should. I'm fairly sure I typed it in correctly in practice. I just misquoted in my email. The other thing to check is in your menu.lst It says: kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro Is that where that kernel is or is it /boot/vmlinuz-2... ? I think that /vmlinuz is a symlink to /boot/vmlinuz-2...; so /vmlinuz might work, but I don't think what you have will work unless that is actually what is in / . Well, in my system, /vmlinuz is a symlink thus: lrwxrwxrwx1 root root 26 Jun 12 08:25 vmlinuz - boot/vmlinuz-2.2.20-idepci and /boot/vmlinuz is: -rw-r--r--1 root root 665509 Jun 21 23:05 vmlinuz-2.2.20-idepci As I read it, my menu.lst which is as follows: title Debian GNU/Linux, kernel 2.2.20-idepci root (hd0,0) kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault first sets root to (hd0,0) (i.e. /dev/hda1 or /boot) then tries to load vmlinuz-2.2.20-idepci , passing it the parameters of root=/dev/hda1 So if the parameters are wrong, it shouldn't matter until after vmlinuz is loaded. My impression of the boot sequence is that Grub stage 1 (in the MBR) loads stage 1.5, which loads stage 2, which loads vmlinuz. And my system doesn't seem to be getting any further than stage 1.5 or so. Hmmm, I suppose it's loading the *right* stage1_5? /boot/boot/grub is full of ???_stage1_5's that install-grub copied there; the one it wants is e2fs_stage1_5.If it loaded the wrong one it certainly wouldn't be able to find the next file in the process.OTOH I just copied e2fs_stage1_5 as stage1_5 - but it made no difference. Unfortunately my /boot is on my root partition here where I just tried this myself. If you think that your MBR settings, whatever those are, might be messed up, you could try installing grub on a floppy. I just did that on my system. I'm pretty hazy about the nuts and bolts of what goes in the MBR, I must admit. First I ran update-grub after installing grub on the system. I edited /boot/grub/menu.lst which had root(hd0,0) to make it (hd0,2) since it is on /dev/hda3. The rest of it seemed fine. Hmmm, update-grub rewrote menu.lst as root (hd0,0) kernel /vmlinuz-2.2.20-idepci root=/dev/hda5 ro I left that unchanged Then I ran 'grub-install /dev/fd0' with a floppy in the drive. So you would do 'grub-install --root-directory=/boot /dev/fd0' I think. Yes, I did that. It produced a floppy which, when booted off, just says 'GRUB' and hangs. I think I'll see if there's a Grub-specific list I can pursue this on. Meanwhile I have a few other Debian things to straighten out Thanks everybody cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fs_passno (was Re: GRUB problem)
On Friday 27 June 2003 08:44, Vineet Kumar wrote: * cr ([EMAIL PROTECTED]) [030626 12:52]: # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/hda1 /boot ext2errors=remount-ro 0 0 /dev/hda5 / ext2errors=remount-ro 0 1 /dev/hda6 noneswapsw 0 0 /dev/hdd5 /cr2ext2defaults0 0 /dev/hdd6 /cr4ext2defaults0 0 /dev/hdc2 /cr3ext2defaults0 0 /dev/hdc1 /mnt/DosC msdos defaults0 0 /dev/hdd1 /mnt/dosD msdos defaults0 0 proc/proc procdefaults0 0 /dev/fd0/floppy autouser,noauto 0 0 /dev/cdrom /cdrom iso9660 ro,user,noauto 0 0 I actually inserted the line for /boot before the line for / , so it had to have a newline character.I'm not sure what the significance of the dump pass numbers is (I just copied the 0 0 of all the drives except / ) Those numbers are described in fstab(5). The short of it is that all of your filesystems except / should have 0 2 and / should have 0 1. Well, when I say all of them, I really mean the ones that are regularly mounted as part of your linux system. In your case, that would mean /boot, /cr2, /cr3, /cr4. All of your disk-based (not /proc, not tmpfs) filesystems. good times, Vineet Thanks. I just amended /etc/fstab as suggested. cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
* cr ([EMAIL PROTECTED]) [030624 01:22]: On Tuesday 24 June 2003 01:27, Hugh Saunders wrote: On Tue, Jun 24, 2003 at 12:52:01AM +1200, cr wrote: I'm still booting off floppy and trying to get GRUB sorted. erm, not quite sure whats wrong but what happens if you boot grub from floppy then run root (hd0,0) then setup (hd0) from floppy? That actually worked previously with Red Hat (on a different hard drive). I just tried it on this setup and got: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) Careful mixing 's' and 'S'; this is a case-sensitive filesystem! I believe the filenames grub uses are all lowercase. I guess that error message above was something you wrote down and typed into the email, since it's difficult to copy and paste from your boot loader =). But make sure that grub indicates that it's looking for stage1 (lowercase) and that the file you have is also called stage1 (lowercase). good times, Vineet -- http://www.doorstop.net/ -- Those who desire to give up freedom in order to gain security will not have, nor do they deserve, either one. --President Thomas Jefferson signature.asc Description: Digital signature
Re: GRUB problem
cr said: I've concluded that there must be something fairly basic wrong with my bios settings or maybe the MBR (though I did run bios autodetect before I started all this and made sure the alternatives I selected gave the same drive/head/sector numbers as the labels on the hard drives did). I'm not sure what tools there are for investigating MBR settings or drive geometry. Meanwhile, boot floppies work (though the Debian one is awfully slow ;) cr quote from original post [The details - I installed GRUB in accordance with /usr/share/doc/grub/README.Debian - 1. grub-install --root-directory=boot /dev/hda 2. Ran update-grub and titleDebian GNU/Linux, kernel 2.2.20-idepci root(hd0,0) kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault cr, it looks like /boot is available from both /etc/fstab and from your df listing. I am assuming that you ran 'update-grub' first to produce menu.lst, but even if you hadn't done that, by now you have rerun grub-install enough. I notice that 1. has --root-directory=boot. That should be --root-directory=/boot according to the README.Debian file. The other thing to check is in your menu.lst It says: kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro Is that where that kernel is or is it /boot/vmlinuz-2... ? I think that /vmlinuz is a symlink to /boot/vmlinuz-2...; so /vmlinuz might work, but I don't think what you have will work unless that is actually what is in / . Unfortunately my /boot is on my root partition here where I just tried this myself. If you think that your MBR settings, whatever those are, might be messed up, you could try installing grub on a floppy. I just did that on my system. First I ran update-grub after installing grub on the system. I edited /boot/grub/menu.lst which had root(hd0,0) to make it (hd0,2) since it is on /dev/hda3. The rest of it seemed fine. Then I ran 'grub-install /dev/fd0' with a floppy in the drive. So you would do 'grub-install --root-directory=/boot /dev/fd0' I think. Anita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
* cr ([EMAIL PROTECTED]) [030625 01:44]:
I think grub-install actually looks for the files in /usr/lib/grub/i386pc/
and copies them to /boot/grub in root dir on /dev/hdaOR, if you specify
(as I do)
grub-install --root-directory=/boot /dev/hda then it copies them to the
/boot partition i.e. /boot/boot/grub/ in Linux terms.
Grub itself when booted from floppy looks for files in both /boot/grub and
/grub, going by the error messages:
root (hd0,0)
setup (hd0)
Checking if /boot/grub/Stage1 exists ... no
Checking if /grub/Stage1 exists ... no
Error 2: Bad file or directory type
Just to avoid confusion, I'll reiterate what you have already so clearly
pointed out earlier in this thread. The above messages indicte that
grub is looking for (hd0,0)/boot/grub/Stage1 (which Linux calls
/boot/boot/grub/Stage1) and then, when that's not found,
(hd0,0)/grub/Stage1 (which Linux calls /boot/grub/Stage1). Okay, so
maybe I increased the confusion!
good times,
Vineet
--
http://www.doorstop.net/
--
#includestdio.h
int main() {
puts(Reader! Think not that \n
technical information \n
ought not be called speech;);
return 0;
}
signature.asc
Description: Digital signature
Re: GRUB problem
On Wednesday 25 June 2003 22:45, [EMAIL PROTECTED] wrote: In linux.debian.user, you wrote: I'm still booting off floppy and trying to get GRUB sorted. I have /boot on /dev/hda1 and root on /dev/hda5 (At first, LILO was just hanging with 'LI 99 99 99' and GRub, when I installed it gave an Error 5 - 'partition table bad'.Eventually I got half a clue and added /boot (/dev/hda1)into /etc/fstab and started again...) Lilo when installed and booted just gives 'LI' and stops. Grub when installed and booted gives the following: GRUB Loading Stage 1.5 GRUB Loading, please wait... Error 2(and that's as far as it gets) Error 2 means Bad file or directory type This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO. Does anyone have any ideas? Could we see your /etc/fstab and the output of 'df mount-partitions, please? I'm thinking that maybe you entered the line for /boot into /etc/fstab and didn't put a new line character at the end of the file. It would then not see /boot. Anita Sure, but I think they're OK. Here's /etc/fstab, copied directly using Kmail's 'Insert file' menu entry: # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/hda1 /boot ext2errors=remount-ro 0 0 /dev/hda5 / ext2errors=remount-ro 0 1 /dev/hda6 noneswapsw 0 0 /dev/hdd5 /cr2ext2defaults0 0 /dev/hdd6 /cr4ext2defaults0 0 /dev/hdc2 /cr3ext2defaults0 0 /dev/hdc1 /mnt/DosC msdos defaults0 0 /dev/hdd1 /mnt/dosD msdos defaults0 0 proc/proc procdefaults0 0 /dev/fd0/floppy autouser,noauto 0 0 /dev/cdrom /cdrom iso9660 ro,user,noauto 0 0 I actually inserted the line for /boot before the line for / , so it had to have a newline character.I'm not sure what the significance of the dump pass numbers is (I just copied the 0 0 of all the drives except / ) And here's df, straight from a terminal window (rxvt): [EMAIL PROTECTED]:~$ df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda5 1662808828224750116 53% / /dev/hda125341 1273 22760 6% /boot /dev/hdd5 806560257372508216 34% /cr2 /dev/hdd6 715280166352512592 25% /cr4 /dev/hdc2 1123088688276377760 65% /cr3 /dev/hdc1 511760433480 78280 85% /mnt/DosC /dev/hdd1 515792408064107728 80% /mnt/dosD I've concluded that there must be something fairly basic wrong with my bios settings or maybe the MBR (though I did run bios autodetect before I started all this and made sure the alternatives I selected gave the same drive/head/sector numbers as the labels on the hard drives did). I'm not sure what tools there are for investigating MBR settings or drive geometry. Meanwhile, boot floppies work (though the Debian one is awfully slow ;) cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
fs_passno (was Re: GRUB problem)
* cr ([EMAIL PROTECTED]) [030626 12:52]: # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/hda1 /boot ext2errors=remount-ro 0 0 /dev/hda5 / ext2errors=remount-ro 0 1 /dev/hda6 noneswapsw 0 0 /dev/hdd5 /cr2ext2defaults0 0 /dev/hdd6 /cr4ext2defaults0 0 /dev/hdc2 /cr3ext2defaults0 0 /dev/hdc1 /mnt/DosC msdos defaults0 0 /dev/hdd1 /mnt/dosD msdos defaults0 0 proc /proc procdefaults0 0 /dev/fd0 /floppy autouser,noauto 0 0 /dev/cdrom/cdrom iso9660 ro,user,noauto 0 0 I actually inserted the line for /boot before the line for / , so it had to have a newline character.I'm not sure what the significance of the dump pass numbers is (I just copied the 0 0 of all the drives except / ) Those numbers are described in fstab(5). The short of it is that all of your filesystems except / should have 0 2 and / should have 0 1. Well, when I say all of them, I really mean the ones that are regularly mounted as part of your linux system. In your case, that would mean /boot, /cr2, /cr3, /cr4. All of your disk-based (not /proc, not tmpfs) filesystems. good times, Vineet -- http://www.doorstop.net/ -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. --Benjamin Franklin signature.asc Description: Digital signature
Re: GRUB problem
On Tuesday 24 June 2003 21:27, Hugh Saunders wrote: For some reason GRUB can't see the files. grub find /boot/grub/stage1 (or any other file) brings up a 'File not found' you could try copying the whole of /usr/lib/grub/i386-pc/ to your /boot/boot Thats what i tend to do [i didnt realise that grub-install copies stuff for you!] That's what I did when I got GRUB working under RedHat. But yes, grub-install (under Debian) did copy them all there, I checked. grub can list files for you once you have set root. type / then tab and see what files actually are on your boot partition. Nope, no files show up with /[tab]. Even though root (hd0,0) seems to work, it correctly iD's the drive as a ext2 filesystem. cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Wednesday 25 June 2003 06:05, David Z Maze wrote: Kevin McKinley [EMAIL PROTECTED] writes: On Tue, 24 Jun 2003 19:21:20 +1200 cr [EMAIL PROTECTED] wrote: grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) Your files are in /boot/boot/grub, and they should be in /boot/grub. To solve your problem, do cp -a /boot/boot/grub /boot. That's not going to help if /boot is a separate partition. You need to separately tell GRUB where to find the stage1.5 and stage2 files and where to install the boot sector; the Info manual suggests that you want root (hd0,0) setup (hd0) In this situation, I believe /boot/boot/grub is the correct directory. Since root (hd0,0) mounts into [what linux calls /boot], then if it looks for (hd0,0)/boot/grub, it will be looking in /boot/boot/grub in Linux terms.Assuming always that /dev/hda1 is mounted as /boot in Linux, which it is in my system.In other words /boot/boot/grub is correct, I think. cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Wednesday 25 June 2003 00:08, Shawn Lamson wrote: On Tue, June 24 at 7:21 PM EDT cr [EMAIL PROTECTED] wrote: I just tried it on this setup and got: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) For some reason GRUB can't see the files. grub find /boot/grub/stage1 (or any other file) brings up a 'File not found' cr Been a while since I mucked around with grub, can't you try grubfind (hd0,0)/boot/grub/Stage1 ? That might have just been me experimenting at the time, though. What about specifying $find /boot/boot/grub/Stage1 from the grub prompt. I also assume that caps count but am not sure. What does $ls -l /boot/boot/grub show? Are you doing this with the drive mounted? I think that since the how-to docs I have seen recommend booting off of the grub-boot floppy that it thinks it is not mounted. Just throwing out ideas in case you were lacking any :) Hope it helps. Shawn Lamson [EMAIL PROTECTED] Debian GNU/Linux 3.0 Any attempts to use 'find' from the grub prompt give 'file not found'. This is after mounting with root (hd0,0) ls -l shows all the files are present in /boot/boot/grub (*and* /boot/grub as well since I copied 'em there!) i.e. stage1, stage2 and a swag of stage1_5's. (And yes, I do have /boot mounted on /dev/hda1, as df confirms.) Thanks for the ideas. :) cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Wednesday 25 June 2003 09:02, Kevin McKinley wrote: On Tue, 24 Jun 2003 14:05:24 -0400 David Z Maze [EMAIL PROTECTED] wrote: Your files are in /boot/boot/grub, and they should be in /boot/grub. To solve your problem, do cp -a /boot/boot/grub /boot. That's not going to help if /boot is a separate partition. You need to separately tell GRUB where to find the stage1.5 and stage2 files and where to install the boot sector; the Info manual suggests that you want root (hd0,0) setup (hd0) In this situation, I believe /boot/boot/grub is the correct directory. You may be right. But why would /boot being a separate partition have anything to do with it? His partition has a directory boot, and inside that directory another called grub. That would be OK if it were mounted on /, but of course we can't do that. Under Linux, /boot/grub is mounted on /boot (/dev/hda1), so Linux thinks it's called /boot/boot/grub. When a partition containing boot/grub is mounted on /boot, the path to the files becomes /boot/boot/grub. Yes, that's what Linux thinks, *and* what grub-install thinks when it's running under Linux (I think). But grub isn't looking there for the files; its looking in /boot/grub and not finding them. When run off a Grub boot floppy, root (hd0,0) mounts /boot as the directory GRUB is 'in', so GRUB thinks the directory the files are in is (hd0,0)/boot/grub. This is the *same* directory as [dev/hda1]/boot/grub i.e. /boot/boot/grub in Linux terms. i.e both Linux and GRUB are looking in the same place - or certainly should be. My solution puts the files where grub expects to see them. I suspect this happens because the default way to install debian is without a separate /boot partition, so grub-install isn't handling the situation well. Maybe it isn't, but copying the files into both /boot/boot/grub *and* /boot/grub should surely let GRUB find 'em in one place or the other. If someone can see a flaw in the above please let me know; I may yet be the learner here. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Wednesday 25 June 2003 03:26, Kevin McKinley wrote: On Tue, 24 Jun 2003 19:21:20 +1200 cr [EMAIL PROTECTED] wrote: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) For some reason GRUB can't see the files. grub find /boot/grub/stage1 (or any other file) brings up a 'File not found' Your files are in /boot/boot/grub, and they should be in /boot/grub. To solve your problem, do cp -a /boot/boot/grub /boot. Then you can delete the directory /boot/boot/grub and its contents. Grub-install should work then. Then consider filing a bug against grub. grub-install should look for its files in /boot/boot/grub as well as /boot/grub; update-grub already does this. Kevin I think grub-install actually looks for the files in /usr/lib/grub/i386pc/ and copies them to /boot/grub in root dir on /dev/hdaOR, if you specify (as I do) grub-install --root-directory=/boot /dev/hda then it copies them to the /boot partition i.e. /boot/boot/grub/ in Linux terms. Grub itself when booted from floppy looks for files in both /boot/grub and /grub, going by the error messages: root (hd0,0) setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 2: Bad file or directory type cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
In linux.debian.user, you wrote: I'm still booting off floppy and trying to get GRUB sorted. I have /boot on /dev/hda1 and root on /dev/hda5 (At first, LILO was just hanging with 'LI 99 99 99' and GRub, when I installed it gave an Error 5 - 'partition table bad'.Eventually I got half a clue and added /boot (/dev/hda1)into /etc/fstab and started again...) Lilo when installed and booted just gives 'LI' and stops. Grub when installed and booted gives the following: GRUB Loading Stage 1.5 GRUB Loading, please wait... Error 2(and that's as far as it gets) Error 2 means Bad file or directory type This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO. Does anyone have any ideas? Could we see your /etc/fstab and the output of 'df mount-partitions, please? I'm thinking that maybe you entered the line for /boot into /etc/fstab and didn't put a new line character at the end of the file. It would then not see /boot. Anita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On (24/06/03 01:20), Kevin McKinley wrote: On Mon, 23 Jun 2003 23:04:47 +0100 Clive Menzies [EMAIL PROTECTED] wrote: When I did this, it took the values and reset them to to the default values. So having gone around in circles more than once, I tried just booting without update grub and it worked fine. Is there a flag in menu.lst that stops it resetting? I'm not aware of a flag to reset to defaults. Did you delete any of the lines in menu.lst, or did you just edit them for your post? No I'm sure that I didn't delete anything. I was aware that I shouldn't do anything other than edit the drive designations. Excerpt from /sbin/update-grub: # Magic markers we use start=### BEGIN AUTOMAGIC KERNELS LIST end=### END DEBIAN AUTOMAGIC KERNELS LIST startopt=## ## Start Default Options ## endopt=## ## End Default Options ## I'm guessing you removed one or more of the magic markers, so update-grub restored the defaults. I don't try to trim the file, I just edit the lines beginning with only one hash and leave the rest alone. The two PC's in question are used by my partner and sons (I'm on a G4 using yaboot) - so I am reluctant to go and muck about with the set-up which is working fine - I have a history of turning a drama into a crisis;) However, I would like to try this again. I'll have to wait until I get the opportunity to convert some other windows PC to Debian although one of the server's on our network is non-critical (currently booting from LILO), so I guess I could experiment with that ;) Not a high priority at present but maybe soon ... Thanks for your help Clive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tuesday 24 June 2003 01:27, Hugh Saunders wrote: On Tue, Jun 24, 2003 at 12:52:01AM +1200, cr wrote: I'm still booting off floppy and trying to get GRUB sorted. erm, not quite sure whats wrong but what happens if you boot grub from floppy then run root (hd0,0) then setup (hd0) from floppy? That actually worked previously with Red Hat (on a different hard drive). I just tried it on this setup and got: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) For some reason GRUB can't see the files. grub find /boot/grub/stage1 (or any other file) brings up a 'File not found' cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tuesday 24 June 2003 08:40, Kevin McKinley wrote: On Tue, 24 Jun 2003 00:52:01 +1200 cr [EMAIL PROTECTED] wrote: ### BEGIN AUTOMAGIC KERNELS LIST # kopt=root=/dev/hda1 ro # groot=(hd0,0) # alternative=true # lockalternative=false # altoptions=(recovery mode) single # howmany=all title Debian GNU/Linux, kernel 2.2.20-idepci root(hd0,0) kernel /vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault The kernel line is wrong. In that line root tells the kernel what partition to mount as the root filesystem. Change it to kernel/vmlinuz-2.2.20-idepci root=/dev/hda5 ro and try again. Kevin Tried that - no change. It may well be wrong but I have the impression that it won't try to execute until after GRUB has found the kernel and loaded it, and the error message I get - GRUB Loading, please wait. Error 2 suggests to me that the boot process isn't getting that far. cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tuesday 24 June 2003 01:56, Clive Menzies wrote: On (24/06/03 00:52), cr wrote: I'm still booting off floppy and trying to get GRUB sorted. I have /boot on /dev/hda1 and root on /dev/hda5 (At first, LILO was just hanging with 'LI 99 99 99' and GRub, when I installed it gave an Error 5 - 'partition table bad'.Eventually I got half a clue and added /boot (/dev/hda1)into /etc/fstab and started again...) Lilo when installed and booted just gives 'LI' and stops. Grub when installed and booted gives the following: GRUB Loading Stage 1.5 GRUB Loading, please wait... Error 2(and that's as far as it gets) Error 2 means Bad file or directory type This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO. Does anyone have any ideas? [The details - I installed GRUB in accordance with /usr/share/doc/grub/README.Debian - I'm not expert on this but have successfully set Grub up on two PC's. I used: http://www.linuxorbit.com/modules.php?op=modloadname=Sectionsfile=indexr eq=viewarticleartid=539page=1 to guide me. The only variation I adopted was to not rerun update grub after editing the menu.lst. It seemed to put all the settings back to their original values. That article was actually one of the sources I used for reference while trying to debug GRUB. I don't have separate boot partitions - your problem seems to be that root is hda5, whereas menu.lst points to hda1. Did update grub set it back that way? No, it didn't, I set it that way. OTOH, changing it to hda5 makes no difference, I think because the boot process isn't getting that far. I also installed a later kernel, 2.4.18, before installing grub - not that this should affect it. HTH Clive Thanks, but the problem seems to be still there. So far as I can tell, GRUB Stage 1 is loading, but it can't 'see' Stage 1.5 or Stage 2 (one or the other). cr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, Jun 24, 2003 at 07:21:20PM +1200, cr wrote: On Tuesday 24 June 2003 01:27, Hugh Saunders wrote: On Tue, Jun 24, 2003 at 12:52:01AM +1200, cr wrote: I'm still booting off floppy and trying to get GRUB sorted. erm, not quite sure whats wrong but what happens if you boot grub from floppy then run root (hd0,0) then setup (hd0) from floppy? That actually worked previously with Red Hat (on a different hard drive). I just tried it on this setup and got: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) For some reason GRUB can't see the files. grub find /boot/grub/stage1 (or any other file) brings up a 'File not found' you could try copying the whole of /usr/lib/grub/i386-pc/ to your /boot/boot Thats what i tend to do [i didnt realise that grub-install copies stuff for you!] grub can list files for you once you have set root. type / then tab and see what files actually are on your boot partition. -- hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, June 24 at 7:21 PM EDT cr [EMAIL PROTECTED] wrote: I just tried it on this setup and got: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) For some reason GRUB can't see the files. grub find /boot/grub/stage1 (or any other file) brings up a 'File not found' cr Been a while since I mucked around with grub, can't you try grubfind (hd0,0)/boot/grub/Stage1 ? That might have just been me experimenting at the time, though. What about specifying $find /boot/boot/grub/Stage1 from the grub prompt. I also assume that caps count but am not sure. What does $ls -l /boot/boot/grub show? Are you doing this with the drive mounted? I think that since the how-to docs I have seen recommend booting off of the grub-boot floppy that it thinks it is not mounted. Just throwing out ideas in case you were lacking any :) Hope it helps. Shawn Lamson [EMAIL PROTECTED] Debian GNU/Linux 3.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, 24 Jun 2003 19:21:20 +1200 cr [EMAIL PROTECTED] wrote: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) For some reason GRUB can't see the files. grub find /boot/grub/stage1 (or any other file) brings up a 'File not found' Your files are in /boot/boot/grub, and they should be in /boot/grub. To solve your problem, do cp -a /boot/boot/grub /boot. Then you can delete the directory /boot/boot/grub and its contents. Grub-install should work then. Then consider filing a bug against grub. grub-install should look for its files in /boot/boot/grub as well as /boot/grub; update-grub already does this. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
Kevin McKinley [EMAIL PROTECTED] writes: On Tue, 24 Jun 2003 19:21:20 +1200 cr [EMAIL PROTECTED] wrote: grub setup (hd0) Checking if /boot/grub/Stage1 exists ... no Checking if /grub/Stage1 exists ... no Error 15: File not found /boot/boot/grub/Stage1 does exist, though. (And df confirms that I have got /dev/hda1 mounted as /boot) Your files are in /boot/boot/grub, and they should be in /boot/grub. To solve your problem, do cp -a /boot/boot/grub /boot. That's not going to help if /boot is a separate partition. You need to separately tell GRUB where to find the stage1.5 and stage2 files and where to install the boot sector; the Info manual suggests that you want root (hd0,0) setup (hd0) In this situation, I believe /boot/boot/grub is the correct directory. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, 24 Jun 2003 14:05:24 -0400 David Z Maze [EMAIL PROTECTED] wrote: Your files are in /boot/boot/grub, and they should be in /boot/grub. To solve your problem, do cp -a /boot/boot/grub /boot. That's not going to help if /boot is a separate partition. You need to separately tell GRUB where to find the stage1.5 and stage2 files and where to install the boot sector; the Info manual suggests that you want root (hd0,0) setup (hd0) In this situation, I believe /boot/boot/grub is the correct directory. You may be right. But why would /boot being a separate partition have anything to do with it? His partition has a directory boot, and inside that directory another called grub. That would be OK if it were mounted on /, but of course we can't do that. When a partition containing boot/grub is mounted on /boot, the path to the files becomes /boot/boot/grub. But grub isn't looking there for the files; its looking in /boot/grub and not finding them. My solution puts the files where grub expects to see them. I suspect this happens because the default way to install debian is without a separate /boot partition, so grub-install isn't handling the situation well. If someone can see a flaw in the above please let me know; I may yet be the learner here. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, Jun 24, 2003 at 12:52:01AM +1200, cr wrote: I'm still booting off floppy and trying to get GRUB sorted. erm, not quite sure whats wrong but what happens if you boot grub from floppy then run root (hd0,0) then setup (hd0) from floppy? -- hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On (24/06/03 00:52), cr wrote: I'm still booting off floppy and trying to get GRUB sorted. I have /boot on /dev/hda1 and root on /dev/hda5 (At first, LILO was just hanging with 'LI 99 99 99' and GRub, when I installed it gave an Error 5 - 'partition table bad'.Eventually I got half a clue and added /boot (/dev/hda1)into /etc/fstab and started again...) Lilo when installed and booted just gives 'LI' and stops. Grub when installed and booted gives the following: GRUB Loading Stage 1.5 GRUB Loading, please wait... Error 2(and that's as far as it gets) Error 2 means Bad file or directory type This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO. Does anyone have any ideas? [The details - I installed GRUB in accordance with /usr/share/doc/grub/README.Debian - I'm not expert on this but have successfully set Grub up on two PC's. I used: http://www.linuxorbit.com/modules.php?op=modloadname=Sectionsfile=indexreq=viewarticleartid=539page=1 to guide me. The only variation I adopted was to not rerun update grub after editing the menu.lst. It seemed to put all the settings back to their original values. I don't have separate boot partitions - your problem seems to be that root is hda5, whereas menu.lst points to hda1. Did update grub set it back that way? I also installed a later kernel, 2.4.18, before installing grub - not that this should affect it. HTH Clive 1. grub-install --root-directory=boot /dev/hda 2. Ran update-grub 3. Checked /boot/boot/grub/menu.lst and didn't need to change a thing - the significant lines (leaving out all the comments) are: default 0 timeout 5 color cyan/blue white/blue ### BEGIN AUTOMAGIC KERNELS LIST # kopt=root=/dev/hda1 ro # groot=(hd0,0) # alternative=true # lockalternative=false # altoptions=(recovery mode) single # howmany=all title Debian GNU/Linux, kernel 2.2.20-idepci root (hd0,0) kernel/vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault title Debian GNU/Linux, kernel 2.2.20-idepci (recovery mode) root (hd0,0) kernel/vmlinuz-2.2.20-idepci root=/dev/hda1 ro single savedefault ### END DEBIAN AUTOMAGIC KERNELS LIST In /boot I have (amongst other files left over from lilo) -rw-r--r--1 root root 224124 Jun 21 23:05 System.map-2.2.20-idepci -rw-r--r--1 root root 3888 Jun 21 23:05 config-2.2.20-idepci -rw---1 root root17408 Jun 21 23:50 map -rw-r--r--1 root root 665509 Jun 21 23:05 vmlinuz-2.2.20-idepci In /boot/boot/grub I have (put there by grub-install) *all* the stage1_5 flavours, including -rw-r--r--1 root root 60 Jun 21 23:06 device.map -rw-r--r--1 root root 7904 Jun 22 00:10 e2fs_stage1_5 -rw-r--r--1 root root 2392 Jun 22 00:10 menu.lst -rw-r--r--1 root root 512 Jun 22 00:10 stage1 -rw-r--r--1 root root95712 Jun 22 00:10 stage2 None of those look like symlinks to me. Have I got root set right in menu.lst, as /dev/hda1? Should it be /dev/hda5? Seems unlikely to be the cause since the boot menu or 'booting in 5 seconds' message never comes up and I wouldn't expect that root setting to take effect until after the menu.. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Mon, 23 Jun 2003 14:56:37 +0100 Clive Menzies [EMAIL PROTECTED] wrote: to guide me. The only variation I adopted was to not rerun update grub after editing the menu.lst. It seemed to put all the settings back to their original values. Perhaps something was wrong with the way you edited menu.lst. What you need to do is go into the AUTOMAGIC KERNELS LIST section, and edit the lines beginning with only one hash -- those are the default settings. Don't delete the lines or remove the single leading hash. Then run update-grub again. I don't have separate boot partitions - your problem seems to be that root is hda5, whereas menu.lst points to hda1. Did update grub set it back that way? That isn't a problem. It means his grub root is /dev/hda1, so he should use root (hd0,0) as the first line in menu.lst. The kernel line should read kernel /boot/vmlinuz-whatever root=/dev/hda5 ro or something like that. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Tue, 24 Jun 2003 00:52:01 +1200 cr [EMAIL PROTECTED] wrote: ### BEGIN AUTOMAGIC KERNELS LIST # kopt=root=/dev/hda1 ro # groot=(hd0,0) # alternative=true # lockalternative=false # altoptions=(recovery mode) single # howmany=all title Debian GNU/Linux, kernel 2.2.20-idepci root (hd0,0) kernel/vmlinuz-2.2.20-idepci root=/dev/hda1 ro savedefault The kernel line is wrong. In that line root tells the kernel what partition to mount as the root filesystem. Change it to kernel /vmlinuz-2.2.20-idepci root=/dev/hda5 ro and try again. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On (23/06/03 16:36), Kevin McKinley wrote: On Mon, 23 Jun 2003 14:56:37 +0100 Clive Menzies [EMAIL PROTECTED] wrote: to guide me. The only variation I adopted was to not rerun update grub after editing the menu.lst. It seemed to put all the settings back to their original values. Perhaps something was wrong with the way you edited menu.lst. What you need to do is go into the AUTOMAGIC KERNELS LIST section, and edit the lines beginning with only one hash -- those are the default settings. Don't delete the lines or remove the single leading hash. Then run update-grub again. When I did this, it took the values and reset them to to the default values. So having gone around in circles more than once, I tried just booting without update grub and it worked fine. Is there a flag in menu.lst that stops it resetting? I don't have separate boot partitions - your problem seems to be that root is hda5, whereas menu.lst points to hda1. Did update grub set it back that way? That isn't a problem. It means his grub root is /dev/hda1, so he should use root (hd0,0) as the first line in menu.lst. The kernel line should read kernel /boot/vmlinuz-whatever root=/dev/hda5 ro or something like that. That is what I meant but didn't make myself very clear ;) Thanks for the guidance Clive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB problem
On Mon, 23 Jun 2003 23:04:47 +0100 Clive Menzies [EMAIL PROTECTED] wrote: When I did this, it took the values and reset them to to the default values. So having gone around in circles more than once, I tried just booting without update grub and it worked fine. Is there a flag in menu.lst that stops it resetting? I'm not aware of a flag to reset to defaults. Did you delete any of the lines in menu.lst, or did you just edit them for your post? Excerpt from /sbin/update-grub: # Magic markers we use start=### BEGIN AUTOMAGIC KERNELS LIST end=### END DEBIAN AUTOMAGIC KERNELS LIST startopt=## ## Start Default Options ## endopt=## ## End Default Options ## I'm guessing you removed one or more of the magic markers, so update-grub restored the defaults. I don't try to trim the file, I just edit the lines beginning with only one hash and leave the rest alone. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub problem SOLVED
Andrej Congratulation on solving your grub problem. You mention a document that describes your situation. Please name it, and tell where it can be found. David On Fri, 18 Jan 2002, andrej hocevar wrote: Hello! I updated grub to 0.9 and it totally amazes me! So many new commands, great! I've also found a document that describes my situation in detail. The solution is to tell grub the first partition be hidden and then boot from a windows floppy. What simplicity. I haven't tried it out yet! :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I hope this is all of the above.)
Re: grub problem SOLVED
The document's url is as follows: linuxdoc.org/HOWTO/mini/Multiboot-with-GRUB.html On Sat, Jan 19, 2002 at 10:12:45AM -0500, David Teague wrote: Andrej Congratulation on solving your grub problem. You mention a document that describes your situation. Please name it, and tell where it can be found. David On Fri, 18 Jan 2002, andrej hocevar wrote: Hello! I updated grub to 0.9 and it totally amazes me! So many new commands, great! I've also found a document that describes my situation in detail. The solution is to tell grub the first partition be hidden and then boot from a windows floppy. What simplicity. I haven't tried it out yet! :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I hope this is all of the above.)
Re: grub problem: cannot read from drive
On Fri, Aug 11, 2000 at 08:27:48PM -0500, Pat Mahoney wrote: I have grub on mbr of /dev/hda. I have a new harddrive at /dev/hdc with Debian. I have an older, 200meg hard drive at /dev/hdb. I am trying to install Debian onto /dev/hdb1. I have done so, but I cannot get grub to boot it. When I am at grub command line, I type this: kernel (hd1,0)/ thats wrong... do: root (hd1,0) kernel=/vmlinuz root=/dev/hdb1 boot the first line tells Grub, where to look for the kernel to boot. the second line specifies the kernel. linux needs a parameter root=, to know which partition it should mount as /. moritz -- /* Moritz Schulte [EMAIL PROTECTED] * http://hp9001.fh-bielefeld.de/~moritz/ * PGP-Key available, encrypted Mail is welcome. */
SOLVED Re: grub problem: cannot read from drive
On Fri, Aug 11, 2000 at 08:27:48PM -0500, Pat Mahoney wrote: I have grub on mbr of /dev/hda. I have a new harddrive at /dev/hdc with Debian. I have an older, 200meg hard drive at /dev/hdb. ^ I am trying to install Debian onto /dev/hdb1. I have done so, but I cannot get grub to boot it. When I am at grub command line, I type this: kernel (hd1,0)/ Then if I hit tab it shows a the listing of files and directories in /. I type vmlinuz so command line looks like this: kernel(hd1,0)/vmlinuz root=/dev/hdb1 This command is totally valid, at least with my version of grub. I'm not sure what version is on the mbr. I think there should be a space after kernel, but anyway... When I press enter I get this error: Bad file or directory type Grub info file says it cannot handle sym links (or directories for that matter), but it does fine on /dev/hdc with symlinks. When I type in the actual file ((hd1,0)/boot/vmlinuz-2.2.17) I get the same error. I cannot get grub to see anything below the toplevel directories in /. SOLUTION: I changed /dev/hdb to LBA mode in the bios; everything works fine now. It was not in LBA mode by default apparently because it is old. Why that made a difference I don't know. Perhaps it's the 1024 cylinder problem? I don't think a 200 meg drive has 1024 cylinders. I don't think that was the problem though because grub didn't just fail to boot; it failed to read the disk at all (below the toplevel). Hmm... -- Pat Mahoney [EMAIL PROTECTED] We waste so many moments standing on convention -- Nick Hexum
Re: grub problem: cannot read from drive
I'm no grub expert (only started using it recently), but in the menu file I have something like: title Linux Foo root (hd0,2) kernel --type=biglinux /vmlinuz root=/dev/hda3 I don't know if specifying the root filesystem and the --type=biglinux (for bzImage) will help. I recall having problems without the biglinux specification. -- MegaHAL quote: I think a blowpipe is a marijuana cigarrette. It'll get you deleted!
