Re: CentOS DASD format
On 7/21/06, Melancon, Ruddy [EMAIL PROTECTED] wrote: It comes back with a message that the file is not available. When I look in the /dev directory there is no dasda, although in looking in /sys I can find the file that describes the disk drive as well as the file that shows it online. But is dasda indeed online? Is the device driver module loaded? -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS DASD format
Richard Pinion wrote: Have done the fdasd command? fdasd comes *after* dasdfmt... [EMAIL PROTECTED] 7/21/2006 10:20:13 AM I am attempting to install CentOS (Red Hat) v4.2 in a zSeries LPAR (standalone). I IPLed the CD-ROM and I am at the point of havint to format the DASD. I entered: Dasdfmt -b 4096 -d cdl -f /dev/dasda Ummm.. I've done several CentOS installations, and I don't recall having to manually format the DASD on any of them... When you SSH/Telnet into the installation system, you end up in the system installer (Anaconda), which is pretty much a bouncing-ball thing, including the setup of the DASD. It comes back with a message that the file is not available. When I look in the /dev directory there is no dasda, although in looking in /sys I can find the file that describes the disk drive as well as the file that shows it online. It's likely that the installer hasn't set up the device nodes for your DASDs yet -- too early in the piece. Where does CentOS put the device descriptor and how do I address it in the 'dasdfmt' command? If you *really* need to format the DASDs manually, you will need to create the device nodes yourself. Check to see that the proc filesystem is mounted, then issue cat /proc/dasd/devices to see what device major/minors have been allocated to the DASDs. Then, mknod /dev/dasdan b maj min with appropriate substitutions for an maj and min, for each of the nodes you want, will get you started. But you really should not need to do any of this. Just follow the installer's prompts and it should get you there. Rob's comments are gold as well: ensure that the DASDs are online (cat the appropriate online pseudofile in the sys filesystem directory you found; a result of 1 is good) and that the DASD modules are loaded. Cheers, Vic Cross -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS DASD format
On 7/21/06, Melancon, Ruddy [EMAIL PROTECTED] wrote: When I look in the /dev directory there is no dasda, although in looking in /sys I can find the file that describes the disk drive as well as the file that shows it online. If the device (/dev/dasda) is not in /dev, maybe you need to create it manually ? Check if it is present in /proc/dasd/devices. You will fin the major and minor in that file. As an example : [EMAIL PROTECTED]:~ cat /proc/dasd/devices 0.0.0150(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 105840 blocks, 413 MB 0.0.0151(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 211860 blocks, 827 MB You can create the dasda device in that example by entering these commands : mknod /dev/dasda b 94 0 mknod /dev/dasda1 b 94 1 mknod /dev/dasda2 b 94 2 mknod /dev/dasda3 b 94 3 Then you will be able to dasdfmt and fdasd. Regards. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS DASD format
Is there a way to restart the loader? When I first connected to the IPLed image I was disconnected before I could do any setup. Now when I login I get a message... Loader has already been run. Starting shell. If I try to rerun the loader I get the same message. Ruddy A. Melancon IT System Specialist - ISD State of Alabama 64 North Union Street Montgomery, AL 36130 334.353.7275 When the only tool you have is a hammer, every problem begins to resemble a nail. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Vic Cross Sent: Friday, July 21, 2006 9:56 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS DASD format Richard Pinion wrote: Have done the fdasd command? fdasd comes *after* dasdfmt... [EMAIL PROTECTED] 7/21/2006 10:20:13 AM I am attempting to install CentOS (Red Hat) v4.2 in a zSeries LPAR (standalone). I IPLed the CD-ROM and I am at the point of havint to format the DASD. I entered: Dasdfmt -b 4096 -d cdl -f /dev/dasda Ummm.. I've done several CentOS installations, and I don't recall having to manually format the DASD on any of them... When you SSH/Telnet into the installation system, you end up in the system installer (Anaconda), which is pretty much a bouncing-ball thing, including the setup of the DASD. It comes back with a message that the file is not available. When I look in the /dev directory there is no dasda, although in looking in /sys I can find the file that describes the disk drive as well as the file that shows it online. It's likely that the installer hasn't set up the device nodes for your DASDs yet -- too early in the piece. Where does CentOS put the device descriptor and how do I address it in the 'dasdfmt' command? If you *really* need to format the DASDs manually, you will need to create the device nodes yourself. Check to see that the proc filesystem is mounted, then issue cat /proc/dasd/devices to see what device major/minors have been allocated to the DASDs. Then, mknod /dev/dasdan b maj min with appropriate substitutions for an maj and min, for each of the nodes you want, will get you started. But you really should not need to do any of this. Just follow the installer's prompts and it should get you there. Rob's comments are gold as well: ensure that the DASDs are online (cat the appropriate online pseudofile in the sys filesystem directory you found; a result of 1 is good) and that the DASD modules are loaded. Cheers, Vic Cross -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS DASD format
Is there a way to restart the loader? #cp ipl 00c Assuming the three punch files are still in your reader, that will just start the install process again. Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS DASD format
Melancon, Ruddy wrote: Is there a way to restart the loader? Not easily that I know of. Re-IPL of your media will probably be the easiest/quickest way. I find that it can take me several IPLs to get used to the installation process of an unfamiliar distro. Time is well spent getting familiar with the parmfile syntax, so that you can get to the point of SSH/Telnet into the installer with few or no console commands having to be entered. In your Load from CD-ROM case you could experiment with writing your own CD containing the installation files (kernel, parmfile, initrd) -- use a CD-RW while getting the parmfile right, unless you need a new set of coasters! :D Cheers, Vic Cross PS: Hoping this is helpful... It's *real* late (early?) over here and I might be starting to ramble :) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
