Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Re: [SLE] LILO vs GRUB
- From: "Carlos E. R." <robin1.listas@xxxxxxxxxx>
- Date: Sat, 5 Nov 2005 15:41:14 +0000 (UTC)
- Message-id: <Pine.LNX.4.61.0511041415320.18854@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El 2005-11-04 a las 08:55 +0100, Gerhard den Hollander escribió:
Please, remember to post to the list.
> > Yes, it does have to do. It is 9.3, an installed system working for
> > several years now; what I was doing is upgrading one HD, not the system.
>
> But in that case, grub (again) has nothing to do with it.
>
> All that matters is if the booted system sees the 3rd disk.
>
> Maybe Im misreading you, but it sounds like you are using grub to diagnose
> wether or not suse 93 can see your /dev/hdd .
No. I said already that Yast sees the disk, fdisk sees the disk, the
kernel sees the disk; and the system is up and running, with that disk.
I said that it is _only_ _grub_ who does not see that disk, but I hope
that now the point is clear. I had to place /boot on another disk, or it
would not see it.
> Of course grub does not see the list.
> You have added a disk, but you have not updated grubs device map
Shouldn't Yast be clever enough to do that? Perhaps it did, perhaps it
didn't. The file is dated on Oct 8, that is fairly recent.
> The autocompletion feature you are using in your original example only
> offers the devices that are listed in /boot/grub/device.map.
I didn't see in the manual a mention of that. Is it needed only for
autocompletion, or something else? If I force hd3 it complains.
| grub> root (hd3,1)
|
| Error 21: Selected disk does not exist
>
> That is something else then saying that grub does not see the disk.
As far as the messages I see go, yes, it does not see the disk. Why, is
another thing, and it is not clearly stated in the manual what I should
do. The troubleshooting section didn't help. I read it.
>
> Suggested reading:
> http://www.gnu.org/software/grub/manual/grub.html
I'm not connected. I have the manual included in the distro, the info
pages. I suppose you mean "grub-install --recheck", but that does nothing
but pop the useless help page again:
|
|Usage: grub-install [OPTION] install_device
|...
| --root-directory=DIR install GRUB images under the directory DIR
| instead of the root directory
|...
| --recheck probe a device map even if it already exists
|
|INSTALL_DEVICE can be a GRUB device name or a system device filename.
|
And INSTALL_DEVICE is: a) where the MBR is b) where /boot partition is c)
where "/" partition is? Mind, all three are different devices in my case.
Should I also use the option --root-directory?
What is the exact command I should use, then?
Anyway, it is a simple text file, I'll edit it by hand. It works. I'll try
booting later. I'll let Yast bootloader install do his job.
[...]
No go. I get "Grub Hard Disk Error" before even getting the boot up menu.
This means:
Hard Disk Error
The stage2 or stage1.5 is being read from a hard disk, and the
attempt to determine the size and geometry of the hard disk failed.
and the systems (plural) were now unbootable, all of them. I went to Yast
rescue thing on DVD, it repaired a few things, broke some others
(including the bootloader) and systems remained unbootable. I tried "boot
installed system", which also failed, because it mounted the root
filesystems RO - even if mount command said that it was RW. I had heard of
that problem before, but without access to my systems, I couldn't read it
up. I booted then the rescue on CD, got a linux, repaired a bit of what
the Yast rescue had broken on /etc/fstab - for instance, this:
dev/hda9 /data2 swap pri=42 0 0
dev/hdb5 /data2 swap pri=42 0 0
It is saying I should MOUNT my swap partitions!!! :-/
and reinstalled grub where it was, getting the command from a backup:
root (hd1,1)
install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd1,1)/grub/menu.lst
quit
rebooted, and up and running.
So, several hours later, I stay where I was at the beginning... grub can
NOT read my big disk. The linux kernel can. MsDOS 6, can. Good grief! :-(
Perhaps I'll try lilo. At least, I can understand how it works.
- --
Saludos
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDbMzwtTMYHG2NR9URAt+UAJwM0uQ+xHlNN6K8rxU0SlSq2K7EIACdFUka
7147FjQyljAm5rvvnUfgilQ=
=/Np0
-----END PGP SIGNATURE-----
Hash: SHA1
El 2005-11-04 a las 08:55 +0100, Gerhard den Hollander escribió:
Please, remember to post to the list.
> > Yes, it does have to do. It is 9.3, an installed system working for
> > several years now; what I was doing is upgrading one HD, not the system.
>
> But in that case, grub (again) has nothing to do with it.
>
> All that matters is if the booted system sees the 3rd disk.
>
> Maybe Im misreading you, but it sounds like you are using grub to diagnose
> wether or not suse 93 can see your /dev/hdd .
No. I said already that Yast sees the disk, fdisk sees the disk, the
kernel sees the disk; and the system is up and running, with that disk.
I said that it is _only_ _grub_ who does not see that disk, but I hope
that now the point is clear. I had to place /boot on another disk, or it
would not see it.
> Of course grub does not see the list.
> You have added a disk, but you have not updated grubs device map
Shouldn't Yast be clever enough to do that? Perhaps it did, perhaps it
didn't. The file is dated on Oct 8, that is fairly recent.
> The autocompletion feature you are using in your original example only
> offers the devices that are listed in /boot/grub/device.map.
I didn't see in the manual a mention of that. Is it needed only for
autocompletion, or something else? If I force hd3 it complains.
| grub> root (hd3,1)
|
| Error 21: Selected disk does not exist
>
> That is something else then saying that grub does not see the disk.
As far as the messages I see go, yes, it does not see the disk. Why, is
another thing, and it is not clearly stated in the manual what I should
do. The troubleshooting section didn't help. I read it.
>
> Suggested reading:
> http://www.gnu.org/software/grub/manual/grub.html
I'm not connected. I have the manual included in the distro, the info
pages. I suppose you mean "grub-install --recheck", but that does nothing
but pop the useless help page again:
|
|Usage: grub-install [OPTION] install_device
|...
| --root-directory=DIR install GRUB images under the directory DIR
| instead of the root directory
|...
| --recheck probe a device map even if it already exists
|
|INSTALL_DEVICE can be a GRUB device name or a system device filename.
|
And INSTALL_DEVICE is: a) where the MBR is b) where /boot partition is c)
where "/" partition is? Mind, all three are different devices in my case.
Should I also use the option --root-directory?
What is the exact command I should use, then?
Anyway, it is a simple text file, I'll edit it by hand. It works. I'll try
booting later. I'll let Yast bootloader install do his job.
[...]
No go. I get "Grub Hard Disk Error" before even getting the boot up menu.
This means:
Hard Disk Error
The stage2 or stage1.5 is being read from a hard disk, and the
attempt to determine the size and geometry of the hard disk failed.
and the systems (plural) were now unbootable, all of them. I went to Yast
rescue thing on DVD, it repaired a few things, broke some others
(including the bootloader) and systems remained unbootable. I tried "boot
installed system", which also failed, because it mounted the root
filesystems RO - even if mount command said that it was RW. I had heard of
that problem before, but without access to my systems, I couldn't read it
up. I booted then the rescue on CD, got a linux, repaired a bit of what
the Yast rescue had broken on /etc/fstab - for instance, this:
dev/hda9 /data2 swap pri=42 0 0
dev/hdb5 /data2 swap pri=42 0 0
It is saying I should MOUNT my swap partitions!!! :-/
and reinstalled grub where it was, getting the command from a backup:
root (hd1,1)
install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd1,1)/grub/menu.lst
quit
rebooted, and up and running.
So, several hours later, I stay where I was at the beginning... grub can
NOT read my big disk. The linux kernel can. MsDOS 6, can. Good grief! :-(
Perhaps I'll try lilo. At least, I can understand how it works.
- --
Saludos
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDbMzwtTMYHG2NR9URAt+UAJwM0uQ+xHlNN6K8rxU0SlSq2K7EIACdFUka
7147FjQyljAm5rvvnUfgilQ=
=/Np0
-----END PGP SIGNATURE-----
| < Previous | Next > |