I think you are seeing bug CSCeb74183 on the MSFC3.
Description:
When the user loads an MSFC3 with the CONFIG_FILE= set in the rommon, the user is unable to save
the running config to startup-config. The show startup config also fails with an error code 89.
The workaround for this issue is to unset the CONFIG_FILE variable in the MSFC rommon.
The user will run into this situation when he migrates from Native IOS to CatOs or if he
intentionally removes the value of the CONFIG_FILE variable in the MSFC rommon.
The error message displayed is "startup-config file open failed (Not enough space)" when doing a wr
mem and when viewing nvram using dir nvram:, the error message displayed is "%Error calling getdents
for nvram:/ (Unknown error 89)"
It is observed that if the CONFIG_FILE variable is unset in the MSFC3 rommon then user is able to
"wr mem" and display the contents of the nvram.
The following procedure should resolve this issue:
With the sup booted up, switch console into the MSFC3, put it into ROMMON and do the following:
rommon 1 > priv
You now have access to the full set of monitor commands.
Warning: some commands will allow you to destroy your
configuration and/or system images and could render
the machine unbootable.
rommon 2 > nvram_erase
Enter in hex the start address [0xbe020000]: be000000
Enter in hex the test size or length in bytes [0x100]: 200000
3) reset the system
rommon 3 > reset
Do NOT make a mistake with this, or it will destroy the MSFC NVRAM.
After that, set the config register to 0x2102 and set the boot variable by typing in the following:
rommon 1 >confreg 0x2102
rommon 2 >BOOT=bootflash:MSFC-image.bin <-Make sure this is the exact filename-please verify!
rommon 3 >sync
rommon 4 >reset
If it comes back up to ROMMON, just type "boot", but it should boot up.
Once booted up, change the hostname and test if you can write the change. You should be able to.
