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 Ubuntu Bugs, which is subscribed to 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1643527/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
