Yes, this seems to be a frequent, but not 100% consistent problem. The insmod/modprobe command segfaults during the load of the DASD driver(s), leaving the disks unusable. The error message that gets generated usually reports the problem as being in "rmmod' though, which just confuses things more.
The only things I've found to get around this are to: 1. Not modify the ramdisk size parameter in the kernel parmfile 2. Keep trying I'm hoping that when I build the new initrd for 10.1, that the newer version of the module utilities won't exhibit this behavior. The _truly_ odd thing is that the binaries on the initrd are the exact same ones that get installed on the DASD file system, and in the final environment, this problem never shows up. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bishop, Peter G Sent: Tuesday, July 19, 2005 2:44 AM To: [email protected] Subject: Re: Slackware 10.0 install failure - dasd_eckd_mod stuck in "initializing" state Extremely bad form to answer my own post, but given the timezone differences, I thought everyone might like to know today that persistence pays off, that is, the seventh (or was it eighteenth?) reboot eventually worked, in that the eckd module eventually finished initialising, and the "setup" command was able to find them, and the rest of the install kicked off. What a very curious turn of events, is all I can say. I'll be repeating this tomorrow, just to make sure (and to fix up a couple of install errors that broke the install anyway). cheers Peter Peter Bishop Mainframe IT Outsourcing Service Delivery EDS Asia-Pacific Phone:+61 2 9378 0113 + mailto:[EMAIL PROTECTED] > _____________________________________________ > From: Bishop, Peter G > Sent: Tuesday, 19 July 2005 3:49 PM > To: '[email protected]' > Subject: Slackware 10.0 install failure - dasd_eckd_mod stuck in "initializing" state > > Hi List, > > I'm trying to install the Slackware from the site at > http://ftp.ibiblio.org/pub/Linux/distributions/slack390/slack390-10.0/ > and am at the point where the VM reader install files are IPLed and > ready to start formatting DASD. > > When I first did this, I did a dasdfmt and got a "cannot open" type > error, as in: > > [EMAIL PROTECTED]:/1 dasdfmt -b 4096 -f /dev/dasda -p > dasdfmt -b 4096 -f /dev/dasda -p > dasdfmt: Unable to open device /dev/dasda: No such device > [EMAIL PROTECTED]:/2 > > So I tried a few things and finally saw that there was something amiss > in "driver" land: > > lsmod > Module Size Used by > reiserfs 243712 0 (unused) > jfs 188472 0 (unused) > ext3 73168 0 (unused) > dasd_diag_mod 5996 0 (autoclean) (unused) > jbd 52056 0 [ext3] > dasd_eckd_mod 57896 1 (initializing) > dasd_fba_mod 5340 0 (unused) > dasd_mod 51036 3 [dasd_diag_mod dasd_eckd_mod dasd_fba_mod] > qeth 149528 1 > qdio 38224 1 [qeth] > [EMAIL PROTECTED]:/5 cat /proc/dasd/devices > cat /proc/dasd/devices > 0200(none) at ( 94: 0) is dasda : accepted > 0201(none) at ( 94: 4) is dasdb : unknown > [EMAIL PROTECTED]:/6 > > I trawled around in the archives, and found this very similar, almost > identical incidence, but am none the wiser: > http://www2.marist.edu/htbin/wlvtype?LINUX-VM.47871 (actually this > link is the end of that particular thread). > > I've rebooted numerous times, reformatted the minidisks in question > both from VM:Secure and native CPFMTXA, enlarged the ramdisk size, > re-downloaded the initrd and vminstall images (i.e. the VM reader > install image, not the tape install one). I even made these minidisks > available to a SLES8 system here and ran a dasdfmt/fdasd on them to > make sure they were OK. Even then, they were still not acceptable to > the Slackware installer. > > Now I'm sorta stuck - anyone care to opine on where I went wrong and > even better, what I can do to get these disks going? At the moment, > I'm in a tight loop doing reboots until it works. Plenty of console > logs, etc., for any who wants them. > > cheers> > Peter > > Peter Bishop > Mainframe > IT Outsourcing Service Delivery > EDS Asia-Pacific > > Phone:+61 2 9378 0113 > + mailto:[EMAIL PROTECTED] > > ---------------------------------------------------------------------- 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
