Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 905745

Summary: dracut drop to the shell on my node
Product: Red Hat Enterprise Linux 7 Reporter: Xiaowei Li <xiaoli>
Component: anacondaAssignee: Will Woods <wwoods>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: low    
Version: 7.0CC: dracut-maint-list, harald, qcai
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-18 08:55:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
console.log none

Description Xiaowei Li 2013-01-30 04:37:33 UTC
Description of problem:

We have a LSI RDAC SAS storage and a server to boot from it. There is a limitation for the array. A target can only be accessed by a single
initiator at a time. So always half paths can not be accessed by the server.

When tried to install RHEL 7.0 to the LSI Lun, the dracut drop to the shell after finding some paths are not readable. But for RHEL 6.4 the dracut handled this well and the OS can be installed successfully.


Version-Release number of selected component (if applicable):
RHEL-7.0-20130120.0 Server x86_64
dracut-024-18.git20130102.el7.x86_64.rpm     
device-mapper-multipath-0.4.9-42.el7.x86_64.rpm    

How reproducible:
100%


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
[   13.617113] scsi 5:0:0:0: Direct-Access     LSI      INF-01-00        0784 PQ: 0 ANSI: 5 
[   13.626036] scsi 5:0:0:0: rdac: LUN 0 (RDAC) (unowned) 
[   13.635234] sd 5:0:0:0: [sdb] 419430400 512-byte logical blocks: (214 GB/200 GiB) 
[   13.642925] scsi 5:0:1:0: Direct-Access     LSI      INF-01-00        0784 PQ: 0 ANSI: 5 
[   13.651210] bnx2 0000:0b:00.0 em1: NIC Copper Link is Up, 1000 Mbps full duplex 
[   13.658502]  
[   13.660089] IPv6: ADDRCONF(NETDEV_CHANGE): em1: link becomes ready 
[   13.666618] sd 5:0:0:0: [sdb] Write Protect is off 
[   13.666740] scsi 5:0:1:0: rdac: LUN 0 (RDAC) (owned) 
[   13.670108] sd 5:0:1:0: [sdc] 419430400 512-byte logical blocks: (214 GB/200 GiB) 
[   13.670800] sd 5:0:1:0: [sdc] Write Protect is off 
[   13.671044] sd 5:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA 
[   13.672810]  sdc: sdc1 
[   13.674215] sd 5:0:1:0: [sdc] Attached SCSI disk 
[   13.704374] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA 
[   13.717649] Dev sdb: unable to read RDB block 0 
[   13.722188]  sdb: unable to read partition table 
[   13.728167] sd 5:0:0:0: [sdb] Attached SCSI disk 
[   15.553782] lpfc 0000:15:00.1: 1:1303 Link Up Event x1 received Data: x1 x1 x10 x0 x0 x0 0 
[-- MARK -- Tue Jan 29 22:20:00 2013] 
[   15.988887] scsi 6:0:0:0: Direct-Access     LSI      INF-01-00        0784 PQ: 0 ANSI: 5 
[   15.997693] scsi 6:0:0:0: rdac: LUN 0 (RDAC) (unowned) 
[   16.006760] sd 6:0:0:0: [sdd] 419430400 512-byte logical blocks: (214 GB/200 GiB) 
[   16.014496] scsi 6:0:1:0: Direct-Access     LSI      INF-01-00        0784 PQ: 0 ANSI: 5 
[   16.015180] sd 6:0:0:0: [sdd] Write Protect is off 
[   16.015513] sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA 
[   16.017715] Dev sdd: unable to read RDB block 0 
[   16.017725]  sdd: unable to read partition table 
[   16.019134] sd 6:0:0:0: [sdd] Attached SCSI disk 
[   16.050277] scsi 6:0:1:0: rdac: LUN 0 (RDAC) (owned) 
[   16.058695] sd 6:0:1:0: [sde] 419430400 512-byte logical blocks: (214 GB/200 GiB) 
[   16.066796] sd 6:0:1:0: [sde] Write Protect is off 
[   16.071944] sd 6:0:1:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA 
[   16.082526]  sde: sde1 
[   16.086365] sd 6:0:1:0: [sde] Attached SCSI disk 
[   43.228249]  rport-5:0-2: blocked FC remote port time out: removing rport 
[   45.656522]  rport-6:0-3: blocked FC remote port time out: removing rport 
dracut-initqueue[378]: Warning: Could not boot.

Comment 1 Xiaowei Li 2013-01-30 04:39:01 UTC
We should fix this issue to support to boot from the LSI RADC storage array.
mark it as a beta blocker.

Comment 2 Harald Hoyer 2013-01-30 12:02:29 UTC
Please boot with "log_buf_len=10M loglevel=7 systemd.log_level=debug systemd.log_target=kmsg rd.debug" added to the kernel command line and show me the output!

Also give me more information about the disk layout or at least the disk configuration and the current kernel command line used.

Comment 3 Xiaowei Li 2013-01-31 08:28:48 UTC
attaching the console log.

Here is the disk layout:

sh-4.1# multipath 
create: mpatha (3600605b002884430184a41ef28a24517) undef IBM,ServeRAID M5014
size=680G features='0' hwhandler='0' wp=undef
`-+- policy='round-robin 0' prio=1 status=undef
  `- 0:2:0:0 sda 8:0  undef ready running
create: mpathb (360080e500017f6ce00000daf50d0841b) undef LSI,INF-01-00
size=200G features='2 pg_init_retries 50' hwhandler='1 rdac' wp=undef
|-+- policy='round-robin 0' prio=6 status=undef
| |- 5:0:0:0 sdb 8:16 undef ready running
| `- 6:0:0:0 sdd 8:48 undef ready running
`-+- policy='round-robin 0' prio=1 status=undef
  |- 5:0:1:0 sdc 8:32 undef ghost running
  `- 6:0:1:0 sde 8:64 undef ghost running

sh-4.1# lvm pvs
  PV                   VG             Fmt  Attr PSize   PFree
  /dev/mapper/mpathap2 vg_storageqe08 lvm2 a--  679.37g    0 
  /dev/mapper/mpathbp1 vg_storageqe08 lvm2 a--  200.00g    0

Comment 4 Xiaowei Li 2013-01-31 08:29:33 UTC
Created attachment 690791 [details]
console.log

Comment 5 Xiaowei Li 2013-02-04 01:59:48 UTC
kernel option :
console=ttyS0,115200 ksdevice=eth0 mpath serial vnc log_buf_len=10M loglevel=7 systemd.log_level=debug systemd.log_target=kmsg rd.debug

Comment 6 Harald Hoyer 2013-02-11 11:31:50 UTC
I am no anaconda expert, but I think you are missing some parameters, or set some parameters wrong.

Reassigning to anaconda.

Comment 7 Xiaowei Li 2013-03-18 08:55:22 UTC
(In reply to comment #6)
> I am no anaconda expert, but I think you are missing some parameters, or set
> some parameters wrong.
> 
> Reassigning to anaconda.

I have checked the installation without the storage array attached. still failed, so i guess if it's the beaker issue. I have asked the beaker team to check the PXE conf. so close this bug.