Strange issue. My Sparc unit thinks it's an x86?

[InTheShires]

I was trying to get RN Photos working a few days/weeks ago, but in doing so hit a problem. Namely this:



Uploaded with ImageShack.us

I had some time today, so sat down to look at this again, but it seems I'm getting this error on all addons I try to install? (Yes, I'm trying to install SPARC based addons)

AFAICT, everything is working fine. Backups run, NZBGET runs, I can access via Frontview, FTP, SCP, and Explorer. Print jobs run fine too.

I've disabled pretty much all I can in Frontview, same error still appears.

I've tried to reinstall the 4.17FW but as expected now, the same error appears. (Via Frontview this is.)

I have yet to try a push of the reset button on the rear, with the 5 second press of the power button. (I'm guessing this performs the same task as a Frontview FW install?) Physically access to the device is not easy, and I only want to go down this route if absolutely necessary.

I have SSH access.

Advice and tips welcome please! 🙂

Apologies if this is in the wrong section, I wasn't sure where it should be.

[mdgm-ntgr]

Your NAS does not think it's x86.

The add-on file may be incomplete or corrupt. Try downloading it via SSH using wget, copying it to your client computer then installing it via Frontview.

cd /c/backup
wget addon_URL

So you've tried rebooting the NAS?

What's the output of the following:

ls -la /tmp

[InTheShires]

mdgm wrote:
Your NAS does not think it's x86.

No, I didn't mean literally. :shock: Just having a joke is all.

So you've tried rebooting the NAS?

What's the output of the following:

ls -la /tmp

Yes NAS been rebooted.

drwxrwxrwt   5 root  root     16384 2011-07-11 20:20 .
drwxr-xr-x  27 admin admin    16384 2011-07-11 17:22 ..
-rwxr-xr-x   1 admin admin     3473 2010-02-07 18:58 action.php
drwxr-xr-x   2 root  root     16384 2011-06-22 00:25 addons
-rw-r--r--   1 root  root         0 2011-04-11 18:26 backup_002_copy.log.1
-rw-r--r--   1 admin admin    11472 2011-06-09 00:06 Backup10787
-rw-r--r--   1 admin admin    11496 2011-06-09 00:06 Backup10792
-rw-r--r--   1 admin admin    11465 2011-06-09 00:06 Backup10796
-rw-r--r--   1 admin admin    11442 2011-06-09 00:06 Backup10802
-rw-r--r--   1 admin admin    11614 2011-06-09 00:06 Backup10804
-rw-r--r--   1 admin admin    11623 2011-06-17 04:05 Backup1855
-rw-r--r--   1 root  root    210940 2011-07-11 16:49 config.zip
-rw-r--r--   1 root  root        12 2011-04-09 17:08 .dhcp_server
-rw-r--r--   1 root  root         0 2011-07-11 20:20 errors_001.log
-rw-r--r--   1 root  root         0 2011-07-11 00:38 errors_002.log
-rw-r--r--   1 root  root         0 2011-07-11 20:10 errors_003.log
-rw-r--r--   1 root  root        65 2011-07-11 00:18 errors_004.log
-rw-r--r--   1 root  root        65 2011-07-11 00:58 errors_005.log
-rw-r--r--   1 root  root        65 2011-07-11 20:05 errors_006.log
-rw-r--r--   1 root  root        65 2011-07-11 20:15 errors_007.log
-rw-r--r--   1 root  root        65 2011-07-11 00:53 errors_008.log
-rw-r--r--   1 root  root        65 2011-07-11 00:13 errors_009.log
-rw-r--r--   1 root  root        65 2011-07-11 18:05 errors_010.log
-rw-r--r--   1 root  root        65 2011-07-11 00:28 errors_011.log
-rw-r--r--   1 root  root        65 2011-07-11 00:33 errors_012.log
-rw-r--r--   1 root  root        65 2011-07-11 00:28 errors_013.log
-rw-r--r--   1 root  root        65 2011-07-11 00:48 errors_014.log
-rw-r--r--   1 root  root        65 2011-07-11 00:08 errors_015.log
-rw-r--r--   1 root  root         0 2011-07-11 00:18 errors_016.log
-rw-r--r--   1 root  root         0 2011-07-11 00:18 errors_017.log
-rw-r--r--   1 root  root         0 2011-07-11 00:33 errors_018.log
-rw-r--r--   1 root  root         0 2011-07-11 00:13 errors_019.log
-rw-r--r--   1 root  root         0 2011-07-11 00:44 errors_020.log
-rw-r--r--   1 root  root     11563 2010-05-25 17:01 evdns.3
-rw-r--r--   1 root  root     17705 2010-05-25 17:01 event.3
-rwxr-xr-x   1 root  root     45502 2010-05-25 16:56 event_rpcgen.py
-rw-rw-r--   1 admin admin       93 2011-04-21 01:18 .htaccess
drwxrwxrwt   2 root  root     16384 2011-04-10 00:14 .ICE-unix
-rwxr-xr-x   1 root  root    220129 2010-05-25 16:55 libtool
-rw-r--r--   1 root  root       821 2011-05-25 03:07 netatalk1476
-rw-r--r--   1 root  root       821 2011-05-26 01:40 netatalk25346
-rw-r--r--   1 root  root       821 2011-07-11 17:21 netatalk32646
-rw-r--r--   1 root  root       821 2011-06-17 03:52 netatalk5106
-rw-r--r--   1 root  root       821 2011-06-23 00:51 netatalk5614
-rw-r--r--   1 root  root       821 2011-05-23 00:38 netatalk977
-rw-r--r--   1 root  root  62341120 2010-11-10 01:12 RAIDiator-4.1.7
-rw-r--r--   1 root  root      2619 2011-06-22 00:25 services
-rw-r--r--   1 root  root      2119 2011-05-20 13:22 settings_empty.json
-rw-r--r--   1 root  root      2063 2011-05-20 13:22 settings.json
-rw-r--r--   1 root  root     90624 2010-06-18 20:27 Thumbs.db
-rw-r--r--   1 root  root    180224 2010-05-08 10:31 typescript
-rw-r--r--   1 admin admin 62341120 2011-07-11 17:12 update_file
drwxrwxrwt   2 root  root     16384 2011-04-10 00:14 .X11-unix
 

WGET gives the same error I get everytime I try this, no matter what the addon, whether it's stored locally or whether I've downloaded it direct from Netgear. The error is what I've posted above.

[mdgm-ntgr]

It seems you may be trying to update to 4.1.7 at the moment. You can't install any add-ons when you're updating the NAS firmware.

What does the following look like?:

ls -la /

Also is there anything in the /tmp/addons folder?

[InTheShires]

mdgm wrote:
What does the following look like?: ls -la / Also is there anything in the /tmp/addons folder?

No, I'm not updating at the moment. That's either leftover from this afternoon, or from when I just ran WGET again.

total 401
drwxr-xr-x  27 admin admin 16384 2011-07-12 00:18 .
drwxr-xr-x  27 admin admin 16384 2011-07-12 00:18 ..
lrwxrwxrwx   1 root  root     16 2011-04-08 14:54 addons-config -> /c/addons-config
lrwxrwxrwx   1 root  root      9 2011-04-07 13:31 backup -> /c/backup
drwxr-xr-x   2 root  root  16384 2011-07-12 00:16 bin
drwxr-xr-x   2 root  root  16384 2011-06-05 23:20 Browser
drwxrwxrwx  23 root  root  16384 2011-06-30 16:33 c
drwxr-xr-x   3 admin admin 16384 2011-04-07 13:31 .Dekoh
drwxr-xr-x   9 root  root  32768 2011-07-12 00:16 dev
lrwxrwxrwx   1 root  root     10 2011-04-11 17:43 Drivers -> /c/Drivers
drwxr-xr-x  58 root  root  16384 2011-07-12 00:17 etc
drwxr-xr-x   6 root  root  16384 2010-11-06 01:47 frontview
lrwxrwxrwx   1 root  root     15 2011-04-10 14:12 GamesConsole -> /c/GamesConsole
lrwxrwxrwx   1 root  root     17 2011-04-10 14:15 GigabyteBackup -> /c/GigabyteBackup
drwxrwsr-x   3 root  root  16384 2011-04-07 13:22 home
drwxr-xr-x   2 root  root   1024 2011-07-12 00:16 initrd
-rw-r--r--   1 root  root      0 2011-07-12 00:16 .init_start
lrwxrwxrwx   1 root  root     14 2011-04-10 14:15 IntelBackup -> /c/IntelBackup
lrwxrwxrwx   1 root  root     16 2011-04-10 14:12 LaptopBackups -> /c/LaptopBackups
drwxr-xr-x   2 root  root  16384 2011-04-08 14:43 Led
drwxr-xr-x   7 root  root  16384 2011-04-08 14:41 lib
drwx------   2 root  root  16384 2002-07-15 21:57 lost+found
lrwxrwxrwx   1 root  root      8 2011-04-07 13:31 media -> /c/media
drwxr-xr-x   2 root  root  16384 2002-02-08 22:23 mnt
drwxr-xr-x   2 root  root  16384 2011-04-08 23:44 Monitor
lrwxrwxrwx   1 root  root     16 2011-04-10 14:15 NetbookBackup -> /c/NetbookBackup
drwxr-xr-x   4 root  root  16384 2011-05-26 00:34 opt
dr-xr-xr-x  55 root  root      0 2003-12-01 12:00 proc
drwxrwxrwt   2 root  root      0 2011-07-12 00:53 ramfs
drwxr-xr-x   2 root  root  16384 2011-05-14 14:29 Remote
-rw-------   1 root  root   1024 2011-04-07 13:34 .rnd
drwx------   4 root  root  16384 2011-05-26 00:34 root
lrwxrwxrwx   1 root  root     11 2011-04-10 14:12 SatFiles -> /c/SatFiles
drwxr-xr-x   2 root  root  16384 2011-04-07 13:23 sbin
lrwxrwxrwx   1 root  root     11 2011-06-23 01:06 snapshot -> /c/snapshot
lrwxrwxrwx   1 root  root     11 2011-04-10 14:12 Software -> /c/Software
-rw-r--r--   1 root  root      2 2011-07-12 00:16 .sync_start
drwxr-xr-x  11 root  root      0 2003-12-01 12:00 sys
drwxrwxrwt   5 root  root  16384 2011-07-12 00:17 tmp
drwxrwxrwt   2 root  root     40 2011-07-12 00:15 USB
drwxr-xr-x  12 admin admin 16384 2008-01-31 23:40 usr
drwxr-xr-x  17 root  root  16384 2008-09-20 12:42 var
lrwxrwxrwx   1 root  root     11 2011-05-23 00:38 VMFolder -> /c/VMFolder
lrwxrwxrwx   1 root  root     10 2011-04-08 14:54 webroot -> /c/webroot
lrwxrwxrwx   1 root  root     12 2011-05-13 00:42 WebServer -> /c/WebServer
lrwxrwxrwx   1 root  root     11 2011-04-10 14:12 Xtreamer -> /c/Xtreamer
lrwxrwxrwx   1 root  root      7 2011-04-19 00:59 Zero -> /c/Zero
 

/Tmp/addons is empty

[mdgm-ntgr]

Well I'd suggest you do

cd /tmp
rm RAIDiator-4.1.7
rm update_file
chmod 1777 /tmp
chown admin:admin /tmp

Then I'd reboot the unit using Frontview and then attempt to install the add-on again (I'd suggest downloading the add-on using wget).

