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: 'linux-390@vm.marist.edu' > 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) > jbd52056 0 [ext3] > dasd_eckd_mod 57896 1 (initializing) > dasd_fba_mod5340 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
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) jbd52056 0 [ext3] dasd_eckd_mod 57896 1 (initializing) dasd_fba_mod5340 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
Is sdb.suse.de down???
Is the sdb.suse.de site is down. I tried sbd2.suse.de too and that didn't work either. Is there anywhere else that I can download updates from? The address is pingable but not accessible... Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -- 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: Is sdb.suse.de down???
I just tried it, and it works for me. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wiggins, Mark Sent: Monday, July 18, 2005 3:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Is sdb.suse.de down??? Is the sdb.suse.de site is down. I tried sbd2.suse.de too and that didn't work either. Is there anywhere else that I can download updates from? The address is pingable but not accessible... -- 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: Is sdb.suse.de down???
I can get to it for SLES9 updates but not SLES8. Any ideas? Maybe YAST differences? Thanks. "Wiggins, Mark" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 07/18/2005 01:11 PM Please respond to Linux on 390 Port To LINUX-390@VM.MARIST.EDU cc Subject Is sdb.suse.de down??? Is the sdb.suse.de site is down. I tried sbd2.suse.de too and that didn't work either. Is there anywhere else that I can download updates from? The address is pingable but not accessible... Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -- 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: Problem with /dev/opt/opt at boot
Lance: am I correct in saying that the mount point for the /dev/opt/opt (lvm) file system is /opt? The approach I follow when creating something like an /opt is to create an /opt-bkup before proceeding (ie. copy recursive opt to opt-bkup). Then I create the vgopt and lvopt (lvm) so I don't have to be checking my glasses by seein double images: opt opt. Then, I manually go through the process (i.e. no yast) and go as far as the step when I am supposed to mount the /opt for the LVM (vgopt and lvopt). Instead of mounting on /opt, I munt on /mnt/copy so I can populate my new LVM with data from my /opt-bkup. Then, I just go to my /etc/fstab, point my LVM to /opt and I reboot. What you may want to do is remove the LVM info pointing in /etc/fstab point your /opt to /dev/opt/opt. If your original /opt has not been corrupted, you should be OK. If you did it through yast and yast tried to delete /opt before creating it, your data might be gone and your backup will become your best friend. Hope this help and thank you for reminding us all about doing our backups. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning "Longstreth, Lance" To: LINUX-390@VM.MARIST.EDU <[EMAIL PROTECTED]cc: ag.com> Subject: Problem with /dev/opt/opt at boot Sent by: Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> 07/18/2005 09:49 AM Please respond to Linux on 390 Port Need some guidance here We issued the shutdown command for a Linux test image and after it went down we IPL'ed the LPAR. In the boot process coming up we are receiving a the message that /dev/opt/opt a LVM reiserfs file system has problems. I can see from the log that FSCK has tried to fix the problem, but is unable to. It then issues the message to run it manually. I have attempted to run it manually issuing the command FSCK.REISERFS --rebuild-sb /dev/opt/opt. When I issues this command it tells me it cannot find the device? Anyone have thoughts as to how I could recover this? We were lacks and had not yet made backups of this LVM file system , so I can not restore it from a back-up. I do have a TAR file back-up of the complete system that resides on another LVM file system. This could be used to rebuild the systems, if I could get the system up. But can not access this because the system does not boot up high enough to get to these files. Is their a way to bypass what's on /opt and get the system up? I could then make a new /opt filesystems if I could just get the system up. Another thought I had was to modify the /etc/fstab file and take the entry for /dev/opt/opt out of it. But, we are unable to connect to the partition via ssh. I am communicating with the system via the HMC reading the message console for the LPAR? Using this method the screen are not friendly and trying to use VI is impossible, as I can't read the screen when in VI from the message console. Thanks for y
Re: DS8000 usage for SLES9 guest
Than you for anwering, Stefan.
No, as far as I understood one of my zLinux-staff colleagues his boot
parameters
mark dasd-device addresses as ('all will be sensed and taken' ...).
After formating the phys. volumes, defining LVM's and appropr. group via
Yast we shutdown
and reboot SLES9. And then does not come up properly. I can only logon via
virt. 3270-console and replace /etc/fstab with an older version without LVM
... :-(
But we can try the method you proposed and I'll keep you informed about the
results
(i.e. screenshots).
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-
Stefan Bader
<[EMAIL PROTECTED]
ibm.com> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: DS8000 usage for SLES9 guest
18.07.2005 18:03
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Hi,
Linux on 390 Port wrote on 15.07.2005 16:44:39:
>
> But up to now we run into problems defining LVM2-groups including these
> large Mdisks. After definition SLES9-guest comes not up properly,
> only in S-mode (maintenance).
>
There shouldn't be a problem with the size of the mdisks in lvm2. Are the
DASDs included in the range of devices that are set online after boot? Did
mkinitrd run and add the lvm2 commands to the initrd?
Maybe you could post the boot messages...
Regards,
Stefan
--
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: SLES9 Installation - Very Basic
What we did around here is the following (we don't have zVM but install zLinux as LPAR) mkdir /sles9 then we downloaded each iso into this location (each for your CD under the same directory). then we downloaded the sp1 iso's (two iso) note: now you can get sp2 as well. then downloaded mksles9root into this same directory. executed mksles9root (which will create a subdirectory called sles9root) note: make sure you have at least 10 GB for the /sles9 directory and subdirectories. Then, we exported (nfs) the mksles9root directory. Now you are ready for the hmc. If you need any more help or details please feel free. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning "Smith, Ann (ISD, IT)" To: LINUX-390@VM.MARIST.EDU <[EMAIL PROTECTED]cc: tford.com> Subject: SLES9 Installation - Very Basic Sent by: Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> 07/18/2005 05:27 PM Please respond to Linux on 390 Port I have finally ordered SLES9 for zseries. I ordered media which I have received. There are 6 CD's for SLES9 64-bit for zseries and 6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9. Why did I think SLES9 was 64-bit only? I'm not sure anyone can answer that question. But hopefully they can answer the one regarding setting up an installation server for network installations- What is the best method to use for getting the data off the CD's to disk and installing using NFS? The release notes in /docu on CD1 just say to enter mkdir -p installroot/sles9/CD1 then copy contents of CD1 into the directory mkdir -p installroot/core9/CD1 then copy contents of CD2 into this directory mkdir -p installroot/core9/CD2 then copy contents of CD3 into this directory and so on ... I guess I just use cp command with -x and -a for this method and let yast do the rest. On the other hand the Redbook on LPAR to virtual servers in Two Days (sg246695.pdf) says to use dd to create ISO images and use mksles9root to creat the SLES9 install tree. Which method is preferred? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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 The information conta
Re: SLES9 Installation - Very Basic
On Mon, 18 Jul 2005, Smith, Ann (ISD, IT) wrote: > I have finally ordered SLES9 for zseries. > I ordered media which I have received. > There are 6 CD's for SLES9 64-bit for zseries and > 6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9. > Why did I think SLES9 was 64-bit only? That would be for Gen 4 s/390 machines. > Which method is preferred? NFS seems relatively straight forward. > > > > * > PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is > for the exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not the intended > recipient, any use, copying, disclosure, dissemination or distribution is > strictly prohibited. If you are not the intended recipient, please notify > the sender immediately by return e-mail, delete this communication and > destroy all copies. > * > > -- > 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 > sleekfreak pirate broadcast http://sleekfreak.ath.cx:81/ -- 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: SLES9 Installation - Very Basic
On Monday 18 July 2005 3:27 pm, Smith, Ann (ISD, IT) wrote: Make a SLES 9 install server, The doc on this is on CD1 under the docu directory. -Cameron > I have finally ordered SLES9 for zseries. > I ordered media which I have received. > There are 6 CD's for SLES9 64-bit for zseries and > 6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9. > Why did I think SLES9 was 64-bit only? > I'm not sure anyone can answer that question. > But hopefully they can answer the one regarding setting up an installation > server for network installations- > What is the best method to use for getting the data off the CD's to disk > and installing using NFS? > The release notes in /docu on CD1 just say to enter > mkdir -p installroot/sles9/CD1 then copy contents of CD1 into the directory > mkdir -p installroot/core9/CD1 then copy contents of CD2 into this > directory > > mkdir -p installroot/core9/CD2 then copy contents of CD3 into this > directory > > and so on ... > I guess I just use cp command with -x and -a for this method and let yast > do the rest. > On the other hand the Redbook on LPAR to virtual servers in Two Days > (sg246695.pdf) > says to use dd to create ISO images and use mksles9root to creat the SLES9 > install tree. > Which method is preferred? > > > > * > PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is > for the exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not the intended > recipient, any use, copying, disclosure, dissemination or distribution is > strictly prohibited. If you are not the intended recipient, please notify > the sender immediately by return e-mail, delete this communication and > destroy all copies. > * > > -- > 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 -- Cameron Seader Novell, Inc. [EMAIL PROTECTED] Tel: 801.861.2686 Cell: 801.913.5992 Fax: 801.861.9478 -- 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: Is sdb.suse.de down???
I'm just not able to perform an "online update" from http://sdb.suse.de/download like I've always been able to do in the past. I've been away for 2 weeks and thought maybe something had changed. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Driscoll Sent: Monday, July 18, 2005 4:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Is sdb.suse.de down??? I can get to it for SLES9 updates but not SLES8. Any ideas? Maybe YAST differences? Thanks. "Wiggins, Mark" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 07/18/2005 01:11 PM Please respond to Linux on 390 Port To LINUX-390@VM.MARIST.EDU cc Subject Is sdb.suse.de down??? Is the sdb.suse.de site is down. I tried sbd2.suse.de too and that didn't work either. Is there anywhere else that I can download updates from? The address is pingable but not accessible... Mark Wiggins University of Connecticut Operating Systems Programmer 860-486-2792 -- 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 -- 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
SLES9 Installation - Very Basic
I have finally ordered SLES9 for zseries. I ordered media which I have received. There are 6 CD's for SLES9 64-bit for zseries and 6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9. Why did I think SLES9 was 64-bit only? I'm not sure anyone can answer that question. But hopefully they can answer the one regarding setting up an installation server for network installations- What is the best method to use for getting the data off the CD's to disk and installing using NFS? The release notes in /docu on CD1 just say to enter mkdir -p installroot/sles9/CD1 then copy contents of CD1 into the directory mkdir -p installroot/core9/CD1 then copy contents of CD2 into this directory mkdir -p installroot/core9/CD2 then copy contents of CD3 into this directory and so on ... I guess I just use cp command with -x and -a for this method and let yast do the rest. On the other hand the Redbook on LPAR to virtual servers in Two Days (sg246695.pdf) says to use dd to create ISO images and use mksles9root to creat the SLES9 install tree. Which method is preferred? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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: DS8000 usage for SLES9 guest
Hi, Linux on 390 Port wrote on 15.07.2005 16:44:39: > > But up to now we run into problems defining LVM2-groups including these > large Mdisks. After definition SLES9-guest comes not up properly, > only in S-mode (maintenance). > There shouldn't be a problem with the size of the mdisks in lvm2. Are the DASDs included in the range of devices that are set online after boot? Did mkinitrd run and add the lvm2 commands to the initrd? Maybe you could post the boot messages... Regards, Stefan -- 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: Problem picking up Virtual Swap on Startup
nope, I'm running it on a 9672 R16 under z/VM 4.4 "Post, Mark K" <[EMAIL PROTECTED] m> To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc <[EMAIL PROTECTED] IST.EDU> Subject Re: Problem picking up Virtual Swap on Startup 07/18/2005 10:12 AM Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> Unless he's running a 64-bit system, in which case the DIAG driver is not available. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Adam Thornton Sent: Monday, July 18, 2005 10:27 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problem picking up Virtual Swap on Startup -snip- If you're having trouble getting dasd_diag_mod loaded (and since swap will be mounted before you have the option to load this) you could either rebuild an initrd with dasd_diag_mod and preload it there, or put it into /etc/modules (not sure that's the right place on SLES 9, and that might not be before swap gets mounted), or take the speed hit and run SWAPGEN in FBA mode and swapon to the raw device /dev/ dasdf/ -- 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: Problem picking up Virtual Swap on Startup
Unless he's running a 64-bit system, in which case the DIAG driver is not available. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Adam Thornton Sent: Monday, July 18, 2005 10:27 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problem picking up Virtual Swap on Startup -snip- If you're having trouble getting dasd_diag_mod loaded (and since swap will be mounted before you have the option to load this) you could either rebuild an initrd with dasd_diag_mod and preload it there, or put it into /etc/modules (not sure that's the right place on SLES 9, and that might not be before swap gets mounted), or take the speed hit and run SWAPGEN in FBA mode and swapon to the raw device /dev/ dasdf/ -- 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: Problem picking up Virtual Swap on Startup
On Jul 18, 2005, at 9:15 AM, John Kaba wrote: I have a SuSE SLES 9 system, that I have configured with a 256 M Virtual Disk for Swap, as well as a secondary minidisk swap disk. Both show up when I do a 'cat /proc/dasd/devices' after booting: 0.0.0301(ECKD) at ( 94:16) is dasde : active at blocksize: 4096, 18 blocks, 703 MB 0.0.0300(FBA ) at ( 94:20) is dasdf : active at blocksize: 512, 524288 blocks, 256 MB but initially only the minidisk shows up as swap. I have to manually 'swapon /dev/dasdf1' in order to start it. I have modified my /etc/fstab to include both, but only the minidisk device shows up. /dev/dasde1 swap swap pri=-2 0 0 /dev/dasdf1 swap swap pri=42 0 0 I am using Sine Nomine's 'Swapgen' to initialize the virtual disk, and am even using the DIAG option, which also does not seem to work, even when I try to manually enable it using the command 'modprobe dasd_diag_mod'. If you're having trouble getting dasd_diag_mod loaded (and since swap will be mounted before you have the option to load this) you could either rebuild an initrd with dasd_diag_mod and preload it there, or put it into /etc/modules (not sure that's the right place on SLES 9, and that might not be before swap gets mounted), or take the speed hit and run SWAPGEN in FBA mode and swapon to the raw device /dev/ dasdf/ Adam -- 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
Problem picking up Virtual Swap on Startup
I have a SuSE SLES 9 system, that I have configured with a 256 M Virtual Disk for Swap, as well as a secondary minidisk swap disk. Both show up when I do a 'cat /proc/dasd/devices' after booting: 0.0.0301(ECKD) at ( 94:16) is dasde : active at blocksize: 4096, 18 blocks, 703 MB 0.0.0300(FBA ) at ( 94:20) is dasdf : active at blocksize: 512, 524288 blocks, 256 MB but initially only the minidisk shows up as swap. I have to manually 'swapon /dev/dasdf1' in order to start it. I have modified my /etc/fstab to include both, but only the minidisk device shows up. /dev/dasde1 swap swap pri=-2 0 0 /dev/dasdf1 swap swap pri=42 0 0 I am using Sine Nomine's 'Swapgen' to initialize the virtual disk, and am even using the DIAG option, which also does not seem to work, even when I try to manually enable it using the command 'modprobe dasd_diag_mod'. Any suggestions? Thanks in advance -- 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
Problem with /dev/opt/opt at boot
Need some guidance here We issued the shutdown command for a Linux test image and after it went down we IPL'ed the LPAR. In the boot process coming up we are receiving a the message that /dev/opt/opt a LVM reiserfs file system has problems. I can see from the log that FSCK has tried to fix the problem, but is unable to. It then issues the message to run it manually. I have attempted to run it manually issuing the command FSCK.REISERFS --rebuild-sb /dev/opt/opt. When I issues this command it tells me it cannot find the device? Anyone have thoughts as to how I could recover this? We were lacks and had not yet made backups of this LVM file system , so I can not restore it from a back-up. I do have a TAR file back-up of the complete system that resides on another LVM file system. This could be used to rebuild the systems, if I could get the system up. But can not access this because the system does not boot up high enough to get to these files. Is their a way to bypass what's on /opt and get the system up? I could then make a new /opt filesystems if I could just get the system up. Another thought I had was to modify the /etc/fstab file and take the entry for /dev/opt/opt out of it. But, we are unable to connect to the partition via ssh. I am communicating with the system via the HMC reading the message console for the LPAR? Using this method the screen are not friendly and trying to use VI is impossible, as I can't read the screen when in VI from the message console. Thanks for your comments and advice , Lance Longstreth Bandag Inc Technical Support & Operations zOS systems/Linux 1-(563)-262-2927 [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
Re: HCPIIO1250I message from z/VM V5.1 at z/VM IPL.
Evidently my MITIME setting is being overridden to 40 seconds as well. So, that must not be the problem. Dave Jones wrote: Hi, gang. I don't have any hands-on experience with the DS8100, but I would suspect that 40 seconds would be a reasonable setting for MIH time out. This sounds silly, I know, but is the device plugged into a wall socket, powered up and correctly connected to the host? Have a good one. DJ Lutz Hamann wrote: Rich, for DS8100 the MIH default seems to be 00:40 (40 seconds). That should be quite enough, shouldn't it ? ciao Lutz - Lutz Hamann BETA Systems Software AG z/OS System Engineering - Rich Smrcina <[EMAIL PROTECTED] om>To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc <[EMAIL PROTECTED] IST.EDU> Subject Re: HCPIIO1250I message from z/VM V5.1 at z/VM IPL. 17.07.2005 16:51 Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> Do you have the missing interrupt handler time set sufficiently high? The newer DASD typically required that the MIH time be set high, you might want to check the documentation for the DS8100 or the hardware bucket doc for VM to determine what the correct value should be. mainframe_s390 wrote: Hi,all Please teach me. I added a new disk device(DS8100). The address range is 1000-1F9F. Next message is showned at z/VM V5.1 every IPL. HCPIIO1250I Device 1000 cannot be varied online because a time-out condition occurred. ・ ・ HCPIIO1250I Device 1F9F cannot be varied online because a time-out condition occurred. The SYSTEM CONFIG file of the z/VM.(Only DEVICES statement) DEVICES, ONLINE_AT_IPL - Please teach me the way of solution. - K.M. __ Save the earth http://pr.mail.yahoo.co.jp/ondanka/ -- 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 -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006 -- 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 -- 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 -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006 -- 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: HCPIIO1250I message from z/VM V5.1 at z/VM IPL.
Hi, gang. I don't have any hands-on experience with the DS8100, but I would suspect that 40 seconds would be a reasonable setting for MIH time out. This sounds silly, I know, but is the device plugged into a wall socket, powered up and correctly connected to the host? Have a good one. DJ Lutz Hamann wrote: > Rich, > > for DS8100 the MIH default seems to be 00:40 (40 seconds). > > That should be quite enough, shouldn't it ? > > > ciao Lutz > > - > Lutz Hamann > BETA Systems Software AG > z/OS System Engineering > - > > > > Rich Smrcina > <[EMAIL PROTECTED] > om>To > Sent by: Linux on LINUX-390@VM.MARIST.EDU > 390 Port cc > <[EMAIL PROTECTED] > IST.EDU> Subject >Re: HCPIIO1250I message from z/VM >V5.1 at z/VM IPL. > 17.07.2005 16:51 > > > Please respond to > Linux on 390 Port > <[EMAIL PROTECTED] > IST.EDU> > > > > > > > Do you have the missing interrupt handler time set sufficiently high? > The newer DASD typically required that the MIH time be set high, you > might want to check the documentation for the DS8100 or the hardware > bucket doc for VM to determine what the correct value should be. > > mainframe_s390 wrote: > >>Hi,all >> >>Please teach me. >>I added a new disk device(DS8100). >>The address range is 1000-1F9F. >> >>Next message is showned at z/VM V5.1 every IPL. >> >>HCPIIO1250I Device 1000 cannot be varied online because a >>time-out condition occurred. >>・ >>・ >>HCPIIO1250I Device 1F9F cannot be varied online because a >>time-out condition occurred. >> >>The SYSTEM CONFIG file of the z/VM.(Only DEVICES >>statement) >>DEVICES, >> ONLINE_AT_IPL - >> >>Please teach me the way of solution. >> >>- >>K.M. >> >>__ >>Save the earth >>http://pr.mail.yahoo.co.jp/ondanka/ >> >>-- >>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 >> > > > -- > Rich Smrcina > VM Assist, Inc. > Main: (262)392-2026 > Cell: (414)491-6001 > Ans Service: (360)715-2467 > rich.smrcina at vmassist.com > > Catch the WAVV! http://www.wavv.org > WAVV 2006 - Chattanooga, TN - April 7-11, 2006 > > -- > 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 -- 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
LCS support and Debian/390
Hello, Anyone having problems during installation of Debian/390 R3.1 with LCS support? Seems that network doesn't come up, so we can't continue install from ftp site. Any hint about? TIA Carlos Bodra Sao Paulo - Brazil -- 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: HCPIIO1250I message from z/VM V5.1 at z/VM IPL.
Rich, for DS8100 the MIH default seems to be 00:40 (40 seconds). That should be quite enough, shouldn't it ? ciao Lutz - Lutz Hamann BETA Systems Software AG z/OS System Engineering - Rich Smrcina <[EMAIL PROTECTED] om>To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc <[EMAIL PROTECTED] IST.EDU> Subject Re: HCPIIO1250I message from z/VM V5.1 at z/VM IPL. 17.07.2005 16:51 Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> Do you have the missing interrupt handler time set sufficiently high? The newer DASD typically required that the MIH time be set high, you might want to check the documentation for the DS8100 or the hardware bucket doc for VM to determine what the correct value should be. mainframe_s390 wrote: > Hi,all > > Please teach me. > I added a new disk device(DS8100). > The address range is 1000-1F9F. > > Next message is showned at z/VM V5.1 every IPL. > > HCPIIO1250I Device 1000 cannot be varied online because a > time-out condition occurred. > ・ > ・ > HCPIIO1250I Device 1F9F cannot be varied online because a > time-out condition occurred. > > The SYSTEM CONFIG file of the z/VM.(Only DEVICES > statement) > DEVICES, > ONLINE_AT_IPL - > > Please teach me the way of solution. > > - > K.M. > > __ > Save the earth > http://pr.mail.yahoo.co.jp/ondanka/ > > -- > 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 > -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006 -- 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
