Forum Discussion

Raja_M's avatar
Raja_M
Icon for Nimbostratus rankNimbostratus
May 05, 2017

Unable to boot the LTM 6400 ver 10.2.4 ...

Hi Team,

 

We did reboot via cli after that We are not able to boot the F5 LTM 6400 ver 10.2.4. Its stucked in as mentioned.

 

+++++++++++++++ *** 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): bash: /usr/bin/id: No such file or directory bash: [: =: unary operator expected +++++++++++++++++++++++++++++++++++

 

Logs

 

+++++++++++++++++++++++

 

+-------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command-line. BIG-IP 10.2.1 Build 297.0 - drive hdc.1 BIG-IP 10.2.4 Build 860.0 - drive hdc.2 BIG-IP 10.2.4 Build 855.0 - drive hdc.3 End User Diagnostics TMOS maintenance The highlighted entry will be booted automatically in 5 seconds. The highlighted entry will be booted automatically in 4 seconds. The highlighted entry will be booted automatically in 3 seconds. BIG-IP 10.2.4 Build 860.0 - drive hdc.2 BIG-IP 10.2.4 Build 855.0 - drive hdc.3 BIG-IP 10.2.4 Build 855.0 - drive hdc.3 BIG-IP 10.2.4 Build 860.0 - drive hdc.2 BIG-IP 10.2.4 Build 860.0 - drive hdc.2 BIG-IP 10.2.1 Build 297.0 - drive hdc.1 BIG-IP 10.2.1 Build 297.0 - drive hdc.1 BIG-IP 10.2.4 Build 860.0 - drive hdc.2 BIG-IP 10.2.4 Build 860.0 - drive hdc.2 BIG-IP 10.2.4 Build 855.0 - drive hdc.3 BIG-IP 10.2.4 Build 855.0 - drive hdc.3 BIG-IP 10.2.4 Build 860.0 - drive hdc.2 Booting 'BIG-IP 10.2.4 Build 860.0 - drive hdc.2'

 

root (hd1,0) Filesystem type is fat, partition type 0xb kernel /boot/2/vmlinuz ro root=UUID=88056044-436f-40aa-bb09-c8ca391b5ece consol e=ttyS0 panic=1 platform=D63a quiet [Linux-bzImage, setup=0x1e00, size=0x198f3c] initrd /boot/2/initrd [Linux-initrd @ 0x37c58000, 0x397161 bytes]

 

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-hdc" using metadata type lvm1 Found volume group "vg-db-hda" using metadata type lvm1 16 logical volume(s) in volume group "vg-db-hdc" now active 0 logical volume(s) in volume group "vg-db-hda" now active /sysroot/sbin/setfiles: labeling files, pretending /sysroot is / /sysroot/sbin/setfiles: labeling files under /sysroot/sbin/init matchpathcon_filespec_eval: hash table stats: 1 elements, 1/65536 buckets used, longest chain length 1 /sysroot/sbin/setfiles: Done. Welcome to BIG-IP 10.2.4 Build 860.0 Setting clock (utc): Fri May 5 03:42:09 EDT 2017 [ OK ] Starting udev: [ OK ]

 

2 Replies

  • Raja_M's avatar
    Raja_M
    Icon for Nimbostratus rankNimbostratus

    Second part of logs +++++++++++ Setting hostname x5981ptc05.inside.sears.ca: [ OK ] Setting up Logical Volume Management: [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/mapper/vg--db--hdc-set.2.root set.2./: clean, 3049/65536 files, 165211/262144 blocks [/sbin/fsck.ext3 (1) -- /shared] fsck.ext3 -a /dev/mapper/vg--db--hdc-dat.share. 1 dat.share.1: clean, 183/3932160 files, 776280/7864320 blocks [/sbin/fsck.ext3 (1) -- /var/log] fsck.ext3 -a /dev/mapper/vg--db--hdc-dat.log.1

     

    dat.log.1 contains a file system with errors, check forced. hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385536, high=3, low= 16053888, sector=66385479 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385479 Buffer I/O error on device dm-1, logical block 98428 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385536, high=3, low= 16053888, sector=66385487 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385487 Buffer I/O error on device dm-1, logical block 98429 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385533, high=3, low= 16053885, sector=66385495 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385495 Buffer I/O error on device dm-1, logical block 98430 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385535, high=3, low= 16053887, sector=66385503 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385503 Buffer I/O error on device dm-1, logical block 98431 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385536, high=3, low= 16053888, sector=66385511 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385511 Buffer I/O error on device dm-1, logical block 98432 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385536, high=3, low= 16053888, sector=66385519 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385519 Buffer I/O error on device dm-1, logical block 98433 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385536, high=3, low= 16053888, sector=66385527 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385527 Buffer I/O error on device dm-1, logical block 98434 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=66385535, high=3, low= 16053887, sector=66385535 ide: failed opcode was: unknown end_request: I/O error, dev hdc, sector 66385535 Buffer I/O error on device dm-1, logical block 98435 Error reading block 98428 (Attempt to read block from filesystem resulted in sho rt read) while doing inode scan.

     

    dat.log.1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) [/sbin/fsck.ext3 (1) -- /config] fsck.ext3 -a /dev/mapper/vg--db--hdc-set.2._con fig set.2./config: clean, 497/131072 files, 41015/524288 blocks [/sbin/fsck.ext3 (1) -- /usr] fsck.ext3 -a /dev/mapper/vg--db--hdc-set.2._usr set.2./usr: clean, 24729/175296 files, 265345/350208 blocks [/sbin/fsck.ext3 (1) -- /var] fsck.ext3 -a /dev/mapper/vg--db--hdc-set.2._var set.2./var: clean, 3640/393216 files, 82402/786432 blocks [FAILED]