Changes between Initial Version and Version 1 of Ticket #12648, comment 4

Timestamp:: Jan 28, 2014 8:53:38 PM (11 years ago)
Author:: wonko1953

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #12648, comment 4

-              initial
+              v1
 Some notes on the disk setup:
+{{{
+/dev/ada4s12     on the host is mapped via disk35s12.vmdk     to ada0      attached as IDE primary master in the VB client.
+/dev/ada{0..5}p4 on the host is mapped via disk3{1..6}p4.vmdk to ada{1..6} attached as SATA ports {0..5} in the VB client.
+}}}
+||= host disk partition =||= VMDK mapping file =||= client attachment =||= client disk =||= size =||
+|| /dev/ada4s12          || disk35s12.vmdk      || IDE primary master  || ada0          || 20 GB  ||
+|| /dev/ada0p4           || disk31p4.vmdk       || SATA port 0         || ada1          || 896 GB ||
+|| /dev/ada1p4           || disk32p4.vmdk       || SATA port 1         || ada2          || 896 GB ||
+|| /dev/ada2p4           || disk33p4.vmdk       || SATA port 2         || ada3          || 896 GB ||
+|| /dev/ada3p4           || disk34p4.vmdk       || SATA port 3         || ada4          || 896 GB ||
+|| /dev/ada4p4           || disk35p4.vmdk       || SATA port 4         || ada5          || 896 GB ||
+|| /dev/ada5p4           || disk36p4.vmdk       || SATA port 5         || ada6          || 896 GB ||
 Therefore, it is interesting to note that the failure messages in VBox.log.1 (remember, this is from the run where there were no problems) reference one host disk twice (ada4p4 == disk35p4.vmdk, FreeBSD in the VB client sees that as ada5). Conversely, the host's ada4s12 (which is seen by the client as ada0 on IDE 0:0) does not exhibit the failure message.