01-07-2012 03:57 PM
Have you seen this potential solution in another thread?
I had the same issue. It seems that Juniper fixed this issue in Release 6.2.0r12.There is a hint in the Release Notes: "587433-Sometimes after OS upgrade, the firewall did not start up because of a certain condition in flash writing mechanism." I was able to upgrade the devices to 6.2.0r12 sucessfully, so I think this issue has been resolved. Even an upgrade to 6.3.0r9 was possible.
01-18-2012 08:35 AM
I upgraded two of three SSG-20 to ssg5ssg184.108.40.206r9.0 without issue. The third one bricked. I applied the latest Loadssg5ssg20v133.d boot loader but it didn't help. I tried all but a couple of the 6.3 versions including the oldest one with no luck. I finally applied version ssg5ssg220.127.116.11r3.0 and the router booted. The the third one was different having a T1 and an ADSL PIM card installed and it is several years older. I tried removing the cards but didn't help. I received the same Data Abort Exception code(1002) as this customer in this thread http://forums.juniper.net/t5/ScreenOS-Firewalls-NO
02-20-2012 10:24 AM
I'm having the exact same issue with a few of my SSG5 units.
Been trying different releases, seems that anything past 6.2R3 is giving the same crash/restart exception code (1002).
Just tried 6.2R13 because the release notes had something that looked promising... "662589—Firewall experienced core dump and rebooted the system when accessing the Dlog process."
02-26-2012 02:38 AM
I had same problem and tried upgrading bootloader, then firmware back to 6.3.0r1.0 but no luck...
Finaly i tried 6.2.0r1.0 and that worked.
05-02-2014 05:48 PM
R12: Reserve CR13: 00000000
0017b068 004c3430 0017b158 0017b1e0 0018377c 007055d0 007056dc 00705d94
FP Trace Dump:
00000000 00000000 8bfffef0 8bffff00 8bffff1c 8bffff38 8bffff4c 8bffff7c
Crash dump, the system will reboot...
Crash dump is done.
sys up far = c9
Keeps on rebooting, downgraded to 6.1 and the bootloader is 1.3.3 --- what is the possible fix to this....
thanks and in advance....
05-06-2014 01:37 PM
By the release notes you probably need to have 6.3.0r9 or 6.2.0r12 for the fix.
If these don't work and moving back to your orginal version fails, you may have a bad flash card.