SSP Platform / ISG 2.3.2.1 - Fresh Box and device is keep rebooting
Article ID: 247465
Updated On:
Products
Issue/Introduction
When booted up the device for the first time, it keeps rebooting on its own, producing the following messages:
Version 2.20.1276. Copyright (C) 2020 American Megatrends, Inc.
S410 BIOS G0.22 (2020-11-24)
Symantec Systems, Inc. [C-NS]
CPU 0: Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz
CPU 1: Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz
BMC Version: 1.28
Booting from Primary SATA device
Symantec UEFI Boot v4.26.255336
This machine has the following bootable system:
>1: Version: ISG 2.3.2.1, Release id: 265086
Created: Friday July 30 2021 01:28:14 UTC
Last-boot: Friday July 29 2022 10:43:47 UTC, FAILED
Attributes: Locked, Signed
The default boot system is: 92
1: Version: ISG 2.3.2.1, Release id: 265086
Press the space key to select an alternate system to boot.
Seconds remaining until the default system is booted: 0
Booting Version: ISG 2.3.2.1, Release id: 265086
+ . /opt/bluecoat/clp/lib/scripts/clp-lib.sh
++ COE_PFS_VER=v2
++ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/bin:/usr/bin:/sbin:/usr/sbin
++ VG_PREFIX=__pre_
++ COE_RESERVED_SNAPSHOT_SIZE=1073741824
++ COE_SNAPSHOT_RESERVE=' encrypted-data:50M cache-data:20M data:2%ORIGIN '
++ SEED=/tmp/.rndlspo
++ GPIO_BASE_DIR=/sys/class/gpio
++ EXPORT_FILE=/sys/class/gpio/export
++ EFI_DIR=/sys/firmware/efi/efivars
++ EFI_MEK=/sys/firmware/efi/efivars/MEK-dbc9ab9c-70f8-4cdb-90f3-d00b27a38064
++ COE_SEC_VARS=/opt/bluecoat/coe_sec_vars/coe_sec_vars.py
++ REASON_FILE=/core/last_reboot/reason
++ EFI_CURRENT_PATH=/sys/firmware/efi/efivars/CurrentSerialSettings-b1b36761-35ae-4d02-e162-e0e8bc7b6d5b
++ INIT_ATTRIBUTES_FILE=/encrypted-config/init-attributes
+++ check_get_fips_env
++++ is_fips_mode_enabled
++++ fips_mode_enabled=false
++++ grep '^FIPS_MODE=1$' /encrypted-config/init-attributes
++++ '[' 1 -eq 0 ']'
++++ echo false
+++ '[' false == true ']'
++ OPENSSL=' /usr/bin/openssl'
+++ check_get_fips_env
++++ is_fips_mode_enabled
++++ fips_mode_enabled=false
++++ grep '^FIPS_MODE=1$' /encrypted-config/init-attributes
++++ '[' 1 -eq 0 ']'
++++ echo false
+++ '[' false == true ']'
++ NGINXCOE=' /etc/init.d/nginx'
+++ check_get_fips_env
++++ is_fips_mode_enabled
++++ fips_mode_enabled=false
++++ grep '^FIPS_MODE=1$' /encrypted-config/init-attributes
++++ '[' 1 -eq 0 ']'
++++ echo false
+++ '[' false == true ']'
++ CONFDCOE=' /opt/tailf/confd/bin/confd'
++ CLOUD_PLATFORMS='AWS Xen Azure GCP'
++ KB=1024
++ MB=1048576
++ GB=1073741824
++ TB=1099511627776
++ PB=1125899906842624
+ /opt/bluecoat/clp/bin/update_boot_meta -f
+ logger -p local1.notice -t /opt/bluecoat/clp/bin/update_boot_meta: 'Marking boot as successful.'
++ mktemp /tmp/cmd-XXXXXXXXXX
+ CMD=/tmp/cmd-yQpeN7PHs3
+ cat
+ chmod +x /tmp/cmd-yQpeN7PHs3
+ /opt/bluecoat/clp_services/bin/update_boot_disks /tmp/cmd-yQpeN7PHs3
+ rm /tmp/cmd-yQpeN7PHs3
+ '[' -d /core/clp/ ']'
+ rm -fR /core/clp/
+ cp -fR /var/log/clp/ /core
+ cp -fR /var/log/clp_alerts.log /var/log/clp_services.log /core/clp/
+ '[' -e /data/bluecoat/clp/last-upgraded-si ']'
+ delete_snapshots
++ lvs --noheadings --nosuffix --separator : -o vg_name,lv_name,lv_attr
+ for lv in '$(lvs --noheadings --nosuffix --separator ":" -o vg_name,lv_name,lv_attr)'
+ IFS=:
+ read VG_NAME LV_NAME LV_ATTR
+ [[ owi-aos--- =~ ^s ]]
+ for lv in '$(lvs --noheadings --nosuffix --separator ":" -o vg_name,lv_name,lv_attr)'
+ IFS=:
+ read VG_NAME LV_NAME LV_ATTR
+ [[ -wi-ao---- =~ ^s ]]
+ for lv in '$(lvs --noheadings --nosuffix --separator ":" -o vg_name,lv_name,lv_attr)'
+ IFS=:
+ read VG_NAME LV_NAME LV_ATTR
+ [[ owi-aos--- =~ ^s ]]
+ for lv in '$(lvs --noheadings --nosuffix --separator ":" -o vg_name,lv_name,lv_attr)'
+ IFS=:
+ read VG_NAME LV_NAME LV_ATTR
+ [[ owi-aos--- =~ ^s ]]
+ for lv in '$(lvs --noheadings --nosuffix --separator ":" -o vg_name,lv_name,lv_attr)'
+ IFS=:
+ read VG_NAME LV_NAME LV_ATTR
+ [[ swi-a-s--- =~ ^s ]]
+ echo y
+ lvremove vg_raid1_1/sn_cache-data
Do you really want to remove active logical volume vg_raid1_1/sn_cache-data? [y/n]: Logical volume "sn_cache-data" successfully removed
+ for lv in '$(lvs --noheadings --nosuffix --separator ":" -o vg_name,lv_name,lv_attr)'
+ IFS=:
+ read VG_NAME LV_NAME LV_ATTR
+ [[ swi-a-s--- =~ ^s ]]
+ echo y
+ lvremove vg_raid1_1/sn_data
Do you really want to remove active logical volume vg_raid1_1/sn_data? [y/n]: Logical volume "sn_data" successfully removed
+ for lv in '$(lvs --noheadings --nosuffix --separator ":" -o vg_name,lv_name,lv_attr)'
+ IFS=:
+ read VG_NAME LV_NAME LV_ATTR
+ [[ swi-a-s--- =~ ^s ]]
+ echo y
+ lvremove vg_raid1_1/sn_encrypted-data
Do you really want to remove active logical volume vg_raid1_1/sn_encrypted-data? [y/n]: Logical volume "sn_encrypted-data" successfully removed
+ echo 'ERROR during system upgrade.'
ERROR during system upgrade.
+ logger -p local1.alert -t abort_upgrade 'ERROR, please check /var/log/clp/upgrade_downgrade and /tmp/mount_persistent_filesystems.log'
+ sleep 5
+ /usr/bin/logger -p local2.notice 'Error in upgrade/downgrade. Rebooting the system...'
+ reboot -f
Rebooting.
Environment
S410 BIOS G0.22 (2020-11-24)
Version: ISG 2.3.2.1, Release id: 265086
Resolution
1. Verify if all slots cards/SSD disks drive and all removable components are seated well and if not try to reshuffle them or take them out and put them back again.
2. If issue still exist after checking (point 1) follow factory default reset with "r" on the device by pressing space bar while seeing over console:
"Press the space key to select an alternate system to boot."
and then type "r" to do factory reset.
You may refer to this graphical steps for factory default reset based on Content Analysis system. Steps are exactly the same
How to perform a factory reset on a Content Analysis System (CAS)
3. This resolution may refer to any other SSP platform and ISG versions as well.
Feedback
