Re: Virtual device

-Original Message- > From: Linux on 390 Port On Behalf Of Stefan > Haberland > Sent: Thursday, October 22, 2020 10:03 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Virtual device > > > [EXTERNAL EMAIL] > > OK, thanks for the complete log. > > For whatev

Re: Virtual device

OK, thanks for the complete log. For whatever reason the first path was given a UID without the z/VM specific part. If you call lsdasd -u it should state also only EMC.09000ATVHC.3000.0f for this disk. You may want to try to set the device offline and online again in Linux and see if this

Re: Virtual device

Am 21.10.20 um 23:25 schrieb Mark Post: > On 10/20/20 11:02 PM, Phil Tully wrote: >> This is SLES12 Sp4 > Hmm. I checked, and the message is the same for that version of the > kernel. If you're sure that is the complete message, and not being > truncated, and the system is running the most recent

Re: sles15sp2 ipl exception

- 1 root root 7092916 Jun  6 21:33 vmlinux-5.3.18-22-default.gz > > Migration was done from local sles15sp2 rmt repositories, which were > newly refreshed (in last Saturday IIRC). > > Regards, > Juha > > On 27.7.2020 17.56, Stefan Haberland wrote: >> Hi Juha, >> >>

Re: sles15sp2 ipl exception

Hi Juha, there have been some fixes in the IPL code recently that will be available for SLES15.2 with one of the next updates. But I can not say definitely that one of them is causing your issue. Are there any additional messages on the screen? How did you IPL the system? Could you please try

Re: Ubuntu 18-04 unable to add DASD

On 11.11.19 09:36, Christian Ehrhardt wrote: > On Fri, Nov 8, 2019 at 5:18 PM van Sleeuwen, Berry > wrote: >> Hi Stefan, >> >> Thanks for this information. So an update looks like the first step. >> >> After initial installation I updated with the most current ports-mirror. The >> current

Re: Ubuntu 18-04 unable to add DASD

On 07.11.19 15:55, van Sleeuwen, Berry wrote: > Hi All, > > I have installed an Ubuntu 19-04 but as it turns out the application requires > version 18-04. So I have installed a new 18-04 system. > > Next I tried to move the LVM from the 19-04 machine into the 18-04 machine. > But I can’t get the

Re: Expanding root VG issue

Hi, yes, by-path or by-uuid is more reliable than the /dev/dasdX name. The /dev/dasdX name depends on the order that the disks are set online in the system. Depending on the distribution this can not reliably be predicted. Regards, Stefan On 12.12.18 17:39, Neal Scheffler wrote: > The Linux

Re: Linux native on Z

On 06.07.2018 16:00, Dick Anderson wrote: Thanks Dave. I knew that they used to, but never could find any docs about doing it today! Hi Dick, there is a lot of documentation on the developerworks website: https://www.ibm.com/developerworks/linux/linux390/index.html The "Device Drivers,

Re: Getting verbose output during boot

On 16.05.2018 17:02, Neale Ferguson wrote: I have built a new image to boot our 7.5.1804 system and it is behaving strangely. After booting it goes through the normal startup but then no messages appears for about 6 minutes. No I/O but lots of syscalls (#CP TR SVC) but no console messages. I

Re: Expanding a zLinux non-LVM disk

On 25.04.2018 05:48, Donald Russell wrote: I have a RHEL 7 zLinux on a single Mod-9 ECKD DASD. there are three partitions: 1 - /boot 2 - swap 3 - / From one Linux system I tried attaching a not-in-use zLinux Mod-9 and a Mod-27 and using fdasd and dd to copy the partitions. That didn’t work,

Re: Remove DASD device

On 30.05.2017 20:53, Mauro Souza wrote: Try vmcp detach 1234 (if your dasd is 1234). It "physically" detaches the device from the guest, so vgscan should lose track of it. But please, before detaching the device from z/VM set the device offline in Linux using chccwdev -d or whatever tool

Re: DASD driver errors - sles 12 sp2 current maintenance

Doing a cat on the host_access_count file gets the same/similar error when running in an LPAR. So, I don't think this is necessarily z/VM related. [1715374.556774] dasd-eckd.b3193d: 0.0.25e8: An error occurred in the DASD device driver, reason=09 [1715374.556791] dasd(eckd): I/O status report

Re: DASD driver errors - sles 12 sp2 current maintenance

I would open a ticket so that that Linux doesn't issue it when using a non-fp minidisk (which it can easily find out). Error messages should never be treated as "oh, just ignore it." If you do that, then you ignore the real error messages. You are right and all I was saying was that the

Re: DASD driver errors - sles 12 sp2 current maintenance

On 02.05.2017 12:34, Stefan Haberland wrote: Hi Marcy, May 01 18:12:35 cdzea02a9919 kernel: dasd-eckd.b3193d: 0.0.8006: An error occurred in the DASD device driver, reason=09 May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): I/O status report for device 0.0.8006

