Hi try follow this should get you back online :)
https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3850-series-switches/117552-technote-cat3850-00.html
Recover from a 3850 Series Switch Boot Failure
There are multiple reasons for a 3850 Series Switch boot failure, such as a corrupt boot image, a corrupt packages.conf file, or missing files. This section describes possible recovery methods.
Note: Ensure that you have knowledge of the two possible boot modes, INSTALL and BUNDLE, before you continue.
Standard Recovery Methods
This section describes the two standard methods that are used in order to recover from a Catalyst 3850 Series Switch boot failure.
USB Recovery
The 3850 Series Switches have a USB port on the front that is used for console access. This USB port is also used with flash drives for image backup and recovery.
If you become stuck at the switch: prompt with a corrupt image or .conf file, you can easily boot to a file that is stored on the USB drive or copy an image from the USB to internal flash. Complete these steps in order to recover from the boot failure:
- Verify that the flash drive is recognized and the .bin file exists:
switch:
dir usbflash0:
Directory of usbflash0:/
74 -rw- 223734376 cat3k_caa-universalk9.SPA.03.03.00.SE.150-1.EZ.bin
- Boot to the USB image:
switch:
boot usbflash0:cat3k_caa-universalk9.SPA.03.03.00.SE.150-1.EZ.bin
Note: This process boots the switch into BUNDLE mode.
Tip: You can also copy the .bin file from usbflash0: to flash:, and point the boot statement towards internal flash.
Corrupt File Recovery
There are instances when the packages.conf calls files that no longer exist in flash. You can manually boot an image from the switch: prompt file; however, upon reload it calls the packages.conf file again and fails to boot. If this occurs, Cisco recommends that you back up the current packages.conf file and rename it or delete it. This process is mandatory, as the next step fails if a .conf file already exists. Once you extract the .bin file, a new packages.conf file is created. Complete these steps in order to recover from a corrupt packages.conf file:
- Once booted (in BUNDLE mode), verify the files in the flash:
Switch#
dir flash:
Directory of flash:/
15500 -rwx 1243 Aug 1 2013 07:04:02 +00:00 packages.conf
- Copy or rename the current packages.conf file:
Switch#
cp flash:packages.conf flash:packages.conf.badop
Destination filename [packages.conf.bad]?
Copy in progress...C
1243 bytes copied in 0.140 secs (8879 bytes/sec)
Switch#
dir flash:
Directory of flash:/
15500 -rwx 1243 Aug 1 2013 07:04:02 +00:00 packages.conf
15502 -rw- 1243 Aug 1 2013 11:53:51 +00:00 packages.conf.bad
Switch#
del flash:packages.conf
Delete filename [packages.conf]?
Delete flash:/packages.conf? [confirm]
- Expand the bundle in order to create a new packages.conf file:
Switch#
software expand running switch 1 to flash:
Preparing expand operation ...
[1]: Expanding the running bundle
[1]: Copying package files
[1]: Package files copied
[1]: Finished expanding the running bundle
- Verify the boot:
Switch#
show boot
---------------------------
Switch 1
---------------------------
Current Boot Variables:
BOOT variable does not exist
Boot Variables on next reload:
BOOT variable = flash:packages.conf;
Manual Boot = no
Enable Break = no
- Reload the switch:
Switch#
reload
Reload command is being issued on Active unit, this will reload the whole stack
Proceed with reload? [confirm]
Emergency Recovery
If the previous recovery methods fail, the 3850 Series Switches have a trap door method that you can use in order to recover the system. You must have a terminal that is connected to the management port of the switch that runs a TFTP server. Download a valid image file from CCO and store it in the root of the TFTP server.
It is likely that the switch is stuck at the switch: prompt. However, if you are in a boot loop, you can use the Mode button on the front of the switch in order to break the cycle: hold the button for approximately ten seconds, and the switch breaks the cycle and stops at the switch: prompt.
Complete these steps in order to perform an emergency recovery:
- Set the switch IP address:
switch:
set IP_ADDR 192.0.2.123/255.255.255.0
- Set the default gateway:
switch:
set DEFAULT_ROUTER 192.0.2.1
- Ping the terminal that contains the TFTP server in order to test the connectivity:
switch:
ping 192.0.2.1
ping 192.0.2.1 with 32 bytes of data ...
Host 192.0.2.1 is alive.
- Verify that the emergency files exist in the switch file system:
switch:
dir sda9:
Directory of sda9:/
2 drwx 1024 .
2 drwx 1024 ..
11 -rwx 18958824 cat3k_caa-recovery.bin
36903936 bytes available (20866048 bytes used)
- Run the emergency install feature:
switch:
emergency-install tftp://192.0.2.1/cat3k_caa-universalk9.
SPA.03.03.00.SE.150-1.EZ.bin
The bootflash will be erased during install operation, continue (y/n)?Y
Starting emergency recovery (tftp://192.0.2.1/cat3k_caa-universalk9.
SPA.03.02.02.SE.150-1.EX2.bin)...
Reading full image into memory......................done
Nova Bundle Image
--------------------------------------
Kernel Address : 0x6042f5d8
Kernel Size : 0x317ccc/3243212
Initramfs Address : 0x607472a4
Initramfs Size : 0xdc6546/14443846
Compression Format: .mzip
Bootable image at @ ram:0x6042f5d8
Bootable image segment 0 address range [0x81100000, 0x81b80000]
is in range [0x80180000, 0x90000000].
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@
File "sda9:cat3k_caa-recovery.bin" uncompressed and installed,
entry point: 0x811060f0
Loading Linux kernel with entry point 0x811060f0 ...
Bootloader: Done loading app on core_mask: 0xf
### Launching Linux Kernel (flags = 0x5)
Initiating Emergency Installation of bundle tftp://192.0.2.1/
cat3k_caa-universalk9.SPA.03.03.00.SE.150-1.EZ.bin
Downloading bundle tftp://192.0.2.1/ cat3k_caa-universalk9.
SPA.03.03.00.SE.150-1.EZ.bin...
Validating bundle tftp://192.0.2.1/ cat3k_caa-universalk9.
SPA.03.03.00.SE.150-1.EZ.bin...
Installing bundle tftp://192.0.2.1/ cat3k_caa-universalk9.
SPA.03.03.00.SE.150-1.EZ.bin...
Verifying bundle tftp://192.0.2.1/ cat3k_caa-universalk9.
SPA.03.03.00.SE.150-1.EZ.bin...
Package cat3k_caa-base.SPA.03.03.00.SE.pkg is Digitally Signed
Package cat3k_caa-drivers.SPA.03.03.00.SE.pkg is Digitally Signed
Package cat3k_caa-infra.SPA.03.03.00.SE.pkg is Digitally Signed
Package cat3k_caa-iosd-universalk9.SPA.150-1.EX2.pkg is Digitally Signed
Package cat3k_caa-platform.SPA.03.03.00.SE.pkg is Digitally Signed
Package cat3k_caa-wcm.SPA.10.0.111.0.pkg is Digitally Signed
Preparing flash...
Syncing device...
Emergency Install successful... Rebooting
Restarting system.
