Jump to content


Photo

booting loop

ipsec boot error

This topic has been archived. This means that you cannot reply to this topic.
2 replies to this topic

#1 NESG

NESG
  • Members
  • 3 posts

Posted 03 May 2017 - 12:08 AM

Hi, 

I created ipsec vpn in barracuda f280 box. I used service ip as same as my management ip. But when i rebooted the system, system is stuck in booting loop 

Is there is any option to delete only ipsec configuration from device so that i can retain my other configurations.

 

I am putting the error i got

 

*******************************************************************************************************************************

ART>
[   31.425794] EXT3-fs: barriers not enabled
[   31.450092] kjournald starting.  Commit interval 5 seconds
[   31.450158] EXT3-fs (sda6): using internal journal
[   31.450163] EXT3-fs (sda6): mounted filesystem with ordered data mode
Looking for ART lock file
ART options: --ART=/ram;ext3;mode=666;art.lock;art/artsetup;art/art.tar.gz
Creating root device.
Mounting root fi[   31.707152] EXT3-fs: barriers not enabled
lesystem.
[   31.738211] kjournald starting.  Commit interval 5 seconds
[   31.738226] EXT3-fs (sda2): mounted filesystem with ordered data mode
Setting up other filesystems.
Switching to new root and running init.
                Welcome to Barracuda NG Firewall 7.0.2-094
                Press 'I' to enter interactive startup.
Starting udev: [  OK  ]
Setting hostname F280:  [  OK  ]
Setting up Logical Volume Management: [  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2
/: clean, 36733/1048576 files, 478159/2097152 blocks
[/sbin/fsck.ext3 (1) -- /art] fsck.ext3 -a /dev/sda3
/art: clean, 12/262144 files, 292106/524288 blocks
[/sbin/fsck.ext3 (1) -- /phion0] fsck.ext3 -a /dev/sda1
/phion0 contains a file system with errors, check forced.
 
 
 
 
/phion0: Inode 4964362 has illegal block(s).
 
/phion0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/sda6
/boot: clean, 100/51200 files, 15647/51200 blocks
[FAILED]
***************************************************************************************************************************


#2 Bartek Moczulski

Bartek Moczulski
  • Barracuda Team Members
  • 102 posts

Posted 03 May 2017 - 03:19 AM

hi,

it's not related to configuration. You have a broken filesystem. Please contact support for assistance if you're not familiar with fixing ext3 issues.



#3 NESG

NESG
  • Members
  • 3 posts

Posted 03 May 2017 - 04:38 AM

Thanks Bartek,

putting management ip under ' additional  server ip' wont be causing above problem, right?.

in ART, i have  access to shell (limited options). 

So how can i solve the issue?