This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Supported is to much said - these 22 TB units are very likely workable like every other non-SMR storage blocks. Never forget the processing time for RAID sync and recovery can be exhausting, theories state that error conditions can be hit before processing is finished.
Does this NAS unit support the Seagate ST22000NT001 harddrives?
It should work with no issues.
There is no known size limit for disks that can be added to OS-6 systems. SMR disks don't work well, and should be avoided.
All ReadyNAS platforms are end-of-life, and Netgear has neglected the HCL for a long time. Best to not use it.
In general, I recommend enterprise class, or Ironwolf, WD Red Plus (but not WD Red, which are SMR).
FWIW, I suggest testing the drive in a Windows PC with Seatools before adding it to the NAS. Personally I run the full non-destructive test, followed by the full erase test. I have had some drives pass one of these tests, but fail the other. This will take a couple of days for a disk this large, but IMO worth the time.
I don't raid my drives anymore in the NAS just using JBOD as I have 4 x 20TB SAS drives in my Dell T7910 Workstation and they sync data to the NAS drives so I have 2 copies all the time.
What are your thoughts on using Seagate EXOS drives in the NAS unit compared with the Ironwolf Pro drives?
What are your thoughts on using Seagate EXOS drives in the NAS unit compared with the Ironwolf Pro drives?
I saw some good pricing and purchased a ST14000NM001G (14 TB EXOS) back in Feb 2021. It's running jbod in an RN202, and I haven't had any issues with it. That said, this particular NAS is just used for weekly backups, so the power-on hours aren't much (829 hours).
A few months later tried to get a second one, but after two arrived DOA from Amazon I gave up and got a WD Red Plus instead. I don't think that had anything to do with Seagate, more likely an issue with how that particular batch of disks were handled/shipped after manufacture. We were of course still in the middle of the supply chain disruption caused by the pandemic back then.
Personally I have had good reliability/longevity from the Red Plus models. I haven't used Ironwolf as long, but so far they are working out equally well. So I haven't seen a need to move up to enterprise-class models. I've been just checking the price on the Red Plus and Ironwolf, and getting whatever is cheapest at the moment.
No, the only thing that is enabled is ReadyCloud but this morning I checked my emails using MS Outlook and saw your reply, clicked on the Re: Hard Drive Upgrade RN314 NAS and the NAS fired up
No, the only thing that is enabled is ReadyCloud but this morning I checked my emails using MS Outlook and saw your reply, clicked on the Re: Hard Drive Upgrade RN314 NAS and the NAS fired up
Does the NAS still have a window open to a NAS share? Or maybe a browser window for the NAS web ui?
Anything on the network that requires the NAS to respond can result in the disks waking up (since the NAS boots from the disks).
Is it normal to lose around 2TB of space on drives using JBOD?
Drive manufacturers use TB (1000*1000*1000*1000) units. The NAS (like Windows) uses TiB (1024*1024*1024*1024) - although it calls it "TB" in the web ui.
Do I need the Home Folders folder on the NAS drive or can I delete it?
You can't actually delete it from the web ui, and shouldn't delete it from ssh.
But you can change the network settings to turn off SMB (and any other file sharing protocol). In that case the "home" user folders won't show up when access the NAS shares list. You will of course still see it in the admin web ui, and if you browse the full data volume using admin credentials.
I've done that on my own systems, as we don't need the feature. Restoring a user's "home" folder from backup is a bit more cumbersome than restoring normal shares, so I'd rather not have them.
I think it is more targeted towards folders using DLNA, I may be wrong
Yes, just add the drives and create a share name then add required services.
I've had a 16TB Seagate EXOS in this NAS for a year and my god is it chatty when transferring data over, the new 20TB EXOS I put in today is quiet as a mouse.
I think it is more targeted towards folders using DLNA, I may be wrong
The "home" folder feature isn't about DLNA (though you can enable DLNA on home folders if you really want to).
The idea is that each NAS user can have a "private" folder, that only appears in the share list when they access the NAS with their credentials. Other users won't see the folder at all (other than admin of course).
Enterprises often use a feature like that, as it is a convenient way to prevent users from accessing other users' files. I'm using my NAS at home, and just keep all the files in ordinary public shares.
What RAID do I use to join 2x10TB drives to make 1x20TB?
I would like to keep the other 2 drives as JBOD
RAID-0. There is no redundancy, and data is striped across both drives. So everything is lost when either drive fails.
FWIW, I generally recommend connecting all NAS to a UPS, so they can cleanly shutdown if the power fails. That does reduce the risk of data corruption/loss.
The only thing you can do in this status with a RAID0 still working will be to take a full backup, drop the complete RAID0, replace the storage block in question, re-create the RAID (hopefully in a smarter way), and restore our data.
