Abort Upgrade Uploaded but Before Restart?

[btaroli]

Got a friend who was so eager to upgrade his NV to support Lion that he uploaded the 4.1.8T5 beta... and then had second thoughts. Is there a way to unravel the staged upgrade so that it won't try applying upon restart? Tried searching forums for older answers on what I'm sure is something people have bumped up against, but came up with nada. Any suggestions or pointers are appreciated!

[mdgm-ntgr]

Do you have SSH access?

[btaroli]

I'm not sure /he/ does, but that can easily be managed (just a few add-ons) if needed to resolve. 🙂 So, let's assume "yes" and go from there. 🙂 Just a few careful rm's I presume?

[TeknoJnky]

well if does not already have ssh access, he is probably screwed... the ssh adon requires rebooting to enable

[btaroli]

He confirms that he indeed had already enabled SSH some time ago. So that won't be a worry. Question is: where's the target path to mop up?

[TeknoJnky]

I would look in the / or /tmp folders for files about the same size as the download

[btaroli]

Indeed I suspect it has staged the file somewhere, but /where/ is the question. I don't have direct access to poke around. I may have to fire up my old NV+ and tinker a bit. It's been looking a bit forlorn under my desk. Perhaps it's time to take him out for a run and give him some love again.

[mdgm-ntgr]

When you do an update via SSH (not recommended as the MD5 of the file isn't checked to see if it's correct) you'd do:

# cd /tmp
# wget http://www.readynas.com/download/beta/raidiator/4.1.8/RAIDiator-4.1.8-T5
# echo /tmp/RAIDiator-4.1.8-T5 > /.cf_update_in_progress
# reboot

So if you have a /.cf_update_in_progress file I'd remove that.

[btaroli]

Have passed along the suggestion and will poke around with it some myself tonight. Thanks! I'll update once he confirms his status, or if I learn anything interesting. 🙂

:naskiller: