converting to raid - Error 2

This is something I've been trying to do for some time and there are 2 older threads, but the last post got no responce, so starting a new thread. The old ones are:

Converting system to raid
Removing drives

The computer with 2 sata drives switched over fine a long time ago, but I have yet to get the one with 3 sata drives to boot with raid. Raid support is built into the kernel, partitions are type fd.

fdisk -l shows:
-----------------------------------------------------------------------
Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x6b381dfe

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        4660    37431418+  83  Linux
/dev/hda2            4661        4865     1646662+   5  Extended
/dev/hda5            4661        4865     1646631   82  Linux swap /

Solaris

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x94140963

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        3040    24418768+  fd  Linux raid

autodetect
/dev/sda2 3041 3649 4891792+ fd Linux raid
autodetect
/dev/sda3 3650 60801 459073440 fd Linux raid
autodetect

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf1814421

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1        3040    24418768+  fd  Linux raid

autodetect
/dev/sdb2 3041 3649 4891792+ fd Linux raid
autodetect
/dev/sdb3 3650 60801 459073440 fd Linux raid
autodetect

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x371b6063

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc3            3650       60801   459073440   fd  Linux raid

autodetect

Disk /dev/md0: 25.0 GB, 25004736512 bytes
2 heads, 4 sectors/track, 6104672 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md2: 940.1 GB, 940182208512 bytes
2 heads, 4 sectors/track, 229536672 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md1: 5009 MB, 5009113088 bytes
2 heads, 4 sectors/track, 1222928 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table
-----------------------------------------------------------------------

Orginaly I had made both md0 and md1 2-way mirrors with a spare. But when it wouldn't boot, I was told it might be because of the spare and to grow them in. That also didn't work. I change md0 and md1 to 2-way mirrors, and removed the boot flag for sdc1 and zeroed superblock And I corrected the mdadm.conf file to reflect the changes to md0/1. Still would not boot from raid. I removed the two partitions sdc1 and sdc2 leaving just sdc3 which is part of md2 raid5. Also re-ran grub on md0 using:

sudo grub
grub>device (hd0) /dev/sda
grub>root (hd0,0)
grub>setup (hd0)

grub>device (hd0) /dev/sdb
grub>root (hd0,0)
grub>setup (hd0)

To copy the current boot drive hda1 over to md0, I use a GRML boot disk, mount /dev/md0 to /mnt/md0 and /dev/sdd1 (/dev/hda1) to /mnt/sdd1, then do:

rsync -caHh --progress --delete /mnt/sdd1/ /mnt/md0.

Then I reboot normally. I have 2 copies of /boot/grub/device.map, /boot/grub/menu.lst and /etc/fstab. one for normal boot and one for raid. On /mnt/md0 I swap the normal boot files for the raid files by adding .old to the names of normal boot and removing .raid from the raid versions. Then reboot again and in cmos move the pata drive to the bottom of the list so cmos tries the sata drives first. That worked for the 32bit linux 2 drive system. But on this 64bit 3 drive I get:

Grub loading stage 1.5
Grub loading, please wait
Error 2

I can't remove the 3rd drive because it has part of md2 and I shouldn't need to anyway. Copies of the above mentioned files I put at:
http://24.255.17.209:2400/vdr/local/raid/

Signature · 3 lines

To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Quoted 90 lines · Timothy D. Lenz

This is something I've been trying to do for some time and there are 2 older threads, but the last post got no responce, so starting a new thread. The old ones are:

Converting system to raid
Removing drives

The computer with 2 sata drives switched over fine a long time ago, but I have yet to get the one with 3 sata drives to boot with raid. Raid support is built into the kernel, partitions are type fd.

fdisk -l shows:
-----------------------------------------------------------------------
Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x6b381dfe

Device Boot Start End Blocks Id System

/dev/hda1   *           1        4660    37431418+  83  Linux
/dev/hda2            4661        4865     1646662+   5  Extended
/dev/hda5            4661        4865     1646631   82  Linux swap /

Solaris

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x94140963

