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 >
