About 019a. Nov 22 07:13:46 JUUB16MS kernel: [ 73.806642] dasd-eckd 0.0.019a: A channel path to the device has become operational Nov 22 07:13:46 JUUB16MS kernel: [ 73.808080] dasd-eckd 0.0.019a: New DASD 3390/0C (CU 3990/01) with 1443 cylinders, 15 heads, 224 sectors Nov 22 07:13:46 JUUB16MS multipathd[505]: dasdi: add path (uevent) Nov 22 07:13:46 JUUB16MS kernel: [ 73.822758] dasd-eckd 0.0.019a: The disk layout of the DASD is not supported
Indeed this device appears to not be recorgised by the kernel. The kernel fails to identify it as a RAWTRACK; or it may be failing linux kernel layout validation. Net result is that bp_block property remains uninitialised. Is 019a device, similar to the 0198 device which was processed correctly? Nov 22 07:12:57 JUUB16MS kernel: [ 24.516335] dasd-eckd 0.0.0198: A channel path to the device has become operational Nov 22 07:12:57 JUUB16MS kernel: [ 24.517719] dasd-eckd 0.0.0198: New DASD 3390/0C (CU 3990/01) with 1443 cylinders, 15 heads, 224 sectors Nov 22 07:12:57 JUUB16MS kernel: [ 24.519920] dasd-eckd 0.0.0198: DASD with 4 KB/block, 1038960 KB total size, 48 KB/track, compatible disk layout Do any other linux systems recognise / can format the 019a device? Soon there will be 4.9 kernel in zesty to try if that kernel does any better job at detecting this device. Is the device damaged in any way, or is somehow special? Looking at the multipath output dasdi (which is 019a) is blacklisted, yet syslog shows that a path to 019a was added. Is 019a a multipath device, and were all paths to it enabled? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643527 Title: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported" Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Problem description: procedure: echo 1 > /sys/bus/ccw/devices/0.0.0199/online /sbin/chzdev dasd-eckd 0199 -e -p /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y dasdfmt fails with: /sbin/dasdfmt: Unable to open device /dev/disk/by-path/ccw-0.0.0199: No such device looking at the syslog i can see a strange message that only comes out when i am having this issue: Nov 21 08:52:12 JUUB16MS kernel: [ 67.412484] dasd-eckd 0.0.0199: The disk layout of the DASD is not supported lsdasd returns: root@JUUB16MS:~# lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks ============================================================================== 0.0.0192 active dasda 94:0 ECKD 4096 5070MB 1298160 0.0.0195 active dasdb 94:4 FBA 512 40MB 81920 0.0.0193 n/f dasdc 94:8 ECKD 0.0.0196 active dasdd 94:12 FBA 512 40MB 81920 0.0.0194 n/f dasde 94:16 ECKD 0.0.0197 n/f dasdf 94:20 ECKD 0.0.0198 n/f dasdg 94:24 ECKD 0.0.0199 n/f dasdh 94:28 ECKD you can see that the 199 is not format and can't be formatted... a workaround is to vary the disk offline and then online again. this time it will start ok and you can format it and work with it. ------------------------------ just to be clear... this happens after linking to an un-formatted disk dynamically and then vary it online... for example: vmcp link '*' 199 199 echo 1 > /sys/bus/ccw/devices/0.0.0199/online /sbin/chzdev dasd-eckd 0199 -e -p /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1643527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
