ReadyNAS Ultra 2 apt-get error

[Dustin1]

I recently bought ReadyNAs Ultra 2 Plus and wanted to install a few things on it that I found in the community forum. One thing it says to do is do apt-get update. I have updated the ReadyNAS to 4.2.21 and am getting this error:

W: GPG error: http://www.readynas.com 4.2.21/ Release: The following signatures were invalid: BADSIG B7F02108D553259A RAIDiator Release Key <admin@readynas.com>
W: You may want to run apt-get update to correct these problems


Is there a fix for this?

[InTheShires]

Dustin wrote:

I recently bought ReadyNAs Ultra 2 Plus and wanted to install a few things on it that I found in the community forum. One thing it says to do is do apt-get update. I have updated the ReadyNAS to 4.2.21 and am getting this error: W: GPG error: http://www.readynas.com 4.2.21/ Release: The following signatures were invalid: BADSIG B7F02108D553259A RAIDiator Release Key <admin@readynas.com> W: You may want to run apt-get update to correct these problems Is there a fix for this?

No. Not yet anyway. It's safe to ignore, it's just annoying is all.

There was a fix, but it must have got pulled, because it seemed to only last a couple weeks or so. There are threads about it if you want to search them out.

[JeremyP1]

IIRC I wasn't getting the error in beta RAIDiator-x86 4.2.21 [T7] but recently updated to release and it's back.

[Dustin1]

Oh hey, I found the solution on Google. The first option worked for me. A little research helped.. although I did search the forums before I posted. Everything I saw showed it was fixed in RAIDiator *.20 release.. guess not. 🙂

Hope this helps!!!

First of all try

sudo apt-get clean

sudo apt-get update && sudo apt-get upgrade

Some ISPs cache the packages and errors like these are reported then. If the above commands don't work, try

sudo apt-get update -o Acquire::http::No-Cache=True

and again

sudo apt-get update && sudo apt-get upgrade

If it still doesn't work,

sudo apt-get update -o Acquire::BrokenProxy=true 

sudo apt-get update && sudo apt-get upgrade

If all set, u can make it permanent, so that no problem in future persists by editing

/etc/apt/apt.conf

APT 
{
// Options for the downloading routines
  Acquire
  {
    http
    {
      No-Cache "true";
    };
  };
}

[InTheShires]

Dustin wrote:
sudo apt-get update && sudo apt-get upgrade

Not sure an APT-GET UPGRADE is recommended, but I'm sure other's can clarify with more certainty.

[mdgm-ntgr]

Don't do an "apt-get upgrade". That may break stuff. If an OS Re-install doesn't unbreak it then NetGear may in some cases be able to help for a fee. Worst case would be needing to ensure backup is up to date, do a factory default (wipes all data, settings, everything) then restore data from backup.

[sventunus]

None of the above work for me.
Clean 4.2.21 install, just did a factory reset.
On an Ultra 6.

[Skywalker]

Thanks for bringing this up. It should be fixed now.

[mdgm-ntgr]

Just tried and works for me on an Ultra 6:

MDGM-NAS:~# apt-get update
Get:1 http://www.readynas.com 4.2.21/ Release.gpg [490B]                              
Ign http://www.readynas.com 4.2.21/ Translation-en_US
Hit http://archive.debian.org etch Release.gpg 
Ign http://archive.debian.org etch/main Translation-en_US
Hit http://archive.debian.org etch Release
Get:2 http://www.readynas.com 4.2.21/ Release [2364B]
Get:3 http://www.readynas.com 4.2.21/ Packages [30.0kB]
Ign http://archive.debian.org etch/main Packages/DiffIndex
Hit http://archive.debian.org etch/main Packages     
Fetched 32.9kB in 2s (12.9kB/s)
Reading package lists... Done

[InTheShires]

mdgm wrote:
Just tried and works for me on an Ultra 6:

Finally. Working for me too, Ultra 2+

[majeds]

First of all try

sudo apt-get clean

sudo apt-get update && sudo apt-get upgrade

Some ISPs cache the packages and errors like these are reported then. If the above commands don't work, try

sudo apt-get update -o Acquire::http::No-Cache=True

and again

sudo apt-get update && sudo apt-get upgrade

If it still doesn't work,

sudo apt-get update -o Acquire::BrokenProxy=true 

sudo apt-get update && sudo apt-get upgrade

If all set, u can make it permanent, so that no problem in future persists by editing

/etc/apt/apt.conf

APT 
{
// Options for the downloading routines
  Acquire
  {
    http
    {
      No-Cache "true";
    };
  };
}

I tried this trick and it failed, then I was about to Factory Reset the Nas.

Today, I restart the device and when I execute the command apt-get update, voila, the signature error disappeared.

Thank you for saving our time.

[Papagaiou]

I have the same issue with 4.2.22 now. Could some netgear folks fix it? thanks.

[Skywalker]

Fixed, and found an error in the scanning procedure, so this shouldn't happen again.

[Papagaiou]

I confirm it is fixed.

btw what are the sources that we can add with trust and won't break anything for Ultra 2 ?

[Skywalker]

Just etch and readynas.com. Most packages are fine to grab from the lenny archive, but you need to be careful not to update things like perl, lvm2, nut, etc. I'll see if we can add some additional pinning for 4.2.23 to make some of this more intuitive.

[Papagaiou]

It would be great to be able to do an apt-get upgrade while critical packages and dependencies are protected somehow. Can apt support that actually?

Otherwise, I would not mind if readynas ultra could be upgraded as easy as any Linux distro! Maybe that is something to consider in future when building the new framework of next NAS.

[chirpa]

Papagaiou wrote:
It would be great to be able to do an apt-get upgrade while critical packages and dependencies are protected somehow. Can apt support that actually?

Yes, that is the 'pinning' Skywalker spoke of. It says to keep specific packages as is, to avoid upgrading and breaking stuff.

[Chlorate]

Hello,
Before spending enough time on this great forum, I did an apt-get upgrade with the default sources.list. The NAS is now in production, everything seems to be working fine. I just have some users complaining about file being locked up, is it related ?

[WhoCares_]

Could be, could as well be some simple permission problems with the configuration of the shares. So it would be helpful if you could open an new thread and give some more details about the configuration, on how the users access the files and what error messages they're seeing.

-Stefan

[Chlorate]

Created this new thread as I'm not able to solve the issue:
http://www.readynas.com/forum/viewtopic.php?f=50&t=69259