Re: grub: not found or no block device
Am Samstag, 20. Januar 2007 06:30 schrieb Andrew Sackville-West: On Fri, Jan 19, 2007 at 11:51:37PM +0100, Bernd Kloss wrote: Hello, Etch installed on a computer with scsii-hd and transferred to a similar computer with ide-hd. Both: first partition primary/bootable and 1 extended partition with 1 logical drive: swap device.map, menu.lst and fstab adapted: hda instead of sda Booting with rescue-system, mounting /dev/hda1 on /mnt chroot /mnt grub-install /dev/hda(1) hda(1) = hda or hda1 = /dev/hda(1) not found or no block device Also tried: grub-install --recheck /dev/hda(1) = still the same okay, I just went through this nightmare (more details to follow in a later post). Unfortunately, I didn't take good detailed notes on what I did... but the best option is... *outside* the chroot grub-install /dev/hda will install the boot loader to the MBR you could also use the grub shell grub root (hd0,0) grub setup (hd0) might work. in my recent adventure with this, the menu did not work properly and I had to boot from the grub command line the first time in. Then I was able to grub-install and update-grub and reboot to the usual grub menu. other things to note that I have learned: if you are booting with an initrd then you need to rebuild that initrd.img file to that the kernel can find the root device. If you are using an initrd that was built on a scsi system, then it will look for sda1 to mount / after the initrd loads, but won't find it and the kernel will panic. this has to been done from the chroot. you'll have to mount proc and you may have to rig up a dev and sys as well, depending on your initrd builder (mkinitrd, yaird, whatever). I just moved the current initrd out of the way and built a new one inside the chroot. its a little finicky and you may have to fix the ROOT= param or the MOUNTDEV param in your initrd configuration. hth. A Thank you, Andrew and the others, from Gerhard Brauer came the solution: only grub as bootloader on /dev/hda 1. booting the clone in rescue-mode and mount /dev/hda1 /mnt 2. mount -o bind /dev /mnt/dev 3. mount -o bind -t proc /proc /mnt/proc 4. chroot /mnt 5. grub-shell with root (hd0,0) and setup (hd0) I tried different ways, but only this one worked. Don't delete stage2 don't run grub-install. It'll produce the error /dev/sda1 does not have corresponding BIOS drive Greetings Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grub: not found or no block device
Hello, Etch installed on a computer with scsii-hd and transferred to a similar computer with ide-hd. Both: first partition primary/bootable and 1 extended partition with 1 logical drive: swap device.map, menu.lst and fstab adapted: hda instead of sda Booting with rescue-system, mounting /dev/hda1 on /mnt chroot /mnt grub-install /dev/hda(1) hda(1) = hda or hda1 = /dev/hda(1) not found or no block device Also tried: grub-install --recheck /dev/hda(1) = still the same How can I solve this problem? Thank you Bernd _ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071distributionid=0066 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub: not found or no block device
On Fri, Jan 19, 2007 at 11:51:37PM +0100, Bernd Kloss wrote: Booting with rescue-system, mounting /dev/hda1 on /mnt chroot /mnt grub-install /dev/hda(1) hda(1) = hda or hda1 = /dev/hda(1) not found or no block device Also tried: grub-install --recheck /dev/hda(1) = still the same How can I solve this problem? What happens if you go right to the grub command line instead of via grub-install? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub: not found or no block device
On 1/19/07, Bernd Kloss [EMAIL PROTECTED] wrote: Etch installed on a computer with scsii-hd and transferred to a similar computer with ide-hd. Both: first partition primary/bootable and 1 extended partition with 1 logical drive: swap device.map, menu.lst and fstab adapted: hda instead of sda Booting with rescue-system, mounting /dev/hda1 on /mnt chroot /mnt grub-install /dev/hda(1) hda(1) = hda or hda1 = /dev/hda(1) not found or no block device I'm no expert, but I'd leave out the chroot step. I suspect the jailed system doesn't see the drive the same way the non-jailed system does. But as mentioned, I'm no expert. -- Kent West http://kentwest.blogspot.com
Re: grub: not found or no block device
On Fri, Jan 19, 2007 at 08:32:29PM -0600, Kent West wrote: On 1/19/07, Bernd Kloss [EMAIL PROTECTED] wrote: Etch installed on a computer with scsii-hd and transferred to a similar computer with ide-hd. Both: first partition primary/bootable and 1 extended partition with 1 logical drive: swap device.map, menu.lst and fstab adapted: hda instead of sda Booting with rescue-system, mounting /dev/hda1 on /mnt chroot /mnt grub-install /dev/hda(1) hda(1) = hda or hda1 = /dev/hda(1) not found or no block device I'm no expert, but I'd leave out the chroot step. I suspect the jailed system doesn't see the drive the same way the non-jailed system does. But as mentioned, I'm no expert. Using Etch installer in rescue mode you can reinstall grub from the menu. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub: not found or no block device
On Fri, Jan 19, 2007 at 11:51:37PM +0100, Bernd Kloss wrote: Hello, Etch installed on a computer with scsii-hd and transferred to a similar computer with ide-hd. Both: first partition primary/bootable and 1 extended partition with 1 logical drive: swap device.map, menu.lst and fstab adapted: hda instead of sda Booting with rescue-system, mounting /dev/hda1 on /mnt chroot /mnt grub-install /dev/hda(1) hda(1) = hda or hda1 = /dev/hda(1) not found or no block device Also tried: grub-install --recheck /dev/hda(1) = still the same okay, I just went through this nightmare (more details to follow in a later post). Unfortunately, I didn't take good detailed notes on what I did... but the best option is... *outside* the chroot grub-install /dev/hda will install the boot loader to the MBR you could also use the grub shell grub root (hd0,0) grub setup (hd0) might work. in my recent adventure with this, the menu did not work properly and I had to boot from the grub command line the first time in. Then I was able to grub-install and update-grub and reboot to the usual grub menu. other things to note that I have learned: if you are booting with an initrd then you need to rebuild that initrd.img file to that the kernel can find the root device. If you are using an initrd that was built on a scsi system, then it will look for sda1 to mount / after the initrd loads, but won't find it and the kernel will panic. this has to been done from the chroot. you'll have to mount proc and you may have to rig up a dev and sys as well, depending on your initrd builder (mkinitrd, yaird, whatever). I just moved the current initrd out of the way and built a new one inside the chroot. its a little finicky and you may have to fix the ROOT= param or the MOUNTDEV param in your initrd configuration. hth. A signature.asc Description: Digital signature
