Boot from UltraATA?

marcheikens · 09-16-2003, 09:41 AM

Hello, I recently got a new Western Digital UltraATA-100 drive (120GB). I have an Asus A7V with onboard Promise controller (Promise Drivers BIOS Rev 2.01.0 Build 39). I am trying to copy my system over to the new drive, and I have looked for discussions about this in these forums to no avail.

The partition table for /dev/hde looks like this:

Code:

   Device Boot    Start       End    Blocks   Id  System
/dev/hde1             1     11672  93755308+  83  Linux
/dev/hde2         11673     11735    506047+  82  Linux swap
/dev/hde3         11736     14593  22956885    b  Win95 FAT32

I've been to http://p-two.net/hard-drive/hard-drive.html and the Hard Disk Upgrade HOW-TO, and I have got to the point where I have copied everything to /dev/hde1. The only problem is I can't get grub to install on the new drive, when I mount hde1 to /new-drive and then chroot /new-drive, I get the following:

Code:

[root@pants /]# chroot /new-drive
[root@pants /]# grub-install /dev/hde
/dev/hde does not have any corresponding BIOS drive.

Why is this? What does that error mean? I messed up grub after I tried this the first time, at least now I know how to fix it, but any ideas how I can accomplish what I'm attempting?

Thanks for any help.

Marc

mhbell · 09-16-2003, 10:22 AM

Quote:

Originally posted by marcheikens
Hello, I recently got a new Western Digital UltraATA-100 drive (120GB). I have an Asus A7V with onboard Promise controller (I believe it's 1.39). I am trying to copy my system over to the new drive, and I have looked for discussions about this in these forums to no avail.

The partition table for /dev/hde looks like this:

Code:

Device Boot Start End Blocks Id System /dev/hde1 1 11672 93755308+ 83 Linux /dev/hde2 11673 11735 506047+ 82 Linux swap /dev/hde3 11736 14593 22956885 b Win95 FAT32

I've been to http://p-two.net/hard-drive/hard-drive.html and the Hard Disk Upgrade HOW-TO, and I have got to the point where I have copied everything to /dev/hde1. The only problem is I can't get grub to install on the new drive, when I mount hde1 to /new-drive and then chroot /new-drive, I get the following:

Code:

[root@pants /]# chroot /new-drive [root@pants /]# grub-install /dev/hde /dev/hde does not have any corresponding BIOS drive.

Why is this? What does that error mean? I messed up grub after I tried this the first time, at least now I know how to fix it, but any ideas how I can accomplish what I'm attempting?

Thanks for any help.

Marc

You might try one of these utilities to do the job.

http://www.partimage.org/

Mondo Rescue
http://www.microwerks.net/~hugo/

If it is simply for transfer of one disk to another, and not for back-up purposes . . . have a look at LinuxChix,
http://www.linuxchix.org/pipermail/t...ry/001899.html
you might not need any extra software, a simple command like

# cat /dev/hda > /dev/hdb

might do the trick
Mel

camelrider · 09-16-2003, 12:36 PM

Has your BIOS an option to enable/disable the SATA drives as boot devices, similar to making floppy/CD-rom drives bootable in the BIOS?

marcheikens · 09-18-2003, 12:23 AM

Quote:

You might try one of these utilities to do the job.
(snip)

Those look like useful utilities, but it seems like these solve the problem of copying stuff over correctly. My problem is that I've copied the data to the new drive, chroot'ed to it and done a grub-install /dev/hde, but I can't start up from it.

Quote:

Has your BIOS an option to enable/disable the SATA drives as boot devices, similar to making floppy/CD-rom drives bootable in the BIOS?

The onboard UltraATA controllers are enabled (Auto-Detect) and the new drive was set before other devices in the boot order. However, the "loading GRUB" message (can't remember exactly what it said even though I started at it for several minutes) appeared and the computer hung there.

Thanks for your suggestions though, keep 'em coming.

marcheikens · 09-20-2003, 12:34 AM

Bumping this up the list hopefully, but with more information:

I decided that maybe I needed to install grub in a more roundabout way, so I installed from the cd's to /dev/hde1, unchecking every option I could. Somehow, with nothing selected, I still had to "install" 528MB or so. I didn't format before I did that, so it didn't delete stuff that was already there (I hope).

Now hde1 will boot, but when I get to the RH Login screen, and everafter, the mouse doesn't work. Plus, I am quite certain that grub is still being found on hda. Ideally I'd like to make hda just a plain old storage device, not my root partition.

Anyhow, starting from hda is more interesting now: I get a grub error:

Code:

Booting 'Maxtor RH 9'

rootnoverify(hd0,0)
chainloader +1

Error 13:  Invalid or unsupported executable format

Press any key to continue

SOooo, having backed up my original grub.conf, I changed some stuff:

Original grub.conf (/etc/grub.conf.backup):

Code:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,0)
#          kernel /boot/vmlinuz-version ro root=/dev/hda1
#          initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-6)
        root (hd0,0)
        kernel /boot/vmlinuz-2.4.20-6 ro root=LABEL=/
        initrd /boot/initrd-2.4.20-6.img

grub.conf after "installing" on hde (grub.install.backup.not.original):

Code:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd1,0)
#          kernel /boot/vmlinuz-version ro root=/dev/hde1
#          initrd /boot/initrd-version.img
#boot=/dev/hde1
default=0
timeout=10
splashimage=(hd1,0)/boot/grub/splash.xpm.gz
title Western Digital RH 9 (2.4.20-6)
        root (hd1,0)
        kernel /boot/vmlinuz-2.4.20-6 ro root=LABEL=/1 hdc=ide-scsi
        initrd /boot/initrd-2.4.20-6.img
title Maxtor RH 9
        rootnoverify (hd0,0)
        chainloader +1

modified grub.conf (had no idea as to what I was doing, just messing around and hoping):

Code:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd1,0)
#          kernel /boot/vmlinuz-version ro root=/dev/hde1
#          initrd /boot/initrd-version.img
#boot=/dev/hde1
default=0
timeout=10
splashimage=(hd1,0)/boot/grub/splash.xpm.gz
title Western Digital RH 9 (2.4.20-6)
        root (hd1,0)
        kernel /boot/vmlinuz-2.4.20-6 ro root=LABEL=/ hdc=ide-scsi
        initrd /boot/initrd-2.4.20-6.img
title Maxtor RH 9
        root (hd0,0)
        kernel /boot/vmlinux-2.4.20-6 ro root=LABEL=/ hdc=ide-scsi
        initrd /boot/initrd-2.4.20-6.img

Anything anyone can think of? When I run that, nothing works, I get a "Kernel panic: No init found. Try passing init= option to kernel."

Anyone? Bueller?

Thanks--

marc