Opened 9 months ago

Closed 3 months ago

#18792 closed bug (duplicate)

Installer fails to detect a hard drive on laptop

Reported by: Redysz Owned by: nobody
Priority: normal Milestone: R1/beta5
Component: Drivers/Disk/AHCI Version: R1/Development
Keywords: Cc:
Blocked By: #18536 Blocking:
Platform: All

Description (last modified by Redysz)

The installer for R1beta4 detects the hard drive in the laptop without any problem, and I can format it properly so as to install Haiku. The R1Development version (hrev57576-x86_64) does not see the same drive. It is impossible to install the system.

Laptop: Lenovo IdeaPAD 110 (trying to install on real machine). Laptop/Enivronment details in attachments.

My steps:

  1. Download haiku-r1beta4-x86_64-anyboot.iso
  2. Make USB-boot with Rufus 4.4 (no options can be modified so I used "standard" ones)
  3. Boot with this USB stick on Legacy bios mode
  4. Select install Haiku
  5. Hard drive visible

~Alternative reality:~

  1. Download haiku-master-hrev57576-x86_64-anyboot.iso
  2. Make USB-boot with Rufus 4.4 (no options can be modified so I used "standard" ones)
  3. Boot with this USB stick on Legacy bios mode
  4. Select install Haiku
  5. Hard drive is not visible

I've tried to format hard drive with gparted, make in "unallocated" and others - nothing works.

Attachments (8)

installator beta4.jpg (1.3 MB ) - added by Redysz 9 months ago.
Installator beta4
partitioning beta4.jpg (1.3 MB ) - added by Redysz 9 months ago.
Partitioning beta4
partitioning development.jpg (767.4 KB ) - added by Redysz 9 months ago.
Partitioning R1/development
installator development.jpg (1.2 MB ) - added by Redysz 9 months ago.
Installator R1/development
listdev.txt (2.3 KB ) - added by Redysz 9 months ago.
Result of listdev command (performed on Haiku R1beta4 - because there hard drive is visible)
listimage.txt (1.5 KB ) - added by Redysz 9 months ago.
Result of listimage | grep drivers command (performed on Haiku R1beta4 - because there hard drive is visible)
syslogR1b4.txt (82.9 KB ) - added by Redysz 9 months ago.
syslog file for R1-beta4
syslogR1development.txt (383.5 KB ) - added by Redysz 9 months ago.
syslog file for R1-development

Change History (23)

by Redysz, 9 months ago

Attachment: installator beta4.jpg added

Installator beta4

by Redysz, 9 months ago

Attachment: partitioning beta4.jpg added

Partitioning beta4

by Redysz, 9 months ago

Partitioning R1/development

by Redysz, 9 months ago

Attachment: installator development.jpg added

Installator R1/development

by Redysz, 9 months ago

Attachment: listdev.txt added

Result of listdev command (performed on Haiku R1beta4 - because there hard drive is visible)

by Redysz, 9 months ago

Attachment: listimage.txt added

Result of listimage | grep drivers command (performed on Haiku R1beta4 - because there hard drive is visible)

comment:1 by Redysz, 9 months ago

Description: modified (diff)

comment:2 by Redysz, 9 months ago

Description: modified (diff)

comment:3 by nephele, 9 months ago

Component: Applications/InstallerDrivers/Disk
Keywords: Hard drive Installer removed
Platform: x86-64All

Can you attach the system log (from /var/log/syslog) for both versions?

Last edited 9 months ago by nephele (previous) (diff)

by Redysz, 9 months ago

Attachment: syslogR1b4.txt added

syslog file for R1-beta4

by Redysz, 9 months ago

Attachment: syslogR1development.txt added

syslog file for R1-development

in reply to:  3 comment:4 by Redysz, 9 months ago

Replying to nephele:

Can you attach the system log (from /var/log/syslog) for both versions?

Added

comment:5 by pulkomandy, 9 months ago

Component: Drivers/DiskDrivers/Disk/AHCI

comment:6 by pulkomandy, 9 months ago

AHCI driver seems to be stuck in a loop of:

614	KERN: ahci: Enable: Starting port already running!
615	KERN: ahci: Disable: port 0 error DMA engine still running
616	KERN: ahci: PortReset: port 0 unable to shutdown!
617	KERN: ahci: ResetDevice: port 0 unable to hard reset device

so the device can't be enabled but also can't be disabled. Then it gives up after a few tries.

comment:7 by waddlesplash, 9 months ago

Keywords: boot-failure added
Milestone: R1/beta5Unscheduled
Priority: criticalnormal

comment:8 by waddlesplash, 9 months ago

Keywords: boot-failure removed

comment:9 by waddlesplash, 9 months ago

Please try booting with ACPI disabled and see what happens (it may just not boot at all, however.)

comment:10 by pulkomandy, 9 months ago

Milestone: UnscheduledR1/beta5

I think we should keep this in he beta5 milestone since it seems to be a regression (worked fine in beta4)

comment:11 by korli, 9 months ago

Looks like it's reading only 0xff values from PCI.

ahci: cap: Interface Speed Support: generation 15
ahci: cap: Number of Ports: 32 (raw 0x1f)

Does the device need a power up?

in reply to:  9 comment:12 by Redysz, 9 months ago

Replying to waddlesplash:

Please try booting with ACPI disabled and see what happens (it may just not boot at all, however.)

Then the hard drive is not visible in both (development and beta4) by the installer.

in reply to:  11 comment:13 by Redysz, 9 months ago

Replying to korli:

Looks like it's reading only 0xff values from PCI.

ahci: cap: Interface Speed Support: generation 15
ahci: cap: Number of Ports: 32 (raw 0x1f)

Does the device need a power up?

Is that question for me? Device is a standard hdd. Model: WD5000LPCX-24VHAT0

comment:14 by pulkomandy, 9 months ago

The pictures in #18536 show a similar error from the AHCI driver. From the complete syslog in that ticket and the rather narrow revision range in the other, we should be able to find a solution?

comment:15 by pulkomandy, 3 months ago

Blocked By: 18536 added
Resolution: duplicate
Status: newclosed

I looked more closely at the syslogs and I see that #18536 has the same SATA controller. So I'm going to close this as a duplicate of the earlier ticket, they are similar enough that this is very likely the same problem.

Let's continue the dscussion there.

Note: See TracTickets for help on using tickets.