Hi Richard, +Heinrich as I think this is an EFI bug.
On Thu, 2 Nov 2023 at 19:37, Hongxing Zhu <hongxing....@nxp.com> wrote: > > Hi Simon: > I found that the EFI complained that the disk install path is not updated for > the second disk. > The install path is “EFI: installed device path > '/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/Scsi(0,0)'” > > when first disk is added. > > But the path is same when the second or later disks are added, and EFI repors > that the path had been installed already. > EFI: Path /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/Scsi(0,0) already > installed > > > > That’s why the below error when run efi_disk_create_raw() function. > > Adding disk for ahci_scsi.id0lun0 failed > (err=-9223372036854775788/0x8000000000000014) > > > > Do you have any clues about this? > > Thanks in advanced. > > Best Regards > > Richard Zhu > > > > From: Hongxing Zhu > Sent: 2023年11月1日 10:57 > To: s...@chromium.org > Cc: u-boot@lists.denx.de > Subject: uboot reports adding disk failed(EFI_NOT_FOUND) and first disk is > gone in next scsi scan > > > > Hi Simon: > Nice to meet you. > The u-boot I used is based on v2023.04 tagged version. > Layerscape LX2160A RDB board has four SATA controllers. > Based on LX2160A RDB board and two or more SATA disks connected. > I encounter one “scsi scan” problem. > > > After the first SATA disk is detected and probed properly in the first “scsi > scan”. > The other disks would complain that “EFI_NOT_FOUND” error listed below, > when run the first “scsi scan” command in uboot environment. > > Does this error matter? > BTW, “scsi info” says that all disk info can be dumped, and all disks are > works well, > > after the first “scsi scan” > > In the consecutive rescan operations issued by “scsi reset” or “scsi scan” > commends, > the disks would report “unable to unbind devices (-1E)” error. > The first disk is disappeared at all after the next “scsi scan” operations is > finished. > > > Did you used to encounter such kind of issue? > > Any suggestions and guidance are very appreciated. > > Logs: > => scsi scan > > scanning bus for devices... > > Target spinup took 0 ms. > > AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode > > flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst > > Device 0: (0:0) Vendor: ATA Prod.: ST1000DM010-2EP1 Rev: CC43 > > Type: Hard Disk > > Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) > > Target spinup took 0 ms. > > AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode > > flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst > > Adding disk for ahci_scsi.id0lun0 failed > (err=-9223372036854775788/0x8000000000000014) > > SATA link 0 timeout. > > AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode > > flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst > > SATA link 0 timeout. > > AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode > > flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst > => scsi info > > Device 0: (0:0) Vendor: ATA Prod.: ST1000DM010-2EP1 Rev: CC43 > > Type: Hard Disk > > Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) > > Device 1: (0:0) Vendor: ATA Prod.: ST500DM002-1BD14 Rev: KC45 > > Type: Hard Disk > > Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) > > => ls scsi 0:1 > > <DIR> 4096 . > > <DIR> 4096 .. > > <DIR> 16384 lost+found > > <snip> > > <DIR> 4096 var > > <SYM> 12 linuxrc > > => ls scsi 1:1 > > <DIR> 4096 . > > <DIR> 4096 .. > > <DIR> 16384 lost+found > > <snip> > > <DIR> 4096 usr > > <DIR> 4096 var > > > > => scsi reset > > > > Reset SCSI > > scanning bus for devices... > > unable to unbind devices (-1E) > => ls scsi 0:1 > > ** Bad device specification scsi 0 ** > > Couldn't find partition scsi 0:1 > > => ls scsi 1:1 > > <DIR> 4096 . > > <DIR> 4096 .. > > <DIR> 16384 lost+found > > <snip> > > <DIR> 4096 var > > > => scsi info > > Device 1: (0:0) Vendor: ATA Prod.: ST500DM002-1BD14 Rev: KC45 > > Type: Hard Disk > > Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) > > > > Best Regards > > Richard Zhu > > Regards, Simon
