Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 2 subscribers
  • Views 806 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ASg 7.503 Failed

JimmyM
OK. I'm away in business this week and can't get to my Firewall. I'm just trying to get a list of best possible causes. I run SMTP proxy, HTTP proxy (no caching), IPSec "roadwarrior" VPN server. No IPS. Hardware is listed in my signature. Just in the last few days, sometimes it will route traffic sometimes it won't. I have my wife hit the reset button and it's a crap shoot whether or not thing will sort of work. VPN hasn't worked at all in days. Sometimes after a restart, her laptop will get a DHCP address, sometimes it won't. Sometimes I can connect through an open HTTPS port to my mail server, sometimes I can't. It hasn't generated an Executive Report in days.

It's been running flawlessly for years.

So, most likely causes... GO!


This thread was automatically locked due to age.
Parents
  • 0
    If it was working fine, and now suddenly stopped, I'd be looking at the HDD possibly going bad, for one.   It's hard to tell without looking in the system log; if you can get that, and the HDD is the issue, you should see some indications of that in the log.  There can be many other things as well, but I've found, often, that sudden loss of performance of the ASG system is often due a failed (or failing) HDD.

    There have been some that have had issues when installing the 7.503 up2date, but that was often corrected with a reboot, and none of their issues sound like what you are seeing; if you wish to risk it, you could try up2dating to 7.504, but it's a shot in the dark unless you can see some tangible evidence of what is going on.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply
  • 0
    If it was working fine, and now suddenly stopped, I'd be looking at the HDD possibly going bad, for one.   It's hard to tell without looking in the system log; if you can get that, and the HDD is the issue, you should see some indications of that in the log.  There can be many other things as well, but I've found, often, that sudden loss of performance of the ASG system is often due a failed (or failing) HDD.

    There have been some that have had issues when installing the 7.503 up2date, but that was often corrected with a reboot, and none of their issues sound like what you are seeing; if you wish to risk it, you could try up2dating to 7.504, but it's a shot in the dark unless you can see some tangible evidence of what is going on.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Children
  • 0 in reply to BrucekConvergent
    Thanks. If it is hardware, that's what I hope it is. I have an extra 40GB HDD. When I get home I'll see if I can even get into the UI. Otherwise I do have a monitor hooked to it and I'll see if there's anything on the console.

    ANother thought I had was some sort of log size explosion. But what would cause that? Up to the point I was getting Executive reports, things looked good.

    If it was working fine, and now suddenly stopped, I'd be looking at the HDD possibly going bad, for one.   It's hard to tell without looking in the system log; if you can get that, and the HDD is the issue, you should see some indications of that in the log.  There can be many other things as well, but I've found, often, that sudden loss of performance of the ASG system is often due a failed (or failing) HDD.

    There have been some that have had issues when installing the 7.503 up2date, but that was often corrected with a reboot, and none of their issues sound like what you are seeing; if you wish to risk it, you could try up2dating to 7.504, but it's a shot in the dark unless you can see some tangible evidence of what is going on.
  • 0 in reply to JimmyM
    Things got working after another restart.

    Looking at the kernel logs.
    A lot of these entries...

    2010:03:14-15:54:18 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-15:54:18 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-15:54:18 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-17:24:05 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-17:24:05 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-17:24:05 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-18:39:08 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-18:39:08 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-18:39:08 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-18:40:06 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-18:40:06 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-18:40:06 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-18:40:39 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-18:40:39 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-18:40:39 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-18:54:12 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-18:54:12 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-18:54:12 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-19:24:09 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-19:24:09 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-19:24:09 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-19:39:09 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-19:39:09 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-19:39:09 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-19:39:09 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-19:39:09 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-19:39:09 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-19:55:50 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-19:55:50 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-19:55:50 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-20:09:12 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-20:09:12 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-20:09:12 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-20:39:07 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-20:39:07 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-20:39:07 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }
    2010:03:14-20:54:06 firewall1 kernel: ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
    2010:03:14-20:54:06 firewall1 kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
    2010:03:14-20:54:06 firewall1 kernel: ata1: error=0x84 { DriveStatusError BadCRC }

    Bad HDD?
  • 0 in reply to JimmyM
    Yep, your hard drive is toast.  I'm not sure, but you should be able to use a 40GB drive; they changed the minimum size of a drive allowed during install some time ago, but I can't recall what the new minimum size is.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Actually, that's good news. It explains a lot and I HAVE a spare 40GB SATA drive. Well, I have my Friday night all planned out for me.
  • 0 in reply to JimmyM
    The drive has been replaced and I re-installed 7.502. It takes a while on my Via mini-itx, but it got done with no great fan fare. I restored a back up and everything is working again.
    I've never restored from a backup before. Almost like cheating.
    Well done Astaro.
  • 0 in reply to JimmyM
    Good to hear you got it running again.  Have a good weekend!

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Cookie Information Banner