[InTheShires]

Thanks. Will give it a try, WGET grabbing the FW again.

[mdgm-ntgr]

I suggested downloading the add-on using wget. It's possible that the copy of the Photos add-on you have downloaded is incomplete or corrupt.

[InTheShires]

mdgm wrote:
I suggested downloading the add-on using wget. It's possible that the copy of the Photos add-on you have downloaded is incomplete or corrupt.

All addons give the same message, even a FW reinstall.

[mdgm-ntgr]

It sounds like there may be a permissions problem with the /tmp folder (just a guess). Doing the chown and chmod commands suggested above perhaps with the recursive option (-R) specified could perhaps be worth a try.

A firmware re-install requires powering down the NAS and using a paperclip. Installing firmware over the top of itself via Frontview is not a true firmware re-install. It may fix some problems, but not as many.

[ewok]

The error message means that the checksum in the addon's header is not matching the checksum of the addon's image. I'd suggest downloading the addon to the NAS and running md5sum on the addon file. Feel free to post the output here and we'll know for sure if the file is corrupted. Once that is established, we can move forward from there.

[InTheShires]

mdgm wrote:
It sounds like there may be a permissions problem with the /tmp folder (just a guess). Doing the chown and chmod commands suggested above perhaps with the recursive option (-R) specified could perhaps be worth a try.

Will have to try that next.

As the problem remains still. 😞

A firmware re-install requires powering down the NAS and using a paperclip. Installing firmware over the top of itself via Frontview is not a true firmware re-install. It may fix some problems, but not as many.

Yes, I know that. I think I said as much in the OP. Unfortunately it looks like I'm running out of options though so will have to relent and get the ladders out. :evil:

[InTheShires]

ewok wrote:
The error message means that the checksum in the addon's header is not matching the checksum of the addon's image. I'd suggest downloading the addon to the NAS and running md5sum on the addon file. Feel free to post the output here and we'll know for sure if the file is corrupted. Once that is established, we can move forward from there.

Ok, will do. Thanks.

How likely though is that they could all be corrupt, in reality? I've tried about 6-7 addons from my PC/Laptop backups, and about the same number of addons that I have redownloaded either via HTTP and/or Wget and saved them to the NAS to eliminate the laptop.

[ewok]

Assuming all of your hardware is good, it's very unlikely. Unfortunately, that's not always a valid assumption.

[InTheShires]

ewok wrote:
Assuming all of your hardware is good, it's very unlikely. Unfortunately, that's not always a valid assumption.

Do I need to install anything on the Duo?

Wouldn't I normally do...?

cd backup
md5sum ReadyNAS_Photos_2.2.bin