Device Boot Start End Blocks Id System
/dev/sda1 * 1 3040 24418768+ fd Linux raid
autodetect
/dev/sda2 3041 3649 4891792+ fd Linux raid
autodetect
/dev/sda3 3650 60801 459073440 fd Linux raid
autodetect

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf1814421

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 3040 24418768+ fd Linux raid
autodetect
/dev/sdb2 3041 3649 4891792+ fd Linux raid
autodetect
/dev/sdb3 3650 60801 459073440 fd Linux raid
autodetect

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x371b6063

Device Boot Start End Blocks Id System
/dev/sdc3 3650 60801 459073440 fd Linux raid
autodetect

Disk /dev/md0: 25.0 GB, 25004736512 bytes
2 heads, 4 sectors/track, 6104672 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md2: 940.1 GB, 940182208512 bytes
2 heads, 4 sectors/track, 229536672 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md1: 5009 MB, 5009113088 bytes
2 heads, 4 sectors/track, 1222928 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table
-----------------------------------------------------------------------

Orginaly I had made both md0 and md1 2-way mirrors with a spare. But when it wouldn't boot, I was told it might be because of the spare and to grow them in. That also didn't work. I change md0 and md1 to 2-way mirrors, and removed the boot flag for sdc1 and zeroed superblock And I corrected the mdadm.conf file to reflect the changes to md0/1. Still would not boot from raid. I removed the two partitions sdc1 and sdc2 leaving just sdc3 which is part of md2 raid5. Also re-ran grub on md0 using:

Quoted 4 lines

sudo grub
grub>device (hd0) /dev/sda
grub>root (hd0,0)
grub>setup (hd0)

You can't use the setup macro (can't remember why, I just know it generally doesn't work) when putting grub on your raid1 array. You need:

install --stage2=/grub/stage2 /grub/stage1 (hd0) /grub/e2fs_stage1_5 /grub/stage2 /grub/grub.conf

and if that doesn't work in your particular configuration, you can add the d option after stage1 and before (hd0), but if you use it, then your boot disk must always be BIOS device 0x80, which means setting your BIOS to boot off of some disk other than the first disk found usually won't work and instead you just have to make whatever disk you want to boot off of the first disk found by the BIOS. You can switch (hd0) to (hd0,0) if you want and if you have a normal DOS master boot record.

Quoted 24 lines

grub>device (hd0) /dev/sdb
grub>root (hd0,0)
grub>setup (hd0)

To copy the current boot drive hda1 over to md0, I use a GRML boot disk, mount /dev/md0 to /mnt/md0 and /dev/sdd1 (/dev/hda1) to /mnt/sdd1, then do:

rsync -caHh --progress --delete /mnt/sdd1/ /mnt/md0.

Then I reboot normally. I have 2 copies of /boot/grub/device.map, /boot/grub/menu.lst and /etc/fstab. one for normal boot and one for raid. On /mnt/md0 I swap the normal boot files for the raid files by adding .old to the names of normal boot and removing .raid from the raid versions. Then reboot again and in cmos move the pata drive to the bottom of the list so cmos tries the sata drives first. That worked for the 32bit linux 2 drive system. But on this 64bit 3 drive I get:

Grub loading stage 1.5
Grub loading, please wait
Error 2

I can't remove the 3rd drive because it has part of md2 and I shouldn't need to anyway. Copies of the above mentioned files I put at:
http://24.255.17.209:2400/vdr/local/raid/

Quoted 36 lines · Doug Ledford

You can't use the setup macro (can't remember why, I just know it generally doesn't work) when putting grub on your raid1 array. You need:

install --stage2=/grub/stage2 /grub/stage1 (hd0) /grub/e2fs_stage1_5 /grub/stage2 /grub/grub.conf

and if that doesn't work in your particular configuration, you can add the d option after stage1 and before (hd0), but if you use it, then your boot disk must always be BIOS device 0x80, which means setting your BIOS to boot off of some disk other than the first disk found usually won't work and instead you just have to make whatever disk you want to boot off of the first disk found by the BIOS. You can switch (hd0) to (hd0,0) if you want and if you have a normal DOS master boot record.

