Loading...
Loading...
issue: 1: H355 PERC controller connects two Micron SSDs configured in non-RAID mode; the OS is installed on the disk in Slot 0. In the Linux environment, the ` lsscsi ` IDs appear as follows: Slot 0 -> SCSI ID 0 (sda), Slot 1 -> SCSI ID 1 (sdb). 2 slot0 disk report failed and phy bad/missing from backplane 3: After replaced the drive in Slot 0, the customer prepared to reinstall the OS on the new drive. It was discovered that the mapping had changed: the drive in Slot 0 was now SCSI ID 2 ( sdb ), and the drive in Slot 1 was SCSI ID 1 ( sda ). Since the customer's installation script requires a disk with SCSI ID 0, the system installation failed. Before replace Slot 0 disk (S0): pci-0000:67:00.0-scsi-0:0:0:0 -> ../../sda (Slot 0) pci-0000:67:00.0-scsi-0:0:1:0 -> ../../sdb (Slot 1) After replace Slot 0 disk (S0): pci-0000:67:00.0-scsi-0:0:1:0 -> ../../sda (Slot 1) pci-0000:67:00.0-scsi-0:0:2:0 -> ../../sdb (Slot 0) Problematic machine: ceeinfra@cee-discovery-image:~> ls -l /dev/disk/by-path/ lrwxrwxrwx 1 root root 9 Jan 23 07:41 pci-0000:67:00.0-scsi-0:0:1:0 -> ../../sda lrwxrwxrwx 1 root root 10 Jan 23 07:41 pci-0000:67:00.0-scsi-0:0:1:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 23 07:41 pci-0000:67:00.0-scsi-0:0:1:0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 9 Jan 23 07:41 pci-0000:67:00.0-scsi-0:0:2:0 -> ../../sdb ceeinfra@cee-discovery-image:~> Good machine: ceeinfra@compute-650-66:~> ls -l /dev/disk/by-path/ lrwxrwxrwx 1 root root 9 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:0:0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:0:0-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:0:0-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:1:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:1:0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Nov 18 01:26 pci-0000:67:00.0-scsi-0:0:1:0-part2 -> ../../sdb2
In non-RAID mode drive enumeration on the H355 controller is determined by discovery order i.e the first discovered Physical Disk is assigned Target ID 0, the next discovered is assigned Target ID 1, and so on. Drive Replacement Behavior: The Target ID 0 remained assigned to the disk already present in the system. Because the controller remembers this assignment and the next available ID is 2, the newly inserted drive is assigned Target ID 2. Workaround: If the platform does not have a middle or rear backplane connected to the controller, switching to directpdmapping mode on this H355 system will order the PD enumeration based on slot order. Documentation Update: Jira ticket has been created to update the user guide to clarify that H355 enumeration is determined by drive discovery order. Current available Reference: Dell PowerEdge RAID Controller 11 User’s Guide PERC H755, H750, H355, and H350 Controller Series
https://www.dell.com/support/manuals/en-in/perc-h755/perc_cli_rg/direct-physical-drive-mapping-commands?guid=guid-2e9c3c53-ab85-42db-ac87-50473339e246&lang=en-us Direct physical drive mapping commands Use Direct Physical Drive Mapping commands to view and configure how drive target IDs are assigned on a controller. Supported commands The PERC Command Line Tool supports the following Direct Physical Drive Mapping commands: perccli /cx show directpdmapping perccli /cx set directpdmapping=<on|off> perccli /cx show directpdmapping Displays whether Direct Physical Drive Mapping is enabled or disabled on the specified controller. Show Direct Physical Drive Mapping setting perccli /c0 show directpdmapping perccli /cx set directpdmapping=<on|off> Enables or disables Direct Physical Drive Mapping on the specified controller. The following options are supported: on - Assigns drive target IDs based on physical drive slot numbers. off - Assigns drive target IDs based on drive discovery order. This is the default setting. Note: When Direct Physical Drive Mapping is enabled, drive target IDs are assigned according to slot number instead of drive discovery order. Note: This setting applies only to controllers that do not already assign target IDs based on slot order, such as H35x controllers. Enabling or disabling this setting on these controllers causes drives to be re-enumerated based on drive discovery order. Note: A system reboot is required after changing this setting for the change to take effect. Caution: Do not enable Direct Physical Drive Mapping on systems with mid-bay or rear-bay backplanes. Because slot numbers can overlap between front and rear or mid-bay backplanes, enabling this feature can result in drive slot conflicts. Enable Direct Physical Drive Mapping perccli /c0 set directpdmapping=on
Click on a version to see all relevant bugs