NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
RN104 on 6.10.10 kernel location
Where on the filesystem should the kernel be located? My device has a current uptime of around 140 days, and I may need to restart it. Netgear-supplied package kernel-image is at 4.4.218-610090002, but dpkg -L kernel-image shows that this package contains no files and it has no dependencies, so I am concerned that if the system needs to be rebooted (e.g. because of power failure longer than the UPS can sustain it) it will not come back up. I have been able to install the upstream Debian package linux-image-marvell, which appears to be the kernel required here if none is otherwise available, but I am not sure if that has properly configured the bootloader. Now, the only files in /boot are the kernel, config and initrd from this kernel.How to boot a Debian Live environment with active SSH on a ReadyNAS with no display or console
During my research for my project on installing OMV on an Intel-based ReadyNAS without the need for a console connection, I discovered GRML, which can serve as a Debian Live boot with SSH access on amd64 machines, including many ReadyNAS (legacy and newer) -- so no console connection needed. This may be helpful for anyone with a really messed up OS or boot flash but no easy way to mount the drives outside the NAS to do a recovery or for those looking to install a different OS. It only takes a couple very simple mods to make it work. I'm going to assume here that you are using a Windows machine to prep the USB. If you have Linux, how to create the USB is covered on the GRML web site and you can figure out how to make the mods. If you are using a Mac -- sorry, I don't speak Mac. You start by downloading the GRML ISO from grml.org Next, use RUFUS to create a bootable USB from that ISO. Use ISO mode to do so when prompted, not dd mode. The USB has to meet the same requirements as a ReadyNAS recovery USB: USB2 and <=32MB. As with a recovery USB, the legacy machines can be picky. Smaller and older is usually best. There are two simple changes you have to make: At top level on the USB drive, create a zero-length file named NTGR_USBBOOT_INFO.txt. Right-click in the USB top-level window and select "New> Text Document", then re-name it. In the \boot\grub folder, edit grml-full-amd64_default.cfg adding the ssh option at the end of the fourth line as shown below. Note that this must be all on one line. You should use an editor that can save a Linux-compatible file (LF instead of CRLF as EoL) such as Notepad++. linux /boot/grmlfullamd64/vmlinuz apm=power-off boot=live live-media-path=/live/grml-full-amd64/ bootid=grmlfullamd64202604 "${loopback}" ${kernelopts} nomce ssh=password This turns on SSH and sets the root and grml users' SSH passwords to password (or you can choose your own). Now you just insert it in the front USB port and boot. Depending on your unit and BIOS version, you may need to hold the backup button while it boots. It's loading via USB2, so give it a couple minutes and then SSH in. It should have the same IP address as it did running the native software unless it hasn't been booted in a very long time. If that's the case or the address you thought it had doesn't work, use device name grml or search the network. I did this on an OS6 sandbox system where I scanned and mounted the MDADM RAIDs (mdadm --assemble --scan) and then mounted the BTRFS file system for /data (which was actually data-0, as reported by the MDADM scan). If you have an expanded system, so also have a data-1, data-2, etc., you should only mount data-0. BTRFS will see and link the others in. Of course, if your main partition isn't /data, use the name you set. I believe it also supports LVM, so can work with OS 4.2.x systems, but I haven't done so. It may even work with OS4.1.x (SPARC) drives in an Intel unit -- I think it should. I also did a dd backup of the boot flash in case USB recovery doesn't work for some reason while I mess with alternate OSes. If you plan to put it on the same USB drive as the GRML boot, you have to re-mount the USB drive as read/write. I leave that for the student to research. Sorry, non-Intel-based ReadyNAS users. GRML only supports amd64 and arm6, not arm5 that the ReadyNAS use and definitely no SPARC. If you really want to try this on a 32-bit Intel unit like an NVX, there are old releases that support that, but I've not tried them.Xpenology - ReadyNAS 628X
Hello! Since the ReadyNAS is no longer supported, has anyone installed Xpenology on a 628x? If so, are there any documented instructions or videos that you followed? I currently also have a Synology and am familiar with the GUI and like it, so putting Xpenology on my ReadyNAS seems logical to me. Any guidance would be appreciated. Thanks!OMV on Pro/Ultra series -- a project
For the Pro and Ultra series units with their limited RAM and processors, I think Open Media Vault (OMV) is the best option for an alternate OS. I'm looking at how to install it without needing the serial console, if possible. Most importantly, I want it to boot without having to hold the reset button to boot from USB. It won't be an "OMV on ReadyNAS for Dummies" exactly, but I hope will be for those with a minimum amount of Linux experience -- as close to a "cookbook" as possible. And I think the need for the console may scare away a lot of users, which is why I'd like to avoid it. I'm posting here to see if anyone has explored any aspects of my plan to make it easier for me to find an answer or realize what I want to do just won't work and stop wasting my time. So, if you're more of a Linux guru than I and would like to help, please reply. Though I know a lot WRT the Linux command line, I've never done an install other than the normal interactive one on a unit or VM with a display. My research says that the only way to have this drive/partition configuration in OMV is to install from an existing Debian instance. Otherwise, OMV expects a dedicated OS drive (which the flash is too small for). And it's also how to install OMV via SSH. So here is my thought: Using GRUB as the boot loader, install Debian with GRUB itself on the internal flash but /boot, / (root), swap, and /data on the drives in RAID. Specifically, I know GRUB can support MDADM RAID and I would make /boot and / EXT4 on MDADM RAID and /data as BTRFS on MDADM RAID, partly duplicating the ReadyNASOS partitioning scheme. / would obviously need to be bigger. /boot, /, and swap would be RAID0 with all drives included and /data would be a RAID type appropriate to the number of drives and desired redundancy. I believe that FAI (Fully Automated Installation) (see https://fai-project.org/FAIme/#) can be used to install Debian with that configuration without any interaction from the user and then OMV can be installed from that Debian instance via SSH. So, no console needed. FAI can definitely be configured to install Debian on MDADM RAID and EXT4 or BTRFS via a disk_config file. It's unclear to me right now if I need to add any GRUB commands to do so. FAI also allows you to install additional packages, so I believe openssh-server can be installed that way to allow SSH access without interaction. My plan is to try this first on a VM, maybe in steps (do an interactive install to the desired configuration before trying to do it with FAI). That won't be definitive because there is no real flash memory, but it will let me debug any major Oopses without bricking a real NAS. Then, I have several NAS on which I can try it, so long as I verify a USB recovery can go back to ReadyNASOS. This should also be able to serve as at least a starting point for other Intel based models -- maybe it can be made to work on all. While there is a lot more to do for it, it could even act as a starting point for some ARMHF based units (probably just 200 series, not 100). But I'm not the guy for ARM-based units. While I don't believe the current OMV works on ARMHF, some older ones do.For NETGEAR NAS Storage
Hello, Respcted NETGEAR Team, We are Purchased NETGEAR BRAND NAS STORAGE : READY NAS526X Model in 2020 and this NAS STORAGE Already Over the Warranty Period in Last Year also our WD Hard Drive Full for Backup Storage so we request you for which brand hard drive supported for it and useable for NEATGEAR NAS STORAGE. last one year + not used and not any further process ahead, so we request you please give me suggestion and we are wait for your suitable answer. Please fill to Call us below number : xxxxxxx Jaymin Modi System Analyst Swarnim Gujarat Sports University Vadodara GujaratMigrating Disks from NV+ to NVX
Hello Folks, I'm new here ... I have / had an old NV+ NAS with four 1TB drives. I hadn't used it for years and when I got it going again the other day, all was well for a few hours, backing up my MBP with TimeMachine, until - I'm guessing here - the PSU failed mid-backup, tripping the ring main breaker; the plug fuse (13A!) is Ok and it won't restart. Rather than try and repair or replace the PSU (my regular MO), I decided to buy a used NVX complete with disk trays - looking forward to the performance upgrade! So I've moved the four 1TB drives - in order - from the NV+ to the NVX and powered it up 'Normally'. Error message says that it can't mount the RAID disks ... Ok, so I boot into 'OS reinstall' mode, which seemed to be Ok until the same error message appeared. Any clues or ideas how to proceed? I'd really like to retain / recover the data on the RAID set. I haven't yet tried connecting over the network ... will try this next and see if RAIDar can see it. Many thanks in advance.Writing to the LCD (RN516)
Does anyone have any notes on how to enable hardware support or load kernel modules etc, in order to obtain a workable method to access the displays on ReadyNAS devices from within alternative linux OSs? Specifically I'm interested in RN516 and Pro6, but it would be great if we could start to share knowledge to help everyone with this particular issue. I've been running various different OSs on an RN516, and have stuff like fan control sorted. I've also sorted out a nasty ACPI issue which hogs a large chunk of CPU power due to interrupts from IRQ9. But, I've run out of talent so far on anything that lets me access the LCD hardware. Any pointers? And no, there's nothing in /dev like /dev/lcd or /dev/ttyS1 or similar that will do that job. Stuff that works inside ReadyNAS OS6 doesn't work in other linux OSs, presumably due to a lack of hardware support in the kernel, or the correct module. So far I've completely failed to work out how to resolve this. I managed for the fan/temperature/PWM hardware, but the LCD is kicking my butt.
