A terrible thing happened: I can't start the Cisco FC switch MDS 9148

System Administration
1

Loading stops with a prompt "loader>"

 loader> dir
  [0:4]bootflash:
 <DIR>       4096 .
 <DIR>       4096 ..
 <DIR>       4096 lost+found
         22309376 m9100-s5ek9-kickstart-mz.6.2.9.bin
         81847938 m9100-s5ek9-mz.6.2.9.bin
             1097 20000301_142659_poap_3359_init.log
            15255 conf
              262 license_JPG888800JV_7.lic
 <DIR>       4096 .partner
             8191 mts.log
 <DIR>       4096 scripts
                0 20000301_141446_poap_3302_init.log
             5500 20000709_024613_poap_3354_init.log
         20486009 mds1.txt
                0 20000201_000953_poap_3366_init.log
              388 20000201_013511_poap_4055_init.log

Continuation of the booting is possible only in manual mode by entering

loader> boot m9100-s5ek9-kickstart-mz.6.2.9.bin
switch(boot)# load m9100-s5ek9-mz.6.2.9.bin

how-to fix it?
help me? please!

2

Somehow it's set to manual boot.
Google finds
https://www.reddit.com/r/sysadmin/comments/9724bz/cisco_mds_9148_not_booting_to_image_automatically/?rdt=40344

3

Hi @freeuser

The issue is likely caused by misconfigured boot variables.

To check the current settings, run (and post the results back):

loader> show boot

Also, you can check all the boot variables after your system has booted (manually or otherwise), with:

show bootvar

Feel free @freeuser to run these commands and post back your results for everyone to review with you.

4

Here is a reply to this question from DeepSeek:

DeepSeek's Reply

It looks like your switch is stopping at the loader> prompt, which typically indicates that the device is unable to automatically locate and load the necessary boot files. Here’s a step-by-step guide to help you resolve this issue:

1. Check Boot Configuration

  • Ensure that the boot variables are correctly set to point to the correct kickstart and system images.
  • You can check the current boot variables by entering:
    loader> show boot

2. Set Boot Variables

  • If the boot variables are not set correctly, you can manually set them. For example:
    loader> set BOOT kickstart m9100-s5ek9-kickstart-mz.6.2.9.bin
loader> set BOOT system m9100-s5ek9-mz.6.2.9.bin
loader> save

3. Boot the Device Manually

  • If the boot variables are correct but the device still doesn’t boot automatically, you can manually boot the device as you have done:
    loader> boot m9100-s5ek9-kickstart-mz.6.2.9.bin
switch(boot)# load m9100-s5ek9-mz.6.2.9.bin

4. Verify Image Integrity

  • Ensure that the kickstart and system images are not corrupted. You can verify the integrity of the files by comparing their checksums with the ones provided by the vendor.

5. Check File System

  • Ensure that the file system on the bootflash is not corrupted. You can check the file system using:
    loader> fsck

6. Reinstall Images if Necessary

  • If the images are corrupted, you may need to reinstall them. This can be done via TFTP or USB if the device supports it.

7. Check Hardware

  • If the issue persists, there might be a hardware problem. Check the status of the hardware components, especially the storage device.

8. Contact Support

  • If none of the above steps resolve the issue, it may be necessary to contact the vendor’s technical support for further assistance.

Example Commands:

Here’s a summary of the commands you might need to use:

loader> show boot
loader> set BOOT kickstart m9100-s5ek9-kickstart-mz.6.2.9.bin
loader> set BOOT system m9100-s5ek9-mz.6.2.9.bin
loader> save
loader> boot m9100-s5ek9-kickstart-mz.6.2.9.bin
switch(boot)# load m9100-s5ek9-mz.6.2.9.bin

By following these steps, you should be able to resolve the issue and get your switch to boot properly. If you encounter any specific errors or need further assistance, feel free to ask!

5

yes, thank you very much. this really helped! :handshake:

1 Like