Problem install FirePower/ RAMDISK: incomplete write/ kernel panic

[jan.hawes]

Hi,

i'am trying to install FirePower Services on a ASA 5515-x and a ASA 5555-x both failed with exact the same error.

Both running the same software version:

ASA Software Version 9.4(3)11

Device Manager Version 7.6(2)150

FirePower 6.1.0(330)

I'am trying to install as described in http://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/118644-configure-firepower-00.html

The last commands are:

...
sw-module module sfr recover configure image disk0:/asasfr-5500x-boot-6.1.0-330.img
sw-module module sfr recover boot

Here is the suspected interesting part of debug module boot output: (complete output attached as file)

...
Mod-sfr 383> [  175.058404] md: Waiting for all devices to be available before autodetect
Mod-sfr 384> [  175.059156] md: If you don't use raid, use raid=noautodetect
Mod-sfr 385> [  175.060053] md: Autodetecting RAID arrays.
Mod-sfr 386> [  175.060534] md: Scanned 0 and added 0 devices.
Mod-sfr 387> [  175.061028] md: autorun ...
Mod-sfr 388> [  175.061357] md: ... autorun DONE.
Mod-sfr 389> [  175.061749] RAMDISK: Compressed image found at block 0
Mod-sfr 390> [  175.285721] RAMDISK: incomplete write (-28 != 32768) 16777216
Mod-sfr 391> [  176.250436] crc error
Mod-sfr 392> [  176.270247] VFS: Cannot open root device "<NULL>" or unknown-block(8,2)
Mod-sfr 393> [  176.271027] Please append a correct "root=" boot option; here are the available
Mod-sfr 394>  partitions:
Mod-sfr 395> [  176.271971] 0800         3145728 sda driver: sd
Mod-sfr 396> [  176.272509] 0b00         1048575 sr0 driver: sr
Mod-sfr 397> [  176.273028] fd00       124969216 vda driver: virtio_blk
Mod-sfr 398> [  176.273639]   fd01       124968815 vda1
Mod-sfr 399> [  176.274084] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown
Mod-sfr 400> -block(8,2)
...

Thanks for your help

Jan

[Dennis Perto]

It seems strange. 

Are you using a Cisco SSD drive?

Try uninstalling and install again:

sw-module module sfr uninstall

[jwilliamsuo · Accepted solution]

I ended up opening up a TAC case and they helped figure out the issue.  Turns out the image file was corrupt.  I didn't think to check the hash of the file after the download, and the error really didn't indicate a corrupt image.

TAC had me verify the hash, and sure enough, it didn't match.  Once I re-downloaded the image file, and verified the hash, the re-imaging completed successfully.

[jan.hawes]

Hi,

my Image was corrupt too.

Jan

[xiangminghui]

hello ,i face the same problem now , how i can check the imag md5 in asa ? and if the image has problem , what's process broken the image ? how i can use ftp to transfer the image to asa ?