Some more info. When creating a raid device it tells you to create your partitions as either 0x83 or 0xFD (Linux Raid). I chose 0x83 and it did not work. (I am trying as we speak using 0XFD as the type) However, I have w/o a doubt used this in the past, including the very system I am working on now. (onboard LSI SCSI, 2x35 scsi-3 on same channel) I just contacted a buddy of mine that does alot of nitty gritty Linux development as he says he remembers something about a bug related to this. I think the SuSE installer should not say to create as either 0x83 or 0xFD, instead it should say 0xFD only. The reason why it works on some other distros is actually because of a bug, lol. (not sure on this, just hear-say from some linux developers I know) I'm not sure what the issue is, but I am reinstalling now trying the oxFD part type. -cc --- mmarseglia wrote:

On Wed, 8 Dec 2004 11:47:56 -0800 (PST), Rhugga wrote:

...

I am trying to install SLES 9 on a system with 2 36gb SCSI disks with a RAID 1 config.

First I create 6 partitions as follows:

On sda and sdb I create 3 partitions each as follows: Primary partition, Type 0X83, no mount point, size 100mb (for /boot) Primary partition, Type 0x83, no mount point, size 1024mb (for swap) Primary partition, Type 0x83, no mount point, size 33gb (for /)

Correct me if I'm wrong, but when doing software RAID don't you create the partitions as type Linux RAID, not as Linux?

You've also created your swap partitions as type Linux instead of Linux Swap (type 82).

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

I recently modified my syslog.conf file and then went to yast to disable/enable the syslogd service as as quick and dirty way to get syslog.conf reread. Big mistake. When you disable syslog in YAST a large number of other services are automatically disabled for you. That's not so bad, but when you reenable syslog those services are not turned back on. I have gone back and reenabled those services as best as I could but I would appreciate it if someone could point me to a list of services that are turned on in a default installation of Suse 9.2 to make sure that I'm not overlooking something. On a related matter, it __seems__ that disable/enable syslogd caused powersaved to be enabled. I'm only 10% confident of this (don't want to mess with syslogd to test this out) but powersaved was enabled after my first disable/enable sequence. Now it might have been enabled earlier but I don't know how. In fact it was the powersaved daemon that made me realize I had a problem because I saw that a stream of error messages were being syslogged by the system saying that it could not connect to the powersaved daemon which led me to fire up the runlevel editor in YAST and that's when I saw a lot of important services were turned off. Thanks, Patrick

On Fri, 2004-12-10 at 11:00, Peter B Van Campen wrote:

On Friday 10 December 2004 9:24 am, Patrick John Hays wrote:

...

I recently modified my syslog.conf file and then went to yast to disable/enable the syslogd service as as quick and dirty way to get syslog.conf reread. Big mistake.

When you disable syslog in YAST a large number of other services are automatically disabled for you. That's not so bad, but when you reenable syslog those services are not turned back on.

Hi Patrick,

This problem deserves a "Feedback". http://www.suse.de/feedback .

Not sure this would require a feedback as it is the correct way that it functions. A better way to get syslog to re-read it's config is rcsyslog reload Which causes syslog to re-read the conf file. -- Ken Schneider UNIX since 1989 SuSE since 1998 * Only reply to the list please*