Upgrading an Affinity using a USB stick
- A USB stick prepared with the
- Cable CAS-DCM-1038 (six-way bayonet to USB type A socket).
- Command line access to the DAS (either via GPIO console cable or ssh).
- Do not connect the USB cable or stick at this time.
- Log in to the DAS as root.
- Issue the following commands, which will switch off automatic disk access. Ignore any errors or messages:
svc Pt-storage stop svc rdisk stop
- Allow a few seconds for the power lines to settle.
- Issue the following commands, to turn on power to the USB stick. Ignore any errors or messages:
ioline -L usb_otg -o 1
- Connect the USB cable and the USB stick.
- Mount the USB stick with the command:
mount -o ro -t ext2 /dev/sda1 /mnt
This should not produce any output, signifying that it has worked. If you do see any error message, try the following:
- Wait ten seconds
- Try repeating the command with
- Check the kernel log to see what the device was called by issuing the following command:
In the last few lines of output there should be something like:
sd 46:0:0:0: [sda] 15826944 512-byte logical blocks: (8.10 GB/7.54 GiB) sd 46:0:0:0: [sda] Write Protect is off sd 46:0:0:0: [sda] Mode Sense: 43 00 00 00 sd 46:0:0:0: [sda] Assuming drive cache: write through sd 46:0:0:0: [sda] No Caching mode page present sda: sda1 sd 46:0:0:0: [sda] Assuming drive cache: write through sd 46:0:0:0: [sda] Attached SCSI removable disk
Check that the token in the output, sda1 above, matches the token in the command:
/dev/sda1. If, instead, you see
dmesgoutput, then you should use
/dev/sdb1in the mount command. (This might be the case if your Affinity has a Compact Flash module, which would have been allocated
sda, forcing the upgrade pod to be
If this still fails, the unit will need to be upgraded by some other method.
- Run the command:
- Wait until you see the message
=================================== Upgrade complete, please reboot now ===================================then reboot the Affinity by interrupting the power or entering the command: