Factory Reset and some questions

So educate me, what does that mean that a release file is missing?  How does that impact us?

I guess for sure there is no chance of getting netgear build essentials or lib6c-dev

anyway my Readynas yesterday suddenly decided to resync itself for no apparent reason and no reported errors.  Not sure what to make of that.  Maybe it’s time to shelf this thing once and for all.

Do you know did netgear take down the so called "dev" repo?  that's where their version of build-essential was I believe, I need netgear's version of lib6c-dev in particular.  It seems this repo is no longer up anywhere...the "dev" section anyway...  Maybe I am missing something.  I am getting and ERROR related to netgear's repo in general, so not sure if that is relevant or not..but well..might be beating my head against a wall if netgear took away the actual dev packages such as libc6-dev and build-essential.

Right, so that explains how I must be getting better action from apt now, as far as non-netgear repos, but I think there is still a problem with netter's repo?

E: The repository 'https://apt.readynas.com/packages/readynasos 6.10.9 Release' does not have a Release file.     
N: Updating from such a repository can't be done securely, and is therefore disabled by default.                  
N: See apt-secure(8) manpage for repository creation and user configuration details.                              
W: GPG error: http://archive.kernel.org/debian-archive/debian jessie Release: The following signatures were invali
d: KEYEXPIRED 1587841717                                                                                          

Also when I try to install build-essential, I get the following error at this point, which makes me wonder if somehow when I did something earlier, some non-netgear version of libc-dev got installed or something, or its not actually trying to fetch from netgear's repo even now....the build-essential, which I seem to recall needs to come from there, but it was a long time when when first set that up on this machine, years and years ago.  Can't remember what I did exactly.

root@webman:/home/sjs# apt install build-essential                                                                
Reading package lists... Done                                                                                     
Building dependency tree                                                                                          
Reading state information... Done                                                                                 
Some packages could not be installed. This may mean that you have                                                 
requested an impossible situation or if you are using the unstable                                                
distribution that some required packages have not yet been created                                                
or been moved out of Incoming.                                                                                    
The following information may help to resolve the situation:                                                      
                                                                                                                  
The following packages have unmet dependencies:                                                                   
 build-essential : Depends: libc6-dev but it is not going to be installed or                                      
                            libc-dev                                                                              
                   Depends: g++ (>= 4:4.9.1) but it is not going to be installed                                  
E: Unable to correct problems, you have held broken packages.                                         

I remember seeing another error at some point that said something about me having some netgear version of one library and not compatible with a non-netgear library or something in build-essentials, etc.. I"m not really sure what is wrong or how I can set this up for compiling again...

But anyway after turning off the need to authorize, it did allow nzbget to install correctly and now I was actually able to use apt to install a couple things like python2, so its progress, and the 'apt list' is MUCH much longer after having done that, but somehow I feel I might have earlier installed something when apt was broken, that has now put my libc stuff in a broken state.  Any advice or comments about that?

So if I can get python3.5+ on here again like I had before I'd be able to ressurect Medusa also, which would be tremendous.  I will either have to compile it, if I can bet build-essential installed and working properly...or...there is someone out that that has a Jessie version of python3.7 in apt repo form, that I might try to install...  so..things are looking up to get this back to where I was before, despite deprecation.

have the following working again since factory reset on 6.10.9:

1. idrive backup
2. shellinbox 2.14 
3. smbplus
4. nzbget (updated to most recent version also)
5. python2
6. nodejs
7. vim (newest from jessie)
8. latest plex server
9. ncdu
10. htop
11. iftop

Only other thing I really need to get back to what I was before factory reset, is medusa...which needs python 3.7 for a much more up to date version of medusa compared to the original App Store version I had in there.  The App Store installer will setup a frontview icon for starting and stopping it and launching it quickly...but medusa has substantially updated since then, so I basically reinstalled medusa using ssh, but still being controlled by the frontview app control...and it was working great, but Alas, I have to get python 3.7 working in order to do that, and pro ably have to get build-essential working right for that...which I would just like to have back anyway, then I'll be happy camper with current situation as long as the existing apt repos never go away.

A direct link to Mhynlo's nzbget x86 deb file is here:

• https://web.archive.org/web/20230204051059/https://apt.readynas.com/packages/readynasos/dists/apps/pool/n/nzbget-rn/nzbget-rn_17.1-6_amd64.deb

Yes thanks.  I had already found that a few days ago and did try it.  It doesn't work for me, from front view I just get an error box that says it can't be ran or can't be installed or something along those lines, no other info.  I would be curious if you try to install it what happens.

It doesn't leave behind anything in /apps either.  However I can manually decompress the deb file and get the contents of the data dir to populate /apps/nxzbget-rn/, ok but whatever setup work that is normally done by the installation system is unknown to me and not handled.  The postinst script inside there doesn't do much, it calls rn_nml whatever that is, which I already tried to do manually also, but didn't make any difference, I think there is more stuff under the covers that the front view app installer does automatically, such as installing the systemd service entry and whatever it needs to do to make the logo.png visible in front view, etc..  but anyway it fails...for some reason.  Since my apt-get is not configured probably as of right now, maybe that's why?   before I did this factory reset, I had a lot of non-standard stuff installed over the years and everything always just worked any dependencies on weird stuff like python or whatever was no problem, but now after the factory reset, its anybody's guess.

