[cisco-voip] FN70379 / VMWare Tools breaks initramfs

[Pawlowski, Adam]

Personally I think I will disregard that, especially for my lab, as it shut down cleanly and there has been no corruption that I would be aware of.

Regarding the VMWare tools information, I suppose in hindsight if you knew that you hadn’t updated and this would happen, then disabling that update would be a good idea.

But again I’m pretty sure the implication of that text is if you’re recovering from a severe issue enough to get what you need from the box and start over.

Adam

From: Lelio Fulgenzi <lelio at uoguelph.ca>
Sent: Tuesday, June 18, 2019 2:13 PM
To: Pawlowski, Adam <ajp26 at buffalo.edu>; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] FN70379 / VMWare Tools breaks initramfs

WHOA. OK, my bad for not reading the recovery disk details, but geez, at least include this information in the field notice. At least something that says, “hey - you need to read the recovery release notes for up to date information, but be prepared to have to rebuild the server after you recover.”

Geeeez.


---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Pawlowski, Adam
Sent: Tuesday, June 18, 2019 1:54 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] FN70379 / VMWare Tools breaks initramfs

Hello all,

Just wanted to throw this one back out there to the group. I’m upgrading our lab emergency responder from 12.0 affected to 12.5(1)a. This upgrade failed for some reason I’ve yet to determine with TAC, but part of the process during the upgrade is to roll back to the previous version and reboot if there is a fault during upgrade.

Once this rebooted I got dumped into the condition described in the field notice and have to recover.

TAC also advises that if you use the recovery ISO that you rebuild the server afterwards. CER for sure has said this before in the documentation, but others do as well:

Rebuild Server After You Use the Recovery Disk

Cisco recommends that you rebuild the server, after you use the recovery disk to bring a server with a corrupted file system into a bootable and semifunctional state. For more information, see http:/​/​tools.cisco.com/​bugsearch/​bug/​CSCth53322<http://tools.cisco.com/bugsearch/bug/CSCth53322>
[https://www.cisco.com/c/dam/en/us/td/i/templates/note.gif]Note

________________________________

You may notice missing directories, lost permissions, or corrupted softlinks, if you do not rebuild the server.



I would claim here that this is not a corrupted file system, but in going back to re-read the field notice, I wonder if the action it is prescribing is to use the recovery ISO to repair the boot image for the appliance before you run into trouble and need to work out of it. That’s unclear to me. I did not expect the upgrade to fail and put me in this boat – if you are planning to upgrade out of the affected versions I suppose have the recovery software handy.

Happy loading.

Adam Pawlowski
University at Buffalo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190618/3bf73416/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1297 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190618/3bf73416/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 1111 bytes
Desc: image002.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190618/3bf73416/attachment.gif>