Forum Discussion
NimbostratusProblems with install RMA unit
New replacement 6900 unit has arrived with 9.4.7x want to upgrade to 10.0.1.x to start with, came across this error (logging a ticket with F5). Anyone had experience of this issue before?
root@localhost:NO LICENSE] images image2disk --instslot=HD1.1 --format=volumes BIGIP-10.0.1.283.0.iso
info: Repository tm_install version/release is 2.5.0/80.0
info: System tm_install version/release is 2.4.2/13.0
info: Updating system tm_install files from BIGIP-10.0.1.283.0.iso
....................................................................
1337 blocks
info: Installer on image is newer, reexec
info: Running updated installer.
warning: This system has old boot configuration utilities.
warning: Services must be stopped during updates.
info: Requested install image location (sda.1) is default for boot.
warning: No license file config/bigip.license found in sda, 1
info: Repository has rpm2; system does not. Installing.
info: Begin Install: BIG-IP 10.0.1 build 283.0 from BIGIP-10.0.1.283.0.iso to sda, 1
info: Updating maintenance OS.
info: No MOS currently exists. Installing 2.5.0 - 80.0
error: copy /mnt/tm_install/4420.DfarKZ/isolinux/initrd.img failed; No space left on device
error: copy /tmp/oeyG5ZHkxE failed; No space left on device
Unable to control MOS.
[root@localhost:NO LICENSE] images
3 Replies
What_Lies_Bene1Cirrostratus
Hmmm, it looks like it's trying to install the image on a USB stick, is there one attached?
Also, I'd suggest you license etc. before doing the upgrade.- nitass
Employee
do you have 10.1.0 iso file? if so, would it be possible to try "Removing the EUD (6900 and 8900 platforms only)" in the following sol? i know the sol does not seem to match yours but i think it may help.
sol10636: Upgrading to BIG-IP version 10.1.0 or later fails with a 'Disk full' error message
http://support.f5.com/kb/en-us/solutions/public/10000/600/sol10636.html?sr=11079577
just my 2 cents. 
portoalegreCorrect answer, I removed EUD and then installed 10.0.1 per document this worked. It should be noted that all RMA units come with this problem, I was told.