for now I just installed nzbget myself manually using a linux installation script from their team, and then I manually installed the systemd service, so its starting up on boot up.....  frontview doesn't know about it, just means I have to start and stop it with ssh.  but I never stop it, so its fine.  Would be nice if I could figure out how to either get MHynlo's installer to work, or else manually do whatever it was doing, in order to get it to show up in front view, but I couldn't figure it out from looking at the control folder of the deb...I think there is a higher level program of some kind when you upload a deb through front view, its doing other tasks automatically, and I don't know how to log that, trace it debug it or do it manually...so I give up on that...and that's fine.  Keep it simple.

FWIW, this is not because of anything Netgear did.  Debian Jessie was deprecated by the Debian community, and they moved their libraries to a new archived location.  The changes above adjust apt so it uses the archived libraries. 

 

These changes are only needed if you install something that requires adding a debian library that is not already

I'll check out those threads, but if it's what I am thinking it was somebody who found a way to mirror the entire repo, which I am not prepared to do.  I understand about the jessie stuff moving and back ports too, I have tried a couple archives and got a few things installed, but I don't want to go much deeper at this point, I'll just leave this thing fairly factory, and use these disks until they die with losable plex content.  In the future I MIGHT use it as a backup server only.  I feel Netgear has more than stopped supporting it, they have proactively deprecated it.  It is what it is.  As long as you stick to factory capabilities though I think it can run fine as a simple file server for many years, but at some point we'll all want faster ethernet...so....  I have an older Readynas Ultra here also that I will try to use for backup server, it might not even have OS6 I can't remember, but it should keep working for basic file service.

The reason I mentioned the Netgear repos is because when I tried to install build-essential or build-essentials, whatever its called, as I recall that had to be Netgear's version of it in order to deal with special libraries and stuff that Netgear made for this device.  but when I tried to install it I got only errors, and at some point I got an error about unable to install it (from a jessie repo maybe) because of dependency on something from Netgear repo.  Well this was a few weeks ago, I can't remember exactly and I tried different repos and now reverted apt sources back to whatever was in my factory reset (which appears to not even know how to find anything called build-essential or build-essentials.  With that I guess I could compile things like python and python 3.6+, etc...

but..like I said...I think I am reversing back to just using this in factory state, though I would like to have apt sources configured for the most up to date and complete repo from Netgear as well as the most up to date jessie and back ports...that doesn't give weird errors and warnings, just in case I ever need to install some little tool., but as of now I already updated vim, added wget, htop, ncdu.  There actually isn't that much I really need that doesn't get massively more complicated to install, such as compiling tools, python, etc.  And clearly...this box is deprecated now.  I think its better to just use it in simple file server tasks...I will use plex server as long as it keeps running.  I have upgraded RAM and Intel it handles all my content perfectly fine.  Nzbget seems tow work easily too, its a self contained binary that seems to work fine with factory Netgear libs that are installed.

In the past I have had all manner of cool things running, crash plan, docker, all different kinds of servers, python, python3 greater than 3.5, and on and on.  But this time around it just feels all blockaded off, and of course whatever resources I used to have a bunch of stuff from readynasextras, etc...  this all helped move me long and up and so forth...but now its just all gone and blocked and basically I think it makes more sense to keep it simple.

However, I would like to to at least have it configured for the most up to date apt-get repo from Netgear and the best archive for jessie and jessie back ports...I was getting some weird errors where it was needing a key or something...strange...

So

• \\nas-ip-address\home\sjs
• \\nas-ip-address\data\home\sjs, and 
• \\nas-ip-address\sjs

Thank you for taking so much time to write that out, I already understood most of what you wrote about how the shares are structured and that they are linked to something at the root level and also under /data...but that isn't the problem I was having.  I created a folder called "extra" inside my /data/raid share.  Somehow that folder was appearing also inside /data/home/sjs share.  

It's remotely possible I tried to do a mv across shares and now I vaguely recall the Netgear version of. mv or cp or both, so some unique things when copying or moving across shares, which my understanding has something to do with them being BTRFS sub volumes or something like that.  I didn't do anything other than mkdir, mv or cp..but somehow that subfolder inside one share, ended up hard linked in some way to a subfolder by the same name over under the other share...except one share didn't show any files..it only showed the folder and all subfolders under it too...but none of the files.  Strange.  I fixed it by temporarily moving all the files underneath to some other folder on /data/raid, then did rm of the one over on /data/home/sjs...and now its gone, so all fine.  Wish I could remember how it got there to begin with, but now I vaguely recall there is something weird about using mv across BTRFS shares.  But might be something else too, dunno.