- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: How I got apt update and install ... Instruction
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How I got apt update and install ... Instruction
Нello, i have readinas pro 2 with firmware 6.10.9. I would like to apply this instruction on my readinas. Because I can't install uTorrent and some other apps. The problem is that I have never used SSS and Putty. Please can someone write me detailed instructions on how to do this...
I can install the transmission. But I can't install uTorrent.
This instruction here: How I got apt update and install to work (with Deb... - Page 2 - NETGEAR Communities
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Fellow @Sandshark has put up some guidance, including the pre-edited config files -> https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/How-I-got-apt-update-and-install-to...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Thanks for the answer. I have looked at this solution. I would like to apply it to me. But I have never used SSH.I don't know commands. Hope someone can help me with this.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@Paniim wrote:
Thanks for the answer. I have looked at this solution. I would like to apply it to me. But I have never used SSH.I don't know commands.
Start by enabling ssh in system->settings->services. Check the box next to password authentication.
Then when you access the NAS with ssh, use root as the account name. The password is the same as the NAS admin password.
Since you don't know the commands, I suggest you install winscp on a Windows PC instead. This is free.
When you launch it, you'll see a "login" screen. Click on new site, and then create a login using the SFTP protocol.
Click on save, and then use this login with winscp.
You can then navigate to the apt folder by selecting <root>, then etc, and then apt in the right pane of winscp.
Drag the two files @Sandshark posted into that folder (apt.conf and the modified sources.list).
I generally rename files I modify to .orig, and also put a second copy of the modified file with a .mod extension. Then if Netgear updates the files later on in a firmware update, I can see what they've changed, and re-apply my mod.
Firmware updates and OS reinstalls can over-write these files (and of course a factory default will too), so you should keep copies on another device.
@Paniim wrote:
Because I can't install uTorrent and some other apps.
Current versions of some apps won't install no matter you do, because they are not compatible with the old Debian 8 Linux that the NAS uses. I don't know if that will prevent installation or updates of the packages currently on apps.readynas.com ("available apps" in the web ui) or not, as I don't use them.
FWIW, I decided some years ago that it would be better to run the apps I wanted on an always-on Windows PC that mapped the NAS data volume to a PC drive letter. For example, Plex is running that way on my setup. In the case of Plex you get better performance on a PC, since even a modest 2-Liter PC has a more powerful CPU and more memory than any stock ReadyNAS platform.
Though it does cost more to set up if you don't have a PC already on hand, it makes it much simpler to get current apps and keep them up to date. Most of the apps on apps.readynas.com are not maintained, and some are not up to date. In your case, managing apps on a Windows PC would be easier for you, since you don't have Linux skills.
Apps can also destabilize the NAS, and keeping the storage server (NAS) separate from the application server prevents that from happening.
In any event, if you do install apps on the NAS, you should make sure to download and save the .deb files. Now that ReadyNAS are all end-of-life, it is possible (IMO likely) that Netgear will take down the apps.readynas.com server at some point. You can browse to https://apps.readynas.com/pages/?page_id=9 and manually download the deb files you want from there.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Thank you very much for your detailed answer! I can download files in an Internet browser. And then download them locally to the NAS device. But the installation fails. Does this mean that the files are not suitable for my system?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@Paniim wrote:
Thank you very much for your detailed answer! I
As I mentioned above, I don't have these apps installed, so !'m not the best person to give you troubleshooting advice on a specific app. But I just tried to install this one on an RN102 I use for testing, and it did install. Removal also worked properly.
Did you follow the instructions on how to add @Sandshark's two files onto your NAS? If you did follow them (and see the files in the apt folder), then try rebooting the NAS.
Note that while I keep both the original and modified files in the folder for convenience later on, the one that is used by the NAS is sources.list. So that has to be the modified version,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@StephenB wrote:Did you follow the instructions on how to add @Sandshark's two files onto your NAS? If you did follow them (and see the files in the apt folder), then try rebooting the NAS.
Yes, I followed these recommendations. But some applications cannot be installed. My system is based on Intel Atom. She's very barn. This is probably an application incompatibility with my system.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@Paniim wrote:
@StephenB wrote:Did you follow the instructions on how to add @Sandshark's two files onto your NAS? If you did follow them (and see the files in the apt folder), then try rebooting the NAS.
Yes, I followed these recommendations. But some applications cannot be installed. My system is based on Intel Atom. She's very barn. This is probably an application incompatibility with my system.
Try downloading the log zip file, there should be more details in there.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Especially for the log snapshot, I tried to install utorrent. And it was installed successfully!!! I do not understand what's the matter? I am attaching the entire zip of the magazine. Because I don't know where exactly to look at this...
https://disk.yandex.ru/d/VgotBtnFaQzafQ
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
look in apt-history:
Start-Date: 2023-09-07 09:00:11
Commandline: apt-get -qq install -fy rn-dictionary freeapp-collection ca-certificates readynasos
Install: freeapp-collection:amd64 (1566939625)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2023-09-07 09:00:11
Start-Date: 2023-09-07 21:05:07
Commandline: apt-get -qq install -fy rn-dictionary freeapp-collection ca-certificates readynasos
Install: freeapp-collection:amd64 (1566939625)
End-Date: 2023-09-07 21:05:13
Start-Date: 2023-09-07 21:07:42
Commandline: apt-get -yq install --reinstall --allow-downgrades -o APT::Status-Fd=5 transmissionr6
Install: transmissionr6:amd64 (3.00.8), transmission:amd64 (2.82-1, automatic)
End-Date: 2023-09-07 21:07:47
Start-Date: 2023-09-07 22:00:19
Commandline: apt-get -yq install --reinstall --allow-downgrades -o APT::Status-Fd=5 htop
Install: htop:amd64 (1.0.0)
End-Date: 2023-09-07 22:00:24
Start-Date: 2023-09-07 22:48:46
Commandline: apt-get -yq install --reinstall --allow-downgrades -o APT::Status-Fd=5 automatic
Install: automatic:amd64 (1.1.1)
End-Date: 2023-09-07 22:48:52
Start-Date: 2023-09-07 22:51:26
Commandline: apt-get -y purge --auto-remove automatic
Purge: automatic:amd64 (1.1.1)
End-Date: 2023-09-07 22:51:31
Start-Date: 2023-09-07 22:51:40
Commandline: apt-get -y purge --auto-remove htop
Purge: htop:amd64 (1.0.0)
End-Date: 2023-09-07 22:51:43
Start-Date: 2023-09-10 00:33:00
Commandline: apt-get -yq install --reinstall --allow-downgrades -o APT::Status-Fd=5 utserver
Install: libxml2-utils:amd64 (2.9.1+dfsg1-5+deb8u6, automatic), utserver:amd64 (3.3.30470)
End-Date: 2023-09-10 00:33:04
and dpkg.log
2023-09-07 09:00:11 startup archives unpack
2023-09-07 09:00:11 install freeapp-collection:amd64 <none> 1566939625
2023-09-07 09:00:11 status half-installed freeapp-collection:amd64 1566939625
2023-09-07 09:00:11 status not-installed freeapp-collection:amd64 <none>
2023-09-07 21:05:07 startup archives unpack
2023-09-07 21:05:07 install freeapp-collection:amd64 <none> 1566939625
2023-09-07 21:05:07 status half-installed freeapp-collection:amd64 1566939625
2023-09-07 21:05:12 status unpacked freeapp-collection:amd64 1566939625
2023-09-07 21:05:12 status unpacked freeapp-collection:amd64 1566939625
2023-09-07 21:05:12 startup packages configure
2023-09-07 21:05:12 configure freeapp-collection:amd64 1566939625 <none>
2023-09-07 21:05:12 status unpacked freeapp-collection:amd64 1566939625
2023-09-07 21:05:12 status half-configured freeapp-collection:amd64 1566939625
2023-09-07 21:05:13 status installed freeapp-collection:amd64 1566939625
2023-09-07 21:05:13 startup packages configure
2023-09-07 21:07:42 startup archives unpack
2023-09-07 21:07:42 install transmission:amd64 <none> 2.82-1
2023-09-07 21:07:42 status half-installed transmission:amd64 2.82-1
2023-09-07 21:07:44 status unpacked transmission:amd64 2.82-1
2023-09-07 21:07:44 status unpacked transmission:amd64 2.82-1
2023-09-07 21:07:44 install transmissionr6:all <none> 3.00.8
2023-09-07 21:07:44 status half-installed transmissionr6:all 3.00.8
2023-09-07 21:07:45 status unpacked transmissionr6:all 3.00.8
2023-09-07 21:07:45 status unpacked transmissionr6:all 3.00.8
2023-09-07 21:07:45 startup packages configure
2023-09-07 21:07:45 configure transmission:amd64 2.82-1 <none>
2023-09-07 21:07:45 status unpacked transmission:amd64 2.82-1
2023-09-07 21:07:45 status half-configured transmission:amd64 2.82-1
2023-09-07 21:07:45 status installed transmission:amd64 2.82-1
2023-09-07 21:07:45 configure transmissionr6:all 3.00.8 <none>
2023-09-07 21:07:45 status unpacked transmissionr6:all 3.00.8
2023-09-07 21:07:45 status half-configured transmissionr6:all 3.00.8
2023-09-07 21:07:47 status installed transmissionr6:all 3.00.8
2023-09-07 21:07:47 startup packages configure
2023-09-07 22:00:19 startup archives unpack
2023-09-07 22:00:19 install htop:amd64 <none> 1.0.0
2023-09-07 22:00:19 status half-installed htop:amd64 1.0.0
2023-09-07 22:00:20 status unpacked htop:amd64 1.0.0
2023-09-07 22:00:20 status unpacked htop:amd64 1.0.0
2023-09-07 22:00:20 startup packages configure
2023-09-07 22:00:20 configure htop:amd64 1.0.0 <none>
2023-09-07 22:00:20 status unpacked htop:amd64 1.0.0
2023-09-07 22:00:20 status half-configured htop:amd64 1.0.0
2023-09-07 22:00:23 status installed htop:amd64 1.0.0
2023-09-07 22:00:24 startup packages configure
2023-09-07 22:48:46 startup archives unpack
2023-09-07 22:48:46 install automatic:amd64 <none> 1.1.1
2023-09-07 22:48:46 status half-installed automatic:amd64 1.1.1
2023-09-07 22:48:46 status triggers-pending systemd:amd64 230-7~bpo8+2.netgear3
2023-09-07 22:48:47 status unpacked automatic:amd64 1.1.1
2023-09-07 22:48:47 status unpacked automatic:amd64 1.1.1
2023-09-07 22:48:47 trigproc systemd:amd64 230-7~bpo8+2.netgear3 <none>
2023-09-07 22:48:47 status half-configured systemd:amd64 230-7~bpo8+2.netgear3
2023-09-07 22:48:47 status installed systemd:amd64 230-7~bpo8+2.netgear3
2023-09-07 22:48:47 startup packages configure
2023-09-07 22:48:47 configure automatic:amd64 1.1.1 <none>
2023-09-07 22:48:47 status unpacked automatic:amd64 1.1.1
2023-09-07 22:48:47 status triggers-pending systemd:amd64 230-7~bpo8+2.netgear3
2023-09-07 22:48:47 status unpacked automatic:amd64 1.1.1
2023-09-07 22:48:47 status half-configured automatic:amd64 1.1.1
2023-09-07 22:48:51 status installed automatic:amd64 1.1.1
2023-09-07 22:48:51 trigproc systemd:amd64 230-7~bpo8+2.netgear3 <none>
2023-09-07 22:48:51 status half-configured systemd:amd64 230-7~bpo8+2.netgear3
2023-09-07 22:48:52 status installed systemd:amd64 230-7~bpo8+2.netgear3
2023-09-07 22:48:52 startup packages configure
2023-09-07 22:51:26 startup packages purge
2023-09-07 22:51:26 status installed automatic:amd64 1.1.1
2023-09-07 22:51:27 remove automatic:amd64 1.1.1 <none>
2023-09-07 22:51:27 status half-configured automatic:amd64 1.1.1
2023-09-07 22:51:27 status half-installed automatic:amd64 1.1.1
2023-09-07 22:51:27 status config-files automatic:amd64 1.1.1
2023-09-07 22:51:27 purge automatic:amd64 1.1.1 <none>
2023-09-07 22:51:27 status config-files automatic:amd64 1.1.1
2023-09-07 22:51:27 status config-files automatic:amd64 1.1.1
2023-09-07 22:51:27 status config-files automatic:amd64 1.1.1
2023-09-07 22:51:30 status config-files automatic:amd64 1.1.1
2023-09-07 22:51:30 status config-files automatic:amd64 1.1.1
2023-09-07 22:51:30 status not-installed automatic:amd64 <none>
2023-09-07 22:51:30 startup packages configure
2023-09-07 22:51:40 startup packages purge
2023-09-07 22:51:40 status installed htop:amd64 1.0.0
2023-09-07 22:51:40 remove htop:amd64 1.0.0 <none>
2023-09-07 22:51:40 status half-configured htop:amd64 1.0.0
2023-09-07 22:51:40 status half-installed htop:amd64 1.0.0
2023-09-07 22:51:40 status config-files htop:amd64 1.0.0
2023-09-07 22:51:41 purge htop:amd64 1.0.0 <none>
2023-09-07 22:51:41 status config-files htop:amd64 1.0.0
2023-09-07 22:51:41 status config-files htop:amd64 1.0.0
2023-09-07 22:51:41 status config-files htop:amd64 1.0.0
2023-09-07 22:51:43 status config-files htop:amd64 1.0.0
2023-09-07 22:51:43 status config-files htop:amd64 1.0.0
2023-09-07 22:51:43 status not-installed htop:amd64 <none>
2023-09-07 22:51:43 startup packages configure
2023-09-10 00:33:00 startup archives unpack
2023-09-10 00:33:01 install libxml2-utils:amd64 <none> 2.9.1+dfsg1-5+deb8u6
2023-09-10 00:33:01 status half-installed libxml2-utils:amd64 2.9.1+dfsg1-5+deb8u6
2023-09-10 00:33:02 status unpacked libxml2-utils:amd64 2.9.1+dfsg1-5+deb8u6
2023-09-10 00:33:02 status unpacked libxml2-utils:amd64 2.9.1+dfsg1-5+deb8u6
2023-09-10 00:33:02 install utserver:amd64 <none> 3.3.30470
2023-09-10 00:33:02 status half-installed utserver:amd64 3.3.30470
2023-09-10 00:33:03 status unpacked utserver:amd64 3.3.30470
2023-09-10 00:33:03 status unpacked utserver:amd64 3.3.30470
2023-09-10 00:33:03 startup packages configure
2023-09-10 00:33:03 configure libxml2-utils:amd64 2.9.1+dfsg1-5+deb8u6 <none>
2023-09-10 00:33:03 status unpacked libxml2-utils:amd64 2.9.1+dfsg1-5+deb8u6
2023-09-10 00:33:03 status half-configured libxml2-utils:amd64 2.9.1+dfsg1-5+deb8u6
2023-09-10 00:33:03 status installed libxml2-utils:amd64 2.9.1+dfsg1-5+deb8u6
2023-09-10 00:33:04 configure utserver:amd64 3.3.30470 <none>
2023-09-10 00:33:04 status unpacked utserver:amd64 3.3.30470
2023-09-10 00:33:04 status half-configured utserver:amd64 3.3.30470
2023-09-10 00:33:04 status installed utserver:amd64 3.3.30470
2023-09-10 00:33:04 startup packages configure
But there is something wrong - looking at the end of systemd-journal.log I see this
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:54 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
Sep 10 00:38:55 NetgearNAS kernel: BTRFS critical (device md0): corrupt leaf, bad key order: block=51789824, root=1, slot=159
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
My device NAS does a not new hard drive installed. This is for information purposes only. Perhaps the problem is in the hard drive? In the future, I will buy new hard drives for the device.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@Paniim wrote:
Perhaps the problem is in the hard drive?
There are some errors reported on the disk, so that might be related to the btrfs errors
ATA Error Count: 556
Reallocated Sectors: 2
Reallocation Events: 2
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
ATA errors are on the SATA interface, so potentially could be in the NAS chassis (though that isn't all that common).
I generally recommend WD Red Plus or Seagate Ironwolf drives, though any enterprise-class drive will work.
Avoid desktop drives and also avoid the WD Red line. WD Reds use SMR (shingled magnetic recording), which doesn't work out well in NAS. Similarly desktop drives smaller than 8 TB almost all use SMR. (8 TB and larger use CMR).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
I would like to buy the WD purple series WD20PURZ 2TB. Or seagate baracuda ST2000DM008 2TB. And make a raid array mirror... Because I have a lot of photos. I bought this box to store photos and download torrents...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Neither one of which is intended for NAS use. The ST2000DM008 is SMR, and is absolutely to be avoided for RAID. The purple series are optimized for continuous write operations, which is not the typical case for a NAS, but at least are CMR. Why would you not stick with drives intended for a NAS? Note that while WD still claims the red series is suitable for a NAS, they are also SMR and not suited for RAID. That is not the case with the Red Plus line.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@Paniim wrote:
I would like to buy the WD purple series WD20PURZ 2TB. Or seagate baracuda ST2000DM008 2TB.
Like @Sandshark, I recommend against those particular choices.
I suggest either the Seagate Ironwolf (ST2000VN004) or the WD Red Plus (WD20EFPX or WD20EFZX).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Good afternoon The problem with installing applications has been successfully resolved. Thanks a lot StephenB !!!
But I think I have another problem. After rebooting the box, I receive a message: the root files are damaged. I checked my hard drive sector by sector. The disc is good. I received two other hard drives from my friend. I do a full factory install but I keep getting the message: corrupt root. This happens after rebooting or turning on the box. The same problem is described here: https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Readynas-Ultra-2-stuck-on-booting/m...
But I don't understand what you're talking about? What's happened 'mdgm' ?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@Paniim wrote:
But I think I have another problem. After rebooting the box, I receive a message: the root files are damaged. I checked my hard drive sector by sector. The disc is good. I received two other hard drives from my friend. I do a full factory install but I keep getting the message: corrupt root.
What drives are you using (manufacturer/model)?
It is possible you need to do a USB recovery. You'd use the OS 4.2 tools, but with an OS-6 image.
You'll likely find that in order to get the usbrecovery tool to work, you will also need to install this:
- You need to download and install vcredist_x86.exe from https://www.microsoft.com/en-us/download/details.aspx?id=14431
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
I have OS6. But should I use the legacy recovery tool?
At first I had an old Hitachi with 160GB. Then I borrowed two 500GB Seagates from a friend. To check the box. With my old Hitachi 160 there was an error - corrupt root. I borrowed hard drives from a friend and did a full reset to factory settings. I made a raid array mirror. Then I rebooted the box. And again the inscription came out - corrupt root.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Yes, to do a USB recovery of a legacy system upgraded to OS6, you must use the OS 4.2.x recovery tool and instructions with an OS6 image. Unlike when converting to OS6 initially, the image doesn't need to be modified. It does need to be named in a way the tool expects it, such as RAIDiator-x86-6.10.9.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
I don't know why, but I couldn't boot the box from the USB flash drive. I tried different ports on the box. I tried two different flash drives. But the box did not load from them.
At one point, the box loaded normally, without the inscription - corrupt root. And I was able to install the firmware locally. It seems that now it works and the inscription - corrupt root does not appear.
Please tell me, is it possible to replace the RAM module in the box with a 2GB module? My box has a 1GB module installed...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
@Paniim wrote:
Please tell me, is it possible to replace the RAM module in the box with a 2GB module? My box has a 1GB module installed...
It is, and I do recommend doing that with OS-6. The simplest thing to do is look at the existing RAM and get something compatible.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
The legacy NAS are quite picky about what USB drives they'll work with, and it does only work with the front port. But it's moot for now since it seems you finally got things worked out.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
Hi - Thanks very much for the detailed process - I got all the way through (readynas rn316) dragged and dropped the two files (apt.conf and sources.list) into /etc/apt/trusted.gpg.d/ and rebooted. Still wont install apps (eg iDrive).
Please advise what I might be missing?
Thanks again.
J Rose
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How I got apt update and install ... Instruction
You still have to do the apt-get update (note NOT upgrade) command from SSH.