Re: DASD driver errors - sles 12 sp2 current maintenance

Hi Marcy, May 01 18:12:35 cdzea02a9919 kernel: dasd-eckd.b3193d: 0.0.8006: An error occurred in the DASD device driver, reason=09 May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): I/O status report for device 0.0.8006: dasd(eckd): in req: 7d437ed8

Re: Anomaly of EDEV mdisk attachment in SLES12

On 12.04.2017 20:54, juha.vu...@pp2.inet.fi wrote: Trying to add fba mdisk from EDEVICE to sles12.2 guest, and dasd_fba driver does not create the full partition node, /dev/dasdh1, for it for some reason: zlnx030:~ # vmcp link '*' 305 a305 mr zlnx030:~ # chccwdev -e a305 Setting device

Re: Ubuntu under z/VM Installation / IPL problem

Am 16.06.2016 um 13:05 schrieb Terry Madge: Hi Stefan, Any feedback you can give would be great. Thanks Terry Hi Terry, after some debugging I found a bug in the FBA loader that seems to occur randomly. But in fact it depends on the size of the the kernel image and/or some offsets within

Re: Ubuntu under z/VM Installation / IPL problem

Am 15.06.2016 um 19:59 schrieb Alan Altmark: On Wednesday, 06/15/2016 at 03:11 GMT, Terry Madge wrote: -> 2590 SSCHB2339000FF20 CC 0 SCH

Re: Redhat DASD Error

Am 16.11.2015 um 16:06 schrieb Michael Weiner: Hello all, In bringing up a Redhat guest I am coming across this error: dasd_eckd_mod: Unknown symbol dasd_generic_path_event (err -2) dasd_eckd_mod: Unknown symbol dasd_device_is_ro (err -2) dasd_eckd_mod: Unknown symbol

Re: DASD error

Hi, the sense data implies that the track format of the request is invalid. As you said your storage server did not go down cleanly: this error can be caused by an error in the storage server where it replaced a defective track with a new one. Please see your storage server logs. Maybe there is

Re: DASD format from Linux only

Hi Tomas, I have a possible solution for you from within Linux. You can set the device online with raw_track_access enabled. $ echo 1 /sys/bus/ccw/devices/0.0./raw_track_access $ chccwdev -e Please ignore the few Buffer I/O errors in syslog. Afterwards you can format the device

Re: CCW CMD REJECT on 'READ SUBSYSTEM DATA' query on z/114 with old DASD

/type of data that is to be returned. The controller (emulated 3390-3) does not support the suborder 0x0e. So the Read SubSystem Data command is being rejected. On Tue, Jun 26, 2012 at 9:52 AM, Stefan Haberland s...@linux.vnet.ibm.comwrote: Hi, this looks like a BUG in handling of older DASD

Re: CCW CMD REJECT on 'READ SUBSYSTEM DATA' query on z/114 with old DASD

Hi, this looks like a BUG in handling of older DASD devices. The query can not be easily disabled but I will have a look if we can fix this for future releases. At first sight this should only happen after a state change interrupt and then unfortunately in a loop... Stefan Am 25.06.2012

Re: PSW 000A0000 00000100

Am 29.06.2010 16:08, schrieb Alan Altmark: On Tuesday, 06/29/2010 at 09:54 EDT, Bernie Wubernard...@ncci.com wrote: Hi Carl, It looks like you have 2 disks, one for SP1 and one for SP1_2. When I go in and attempt to IPL, it works... How do you IPL ? Like IPL 100 . Are you pointing to the