On Tue, Mar 10, 2020 at 1:18 AM John Donnelly <john.p.donnelly@xxxxxxxxxx> wrote: > > > > > On Mar 9, 2020, at 1:51 PM, Bhupesh Sharma <bhsharma@xxxxxxxxxx> wrote: > > > > Hi John, > > > > On Mon, Mar 9, 2020 at 10:38 PM John Donnelly > > <john.p.donnelly@xxxxxxxxxx> wrote: > >> > >> Hi kexec/kdump team. > >> > >> I am not sure if this is the appropriate dlist to ask . If not , I apologize . > >> > >> > >> I am having difficulties mounting a iSCSI target under kdump . > > > > We have had several known issues with iSCSI targets under kdump which > > have been fixed, so just wanted to check which kexec-tools version you > > are using: upstream or fedora? > > > > Can you please share the output of: > > $ kexec -v > > # kexec -v > kexec-tools 2.0.15 > /usr/sbin/kexec > # rpm -qf `which kexec ` > kexec-tools-2.0.15-33.0.9.el7.x86_64 Ok, so it seems to me that you are using a RHEL-7 kexec-tools version for x86_64. I am not sure if this list is an appropriate forum for the same. I would suggest that you can look at a newer RHEL-7 kexec-tools version to try (which have several kexec-tools iSCSI issues fixed), or search the RH Bugzilla for iSCSI related issues and fixes (for example: <https://bugzilla.redhat.com/show_bug.cgi?id=1566331>). If you suspect that this could be a new/regression issue, I would suggest that you open a new BZ against the RHEL-7 kexec-tools component, so that someone from RH can help you with it. > >> The target is discovered , > >> > >> [ 154.118729] sd 2:0:0:0: [sda] Attached SCSI disk > >> [ OK ] Found device ZFS_Storage_7350 4. > >> Starting File System Check on /dev/...a-5ef4-4838-b5e7-dff852dfc673... > >> [ OK ] Started File System Check on /dev/d...46a-5ef4-4838-b5e7-dff852dfc673. > >> [ 275.766578] dracut-initqueue[420]: Warning: dracut-initqueue timeout - startinging > >> > >> > >> The fsck step never finishes, and dracut timeout eventually drops into the rescue shell. > >> > >> > >> I can see it is attempting to fsck root from the UUID : > >> > >> > >> # blkid | grep b5 > >> /dev/sda4: UUID="fb01846a-5ef4-4838-b5e7-dff852dfc673" TYPE="xfs" PARTUUID="f8831f2d-b2c6-4b27-97db-0513e4d3fe42" > >> 3:02 > >> " /dev/sda4 30G 3.5G 27G 12% / > >> > >> > >> And I mount root manually and look around. > >> > >> # kdump:/# mkdir /mnt > >> # kdump:/# mount /dev/sda4 /mnt > >> [ 542.856035] SGI XFS with ACLs, security attributes, realtime, scrub, repair, no debug enabled > >> [ 542.885016] XFS (sda4): Mounting V4 Filesystem > >> [ 542.938507] XFS (sda4): Starting recovery (logdev: internal) > >> [ 542.994720] XFS (sda4): Ending recovery (logdev: internal) > >> [ 543.018918] xfs filesystem being mounted at /mnt supports timestamps until 2038 (0x7fffffff) > >> kdump:/# > >> kdump:/# > >> kdump:/# chroot /mnt/ /usr/bin/bash > >> bash-4.2# > >> > >> Now my iSCSI target is mounted as /mnt > >> > >> > >> Is there a way start dracut so it stops BEFORE the fsck step ? Not after it fails ? > > > > I think you can try using 'rd.break' dracut option: > > > > rd.break={cmdline|pre-udev|pre-trigger|initqueue|pre-mount|mount|pre-pivot|cleanup} > > drop to a shell on defined breakpoint > > > > Thanks for the hint ! I will try these. Ok. Regards, Bhupesh _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
