Bug 106915
| Summary: | Installer does not recognize non-ECKD drives | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux Beta | Reporter: | Chip Bryant <cbryant> |
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | beta5 | CC: | borgan, jlamb, karsten, laroche |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | s390 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-10-04 21:44:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chip Bryant
2003-10-13 14:54:22 UTC
don't put dasd= at the beginning of the line )workaround, bug actually fixed in our current internal version) and change it to DASD= greetings, Florian La Roche I changed the PARM file as you stated but I still received the same results. I moved the DASD= to the end of another line and put it all in caps but it still did not work. My PARM file is below: hostname=li3000.sial.com root=/dev/ram0 R0 CHANDEV=ctc0,0x3000,0x3001 chandev=ctc0,0x3000,0x3001 nettype=ctc ipaddr=141.247.10.52 DASD=200-206 network=141.247.10.0 netmask=255.255.255.0 broadcast=255.255.255.255 gateway=255.255.10.50 mtu=1500 dns=141.247.9.19 searchdns=sial.com Please advise as what to try/do next. Thanks, Chip You can ssh to debug.0.1 (your Linux install environment) and use mknod to create the appropriate device and insmod/dasdfmt to format your dasd devices within the Red Hat install environment. greetings, Florian La Roche I installed the ssh software on my PC so I can get onto the system from that before I do the install dialog. Please remember, I am from the mainframe background and don't understand some of what you are saying. I found and printed out a device drivers manual from IBM where I found the mknod command but was not too sure what parameters to give it. Based on what comes out on the VM server, I keyed in seven of them like the following: mknod -m 660 /dev/dasda1 (thru g1) b 94 0 (thru 6) It came back with the prompt so I figured it worked OK. I then found the insmod command but again, was not too sure what to put into it. It said to replace the dasd_mod with the name of the device driver module (which I don't know what that is). As a result, I keyed in: insmod dasd_mod dasd=200-206 It took the command without an error so I figured it worked OK. However, when I try to run the dasdfmt command, I get the no devices found error again. I am probably doing something wrong but I don't know what. Please let me know what I should be putting in for these mknod and insmod commands or point me in the direction to find out what should go there. Thanks, Chip Hi Chip, the problem lies in how the installer handles the case where the dasd module presents an ICKDSF-formatted device to the linux kernel. Here is a sample /proc/dasd/devices showing two volumes with a problem similar to yours: -/bin/sh-2.05b# cat /proc/dasd/devices 0300(ECKD) at ( 94: 0) is dasda : ready 0301(ECKD) at ( 94: 4) is dasdb : ready 0302(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 360000 blocks, 1406 MB 0303(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 180000 blocks, 703 MB -/bin/sh-2.05b# in the above example, dasda and dasdb are formatted by ickdsf (as you have done) but are not useable without first manually running dasdfmt. Note that dasdc and dasdd in the above example are formatted properly already and ready for use w/anaconda (even though status is "ready" dasda and dasdb are not usuable by anaconda), so we will perform the steps that make dasda and dasdb have the same status as dasdc and dasdd ... to do this, 1) start your install 2) proceed to the "Welcome to Red Hat Enterprise Linux AS!" screen (first screen after picking network/harddrive install type) 3) in a second terminal, connect again (through telnet or ssh) to your linux install image in the second terminal, enter the following commands: 4) use mknod for each ickdsf formatted device (dasda and dasdb in my above sample). the major and minor numbers are available by looking at /proc/dasd/devices (ie 94 0 for dasda, etc.): -/bin/sh-2.05b# mknod /a b 94 0 -/bin/sh-2.05b# mknod /b b 94 4 5) now manually run the dasdfmt command on each ickdsf formatted device (shown here for /a only; the same command with /b should be run for dasdb): -/bin/sh-2.05b# dasdfmt -f /a Please enter the blocksize of the formatting [4096]: Drive Geometry: 5000 Cylinders * 15 Heads = 75000 Tracks I am going to format the device /a in the following way: Device number of device : 0x300 Labelling device : yes Disk label : VOL1 Disk identifier : 0X0300 Extent start (trk no) : 0 Extent end (trk no) : 74999 Compatible Disk Layout : yes Blocksize : 4096 --->> ATTENTION! <<--- All data of that device will be lost. Type "yes" to continue, no will leave the disk untouched: yes Formatting the device. This may take a while (get yourself a coffee). Finished formatting the device. Rereading the partition table... ok -/bin/sh-2.05b# re-ipl the installer (ie repeat steps 1), 2) and 3) ) ... when connecting with the second terminal (first terminal is at "Welcome to Red Hat Enterprise Linux AS" screen again) notice the change in dasda, dasdb in /proc/dasd/devices: -/bin/sh-2.05b# cat /proc/dasd/devices 0300(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 900000 blocks, 3515 MB 0301(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 360000 blocks, 1406 MB 0302(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 360000 blocks, 1406 MB 0303(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 180000 blocks, 703 MB -/bin/sh-2.05b# now, you should be able to perform your install using anaconda (at the first terminal/welcome screen) with the dasd available for use ... HTH, Brock Hi Brock, Thanks so much for your information and instructions. Since I am from a mainframe background, much of this is very foreign to me. Anyway, what you told me worked perfectly on the one dasd (address = 206), which was, in fact, an ICKDSF-formatted "full pack" 3390 disk drive. However, the other 6 packs won't format. They are not full packs and they were not ICKDSF formatted. They are VM "mini-disks" and were formatted with the CMS "format" command followed by the CMS "reserve" command as stated in the RedHat install instructions. When I IPL the VM server with the LINUX, I don't see them the way your example showed them. I see the following: Partition check: dasda:CMS1/ RED200(MDSK): dasda1 dasdb:CMS1/ RED201(MDSK): dasdb1 dasdc:CMS1/ RED202(MDSK): dasdc1 dasdd:CMS1/ RED203(MDSK): dasdd1 dasde:CMS1/ RED204(MDSK): dasde1 dasdf:CMS1/ RED205(MDSK): dasdf1 They don't show as ECKD but as MDSK. When I looked at the /proc/dasd/devices, I see the following: Welcome to the Red Hat Linux install environment 1.01 for S/390 -bash-2.05b# cat /proc/dasd/devices 0200(DIAG) at ( 94: 0) is dasda : active at blocksize: 4096, 3600 blocks, 14 MB 0201(DIAG) at ( 94: 4) is dasdb : active at blocksize: 4096, 180000 blocks , 703 MB 0202(DIAG) at ( 94: 8) is dasdc : active at blocksize: 4096, 180000 blocks , 703 MB 0203(DIAG) at ( 94: 12) is dasdd : active at blocksize: 4096, 228240 blocks , 891 MB 0204(DIAG) at ( 94: 16) is dasde : active at blocksize: 4096, 300420 blocks , 1173 MB 0205(DIAG) at ( 94: 20) is dasdf : active at blocksize: 4096, 300420 blocks , 1173 MB 0206(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 601020 blocks , 2347 MB As you can see, the 206 is good which is the full pack volume and it shows as an ECKD device. However, the other ones, 200-205 all show as DIAG rather than ECKD. I did the mknod on each of them and it appeared to work fine. Then, when I tried to do the dasdfmt on them, I received the error as follows: -bash-2.05b# mknod /a b 94 0 -bash-2.05b# mknod /b b 94 4 -bash-2.05b# mknod /c b 94 8 -bash-2.05b# mknod /d b 94 12 -bash-2.05b# mknod /e b 94 16 -bash-2.05b# mknod /f b 94 20 -bash-2.05b# dasdfmt -b 4096 -f /a dasdfmt: Unsupported disk type /a is not an ECKD disk! -bash-2.05b# dasdfmt -f /a Please enter the blocksize of the formatting [4096]: 4096 dasdfmt: Unsupported disk type /a is not an ECKD disk! It is telling me that it is an Unsupported disk type and not an ECKD disk. Do I have to do something special for the VM mini-disks or are they not supported? Is the only disk I can use full pack volumes? I did try to continue on and I did get further. I got past the auto-partition and it asked me more questions. It then came up and said "Reading package information..." I am doing the FTP install. After a couple of minutes, it comes up and says "Unable to read header list. This may be due to a missing file or bad media. Press <return> to try again" When I do, it just keeps going between those two dialogs. I don't know if this is a different problem or still because of the disk issue. If I continue to get this error after the disk issue is resolved, should I open this as a new bug? Thanks for all your help, Chip jlamb |