Red Hat Bugzilla – Bug 106602
LTC4825-dasd_diag device not recognized
Last modified: 2007-11-30 17:06:58 EST
The following has be reported by IBM LTC: dasd_diag device not recognized Hardware Environment: z990 Software Environment: RHEL 3 RC1 Steps to Reproduce: 1. VM format device 2. issue reserve command against device 3. added dasd_diag_mod to /sbin/mkinitrd before dasd_fba_mod 4. issue mkinitrd and zipl 5. reboot 6. lsmod shows dasd_diag_mod loaded 7. issue echo add device range=4730 > /proc/dasd/devices Actual Results: cat /proc/dasd/devices shows 4730 (ECKD) Console message: end_request: I/O error, dev 5e:14 (dasd), sector 0 unable to read partition table Expected Results: should show (DIAG) Additional Information:
Forget it, seriously. For some reason Martin Schwindefsky thinks it is unsafe to enable disk diagnostics on s390x. It is the same way in 2.6. So, one part of IBM thinks it cannot be done, another part of IBM thinks it should be done. I don't want to meddle into it. NOTABUG.
*** This bug has been marked as a duplicate of 105023 ***
Hi, I've read the duplicate record (105023) and that discusses s390x (64bit) but says it should work on s390 (31bit). My attempts detailed above were made on a s390 (31bit) image. This disk can be used as vdisk space for increased performance. Thanks.
I'm on vacation until 10/23, so I am reopening and reassigning to keep this on radar.
No need to keep it open Pete. The device was not getting properly attached to the image. Sorry, our error. Works fine on 31bit. Please close.