Hello in my Scenario the LUN values in Production are different and DR are different.
whatt are the places where the LUN ID needs to be modified ? I am thinking of modifying temporarily in production and copy over again to DR so that the linux in DR can see the LUN defined in DR storage box. On Wed, Aug 7, 2024 at 9:40 PM Peter <dbajava...@gmail.com> wrote: > hello Sam, > > Thank you so much > > Can I alter the zfcp value in Production and copy to DR. then boot up the > linux from DR and will it fix this issue. > > the WWPN for the Production and DR are different. so while IBM replication > the DR took the Production value. > > > > On Wed, Aug 7, 2024 at 9:35 PM Cohen, Sam < > 000004c773ec874a-dmarc-requ...@listserv.uark.edu> wrote: > >> If you are pointing to a SAN-based device and are using the SCSI drivers, >> check zfcp.config or udev to ensure your WWPN/LUN combinations are correct >> for the new disks (which will have different UUIDs). You may need to >> manually mount the devices. If they are mounting, since it looks like you >> are using lvm, run a pvscan, then an lvscan to verify they are readable. >> You may need to change the status on the lv to ensure that it is available. >> >> >> >> Thanks, >> >> >> >> Sam >> >> >> >> *From:* The IBM z/VM Operating System <ib...@listserv.uark.edu> *On >> Behalf Of *Peter >> *Sent:* Wednesday, August 7, 2024 10:01 >> *To:* ib...@listserv.uark.edu >> *Subject:* linux guest kernel crash >> >> >> >> Hello, >> >> >> >> I was trying to bring up the DRed Linux redhat but it failed with kernel >> crash as below. The linux guest is using the SCSI device. Not sure if the >> Copying from Production to DR was missing on something ? But i was getting >> emergency linux logon that means the copying was good but it is corrupted ? >> >> >> >> 00: LINEND # , LINEDEL OFF, CHARDEL OFF, ESCAPE " , TABCHAR OFF >> >> 00: LINESIZE 080, ATTN OFF, APL OFF, TEXT OFF, MODE VM, HILIGHT OFF >> >> 00: CONMODE 3215, BREAKIN IMMED , BRKKEY PA1 , SCRNSAVE OFF >> >> 00: AUTOCR OFF, MORE 001 000, HOLD OFF, TIMESTAMP OFF, SYS3270 OFF >> >> 00: CONS 0009 ON LDEV L0004 TERM STOP HOST TCPIP FROM 10.33.xx.xxx >> >> Ý 3.052732¨ systemdÝ1¨: Starting >> Slices. >> >> Ý Ý32m OK Ý0m¨ Listening on udev Kernel >> Socket. >> >> Ý 3.052756¨ systemdÝ1¨: Listening on udev Kernel >> Socket. >> >> Ý 3.052761¨ systemdÝ1¨: Starting udev Kernel >> Socket. >> >> Ý Ý32m OK Ý0m¨ Listening on Journal >> Socket. >> >> Ý 3.052816¨ systemdÝ1¨: Listening on Journal >> Socket. >> >> Ý 3.052822¨ systemdÝ1¨: Starting Journal Socket. >> >> >> Ý 3.053310¨ systemdÝ1¨: Starting Load Kernel >> Modules... >> >> Starting Load Kernel >> Modules... >> >> Ý 3.053672¨ systemdÝ1¨: Starting Create list of required static device >> nodes >> >> for the current >> kernel... >> >> Starting Create list of required st... nodes for the current >> kernel... >> >> Ý Ý32m OK Ý0m¨ Reached target >> Sockets. >> >> Ý 3.053849¨ systemdÝ1¨: Reached target >> Sockets. >> >> Ý 3.053855¨ systemdÝ1¨: Starting >> Sockets. >> >> Ý 3.054839¨ systemdÝ1¨: Starting Journal >> Service... >> >> Starting Journal >> Service... >> >> Ý 3.055271¨ systemdÝ1¨: Starting dracut cmdline >> hook... >> >> Starting dracut cmdline >> hook... >> >> Ý 3.055864¨ systemdÝ1¨: systemd-modules-load.service: main process >> exited, co >> >> de=exited, >> status=1/FAILURE >> >> Ý Ý1;31mFAILED Ý0m¨ Failed to start Load Kernel >> Modules. >> >> See 'systemctl status systemd-modules-load.service' for >> details. >> >> Ý 3.056016¨ systemdÝ1¨: Failed to start Load Kernel >> Modules. >> >> Ý 3.056022¨ systemdÝ1¨: Unit systemd-modules-load.service entered >> failed stat >> >> e. >> >> >> Ý 3.062691¨ systemdÝ1¨: systemd-modules-load.service >> failed. >> >> Ý Ý32m OK Ý0m¨ Started Create list of required sta...ce nodes for the >> current >> >> kernel. >> >> >> Ý 3.062833¨ systemdÝ1¨: Started Create list of required static device >> nodes f >> >> or the current >> kernel. >> >> Ý 3.063226¨ systemdÝ1¨: Starting Create Static Device Nodes in >> /dev... >> >> Starting Create Static Device Nodes in >> /dev... >> >> Ý 3.063597¨ systemdÝ1¨: Starting Apply Kernel >> Variables... >> >> Starting Apply Kernel >> Variables... >> >> Ý Ý32m OK Ý0m¨ Started Create Static Device Nodes in >> /dev. >> >> Ý 3.066919¨ systemdÝ1¨: Started Create Static Device Nodes in >> /dev. >> >> Ý Ý32m OK Ý0m¨ Started Journal >> Service. >> >> Ý 3.068635¨ systemdÝ1¨: Started Journal >> Service. >> >> Ý Ý32m OK Ý0m¨ Started Apply Kernel >> Variables. >> >> Ý Ý32m OK Ý0m¨ Started dracut cmdline >> hook. >> >> Starting dracut pre-udev >> hook... >> >> Ý 3.253084¨ device-mapper: uevent: version >> 1.0.3 >> >> Ý 3.253189¨ device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) >> initialised: dm- >> >> Ý 8.505441¨ XFS (dm-22): Mounting V5 >> Filesystem >> >> Ý 8.519646¨ XFS (dm-20): Starting recovery (logdev: >> internal) >> >> Ý 8.527263¨ XFS (dm-20): Ending recovery (logdev: >> internal) >> >> Ý Ý32m OK Ý0m¨ Mounted >> /u02. >> >> Ý 8.532497¨ XFS (dm-22): Starting recovery (logdev: >> internal) >> >> Ý 8.536582¨ XFS (dm-22): Ending recovery (logdev: >> internal) >> >> Ý Ý32m OK Ý0m¨ Mounted >> /u03. >> >> Ý 8.541658¨ XFS (dm-23): Mounting V5 >> Filesystem >> >> Ý 8.552250¨ XFS (dm-23): Starting recovery (logdev: >> internal) >> >> Ý 8.559279¨ XFS (dm-23): Ending recovery (logdev: >> internal) >> >> Ý Ý32m OK Ý0m¨ Mounted >> /ftp. >> >> Ý Ý32m OK Ý0m¨ Started Activation of DM RAID >> sets. >> >> Ý Ý32m OK Ý0m¨ Reached target Local Encrypted >> Volumes. >> >> Ý 8.605445¨ XFS (dm-21): Starting recovery (logdev: >> internal) >> >> Ý 8.610432¨ XFS (dm-21): Ending recovery (logdev: internal) >> >> >> Ý Ý32m OK Ý0m¨ Mounted >> /u01. >> >> Ý Ý32m OK Ý0m¨ Started Apply Kernel >> Variables. >> >> Ý Ý0m Ý31m* Ý0m¨ (1 of 2) A start job is running >> for...g3-u05_lv.device (6s >> >> / 1min 30s) ÝKÝ Ý1;31m* Ý0m Ý31m* Ý0m¨ (1 of 2) A start job is >> running for >> >> ...g3-u05_lv.device (7s / 1min 30s) ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ >> (1 of 2 >> >> ) A start job is running for...g3-u05_lv.device (7s / 1min 30s) ÝKÝ >> Ý31m* Ý1;3 >> >> 1m* Ý0m Ý31m* Ý0m¨ (2 of 2) A start job is running >> for...g3-u04_lv.device (8s >> >> * Ý0m Ý31m* Ý0m¨ (1 of 2) A start job is running for...3-u05_lv.device >> (25s / 1m >> >> in 30s) ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ (1 of 2) A start job is >> running for >> >> ...3-u05_lv.device (25s / 1min 30s) ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ >> (2 of 2 >> >> ) A start job is running for...3-u04_lv.device (26s / 1min 30s) ÝKÝ >> Ý31m* Ý1;31 >> >> m* Ý0m Ý31m* Ý0m¨ (2 of 2) A start job is running >> for...3-u04_lv.device (26s >> >> / 1min 30s) ÝKÝ Ý1;31m* Ý0m Ý31m* Ý0m¨ (2 of 2) A start job is >> running for. >> >> ..3-u04_lv.device (27s / 1min 30s) ÝKÝ Ý0m Ý31m* Ý0m¨ (1 of 2) A >> start job >> >> is running for...3-u05_lv.device (27s / 1min 30s) ÝKÝ Ý1;31m* Ý0m >> Ý31m* Ý0 >> >> m¨ (1 of 2) A start job is running for...3-u05_lv.device (28s / 1min >> 30s) ÝKÝ Ý >> >> 31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ (1 of 2) A start job is running for... >> 3-u05_lv.de >> >> vice (28s / 1min 30s) ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ (2 of 2) A >> start job >> >> is running for...3-u04_lv.device (29s / 1min 30s) ÝKÝ Ý31m* Ý1;31m* >> Ý0m Ý31m* >> >> Ý0m¨ (2 of 2) A start job is running for...3-u04_lv.device (29s / 1min >> 30s) Ý >> >> KÝ Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ (2 of 2) A start job is running >> for...3-u04_l >> >> v.device (30s / 1min 30s) ÝKÝ Ý31m* Ý1;31m* Ý0m¨ (1 of 2) A start >> job is ru >> >> nning for...3-u05_lv.device (30s / 1min 30s) ÝKÝ Ý31m* Ý0m¨ (1 of >> 2) A sta >> >> rt job is running for...3-u05_lv.device (31s / 1min 30s) ÝKÝ Ý31m* >> Ý1;31m* >> >> Ý0m¨ (1 of 2) A start job is running for...3-u05_lv.device (31s / 1min >> 30s) ÝKÝ >> >> Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ (2 of 2) A start job is running >> for...3-u04_lv. >> >> device (32s / 1min 30s) ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ (2 of 2) A >> start jo >> >> b is running for...3-u04_lv.device (32s / 1min 30s) ÝKÝ Ý31m* Ý1;31m* >> Ý0m Ý31m >> >> * Ý0m¨ (2 of 2) A start job is running for...3-u04_lv.device (33s / >> 1min 30s) >> >> >> ------------------------------ >> >> To unsubscribe from the IBMVM list, click the following link: >> http://listserv.uark.edu/scripts/wa-UARKEDU.exe?SUBED1=IBMVM&A=1 >> >> ------------------------------ >> >> To unsubscribe from the IBMVM list, click the following link: >> http://listserv.uark.edu/scripts/wa-UARKEDU.exe?SUBED1=IBMVM&A=1 >> > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
