I/O Error during startup of linux
Hi
What means "I/O Error" output below during startup of Linux ? <pre> dasd_erp: 0.0.0100: Channel program (complete): dasd_erp: 0.0.0100: 00000000099c1af0: 63400010 099c1b08 47400010 099c1b28 dasd_erp: 0.0.0100: 00000000099c1b00: 85001000 090dd000 80c00000 00000000 end_request: I/O error, dev dasda, sector 468656 dasd_erp(3990): 0.0.0100: EXAMINE 24: Command Reject detected - fatal error dasd(eckd): I/O status report for device 0.0.0100: dasd(eckd): in req: 00000000099c18f0 CS: 0x00 DS: 0x02 dasd(eckd): device 0.0.0100: Failing CCW: 00000000099c19d0 dasd(eckd): Sense(hex) 0- 7: 80 02 00 00 00 00 00 00 dasd(eckd): Sense(hex) 8-15: 00 00 00 00 00 00 00 00 dasd(eckd): Sense(hex) 16-23: 00 00 00 00 66 02 0f 00 dasd(eckd): Sense(hex) 24-31: 00 00 60 e0 00 00 00 00 dasd(eckd): 24 Byte: 0 MSG 0, no MSGb to SYSOP </pre> On the disk there can be : - software errors - hardware errors How to get this info in Linux (I mean in which files this info is stored and what kind of entries determines) ? |
Well, I think it means what it says, you had an input / output error on your 100-disk.
Is that a CMS disk or your Linux ipl volume? Is it formatted? (It doesn't sound like it is.) Does the system successfully ipl? Also, what level of RHEL is this system. |
It is zLinux on zVM and it is SLES9.
My system boots into maintenance mode because there is no disks available <tt>lsdasd</tt> cmd shows me only 1 dasd and I should have much more. How can I force disk discovery in SLES9 ? thx for help. |
Disk recovery is what you are dropped into when you can't mount a required volume (either your root volume or something later in /etc/fstab). If 'lsdasd' shows no disks, there is not much you can do there.
I'm sure you know most of this, but to start with you need to make sure that all required disks are attached to your guest before you ipl your Linux OS volume. That means they are either in the VM directory for your guest or accessed by your guests PROFILE EXEC. My experience is with RHEL and I'm not sure how much of this is applicable to SLES. If you do a "#CP Q DASD" command and all the the disks you require are present but your 'lsdasd' only shows the one 0.0.0100 disk then (in RHEL) it would mean that your initrd is only activating that one disk. In RHEL there is an entry in /etc/modprobe.conf that is similar to this Code:
options dasd_mod dasd=0201 Code:
echo "Loading dasd_mod.ko module" Code:
[root ~]# cat /etc/modprobe.conf |
All times are GMT -5. The time now is 04:31 PM. |