Okay, I stand corrected. I haven't tried multiple partitions because with VM minidisks and LVM, there didn't seem to be much point.
I do recall reading once that more than one partition wasn't actually supported by all of the components involved, but that was back in the early SLES7 days, so if that actually was the case at one time, it's not surprising it's been fixed. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Post, Mark K > Sent: Monday, January 26, 2004 12:43 PM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] adding DASD in SuSE8 > > > Ummm, just _what_ supposedly doesn't work? Using multiple > partitions on > DASD? If so, then I have to emphatically state that it > _does_ work. I'm > using it on a number of my systems with absolutely no problems. > $ df > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/dasda1 2365528 1498760 842736 65% / > /dev/dasdb1 2365528 2194008 123456 95% /usr > /dev/dasdc1 2365528 2066556 274940 89% > /usr/src/slackware-current > /dev/dasdd1 1024680 913908 100364 91% > /usr/src/slackware-current/slackware > /dev/dasdd2 1340760 1012636 260016 80% /mnt/hd > > > Mark Post > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Hall, Ken (IDS ECCS) > Sent: Monday, January 26, 2004 12:31 PM > To: [EMAIL PROTECTED] > Subject: Re: adding DASD in SuSE8 > > > Looks like you haven't created the partition: > > fdasd -a /dev/dasdd > > dasdd is the whole disk > > dasdd1 is the first partition created by fdasd. dasdd2 would > be the second, > but supposedly that doesn't work. > > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > > Behalf Of Ken > > Vance > > Sent: Monday, January 26, 2004 11:45 AM > > To: [EMAIL PROTECTED] > > Subject: [LINUX-390] adding DASD in SuSE8 > > > > > > Hi, > > > > I am trying to add DASD to a new SuSE8 install. I am trying > > ti use the > > same procedure that I used for the 2.4.7 kernel. > > > > 1.) ICKDSF format the packs, and then CMS format the MDISK areas > > 2.) echo -n "add device range=204-207">>/proc/dasd/devices > > 3.) UPDATE zipl.conf and then perform a zipl > > 4.) I normally would then use dasdfmt -n 204 -b 4096, but > that did not > > work. I noticed in a thread that I should use dasdfmt -f > > /dev/dasdd -b > > 4096 This command would allow me to format the dasd. > > > > I then went to yast2 to create a LVM. When the system tries > > to add the > > dasd to a LVM, it says "pvcreate -- invalid physical volume > > "/dev/dasdd1" > > I can issue the pvcreate command pvcreate -ff /dev/dasdd and > > it says it > > works. The system seems to have a problem with the numeric > > part of the > > dasdx . I tried just formatting the dasd in the partition > > section but it > > also has a problem when it tries to format /dev/dasdd1. > > > > Is there a setting that needs to be turned on to allow the > > numerics? Also, > > someone mentioned that DEVFS needs to be active to use the -n > > 204 option > > on a dasdfmt. How is this turned on? > > > > Thanks, > > > > Ken Vance > > Amadeus > > >
