[opensuse] Suse 10.2 installation on Raid 1

older
[opensuse] About install nvidia...

Art Fore

9 Aug 2007 9 Aug '07

12:10

I have ra1d1 setup as follows. MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb Installation went fine on installation, but on reboot, it says disk has no operating system. What did I do wrong and how can I fix it? Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Jack Malone

9 Aug 9 Aug

13:22

...

I have ra1d1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

Without more info I would check to make sure that you have the right disk set to boot from in the bios. I had this problem ones and had to set it to boot from device / driver that the raid setup was on in the bios. Jack Malone -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ian Marlier

13:44

On 8/9/07 9:22 AM, "Jack Malone" wrote:

...

...
I have ra1d1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

Without more info I would check to make sure that you have the right disk set to boot from in the bios. I had this problem ones and had to set it to boot from device / driver that the raid setup was on in the bios.

Jack Malone

By default, opensuse wants to install grub onto the root partition. However, with an md root, that won't work. Basically, you need to boot into the rescue system, get the md array up, bind /proc and /dev into it, and then install grub onto the MBR. (I'm typing those commands out from memory, so I may have the syntax slightly wrong, but it should be pretty close.) Getting the MD array up is a little tricky. Once you're in the rescue system, you need to edit /etc/mdadm.conf, and add the lines DEVICE /dev/sda2 DEVICE /dev/sdc2 Then you can do `mdadm --examine --scan`, and it should find the array. Verify that the correct info is output to the console, and if so do `mdadm --examine --scan >> /etc/mdadm.conf`, and then `mdadm --activate --scan` to get the array active. Then, do `mount /dev/md3 /mnt`. Bind the /proc and /dev filesystems to the md array by doing `mount -o bind /proc /mnt/proc` `mount -o bind /dev /mnt/dev` Chroot to your real system by doing `chroot /mnt` Enter grub, by doing `grub`. In the grub shell, do `root (hd0,1)` And then `setup (hd0)` `setup (hd2)` That should get the correct config installed onto the MBR of the disks. Note that by doing the setup for both hd0 and hd2, you've got the boot info installed on the MBR of sdc as well; that way, if the first disk fails, you don't need to repeat this process -- your machine will be bootable using the remaining disk. (yes, setting root to (hd0,1) is counterintuitive, since that's just a RAID member. But, it works...) This process is actually one of the things that drives me batty about opensuse. I'm using it in a production environment, and have bunches of machines with md roots, and have to do this with every single one of them. The bootloader installation part of the installer is simply incapable of dealing with an install onto the MBR of two separate disks. I don't know why, but it is. HTH, Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Art Fore

14:52

On Thu, 2007-08-09 at 09:44 -0400, Ian Marlier wrote:

...

On 8/9/07 9:22 AM, "Jack Malone" wrote:

...
...
I have ra1d1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

Without more info I would check to make sure that you have the right disk set to boot from in the bios. I had this problem ones and had to set it to boot from device / driver that the raid setup was on in the bios.

Jack Malone

By default, opensuse wants to install grub onto the root partition. However, with an md root, that won't work.

Basically, you need to boot into the rescue system, get the md array up, bind /proc and /dev into it, and then install grub onto the MBR.

