Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

F5 not booting up in normal mode

Hi Guys, F5 device BIG-IP 2200 went down suddenly. After doing a console connection this message comes:

Booting 'BIG-IP 12.1.2 Build 2.12.276 - drive sda.2' ‚Red Hat nash version 5.1.19.6 startingIG-IP 11.5.3 Build 2.0.196 - drive sda.1 *
mdadm: No arrays found in config file or automatically *
Reading all physical volumes. This may take a while... *
Found volume group "vg-db-sda" using metadata type lvm2 *
12 logical volume(s) in volume group "vg-db-sda" now active *
mdadm: No arrays found in config file or automatically *
* Welcome to BIG-IP 12.1.2 Build 2.12.276 *
Starting udev: [ OK ] *
Set system time from hardware clock [ OK ] *
Setting hostname ss313-zlb101a.cps.intel.com: [ OK ] *
Setting up Logical Volume Management: 12 logical volume(s) in volume group "vg-db-sda" now active [ OK ] *
Checking filesystems********************************************************
Checking all file systems. to select which entry is highlighted.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/mapper/vg--db--sda-set.2.root
set.2./: Superblock last mount time (Fri Dec 8 01:41:11 2017,nts
benow = Fri Dec 31 18:22:32 2010) is in the future.

The highlighted entry will be booted automatically in 1 seconds.
set.2./: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
[FAILED]

*** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovGive root password for maintenance (or type Control-D to continue): Login incorrect. Give root password for maintenance (or type Control-D to continue): Login incorrect. Give root password for maintenance (or type Control-D to continue):

After entering the root password, I ran commands fsck -y /dev/mapper/var and did a reboot. But no luck. The same message was displayed again.

I also tried to fsck -A -y and did a reboot, but no luck.

Could you guys suggest? Thanks in advance.

0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Maybe the HDD days are over? Can you boot the system from another boot location (if one exists?). RHEL underneath TMOS doesn't break by itself, so the odds of a hardware problem are high, unfortunately. Do you have active support? Get in contact with F5 to see what your options are. HW appliance could have an active warranty in which case you are eligible for a replacement unit.

0
Comments on this Answer
Comment made 07-Apr-2018 by Ayush Gupta 62

Hi Hannes thanks for your suggestions. How to boot from another boot location using console?

0
Comment made 07-Apr-2018 by Hannes Rapp 3880
1
Comment made 07-Apr-2018 by Ayush Gupta 62
  1. Maybe the HDD days are over?---Does it mean the Hard Disk Drive got corrupted?

  2. RHEL underneath TMOS doesn't break by itself, so the odds of a hardware problem are high, unfortunately.---Could you explain what does it mean (what is RHEL)

0
Comment made 07-Apr-2018 by Hannes Rapp 3880

Note that this is best-effort analysis based on the brief information you gave. You should get in contact with F5 for final confirmation, I can't check your appliance remotely.

  1. Yes, potentially
  2. RHEL is RedHat Linux that boots up the system and sits underneath TMOS microkernel which runs BigIP services.

Did you already try to boot from another location? If it works, you can attempt a fresh install of BigIP on the corrupt boot location and see if that resolves the issue. That's about the last recommendation I can give here, otherwise this troubleshooting session can be 10 questions/answers long and it's more effort than I'm willing to put in.

0
Comment made 07-Apr-2018 by Ayush Gupta 62

Hi Hannes thank you for explaining, I would be opening a service request with F5.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hi, you are using HDD volumes or MD (Raid array)?

If you are getting at least CLI prompt use switchboot -b command to boot with different volume.

For example: switchboot -b HD1.2 or switchboot -b MD1.2

If you are not reaching CLI itself and failing at boot level only suggest you to contact F5 vendor, it may be a hadware issue.

0
Comments on this Answer
Comment made 07-Apr-2018 by Ayush Gupta 62

Hi Raghav, thanks for the suggestion.

LTM uses HD. But not reaching CLI. I will contact F5.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Sure.thanks and please let us know the RCA once F5 fixed the issue.

0