Quoted 22 lines

grub>device (hd0) /dev/sdb
grub>root (hd0,0)
grub>setup (hd0)

To copy the current boot drive hda1 over to md0, I use a GRML boot disk, mount /dev/md0 to /mnt/md0 and /dev/sdd1 (/dev/hda1) to /mnt/sdd1, then do:

rsync -caHh --progress --delete /mnt/sdd1/ /mnt/md0.

Then I reboot normally. I have 2 copies of /boot/grub/device.map, /boot/grub/menu.lst and /etc/fstab. one for normal boot and one for raid. On /mnt/md0 I swap the normal boot files for the raid files by adding .old to the names of normal boot and removing .raid from the raid versions. Then reboot again and in cmos move the pata drive to the bottom of the list so cmos tries the sata drives first. That worked for the 32bit linux 2 drive system. But on this 64bit 3 drive I get:

Grub loading stage 1.5
Grub loading, please wait
Error 2

Quoted 3 lines

Quoted 3 lines

I can't remove the 3rd drive because it has part of md2 and I shouldn't need to anyway. Copies of the above mentioned files I put at:
http://24.255.17.209:2400/vdr/local/raid/

grrr, used reply instead of reply all again, sorry:

I don't understand why using those commands at the grub> prompt won't work. It worked on the other computer.

This is grub 1, not grub 2.

I
haven't updated it yet. It is using lenny. I did start the upgrade to grub2 on the other computer a short time ago, but haven't yet done the final command to finish the change. Trying to solve one thing at a time and right now this is the oldest. I don't recall ever doing any install --stage2=/grub/st.... on the other system.

Here is what I get when I do this for sda:
---------------------------------------
grub> device (hd0) /dev/sda

grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are
embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p
(hd0,0)/boot/grub/stage2 /boot/grub/menu.l
st"... succeeded
Done.
---------------------------------------

And I just noticed something.I used sda, not sda1. I can't remember which I did before with the other, but my notes show sda. Would that matter?

Quoted 40 lines · Timothy D. Lenz

Quoted 36 lines · Doug Ledford

You can't use the setup macro (can't remember why, I just know it generally doesn't work) when putting grub on your raid1 array. You need:

install --stage2=/grub/stage2 /grub/stage1 (hd0) /grub/e2fs_stage1_5 /grub/stage2 /grub/grub.conf

and if that doesn't work in your particular configuration, you can add the d option after stage1 and before (hd0), but if you use it, then your boot disk must always be BIOS device 0x80, which means setting your BIOS to boot off of some disk other than the first disk found usually won't work and instead you just have to make whatever disk you want to boot off of the first disk found by the BIOS. You can switch (hd0) to (hd0,0) if you want and if you have a normal DOS master boot record.

Quoted 22 lines

grub>device (hd0) /dev/sdb
grub>root (hd0,0)
grub>setup (hd0)

To copy the current boot drive hda1 over to md0, I use a GRML boot disk, mount /dev/md0 to /mnt/md0 and /dev/sdd1 (/dev/hda1) to /mnt/sdd1, then do:

rsync -caHh --progress --delete /mnt/sdd1/ /mnt/md0.

Then I reboot normally. I have 2 copies of /boot/grub/device.map, /boot/grub/menu.lst and /etc/fstab. one for normal boot and one for raid. On /mnt/md0 I swap the normal boot files for the raid files by adding .old to the names of normal boot and removing .raid from the raid versions. Then reboot again and in cmos move the pata drive to the bottom of the list so cmos tries the sata drives first. That worked for the 32bit linux 2 drive system. But on this 64bit 3 drive I get:

Grub loading stage 1.5
Grub loading, please wait
Error 2

Quoted 8 lines

Quoted 3 lines

Quoted 3 lines

I can't remove the 3rd drive because it has part of md2 and I shouldn't need to anyway. Copies of the above mentioned files I put at:
http://24.255.17.209:2400/vdr/local/raid/

grrr, used reply instead of reply all again, sorry:

I don't understand why using those commands at the grub> prompt won't work. It worked on the other computer.

Can't answer that for you. I didn't bother to work out *why* it didn't work, just that it's known to fail in some situations (the setup command). Maybe it's because it pulls information from the device map and gets the device line wrong (and yes, the setup macro redoes whatever device line you put in based upon the information in the device map file). Maybe it's something else. Regardless, it's known to fail.

Quoted 1 line

This is grub 1, not grub 2.

Yes, my instructions were for grub1.

Quoted 14 lines

I
haven't updated it yet. It is using lenny. I did start the upgrade to grub2 on the other computer a short time ago, but haven't yet done the final command to finish the change. Trying to solve one thing at a time and right now this is the oldest. I don't recall ever doing any install --stage2=/grub/st.... on the other system.

Here is what I get when I do this for sda:
---------------------------------------
grub> device (hd0) /dev/sda

grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd

Quoted 12 lines

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are
embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p
(hd0,0)/boot/grub/stage2 /boot/grub/menu.l
st"... succeeded
Done.
---------------------------------------

I know, it looks fine. But it screws it up anyway. It isn't reliable.
You have to use the bare install command like I pointed out above. You
also need to make sure that your boot partitions on the two drives are *identical* in terms of placement on the drives (aka, the partitions need to occupy the same logical sector numbers on both drives, which is normal when they are both the first partition on each drive and the drives use the same sector/head counts per track which is typical now a days).

Quoted 3 lines

And I just noticed something.I used sda, not sda1. I can't remember which I did before with the other, but my notes show sda. Would that matter?

Normally sda would be the one I would use, but sda1 would work as long as you have a normal DOS master boot record on the drive.

Quoted 12 lines

Quoted 12 lines

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are
embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p
(hd0,0)/boot/grub/stage2 /boot/grub/menu.l
st"... succeeded
Done.
---------------------------------------

Quoted 3 lines

Normally sda would be the one I would use, but sda1 would work as long as you have a normal DOS master boot record on the drive.

I was thinking making one more try, but ether using su instead of sudo or just logging in as root as some stuff doesn't seem to work with sudo. Need to find the time when I'm home long enough with no interruptions to try it:).

Before I try the manual install, do you know what the "1+15 p" is in the install line the auto system did?

Quoted 13 lines · Timothy D. Lenz

Quoted 12 lines

Quoted 12 lines

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are
embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p
(hd0,0)/boot/grub/stage2 /boot/grub/menu.l
st"... succeeded
Done.
---------------------------------------

Quoted 3 lines

Quoted 3 lines

Normally sda would be the one I would use, but sda1 would work as long as you have a normal DOS master boot record on the drive.

A normal DOS master boot record is one that resides in the master boot record of the drive and that knows to chain load the next boot sector from the first sector of the partition that's marked active. So, if you install a boot loader on sda1, you have to have the normal DOS master boot record in the master boot record of the drive. Once you install grub on the bare drive (aka, on sda instead of sda1), you wipe out any other boot loader in the master boot record and replace it with a grub master boot record. So, at this point you probably don't have a normal DOS master boot record (unless the grub one suffices but I don't think it does) and will need to make sure to install whatever new boot loader you install to sda versus sda1 or else it won't overwrite the previous grub master boot record.

Quoted 4 lines

I was thinking making one more try, but ether using su instead of sudo or just logging in as root as some stuff doesn't seem to work with sudo. Need to find the time when I'm home long enough with no interruptions to try it:).

Sudo versus su versus logging in as root shouldn't matter as long as whatever command you are running doesn't come back with some sort of error message.

Quoted 2 lines

Before I try the manual install, do you know what the "1+15 p" is in the install line the auto system did?

Prior to the install line that the setup macro does, it embedded the e2fs_stage1_5 on the disk between the partition table and the start of the first partition. The (hd0)1+15 means to load sectors 1 through 15 of (hd0) as the next stage in the boot loader. The p is separate and merely means patch the block list for the next part of the boot loader into the previous part. It can be omitted as grub does this anyway based upon the number of stages you specify.