(I'm typing those commands out from memory, so I may have the syntax slightly wrong, but it should be pretty close.)

Getting the MD array up is a little tricky. Once you're in the rescue system, you need to edit /etc/mdadm.conf, and add the lines DEVICE /dev/sda2 DEVICE /dev/sdc2

Then you can do `mdadm --examine --scan`, and it should find the array. Verify that the correct info is output to the console, and if so do `mdadm --examine --scan >> /etc/mdadm.conf`, and then `mdadm --activate --scan` to get the array active.

Then, do `mount /dev/md3 /mnt`.

Bind the /proc and /dev filesystems to the md array by doing `mount -o bind /proc /mnt/proc` `mount -o bind /dev /mnt/dev`

Chroot to your real system by doing `chroot /mnt`

Enter grub, by doing `grub`.

In the grub shell, do `root (hd0,1)` And then `setup (hd0)` `setup (hd2)`

That should get the correct config installed onto the MBR of the disks. Note that by doing the setup for both hd0 and hd2, you've got the boot info installed on the MBR of sdc as well; that way, if the first disk fails, you don't need to repeat this process -- your machine will be bootable using the remaining disk.

(yes, setting root to (hd0,1) is counterintuitive, since that's just a RAID member. But, it works...)

This process is actually one of the things that drives me batty about opensuse. I'm using it in a production environment, and have bunches of machines with md roots, and have to do this with every single one of them. The bootloader installation part of the installer is simply incapable of dealing with an install onto the MBR of two separate disks. I don't know why, but it is.

HTH,

Ian

Thanks for the info. I will try that tomorrow. It is getting pretty late here in Taiwan now. Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Art Fore

11 Aug 11 Aug

11:01

New subject: [opensuse] Suse 10.2 installation on Raid 1(solved)

On Thu, 2007-08-09 at 22:52 +0800, Art Fore wrote:

...

On Thu, 2007-08-09 at 09:44 -0400, Ian Marlier wrote:

...
On 8/9/07 9:22 AM, "Jack Malone" wrote:

...
...
I have ra1d1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

Without more info I would check to make sure that you have the right disk set to boot from in the bios. I had this problem ones and had to set it to boot from device / driver that the raid setup was on in the bios.

Jack Malone

By default, opensuse wants to install grub onto the root partition. However, with an md root, that won't work.

Basically, you need to boot into the rescue system, get the md array up, bind /proc and /dev into it, and then install grub onto the MBR.

(I'm typing those commands out from memory, so I may have the syntax slightly wrong, but it should be pretty close.)

Getting the MD array up is a little tricky. Once you're in the rescue system, you need to edit /etc/mdadm.conf, and add the lines DEVICE /dev/sda2 DEVICE /dev/sdc2

Then you can do `mdadm --examine --scan`, and it should find the array. Verify that the correct info is output to the console, and if so do `mdadm --examine --scan >> /etc/mdadm.conf`, and then `mdadm --activate --scan` to get the array active.

Then, do `mount /dev/md3 /mnt`.

Bind the /proc and /dev filesystems to the md array by doing `mount -o bind /proc /mnt/proc` `mount -o bind /dev /mnt/dev`

Chroot to your real system by doing `chroot /mnt`

Enter grub, by doing `grub`.

In the grub shell, do `root (hd0,1)` And then `setup (hd0)` `setup (hd2)`

That should get the correct config installed onto the MBR of the disks. Note that by doing the setup for both hd0 and hd2, you've got the boot info installed on the MBR of sdc as well; that way, if the first disk fails, you don't need to repeat this process -- your machine will be bootable using the remaining disk.

(yes, setting root to (hd0,1) is counterintuitive, since that's just a RAID member. But, it works...)

This process is actually one of the things that drives me batty about opensuse. I'm using it in a production environment, and have bunches of machines with md roots, and have to do this with every single one of them. The bootloader installation part of the installer is simply incapable of dealing with an install onto the MBR of two separate disks. I don't know why, but it is.

HTH,

Ian

Thanks for the info. I will try that tomorrow. It is getting pretty late here in Taiwan now.

Art

This worked up to "mdadm --activate --scan" where mdadm said no such command --activate or something to that effect. Went ahead and mounted md3 on /mnt, chroot to /mnt, done a grub, then root (hd0,1) it comes up no such device. Found a suse howto at http://en.opensuse.org/How_to_install_SUSE_Linux_on_software_RAID which worked, of course I had to do a reinstall. Guess the /boot partition is needed for suse. Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris (NTM)

12:41

New subject: [opensuse] Suse 10.2 installation on Raid 1(solved)

On 08/11/2007 07:01 PM, Art Fore wrote:

...

This worked up to "mdadm --activate --scan" where mdadm said no such command --activate or something to that effect. Assuming you used the 10.2 rescue system, there is no need for that. Went ahead and mounted md3 on /mnt, chroot to /mnt, done a grub, then root (hd0,1) it comes up no such device.

What device had your /boot/grub files in it? That would have been /dev/hda2. Didn't you say you had SATA? Are they first, according to device.map? if so, then /dev/sda2. You probably also needed to, after mount /dev/md3 /mnt, you need to: mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys Then, cd /mnt, then chroot /mnt. Then it should have worked. After chrooting to mnt without /dev, there may not have been any devices there.

...

Found a suse howto at

http://en.opensuse.org/How_to_install_SUSE_Linux_on_software_RAID

which worked, of course I had to do a reinstall. Guess the /boot partition is needed for suse.

I can guarantee it is not. I have 2 machines running software RAID 1, one with PATA and one with mixed (3 RAID 1 partitions across 4 disks). On both, I have boot as a directory on the root partition. joe@jmorris:~> cat /etc/fstab /dev/md0 / ext3 acl,user_xattr 1 1 /dev/md1 /home ext3 acl,user_xattr 1 2 /dev/hda1 swap swap pri=42 0 0 /dev/hdc1 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 /dev/hdc7 /media/backup ext3 acl,user_xattr 1 2 LABEL=USBBackup /media/USBBackup ext3 user,noauto,acl,user_xattr 0 0 I have manually installed GRUB on the MBR of my disks many times (especially with 10.1). Too bad you reinstalled. I guess this is all moot at this point. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen

9 Aug 9 Aug

15:27

Ian Marlier wrote:

...

This process is actually one of the things that drives me batty about opensuse. I'm using it in a production environment, and have bunches of machines with md roots, and have to do this with every single one of them. The bootloader installation part of the installer is simply incapable of dealing with an install onto the MBR of two separate disks.

Might be worth raising an enhancement request. /Per Jessen, Zürich -- http://www.spamchek.com/ - your spam is our business. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris (NTM)

13:42

On 08/09/2007 08:10 PM, Art Fore wrote:

...

I have ra1d1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

What is saying disk has no operating system, BIOS or grub? If BIOS, I would suggest installing grub in the MBR of both drives. If grub, post your menu.lst and device.map files, and a ls -l /boot and maybe cat /etc/fstab to be more complete. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott

14:04

Art Fore wrote:

...

I have ra1d1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

Is /boot on it's own partition, outside of the RAID array? If you are using RAID or LVM, /boot has to have it's own partition. BTW, you can use LVM inside RAID, to make it easier to have multiple partitions. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris (NTM)

14:12

On 08/09/2007 10:04 PM, James Knott wrote:

...

Is /boot on it's own partition, outside of the RAID array? If you are using RAID or LVM, /boot has to have it's own partition.

Wrong. I think it used to be so (8.0), but I have an md root and home similar to the OP with NO separate boot partition. I do think grub has to be installed in the MBR though, as was suggested. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott

28 Aug 28 Aug

15:14

Joe Morris (NTM) wrote:

...

On 08/09/2007 10:04 PM, James Knott wrote:

...
Is /boot on it's own partition, outside of the RAID array? If you are using RAID or LVM, /boot has to have it's own partition.

Wrong. I think it used to be so (8.0), but I have an md root and home similar to the OP with NO separate boot partition. I do think grub has to be installed in the MBR though, as was suggested.

I finally got around to trying this. During install, when I create a logical volume on RAID for /boot, I get the error message: 'You cannot use the mount point "/boot" for LVM.' If I try without a separate /boot LVM, I get the error message: 'Warning: With your current setup, your OpenSUSE 10.2 installation will encounter problems when booting, because you have no "boot" partition and your "root" partition is an LVM logical volume. This does not work.' So it appears I'm correct. You need a boot partition outside of LVM & RAID, at least with LVM on RAID. When I create a separate RAID array for /boot, I get the error message: 'Warning: With your current setup, you OpenSUSE 10.2 installation might not be directly bootable, because your files below "/boot" are on a software RAID device. The boot loader setup sometimes fails in this configuration.' Then, if I click on "Accept", I go back to the "Installation Settings" screen, where under "Booting", I get the message: "Because of the partitioning, the bootloader cannot be installed properly." So, once again, with software RAID, with or without LVM, /boot cannot be on a RAID array. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris (NTM)

29 Aug 29 Aug

01:05

On 08/28/2007 11:14 PM, James Knott wrote:

...

Joe Morris (NTM) wrote:

...
On 08/09/2007 10:04 PM, James Knott wrote:

...
Is /boot on it's own partition, outside of the RAID array? If you are using RAID or LVM, /boot has to have it's own partition.

Wrong. I think it used to be so (8.0), but I have an md root and home similar to the OP with NO separate boot partition. I do think grub has to be installed in the MBR though, as was suggested.

I finally got around to trying this. During install, when I create a logical volume on RAID for /boot, I get the error message: 'You cannot use the mount point "/boot" for LVM.'

LVM I would agree. A separate /boot where grub can locate its files are required.

...

If I try without a separate /boot LVM, I get the error message: 'Warning: With your current setup, your OpenSUSE 10.2 installation will encounter problems when booting, because you have no "boot" partition and your "root" partition is an LVM logical volume. This does not work.'

Again, with LVM it makes sense.

...

So it appears I'm correct. You need a boot partition outside of LVM & RAID, at least with LVM on RAID.

Correct.

...

When I create a separate RAID array for /boot, I get the error message: 'Warning: With your current setup, you OpenSUSE 10.2 installation might not be directly bootable, because your files below "/boot" are on a software RAID device. The boot loader setup sometimes fails in this configuration.'

That is when IIUC you install grub loader to something besides the MBR. If GRUB stage 1 is installed in the MBR, it works fine (though finds its files on one of the disks). It even, since it is a RAID 1, works with a fallback to the second disk in case the first disk failed.

...

Then, if I click on "Accept", I go back to the "Installation Settings" screen, where under "Booting", I get the message: "Because of the partitioning, the bootloader cannot be installed properly."

...

So, once again, with software RAID, with or without LVM, /boot cannot be on a RAID array. I'm glad my system does not have artificial intelligence and know what you said. It might decide it cannot work as it is now and cause me

BTW, did you set, in Yast, System, etc/sysconfig Editor, System, Bootloader, LOADER_LOCATION to mbr? problems. I boot from a system with software raid 1 / with /boot on it every day, with 10.2 (though it has worked since at least 9.3). I will say I have had problems with Yast with 10.1 and got used to installing grub manually every time there was a kernel update. 10.2 just works correctly (i.e grub should not be messed with at all with a kernel update). So it does boot with /boot on a software raid 1, WITH the caveat grub stage 1 needs to be installed in the mbr. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott

01:20

Joe Morris (NTM) wrote:

...

...
When I create a separate RAID array for /boot, I get the error message: 'Warning: With your current setup, you OpenSUSE 10.2 installation might not be directly bootable, because your files below "/boot" are on a software RAID device. The boot loader setup sometimes fails in this configuration.'

That is when IIUC you install grub loader to something besides the MBR. If GRUB stage 1 is installed in the MBR, it works fine (though finds its files on one of the disks). It even, since it is a RAID 1, works with a fallback to the second disk in case the first disk failed.

I was using RAID 5 and the installer refused to configure the boot loader.

...

...
Then, if I click on "Accept", I go back to the "Installation Settings" screen, where under "Booting", I get the message: "Because of the partitioning, the bootloader cannot be installed properly."

BTW, did you set, in Yast, System, etc/sysconfig Editor, System, Bootloader, LOADER_LOCATION to mbr?

How would I get to Yast, when I couldn't install a bootable system?

...

...
So, once again, with software RAID, with or without LVM, /boot cannot be on a RAID array.

I'm glad my system does not have artificial intelligence and know what you said. It might decide it cannot work as it is now and cause me problems. I boot from a system with software raid 1 / with /boot on it every day, with 10.2 (though it has worked since at least 9.3). I will say I have had problems with Yast with 10.1 and got used to installing grub manually every time there was a kernel update. 10.2 just works correctly (i.e grub should not be messed with at all with a kernel update). So it does boot with /boot on a software raid 1, WITH the caveat grub stage 1 needs to be installed in the mbr.

As I mentioned above, I was using RAID 5, not RAID 1 and SUSE refused to install a boot loader with /boot on a RAID 5 array. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris (NTM)

11:49

On 08/29/2007 09:20 AM, James Knott wrote:

...

I was using RAID 5 and the installer refused to configure the boot loader.

RAID 5 I am not sure of.

...

How would I get to Yast, when I couldn't install a bootable system?

Don't you install from Yast? I am pretty sure the configuration of the bootloader is a part of what can be configured via the Yast install setup.

...

As I mentioned above, I was using RAID 5, not RAID 1 and SUSE refused to install a boot loader with /boot on a RAID 5 array.

It may not work with Raid 5, but it does with Raid 1. So it is limited to needing a separate boot with Raid 5, probably Raid 0, and LVM. It isn't that it is software Raid, but the array type. Raid 1 works great. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Richard Creighton

03:18

James Knott wrote:

...

Joe Morris (NTM) wrote:

...
On 08/09/2007 10:04 PM, James Knott wrote:

...
Is /boot on it's own partition, outside of the RAID array? If you are using RAID or LVM, /boot has to have it's own partition.

Wrong. I think it used to be so (8.0), but I have an md root and home similar to the OP with NO separate boot partition. I do think grub has to be installed in the MBR though, as was suggested.

I finally got around to trying this. During install, when I create a logical volume on RAID for /boot, I get the error message: 'You cannot use the mount point "/boot" for LVM.'

Try going to http://en.opensuse.org/How_to_install_SUSE_Linux_on_software_RAID for an article that worked for me. I have 10.3 running on a 1.4TB raid 3 MD partitions, 1 Raid 0, 1 Raid 1 and 1 Raid 5 partition on 4 drives. You do not need an external drive to boot from. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen

9 Aug 9 Aug

14:35

Art Fore wrote:

...

I have ra1d1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

Check that you've got your boot-manager properly configured. /Per Jessen, Zürich -- http://www.spamchek.com/ - your spam is our business. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Stuart Murray-Smith

10 Aug 10 Aug

13:37

On 8/9/07, Art Fore wrote:

...

I have raid-1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

I'm going to guess that you've installed this onto SATA drives, and/or you've enabled RAID in your BIOS. RAID-1 works awesomely on PATA drives, but one {may|may not} get the above error message when installing to SATA on some of the 'less-expensive' mobo's. Things get tricky when one writes grub to the MBR, and need to swap out the primary drive. You can also put swap into RAID as well. Consider two PATAs in parallel: md0-swap-swap-{hda1|hdb1} md1-ext3-/boot-{hda2|hdb2} md2-ext3-/{hda3|hdb3} What does: cat /proc/mdstat say? BTW, mdadm automaticly rebuilds your RAID devices if you startup using 'Rescue' on the 10.2 DVD :-) Way cool! HTH Stuart -- Then you will know the truth, and the truth will set you free. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Art Fore

13:35

On Fri, 2007-08-10 at 15:37 +0200, Stuart Murray-Smith wrote:

...

On 8/9/07, Art Fore wrote:

...
I have raid-1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

I'm going to guess that you've installed this onto SATA drives, and/or you've enabled RAID in your BIOS. RAID-1 works awesomely on PATA drives, but one {may|may not} get the above error message when installing to SATA on some of the 'less-expensive' mobo's. Things get tricky when one writes grub to the MBR, and need to swap out the primary drive.

You can also put swap into RAID as well. Consider two PATAs in parallel:

md0-swap-swap-{hda1|hdb1} md1-ext3-/boot-{hda2|hdb2} md2-ext3-/{hda3|hdb3}

What does:

cat /proc/mdstat

say?

BTW, mdadm automaticly rebuilds your RAID devices if you startup using 'Rescue' on the 10.2 DVD :-) Way cool!

HTH

Stuart

-- Then you will know the truth, and the truth will set you free.

No, raid is not enabled in bios, I am using the Suse software raid1. It was originally partitioned with Ubuntu, but on Suse installation, I set MD3 to / and MD4 to /home and formated them extt3. Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Stuart Murray-Smith

13:59

On 8/10/07, Art Fore wrote:

...

On Fri, 2007-08-10 at 15:37 +0200, Stuart Murray-Smith wrote:

...
On 8/9/07, Art Fore wrote:

...
I have raid-1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

I'm going to guess that you've installed this onto SATA drives, and/or you've enabled RAID in your BIOS. RAID-1 works awesomely on PATA drives, but one {may|may not} get the above error message when installing to SATA on some of the 'less-expensive' mobo's. Things get tricky when one writes grub to the MBR, and need to swap out the primary drive.

You can also put swap into RAID as well. Consider two PATAs in parallel:

md0-swap-swap-{hda1|hdb1} md1-ext3-/boot-{hda2|hdb2} md2-ext3-/{hda3|hdb3}

What does:

cat /proc/mdstat

say?

BTW, mdadm automaticly rebuilds your RAID devices if you startup using 'Rescue' on the 10.2 DVD :-) Way cool!

...

No, raid is not enabled in bios, I am using the Suse software raid1. It was originally partitioned with Ubuntu, but on Suse installation, I set MD3 to / and MD4 to /home and formated them extt3.

The Ubuntu partitioning shouldn't be a problem, though I usually give new drives the once-over with: shred -n 0 /dev/[drive_to_be_shredded_here] -vz Are these PATA (old ATA) or SATA drives? S~ -- Then you will know the truth, and the truth will set you free. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Art Fore

13:54

On Fri, 2007-08-10 at 15:59 +0200, Stuart Murray-Smith wrote:

...

On 8/10/07, Art Fore wrote:

...
On Fri, 2007-08-10 at 15:37 +0200, Stuart Murray-Smith wrote:

...
On 8/9/07, Art Fore wrote:

...
I have raid-1 setup as follows.

MD3, 20 GB as / (SDA2, SDC2) MD4, 267 GB as /home (SDA3, SDC3) Swap as SDA5 1 gb and SDC5 1 gb

Installation went fine on installation, but on reboot, it says disk has no operating system.

What did I do wrong and how can I fix it?

I'm going to guess that you've installed this onto SATA drives, and/or you've enabled RAID in your BIOS. RAID-1 works awesomely on PATA drives, but one {may|may not} get the above error message when installing to SATA on some of the 'less-expensive' mobo's. Things get tricky when one writes grub to the MBR, and need to swap out the primary drive.

You can also put swap into RAID as well. Consider two PATAs in parallel:

md0-swap-swap-{hda1|hdb1} md1-ext3-/boot-{hda2|hdb2} md2-ext3-/{hda3|hdb3}

What does:

cat /proc/mdstat

say?

BTW, mdadm automaticly rebuilds your RAID devices if you startup using 'Rescue' on the 10.2 DVD :-) Way cool!

...
No, raid is not enabled in bios, I am using the Suse software raid1. It was originally partitioned with Ubuntu, but on Suse installation, I set MD3 to / and MD4 to /home and formated them extt3.

The Ubuntu partitioning shouldn't be a problem, though I usually give new drives the once-over with:

shred -n 0 /dev/[drive_to_be_shredded_here] -vz

Are these PATA (old ATA) or SATA drives?

SATA Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

6091

Age (days ago)

6111

Last active (days ago)

List overview

Download

19 comments

8 participants

participants (8)

Art Fore
Ian Marlier
Jack Malone
James Knott
Joe Morris (NTM)
Per Jessen
Richard Creighton
Stuart Murray-Smith