Upgrade from 1.00.06.5 to 1.00.07 issue

[Arctra]

Hey there happy Thecus Community.

Well, like many of u I downloaded the latest 1.00.07 firmware and installed it. Well... kind of installed it... twice... and it still tells me I'm on 1.00.06.5

I went through the standard upgrade routine and it tells me the upgrade is successful and do I want to reboot. I say yes, it does the countdown and says the reboot is complete but in reality the N5200 doesn't reboot, it just carries on running.

I turned the N5200 off at the wall and restarted it and it still reports I'm still on 06.5. The log says the firmware upgrade has been a success however. Do you think this is just a case of a certain file not being upgraded? A module affecting the upgrade? something else?

FYI, I have the following modules installed and enabled:

• META
  
• SHUTDOWN
  
• SSHD
  
• SYSUSER
  
• INFO
  
• PERL
  
• IMGDUP
  

I'm actually tempted to do a full reset of my box so it reverts to the original virgin 1.00.03 firmware where I can upgrade to .07 and install all the modules again from scratch. I'm just really concerned that this will cause me to lose my data currently on the raid volume. Has anyone actually done this yet?

All help, any help is welcomed.

Thanks in advance.

[jamis]

I had no problems going from 6.5 to 0.7 ... though I didn't have any modules installed (hadn't got around to reinstalling any after the upgrade to 6.5

[drewpuppy]

I'm afraid it just worked for me too, though I just had SSHD, SYSUSER and INFO installed.

How about uninstalling all the modules, or all except my set, and then trying again?

Andrew.

[omega]

Hey Arctra,

I think your problem upgrading to 1.00.07 is that for the upgrade you should have the IMGDUP disabled (or uninstalled, but disabled should be enough).

The firmware version is taken from the file /img/version so this supports my theory.

After disabling the IMGDUP module try the firmware upgrade again and quite sure that everything is OK again.

For all others using IMGDUP and the new firmware: whenever the IMGDUP module gets disabled or uninstalled, all files that have been modified are saved in /raid/data/module/backup/IMGDUP so they can be restored after (re-)installing the module again. Maybe the changed files are not valid for the new firmware anymore so you need to check this.

These are one of the reasons why I suggested to be patient about installing the new firmware in combination with the modules.

Andreas

[Arctra]

Thanks boet! I'll try uninstalling IMGDUP and doing the upgrade again in the morning when I'm sober.

Still quite keen to hear if anyone has experience resetting to factory settings and whether their data in the raid remained intact or now.

Cheers

[gideon007]

IMGDUP is a bad boy in regard to shutdowns and reboots Didn't behave for me on .06.5 and doesn't on .07.

[Arctra]

WOO-HOO!!! It worked! After I disabled IMGDUP the upgrade worked perfectly and the box rebooted without me having to hard power-cycle it.

Thanks for your help guys.

[Arctra]

OK, a bit more playing around shows that with even after the upgrade when you re-enable IMGDUP it reverts to showing that I'm firmware 06.5

It doesn't really affect me too much but I just thought I'd post that for anyone else who might find it interesting.

[omega]

Hi Arctra,

even though it doesn't bother you it bothers me....

Please do me a favour: what does the command "cat /img/version" give you?

If that file isn't showing the right version, then there are two explanations for this: either the upgrade process was buggy or you are just watching the (old) imgdup clone directory.

Aaahhh: did you uninstall/install the IMGDUP module after upgrading to 1.00.07? If not, the clone directory /raid/data/module/IMGDUP/img isn't updated and still shows the 1.00.06.5 files. This also means that you're using the old files.....

So please check this out soon.......

Andreas

[chriss]

just want to report: TwonkyMedia module is still running fine after upgrading to .07
I just had a problem with the communication to my UPS after reboot: communication was lost via RS232 and did not re-establish no matter what I tried... after powering down both systems completely and a neatly done re-install of RS232 cable and enabling UPS support all works fine now.

Chris

[Arctra]

omega said:

Please do me a favour: what does the command "cat /img/version" give you?

With IMGDUP disabled:
root@127.0.0.1:/# cat /img/version
1.00.07

With IMGDUP enabled:
root@127.0.0.1:/# cat /img/version
1.00.06.5

omega said:

Aaahhh: did you uninstall/install the IMGDUP module after upgrading to 1.00.07? If not, the clone directory /raid/data/module/IMGDUP/img isn't updated and still shows the 1.00.06.5 files. This also means that you're using the old files.....

Yip, loos like you're right. I uninstalled IMGDUP, re-installed it, then enabled it and the output shows :
root@127.0.0.1:/# cat /img/version
1.00.07


I'll go and put a note in the Wiki about having to uninstall IMGDUP prior to upgrading the firmware.

Thanks for your help