Opened 5 years ago

Closed 3 years ago

#4583 closed bug (fixed)

"PANIC did not find any boot partitions" message with SIS IDE controller

Reported by: peapa Owned by: marcusoverhagen
Priority: normal Milestone: R1
Component: Drivers/Disk Version: R1/alpha1
Keywords: Cc:
Blocked By: Blocking: #7665
Has a Patch: no Platform: x86

Description

When attempting to start Haiku Alpha 1 on my computer from a cdrom I got this error message just after the splash screen appeared. I already tried to disable DMA in the safe mode otions but it did not help.

My motherboard is an MS-6533 with a SIS 5513 IDE controller.

Attachments (2)

haiku_p4_Intel850_noboot.txt (50.7 KB) - added by andzs 5 years ago.
haiku-alpha-1-no-boot-partitions.jpg (22.9 KB) - added by sikosis 5 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 5 years ago by peapa

  • Summary changed from "PANIC did not find any boot partitions message" with SIS IDE controller to "PANIC did not find any boot partitions" message with SIS IDE controller

comment:2 Changed 5 years ago by andzs

The same problem on P4 system with Intel 850 chipset where original Beos boots fine. I'll add serial debugging output.

Changed 5 years ago by andzs

comment:3 Changed 5 years ago by sikosis

I have the same issue on a Dell Optiplex 960 and my MSI Wind U100. Strangely, I've been able to get the alpha to boot into the live mode prior and the same CD now won't.

Changed 5 years ago by sikosis

comment:4 follow-up: Changed 5 years ago by Disreali

Is this a duplicate of ticket #4058 ?

comment:5 in reply to: ↑ 4 Changed 5 years ago by andzs

Replying to Disreali:

Is this a duplicate of ticket #4058 ?

Could be. But #4058 emphasizes switching to new ATA stack in development versions, but this one is related to Alpha release.

comment:6 Changed 4 years ago by tonestone57

I noticed in syslog:
ata 0 error: command failed, error bit is set. status 0x51, error 0x04

Did a little searching on it. Usually one of 3 things 1) failing drive (sector not found) - should test with manufacturer diagnostics software (quick+full) 2) BIOS settings 3) buggy driver.

You can try playing with BIOS settings, enable SMART, disable DMA, setting UDMA mode 2 (rather than auto), checking over your primary and secondary drive info to match installed hardware, (looking over drive connections can't hurt either), etc.

A little extra information about this error on Linux:
http://www.captain.at/howto-linux-driveready-seekcomplete-error-drivestatuserror.php

comment:7 Changed 3 years ago by scottmc

Can you recheck this with a recent Haiku build? It may have been fixed recently.

comment:8 Changed 3 years ago by scottmc

  • Blocking 7665 added

comment:9 Changed 3 years ago by peapa

I just tried with Haiku hrev42190 and everything works perfectly

The cdrom loaded without problems, I installed Haiku and was able to start it.
I think this bug is fixed.

comment:10 Changed 3 years ago by anevilyak

  • Resolution set to fixed
  • Status changed from new to closed

Thanks for the update!

Note: See TracTickets for help on using tickets.