Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Geometry unrecognized error 36

    Installation and Upgrades
    1
    2
    1659
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      gregober last edited by

      Hello,

      I am trying to install a toshiba HD on an appliance, the Toshiba is a MK2565GSX of 250GB described here: http://www3.toshiba.co.jp/storage/english/spec/hdd25/65.htm#spec02

      I am not a 100% sure about the disk geometry… as It is not quite clear.

      What is sure is that disk has 488 397 168 sectors…

      Normally It should have 484 521 cylinder 16 heads and 63 sectors, but I am not certain this setting is ok… 
      If I have a look at the BIOS setting after install, It tells me that disk has 65535 cylinder, 16 head, 255 sector which is not quite the same as the above…

      If I use a "simple install" I generally end up with an error on my HD after boot, once he tries to mount the disk… 
      Kernel is loaded ok, up until he reaches the disk da0 then there is an error:

      ad1: FAILURE - READ_DMA48 status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=18446744073709551553
      SMP: AP CPU #1 Launched!
      Trying to mount root from ufs:/dev/ad1s1a
      Trying to mount root from ufs:/dev/ad1s1a
      Trying to mount root from ufs:/dev/ad1s1a
      Trying to mount root from ufs:/dev/ad1s1a
      Trying to mount root from ufs:/dev/ad1s1a
      Trying to mount root from ufs:/dev/ad1s1a
      […]

      Then I do not have access to the device using manual system mounting…

      What would be your advise? 
      Any idea what is precisely going wrong?

      Thank you very much.

      G.B.</nid_not_found></ready,dsc,error>

      1 Reply Last reply Reply Quote 0
      • G
        gregober last edited by

        This has turned out to be a problem of BIOS settings.

        The LBA option had to be activated in the BIOS options.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post