The second disk failed completely on VICTORIA.
Used the procedure described in 05 Install OVMS 3.3.1 with the following changes:
Option
Disks
Boot
Value
/dev/sda
/dev/sda MBR
Because of the loss of the second disk drive, there is no unused disk partition on the first to use as I did in 06 Set Up OVS File System. I decided to mount /dev/sda4 as the /OVS filesystem instead.
As before, I used the blkid command as follows to get the UUID for /dev/sda4:
blkid
The output is:
/dev/sda1: UUID="91f3ebbe-4269-432a-bff0-b767eab8691a" TYPE="ext4" /dev/sda2: UUID="e705f867-4704-4e60-bf54-2d9d1c5a8138" TYPE="ext4" /dev/sda3: UUID="34e2fd88-fe58-4a07-a637-c65570ef2c22" TYPE="swap" /dev/sda4: UUID="a4e22e19-befa-445f-8066-785fbe069d4c" TYPE="ext4" /dev/mapper/OVM_SYS_REPO_PART_35000c50040068cd3: UUID="a4e22e19-befa-445f-8066-785fbe069d4c" TYPE="ext4"
I used the following commands to update /etc/fstab, and to mount /OVS:
cat >>/etc/fstab <<DONE UUID=a4e22e19-befa-445f-8066-785fbe069d4c /OVS ext4 defaults 1 2 DONE mount -a df -hl
The output of the df command confirms that the file-system was mounted successfully:
Filesystem Size Used Avail Use% Mounted on /dev/sda2 50G 1.2G 46G 3% / tmpfs 502M 0 502M 0% /dev/shm /dev/sda1 477M 47M 401M 11% /boot none 502M 40K 502M 1% /var/lib/xenstored /dev/mapper/OVM_SYS_REPO_PART_35000c50040068cd3 860G 72M 816G 1% /OVS
I created the standard OVS sub-directories as follows:
mkdir /OVS/running_pool /OVS/seed_pool /OVS/iso_pool
I set up the XEN Network as described by 07 Set Up XEN Network.