Forum Discussion

Romain_DA_ROIT_'s avatar
Romain_DA_ROIT_
Icon for Nimbostratus rankNimbostratus
Feb 06, 2014

Trying to donwgrade from v11.2.1 to v10.2.2 (on a BIG-IP 6900 system), the appliance does not boot correctly.

Hello all,

 

I am new here.

 

I tried to downgrade my system from v11.2.1 to v10.2.2. After changing the boot location, the system rebooted but it seems that it is stucked in a reboot loop. The LED status is now in a blinking yellow state.

 

From the serial console, the grub seems to be OK but then, I have the error below :

 

ACPI: Unable to locate RSDP Memory for crash kernel (0x0 to 0x0) notwithin permissible range Red Hat nash version 5.1.19.6 starting Reading all physical volumes. This may take a while... Found volume group "vg-db-hda" using metadata type lvm1 1 logical volume(s) in volume group "vg-db-hda" now active mdadm: no devices found for /dev/md0 mdadm: no devices found for /dev/md1 mdadm: no devices found for /dev/md2 mdadm: no devices found for /dev/md3 mdadm: no devices found for /dev/md4 mdadm: no devices found for /dev/md5 mdadm: no devices found for /dev/md6 mdadm: no devices found for /dev/md7 mdadm: no devices found for /dev/md8 mdadm: no devices found for /dev/md9 mdadm: no devices found for /dev/md14 mdadm: no devices found for /dev/md15 mdadm: no devices found for /dev/md16 mdadm: no devices found for /dev/md10 mdadm: no devices found for /dev/md11 mdadm: no devices found for /dev/md12 mdadm: no devices found for /dev/md13 EXT3-fs: unable to read superblock mount: error mounting /dev/md10 on /sysroot as ext3: Invalid argument umount /sysroot failed: Invalid argument mount: could notKernel panic - not syncing: Attempted to kill init! find filesystem '/dev/root' se

 

I found the SOL13654, but swapping the disks did not solve the issue.

 

Thanks in advance for your help.

 

Romain

 

9 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Romain,

     

    My only suggestion would be to run an EUD and do a diags test to see if it points to a specific issue. You might then need to engage the resources at F5 support I'm afraid (in which case they'll no doubt as for a EUD report).

     

    Others on DC may have better clues.

     

    HTH,

     

    N

     

  • did you install version 10 while running 11? or are you trying to go back to an earlier installed version 10? did you change the hdd partitioning scheme from partitions to volumes? might be that is causing the issue now.

     

    anyway if you got a support contract, use it now.

     

  • I am currently working on a lab environment. I was running v10.2.2 and then I upgraded to v11.2.1. Now I want to go back to the 10.2.2 to reproduce an issue which occured on a production environment. I was already using LVM with v10.

     

    Thanks for your time.

     

  • interesting, if that is all checked off i wouldnt know how to proceed except for contacting support.

     

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    Ah! Exactly what I experienced before. See https://devcentral.f5.com/questions/most-stable-current-v11-release .

     

  • Thanks everybody for your answers. I am still working on this issue.

     

    I am trying to make a clean install from v10.2.2.

     

    Using a DVD, i get the result below :

     

    info: Initializing partition table on disk: hda debug: creating steamboat ptable hda: hda1 hda2 hda3debug: No style controls for steamboat info: Adding boot partition to disk: hda info: adding hda.dat.boot... debug: tm_install::Volume::Volume_add -- name=hda.dat.boot, size=0, fstype=b debug: tm_install::DosPtable::DosPtable_get_all_devices -- current = 1 debug: tm_install::Volume::Volume_fs_part -- disk=hda, index=1, type=b, label=dat.boot.1 debug: tm_install::Device::Device_make_fs -- Calling: /sbin/mkfs.msdos -n dat.boot.1 /dev/hda1 info: Adding swap partition to disk: hda info: adding hda.dat.swap... debug: tm_install::Volume::Volume_add -- name=hda.dat.swap, size=0, fstype=82 debug: tm_install::DosPtable::DosPtable_get_all_devices -- current = 1 debug: tm_install::Volume::Volume_fs_part -- disk=hda, index=2, type=82, label=dat.swap.1 info: adding hda.dat.dbvg... debug: tm_install::Volume::Volume_add -- name=hda.dat.dbvg, size=0, fstype=8e debug: tm_install::DosPtable::DosPtable_get_all_devices -- current = 1 debug: tm_install::Volume::Volume_fs_part -- disk=hda, index=3, type=8e, label=dat.dbvg.1 debug: tm_install::DiskArray::DiskArray_autojoin -- No fixed scsi disks found; no array created. info: Creating standard volumes for hda info: Creating standard volumes for cpmirror info: tm_install::Process::Process_add_std_volumes -- Using cpmirror for volume sets. error: tm_install::MultiVolume::MultiVolume_size_scheme -- array cpmirror has no members present info: adding cpmirror.dat.share, size 0... error: tm_install::MdArray::MdArray_volume_add -- requested multi-disk, cpmirror, has no members present. error: MultiVolume_add cpmirror.dat.share failed.

     

    Using a USB key, i get the result below :

     

    info: Initializing partition table on disk: hda hda: hda1 hda2 hda3info: Adding boot partition to disk: hda info: adding hda.dat.boot... info: Adding swap partition to disk: hda info: adding hda.dat.swap... info: adding hda.dat.dbvg... info: Creating standard volumes for hda info: Creating standard volumes for cpmirror info: tm_install::Process::Process_add_std_volumes -- Using cpmirror for volume sets. error: tm_install::MultiVolume::MultiVolume_size_scheme -- array cpmirror has no members present info: adding cpmirror.dat.share, size 0... error: tm_install::MdArray::MdArray_volume_add -- requested multi-disk, cpmirror, has no members present. error: MultiVolume_add cpmirror.dat.share failed. Installing with command: image2disk --format=volumes --nosaveconfig --nvlicenseok /usbrma/images/BIG-IP/BIGIP-10.2.2.763.3.iso

     

    info: Expert mode enabled for non-TMOS context. info: Repository tm_install version/release is 2.7.0/487.0 info: System tm_install version/release is 2.7.1/23.0 info: Platform id is Gemini start: (c,h,s) expected (1023,63,32) found (190,120,0)end: (c,h,s) expected (1023,63,32) found (544,125,44)start: (c,h,s) expected (1023,63,32) found (1010,16,43)end: (c,h,s) expected (1023,63,32) found (205,205,22)start: (c,h,s) expected (1023,63,32) found (252,139,46)end: (c,h,s) expected (1023,63,32) found (367,195,2)start: (c,h,s) expected (1023,63,32) found (0,10,0)end: (c,h,s) expected (1023,63,32) found (0,0,0)Terminal error: Could not find a Volume Set to retrieve configuration and/or license from. at /usr/sbin/image2disk line 146.umount: /usbrma: device is busyumount: /usbrma: device is busy

     

    WARN: Error unmounting USB flash drive.

     

    Please remove the USB flash drive from this device and press enter to reboot.

     

    • JG's avatar
      JG
      Icon for Cumulonimbus rankCumulonimbus
      I am just guessing, but the firmware installed with v11.2 may not be compatible with v10.2. You may want to test this out.