Mouting root filesystem with error 19 in bhyve

Router distribution based on FreeBSD with FFRouting and Bird

Brought to you by: cochard

#14 Mouting root filesystem with error 19 in bhyve

Milestone: v1.54

Status: open

Owner: Olivier Cochard-Labbe

Labels: None

Priority: 1

Updated: 2015-02-26

Created: 2015-01-04

Creator: Anonymous

Private: No

Hi. Problem with BSDRP 1.54 (still no milestone v1.54 in sourceforge)

I've try to create BSDRP profile for cbsd ( https://github.com/olevole/cbsd/blob/master/etc/defaults/bhyve-freebsd-BSDRP-x64-1.54.conf ) but when i start bhyve-vm, system is unable to mount root with symptoms:

...
random: unblocking device.
Timecounter "TSC-low" frequency 1754922245 Hz quality 1000
Trying to mount root from ufs:/dev/ufs/BSDRPs1a [ro]...
mountroot: waiting for device /dev/ufs/BSDRPs1a ...
Mounting from ufs:/dev/ufs/BSDRPs1a failed with error 19.

Loader variables:
  vfs.root.mountfrom=ufs:/dev/ufs/BSDRPs1a
  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> ?

List of GEOM managed disk devices:
  diskid/DISK-BHYVE-FE84-1567-A63 vtbd0

mountroot>

Also i've try to load directly from vtbd (virtio-blk):

mountroot> ufs:/dev/vtbd0s1 ro
Trying to mount root from ufs:/dev/vtbd0s1 [ro]...
mountroot: waiting for device /dev/vtbd0s1 ...
Mounting from ufs:/dev/vtbd0s1 failed with error 19.

When i change storage driver from virtio-blk to ahci-hd, the situation does not change

mountroot> ufs:/dev/ada0s1a
Trying to mount root from ufs:/dev/ada0s1a []...
mountroot: waiting for device /dev/ada0s1a ...
Mounting from ufs:/dev/ada0s1a failed with error 19.

Looks like image is ok:

% mdconfig -a -t vnode -f BSDRP-1.54-full-amd64-serial.img

% file -s /dev/md0*
/dev/md0:    DOS/MBR boot sector; partition 1 : ID=0xa5, active, start-CHS    (0x0,1,1), end-CHS (0x1c,254,63), startsector 63, 465822 sectors; partition 2 : ID=0xa5, start-CHS (0x1d,1,1), end-CHS (0x39,254,63), startsector 465948, 465822 sectors; partition 3 : ID=0xa5, start-CHS (0x3a,0,1), end-CHS (0x3b,254,63), startsector 931770, 32130 sectors; partition 4 : ID=0xa5, start-CHS (0x3c,0,1), end-CHS (0x3d,254,63), startsector 963900, 32130 sectors
/dev/md0s1:  DOS/MBR boot sector, BSD disklabel
/dev/md0s1a: Unix Fast File system [v1] (little-endian), last mounted on /mnt, last written at Sun Jan  4 17:28:35 2015, clean flag 0, number of blocks 465806, number of data blocks 457997, number of cylinder groups 18, block size 4096, fragment size 512, minimum percentage of free blocks 0, rotational delay 0ms, disk rotational speed 60rps, SPACE optimization
/dev/md0s2:  data
/dev/md0s3:  Unix Fast File system [v1] (little-endian), last mounted on /usr/obj/BSDRP.amd64/_.mnt, last written at Fri Jan  2 11:12:13 2015, clean flag 1, number of blocks 32130, number of data blocks 31489, number of cylinder groups 4, block size 4096, fragment size 512, minimum percentage of free blocks 0, rotational delay 0ms, disk rotational speed 60rps, SPACE optimization
/dev/md0s4:  Unix Fast File system [v1] (little-endian), last mounted on /usr/obj/BSDRP.amd64/_.mnt, last written at Fri Jan  2 11:12:13 2015, clean flag 1, number of blocks 32130, number of data blocks 31489, number of cylinder groups 4, block size 4096, fragment size 512, minimum percentage of free blocks 0, rotational delay 0ms, disk rotational speed 60rps, SPACE optimization

Also, looks like all labels is present:

% geom list
Geom name: md0s3
Providers:

1. Name: ufsid/54a652dcf9e425a4
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 477066240
   Mode: r0w0e0
   secoffset: 0
   offset: 0
   seclength: 32130
   length: 16450560
   index: 0
Consumers:
1. Name: md0s3
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 477066240
   Mode: r0w0e0

Geom name: md0s3
Providers:

1. Name: ufs/BSDRPs3
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 477066240
   Mode: r0w0e0
   secoffset: 0
   offset: 0
   seclength: 32130
   length: 16450560
   index: 0
Consumers:
1. Name: md0s3
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 477066240
   Mode: r0w0e0

Geom name: md0s4
Providers:

1. Name: ufsid/54a652ddbffbc94a
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 493516800
   Mode: r0w0e0
   secoffset: 0
   offset: 0
   seclength: 32130
   length: 16450560
   index: 0
Consumers:
1. Name: md0s4
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 493516800
   Mode: r0w0e0

Geom name: md0s4
Providers:

1. Name: ufs/BSDRPs4
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 493516800
   Mode: r0w0e0
   secoffset: 0
   offset: 0
   seclength: 32130
   length: 16450560
   index: 0
Consumers:
1. Name: md0s4
   Mediasize: 16450560 (16M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 493516800
   Mode: r0w0e0

I have not tried to load vga image because bhive not support graphics.
Do you have any idea what could be the reason for such behavior? Thanks

Discussion

Olivier Cochard-Labbe - 2015-01-04

Hi,

(thanks for the milestone reminder!)

I'm using bhyvhttps://sourceforge.net/p/bsdrp/bugs/14/#e for testing BSDRP: The VGA AND serial release works great with bhyve (VGA release has the serial port enabled by default).
For example, with my bhyve-lab-script (available on the BSDRP sources) I can start it without problem:

# BSDRP/tools/BSDRP-lab-bhyve.sh -i /usr/obj/BSDRP.amd64/BSDRP-1.54-full-amd64-serial.img.xz BSD Router Project (http://bsdrp.net) - bhyve full-meshed lab script Setting-up a virtual lab with 1 VM(s): - Working directory: /tmp/BSDRP - Each VM have 1 core(s) and 256M RAM - 1 LAN(s) between all VM - Full mesh Ethernet links between each VM VM 1 have the following NIC: - vtnet0 connected to LAN number 1 For connecting to VM'serial console, you can use: - VM 1 : cu -l /dev/nmdm1B # cu -l /dev/nmdm1B Connected FreeBSD/amd64 (router.bsdrp.net) (ttyu0) login: root

Last edit: Olivier Cochard-Labbe 2015-01-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Anonymous
  
  Add attachments
  Cancel
  You seem to have CSS turned off. Please don't fill out this field.
  
  You seem to have CSS turned off. Please don't fill out this field.

Olivier Cochard-Labbe - 2015-01-04

Group: v1.53 --> v1.54
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Anonymous
  
  Add attachments
  Cancel
  You seem to have CSS turned off. Please don't fill out this field.
  
  You seem to have CSS turned off. Please don't fill out this field.

Anonymous

Mouting root filesystem with error 19 in bhyve

Router distribution based on FreeBSD with FFRouting and Bird

Group

Searches

Help

#14 Mouting root filesystem with error 19 in bhyve

I've try to create BSDRP profile for cbsd ( https://github.com/olevole/cbsd/blob/master/etc/defaults/bhyve-freebsd-BSDRP-x64-1.54.conf ) but when i start bhyve-vm, system is unable to mount root with symptoms:

Discussion