But I'm not getting any further output?

[mdgm-ntgr]

If something is messed up e.g. with the permissions in the /tmp folder, I believe it's possible all add-ons may refuse to install with that error message. I think the /tmp permissions looked alright above. Also remember that NetGear doesn't test community add-ons so if you run some of those there could be unexpected problems related to your selection of those that you are running. There could be a problem caused by a community add-on not doing something right.

Usually a reboot, a firmware re-install with a paperclip and/or cleaning the /tmp folder (removing files no longer needed in there and ensuring correct permissions are set) would resolve the issue, I think.

[mdgm-ntgr]

InTheShires wrote:
ewok wrote: Assuming all of your hardware is good, it's very unlikely. Unfortunately, that's not always a valid assumption. Do I need to install anything on the Duo? Wouldn't I normally do...? cd backup md5sum ReadyNAS_Photos_2.2.bin But I'm not getting any further output?

No need to install anything else, but don't forget the slash (unless you already did a "cd /"). You need to do e.g.

cd /backup
ls -la
md5sum ReadyNAS_Photos_2.2.bin

The ls command allows you to double check the file is there and get the case of what you type in correct.

[ewok]

You should be getting something like this:

april:~# md5sum ReadyNAS_Photos_2.2.bin 
370c1041a2e4e064038dac3c069a9511  ReadyNAS_Photos_2.2.bin

Go ahead and send me the logs and I'll take a look. Also, attach the addon just in case that might be useful.

[InTheShires]

ewok wrote:
You should be getting something like this: april:~# md5sum ReadyNAS_Photos_2.2.bin 370c1041a2e4e064038dac3c069a9511 ReadyNAS_Photos_2.2.bin Go ahead and send me the logs and I'll take a look. Also, attach the addon just in case that might be useful.

Thanks, thats what I thought, but as it was just going back the prompt I wondered if perhaps I was missing something.

Will send you the logs now.

[InTheShires]

Argh! Ok, now can't get the logs either! I'm getting a 500 Internal Server Error eventually, when trying to download them.

Can I get what you need manually?

[ewok]

If you can get me the contents of /var/log, that would be great. If tar is misbehaving, I can probably get by with just /var/log/messages.

[InTheShires]

ewok wrote:
If you can get me the contents of /var/log, that would be great. If tar is misbehaving, I can probably get by with just /var/log/messages.

Thanks, getting them now. Will email them shortly.

[ewok]

Thanks for the logs. I don't see any real indication of a hardware problem, but at the very least there is a problem with md5sum. I'd suggest doing an OS reinstall and running a volume check just to be sure. FYI, the addon you attached to the logs checked out fine.

[chirpa]

Does /usr/bin/awk exist and set executable? I saw a system missing that once, which caused firmware/addon updates to fail install, since the md5sum gets piped to that.

[InTheShires]

ewok wrote:
Thanks for the logs. I don't see any real indication of a hardware problem, but at the very least there is a problem with md5sum. I'd suggest doing an OS reinstall and running a volume check just to be sure. FYI, the addon you attached to the logs checked out fine.

Thanks Ewok. And thanks for confirming I was not indeed going nuts. 😄