Forum Discussion
F5 Big IP errror
Dear all My F5 BIG-IP LTM 1600 had OS version 11. After reboot, this device can't start service. I had connected via console. The message displayed:
Login incorrect. Give root password for maintenance (or type Control-D to continue):
How to resolve problem ? Thanks
3 Replies
- nathe
Cirrocumulus
vhv84,
Do you know the root password? If not then this SOL walks you through it:
http://support.f5.com/kb/en-us/solutions/public/13000/100/sol13121.html
Not sure why this has happened but may be useful to run an End User Diags on the box. See this SOL for info:
http://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnotes_eud.html
Hope this helps,
- vhv84_96225
Nimbostratus
Dear all
After I enter Ctrl + D. The BIG-IP reboot and display: Red Hat nash version 5.1.19.6 starting * Reading all physical volumes. This may take a while... * Found volume group "vg-db-sda" using metadata type lvm1******************* 18 logical volume(s) in volume group "vg-db-sda" now activeed. /sysroot/sbin/setfiles: labeling files, pretending /sysroot is / /sysroot/sbin/setfiles: labeling files under /sysroot/sbin/inits matchpathcon_filespec_eval: hash table stats: 1 elements, 1/65536 buckets used, longest chain length 1 /sysroot/sbin/setfiles: Done. Welcome to BIG-IP 11.0.0 Build 8037.0 Setting clock (utc): Mon Oct 28 14:23:43 ICT 2013 [ OK ] Starting udev: [ OK ] Setting hostname bigip.vpn.gov.vn: [ OK ] Setting up Logical Volume Management: [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/mapper/vg--db--sda-set.1.root set.1./: clean, 2771/65536 files, 204426/262144 blocks [/sbin/fsck.ext3 (1) -- /shared] fsck.ext3 -a /dev/mapper/vg--db--sda-dat.share.1 dat.share.1: clean, 203/3932160 files, 829916/7864320 blocks [/sbin/fsck.ext3 (1) -- /var/log] fsck.ext3 -a /dev/mapper/vg--db--sda-dat.log.1 dat.log.1: clean, 150/917504 files, 73736/1835008 blocks [/sbin/fsck.ext3 (1) -- /config] fsck.ext3 -a /dev/mapper/vg--db--sda-set.1._config set.1./config: ext3 recovery flag is clear, but journal has data. set.1./config: Run journal anyway[/sbin/fsck.ext3 (1) -- /usr] fsck.ext3 -a /dev/mapper/vg--db--sda-set.1._usr
set.1./config: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) set.1./usr: clean, 27647/219520 files, 284809/438272 blocks (check in 2 mounts) [/sbin/fsck.ext3 (1) -- /var] fsck.ext3 -a /dev/mapper/vg--db--sda-set.1._var set.1./var: clean, 4768/393216 files, 64618/786432 blocks [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 recovery. *** Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue): Login incorrect. Give root password for maintenance (or type Control-D to continue):
I think my os BIG-IP 11.0.0 Build 8037.0 had problem and it can't start. How to resolve it ?
- nathe
Cirrocumulus
Looks like a disk error than a software one I think.
Sol10328 details running an fsck but I'd also suggest an EUD too.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com