Rikard Johnels wrote:

On Friday 12 January 2007 23:07, Sandy Drobic wrote:

...

Rikard Johnels wrote:

...

...

But the installer doesn't recognize them at all. It sees /dev/rd/c0d0 as a full partition, and states it cannot do anything with it.

How do i get the table read? How do i initialize the array for usage in the installer?

...

I am eagerly waiting for the answer as well because I suspect that I currently have the same problem with an old FSC Primergy 470 with Mylex DAC960PRL Controller. Can you delete the partitions and create them in yast again? If not, I can't update to Suse 10.2 either.

This is how i got around the problem so far;

1. I did a clean install of 10.0 from CD's This worked perfectly. Both removing the old w2k server partition, and creating new ones for Linux

This is what I ended up doing as well. In my case I had an existing Suse 9.2 installation which I was iching to upgrade because it is no longer supplied with security updates. But the update went without a hitch. So now I can finally enjoy a supported version again. Neither 10.1 nor 10.2 are able to read the partition table of the installed System on the Mylex DAC960 raid. As this is still a frequently used controller in older machines I am a bit aggravated that a fresh install is not possible.

2. Added a online repository for 10.2 in Yast, and ran a full upgrade

3. I also tried adding a DVD "mounted" and shared from a XP desktop, This also works.

I just finished recompiling the all the packages for my mailserver, so I'll just call it a day and maybe wait for version 10.3 to appear.

So from what i can understand, the partition tool "parted" that is used in 10.2 does NOT work on the RAID partition created from the Mylex BIOS.

Yes, that is my experience as well. I had additional trouble even getting the installation to start. Since an Ubuntu CD resulted in similar trouble I am inclined to believe that it's the kernel itself that has changed and not just the Suse version of the installation kernel.

This is very cumbersome, not to mention irritating, as i refurbish several older server systems, and give them a Non-microsoft environment.

Any particular reason as to why SuSE/Novell changed partition manager from 10.0 to 10.2??

No idea, though I think they actually changed to parted in 10.1. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ken Gramm wrote:

On Sun, 2007-01-14 at 00:23 +0100, Sandy Drobic wrote:

...

No idea, though I think they actually changed to parted in 10.1.

I don't know which partitioning tool they used in 10.1, but I do know that I was able to fresh install 10.1 onto my Mylex DAC960 controllers.

Which version of DAC960? The installation in 10.2 (or 10.1) only started, if I used "maxcpus=0" as bootoption with my Mylex DAC960PRL on an Intel GX440 chipset mainboard. I haven't tried it with a Mylex DAC960PD, though I could probably dust it off and give it a try. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ken Gramm wrote:

On Sun, 2007-01-14 at 03:07 +0100, Sandy Drobic wrote:

...

Which version of DAC960?

Well, since my 960 came out of an old Alpha Server 2100, it is technically a DEC KZPSC. But I've flashed its firmware with the latest version available to that model and SUSE sees it as a DAC960PD running the 2.73 version of firmware.

I think I've got another DAC960PRL and a DAC960PD in one of my boxes. I'll give it a try tomorrow and see if it's the controller or the combination of controller and mainboard. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ken Gramm wrote:

On Sun, 2007-01-14 at 05:11 +0100, Sandy Drobic wrote:

...

I think I've got another DAC960PRL and a DAC960PD in one of my boxes. I'll give it a try tomorrow and see if it's the controller or the combination of controller and mainboard.

As a quick test, I just ran the 10.2 install on the box that contains my 960. When I get to the partition screens, I'm told I can use the current partitions, but I can't change them.

K

Have you tried the custom setup? -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joseph Loo wrote:

Ken Gramm wrote:

...

On Sun, 2007-01-14 at 05:11 +0100, Sandy Drobic wrote:

...

I think I've got another DAC960PRL and a DAC960PD in one of my boxes. I'll give it a try tomorrow and see if it's the controller or the combination of controller and mainboard.

As a quick test, I just ran the 10.2 install on the box that contains my 960. When I get to the partition screens, I'm told I can use the current partitions, but I can't change them.

Have you tried the custom setup?

Yes, no joy. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 14 January 2007 00:23, Sandy Drobic wrote:

Rikard Johnels wrote:

...

On Friday 12 January 2007 23:07, Sandy Drobic wrote:

...

Rikard Johnels wrote:

...

But the installer doesn't recognize them at all. It sees /dev/rd/c0d0 as a full partition, and states it cannot do anything with it.

How do i get the table read? How do i initialize the array for usage in the installer?

I am eagerly waiting for the answer as well because I suspect that I currently have the same problem with an old FSC Primergy 470 with Mylex DAC960PRL Controller. Can you delete the partitions and create them in yast again? If not, I can't update to Suse 10.2 either.

