[haiku-bugs] Re: [Haiku] #6665: Haiku installer KDL when using a 20GB primary slave drive specifically

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Mon, 27 Sep 2010 19:22:28 -0000

#6665: Haiku installer KDL when using a 20GB primary slave drive specifically
  Reporter:  jstressman     |         Owner:  axeld         
      Type:  bug            |        Status:  new           
  Priority:  normal         |     Milestone:  R1            
 Component:  System/Kernel  |       Version:  R1/Development
Resolution:                 |      Keywords:                
Blocked By:                 |   Has a Patch:  0             
  Platform:  All            |      Blocking:                

Comment (by bonefish):

 Replying to [comment:4 jstressman]:
 > bonefish: Every test done except for the one with the drive named
 "Backup3.vdi" were done with unpartitioned, unformatted disk images as
 created by virtualbox for the slave drives.
 > For instance all 3 of the serial logs I just posted were done with
 completely blank slave drive images.

 I looked closer only at `serial-log-20GB-20GB-KDL.txt`, which shows
 identically sized BFS volumes on both hard disks.

 > Do you want me to try with 2 identically sized totally blank images?
 Both for the primary master and primary slave? And try booting from the
 installer CD then to see if the crash still occurs?
 > Ok, I've just tested with completely blank fresh 2GB disk images for
 primary master and slave and still get the KDL. I'm attaching the serial
 debug output.

 OK, thanks, that does at least rule out that the other BFS volumes caused
 confusion somehow.

 Replying to [comment:5 jstressman]:
 > This has been with both the images I've been building myself and with
 the nightlies from haiku-files.org. I just downloaded the anyboot nightly
 for r38811 and tested to confirm that it's not just my builds, but the
 official nightlies as well.

 I don't suspect a build problem. I was just wondering how one could get
 additional debug output to you. If you build your own images, then
 enabling tracing would be the easiest way. Unfortunately at the moment
 there is no useful tracing output at all in the concerned code, so someone
 would have to add that first. Assuming that this problem is reproducible
 elsewhere, that someone could problem just debug it locally, though.

Ticket URL: <http://dev.haiku-os.org/ticket/6665#comment:7>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: