Booting issue with 9.1-RELEASE and net4801

[Gary Aitken]

On 02/04/13 11:54, Alberto Mijares wrote:
> Hi list,
> 
> I'm finally playing with my net4801 and nanobsd. SanDisk CF is recognized.
> 
> At my first try I had to disable DMA in ATA because it hanged out. Now
> it hangs when trying to mount root filesystem and mountroot> prompt
> appears. However, if a stop in loader prompt and type ls, files and
> dirs are displayed on disk0s1a.
> 
> Any suggestion?
> 
> Verbose boot log next:
> 
> OK boot -v log

> ada0 at ata0 bus 0 scbus0 target 0 lun 0
> ada0: <SanDisk SDCFH-004G HDX 6.03> CFA-0 device
> ada0: Serial Number BOZ111711234413
> ada0: 16.700MB/s transfers (PIO4, PIO 512bytes)
> ada0: 3815MB (7813120 512 byte sectors: 16H 63S/T 7751C)
> ada0: Previously was known as ad0
> GEOM: new disk ada0
> GEOM_PART: partition 2 has end offset beyond last LBA: 7999487 > 7813119
> GEOM_PART: partition 3 has start offset beyond last LBA: 7999488 > 7813119
> GEOM_PART: partition 3 has end offset beyond last LBA: 8002511 > 7813119
> GEOM_PART: integrity check failed (ada0, MBR)
> uhub0: 3 ports with 3 removable, self powered
> Trying to mount root from ufs:/dev/ada0s1a [ro]...
> mountroot: waiting for device /dev/ada0s1a ...
> Mounting from ufs:/dev/ada0s1a failed with error 19.
> 
> Loader variables:
>   vfs.root.mountfrom=ufs:/dev/ada0s1a
>   vfs.root.mountfrom.options=ro
> 
> Manual root filesystem specification:
>   <fstype>:<device> [options]
>       Mount <device> using filesystem <fstype>
>       and with the specified (optional) option list.
> 
>     eg. ufs:/dev/da0s1a
>         zfs:tank
>         cd9660:/dev/acd0 ro
>           (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)
> 
>   ?               List valid disk boot devices
>   .               Yield 1 second (for background tasks)
>   <empty line>    Abort manual input
> 
> mountroot>

I believe I got this error when the root boot block is written properly,
but the first partition on the disk does not have the proper gpart boot code
in it.

Try listing the gpt partition scheme:

# gpart show -l ada1
=>       34  156301421  ada1  GPT  (74G)
         34       1024     1  gptboot  (512k)
       1058          6        - free -  (3.0k)
       1064    4194304     2  hdd-80G-root  (2.0G)
    4195368    4194304     3  hdd-80G-swap  (2.0G)
    8389672    4194304     4  hdd-80G-var  (2.0G)
   12583976    4194304     5  hdd-80G-tmp  (2.0G)
   16778280  139523168     6  hdd-80G-usr  (66G)
  156301448          7        - free -  (3.5k)

Notice in the above partition 1, labeled gptboot (a label I gave it)
That's the boot code, which can be written as follows:
  gpart bootcode -p /boot/gptboot -i 1 ada1
assuming the system you're running on has /boot/gptboot on it.

Gary