This is how i got around the problem so far;

1. I did a clean install of 10.0 from CD's This worked perfectly. Both removing the old w2k server partition, and creating new ones for Linux

This is what I ended up doing as well. In my case I had an existing Suse 9.2 installation which I was iching to upgrade because it is no longer supplied with security updates. But the update went without a hitch. So now I can finally enjoy a supported version again.

Neither 10.1 nor 10.2 are able to read the partition table of the installed System on the Mylex DAC960 raid. As this is still a frequently used controller in older machines I am a bit aggravated that a fresh install is not possible.

...

2. Added a online repository for 10.2 in Yast, and ran a full upgrade

3. I also tried adding a DVD "mounted" and shared from a XP desktop, This also works.

I just finished recompiling the all the packages for my mailserver, so I'll just call it a day and maybe wait for version 10.3 to appear.

...

So from what i can understand, the partition tool "parted" that is used in 10.2 does NOT work on the RAID partition created from the Mylex BIOS.

Yes, that is my experience as well. I had additional trouble even getting the installation to start. Since an Ubuntu CD resulted in similar trouble I am inclined to believe that it's the kernel itself that has changed and not just the Suse version of the installation kernel.

...

This is very cumbersome, not to mention irritating, as i refurbish several older server systems, and give them a Non-microsoft environment.

Any particular reason as to why SuSE/Novell changed partition manager from 10.0 to 10.2??

No idea, though I think they actually changed to parted in 10.1.

Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

It shouldnt be kernel related, as the ordinary fdisk from either rescue boot or another terminal sessin works perfectly. The installer clearly states that "tihs version of parted..." So its actually parted that isnt playing... I have no idea on what card i have right now.. But ill check later today. (Ill grab the complete specs of the server) --          /Rikard ----------------------------------------------------------------------------- email   : rikard.j@rikjoh.com web     : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78  46 1C EE 56 >

Sandy Drobic writes:

Rikard Johnels wrote:

...

I have an older Intel server with a Mylex RAID card in it. The array is 6 drives in RAID 5, no spares. The installer complains about not being able to do anything on the array, so i got into a rescue kernel boot and used fdisk to make three parttitions on it. /dev/rd/c0d0p1 - /boot (ext2) /dev/rd/c0d0p2 - swap (swap) /dev/rd/c0d0p3 - / (xfs) I made the filesystems after syncing the disks.

But the installer doesn't recognize them at all. It sees /dev/rd/c0d0 as a full partition, and states it cannot do anything with it.

How do i get the table read? How do i initialize the array for usage in the installer?

I am eagerly waiting for the answer as well because I suspect that I currently have the same problem with an old FSC Primergy 470 with Mylex DAC960PRL Controller. Can you delete the partitions and create them in yast again? If not, I can't update to Suse 10.2 either.

Did you report this in bugzilla? Which bug number is it? Without a bug report - and testers that test during the beta phase - there's not chance to get this fixed, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

On Monday 15 January 2007 10:52, Sandy Drobic wrote:

Andreas Jaeger wrote:

...

Sandy Drobic writes:

...

Rikard Johnels wrote:

...

I have an older Intel server with a Mylex RAID card in it. The array is 6 drives in RAID 5, no spares. The installer complains about not being able to do anything on the array, so i got into a rescue kernel boot and used fdisk to make three parttitions on it. /dev/rd/c0d0p1 - /boot (ext2) /dev/rd/c0d0p2 - swap (swap) /dev/rd/c0d0p3 - / (xfs) I made the filesystems after syncing the disks.

But the installer doesn't recognize them at all. It sees /dev/rd/c0d0 as a full partition, and states it cannot do anything with it.

How do i get the table read? How do i initialize the array for usage in the installer?

I am eagerly waiting for the answer as well because I suspect that I currently have the same problem with an old FSC Primergy 470 with Mylex DAC960PRL Controller. Can you delete the partitions and create them in yast again? If not, I can't update to Suse 10.2 either.

Did you report this in bugzilla? Which bug number is it?

Without a bug report - and testers that test during the beta phase - there's not chance to get this fixed,

I was hoping that someone else has already stumbled upon a solution, but it seems that it is indeed yet unsolved. I'll file a bug report.

Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com

I actually didnt see it as a bug, more of a "parted doenst work with certain RAID arrays". A bug to me is when something goes wrong, not "unimplemented features" Thank you Sandy for opening the bug. Please let me know the # of it, and ill take a lok if i can add some light to it. --          /Rikard ----------------------------------------------------------------------------- email   : rikard.j@rikjoh.com web     : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78  46 1C EE 56 >