NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
524X Can't factory reset, help
Using 524X with firmware 6.10.9
Finally had a disk fail. the disk test option from front view reporting error, but no reasons given, smart status wasn't showing errors.
well I tried to resync it just in case, but that just led to corrupted volumed, so then I basically did a boot menu disk test...which ran all the way through and reported one disk with failures, so I pulled that disk out and attempted to do a factory reset with the 3 remaining disks (which have some corrupted volume state).
The factory reset from boot menu fails and raider gives message about corrupt root. One of the disks showed up as RED in front view and I see message about removing the other two in order to use it, or something..
well anyway I tried to remove that disk and did a factory reset successfully with just two disks..and that worked fine. However, then its reseting as Raid1 rather then raid5. I tried to "format" the one showing up as red, didn't seem to make any difference. or maybe didn't work I can't remember now. Eventually I figured out it was showing the old corrupted volume still, so I managed to destroy that volume and then it no longer displayed as red, however doing another factory reset with all three drives, hoping for raid5, fails...and raidar says corrupt root.
What is the secret method to completely wipe all three disks and factory reset this thing to a clean slate?
as I understand it, ReadyNAS OS is doing something to prevent me from being able to wipe it as as protection to make sure we don't accidentally lose important data..but in this case I want to wipe it, completely and start over...is there no way to do this?
21 Replies
The factory reset from boot menu fails
That is unusual, and makes me wonder if there are some other disk issues.
You can connect the disks to a Windows PC and remove the partitions using the Windows Disk Manager (Windows calls them "volumes"). Then put them in the NAS and boot up. The NAS will then do a factory install (which is really the same as the factory reset).
Though you might see if you can do a full write test using vendor tools while connected to the PC.
Sorry it took me so long to come back. I tried to run dd on disk#4. Twice. Both times it ran for 4-5 days without finishing. I could see dd running on ps -ef, but it wasn't using much cpu either according to htop.
Unfortunately I was not able to keep an ssh window open to view any progress messaging. My understanding is that it should not take nearly that long to dd the drive, so I have to conclude its fubar. DDing it did remove the weird messages I was seeing through the frontview interface. now it's just showing as greyed out, instead of red and there are no messages about needing to unmount the others.
I also tried numerous times to run smartctl -t long on it... That reports a bunch of weird info, even though it says PASSED, I don't think I trust it. I am going to pull it and flag it as a bad drive. Forum won't let me post the whole output from smartctl -a because its too big apparently.
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.218.x86_64.1] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD60EFAX-68SHWN0 Serial Number: WD-WX51D8986KL9 LU WWN Device Id: 5 0014ee 2bcbe141f Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Wed Jul 16 12:07:03 2025 MDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (53160) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 724) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x303d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 187 083 051 Pre-fail Always - 490 3 Spin_Up_Time 0x0027 229 228 021 Pre-fail Always - 3508 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 49 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 042 042 000 Old_age Always - 42603 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 49 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 33 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 30 194 Temperature_Celsius 0x0022 117 111 000 Old_age Always - 33 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 196 000 Old_age Offline - 369 SMART Error Log Version: 1 ATA Error Count: 19443 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 19443 occurred at disk power-on lifetime: 42602 hours (1775 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 08 15d+23:43:02.801 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.746 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 15d+23:43:02.746 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 15d+23:43:02.746 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.701 IDENTIFY DEVICE Error 19442 occurred at disk power-on lifetime: 42602 hours (1775 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 15d+23:43:02.746 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 15d+23:43:02.746 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.701 IDENTIFY DEVICE ef 10 02 00 00 00 a0 08 15d+23:43:02.690 SET FEATURES [Enable SATA feature] Error 19441 occurred at disk power-on lifetime: 42602 hours (1775 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 08 15d+23:43:02.746 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.701 IDENTIFY DEVICE ef 10 02 00 00 00 a0 08 15d+23:43:02.690 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.635 IDENTIFY DEVICE Error 19440 occurred at disk power-on lifetime: 42602 hours (1775 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 02 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 10 02 00 00 00 a0 08 15d+23:43:02.690 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.635 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 15d+23:43:02.635 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 15d+23:43:02.635 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.589 IDENTIFY DEVICE Error 19439 occurred at disk power-on lifetime: 42602 hours (1775 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 15d+23:43:02.635 SET FEATURES [Set transfer mode] ef 10 02 00 00 00 a0 08 15d+23:43:02.635 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 15d+23:43:02.589 IDENTIFY DEVICE ef 10 02 00 00 00 a0 08 15d+23:43:02.579 SET FEATURES [Enable SATA feature] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 42532 - # 2 Short offline Completed without error 00% 42350 - # 3 Extended offline Completed without error 00% 42350 - # 4 Extended offline Completed without error 00% 42213 - # 5 Extended offline Completed without error 00% 42198 - # 6 Extended offline Completed without error 00% 42186 - # 7 Extended offline Completed without error 00% 42139 - # 8 Extended offline Completed without error 00% 42041 - # 9 Extended offline Completed without error 00% 41972 - #10 Extended offline Completed without error 00% 41613 - #11 Extended offline Interrupted (host reset) 80% 40859 - #12 Extended offline Completed without error 00% 40419 - #13 Extended offline Completed without error 00% 39596 - #14 Extended offline Completed without error 00% 38842 - #15 Extended offline Completed without error 00% 38510 - #16 Extended offline Completed without error 00% 38042 - #17 Extended offline Completed without error 00% 37322 - #18 Extended offline Completed without error 00% 36579 - #19 Extended offline Completed without error 00% 35860 - #20 Extended offline Completed without error 00% 35116 - #21 Extended offline Completed without error 00% 34373 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.My drive 3 is also suspect. It says passed, but I would appreciate comment on this. Its currently installed in raid5 configuration with the first two drives...and has been running a couple weeks ago while I was trying to run the other tests on drive4...no errors reported so far regarding disks 1-3, but anyway here is the smartctl info for drive3, appreciate comments:
root@webman:/home/sjs# smartctl -a /dev/sdc smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.218.x86_64.1] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD60EFRX-68L0BN1 Serial Number: WD-WX11DA7R3VVX LU WWN Device Id: 5 0014ee 264c444a4 Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Wed Jul 16 12:47:22 2025 MDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 118) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 2624) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 680) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 154 001 051 Pre-fail Always In_the_past 2288 3 Spin_Up_Time 0x0027 219 198 021 Pre-fail Always - 8033 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 59 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 018 018 000 Old_age Always - 60507 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 59 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 38 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1236 194 Temperature_Celsius 0x0022 115 109 000 Old_age Always - 37 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 184 131 000 Old_age Offline - 7960 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 60% 60172 1210183120 # 2 Extended offline Completed: read failure 10% 60161 1433936648 # 3 Short offline Completed without error 00% 60146 - # 4 Short offline Completed without error 00% 60123 - # 5 Extended offline Completed: read failure 40% 60105 1325550976 # 6 Extended offline Completed: read failure 50% 60063 1269598024 # 7 Extended offline Completed: read failure 50% 60015 1132039160 # 8 Extended offline Completed: unknown failure 90% 59914 - # 9 Extended offline Completed: unknown failure 90% 59845 - #10 Extended offline Completed: unknown failure 90% 59487 - #11 Extended offline Completed without error 00% 58756 - #12 Extended offline Completed without error 00% 58306 - #13 Extended offline Completed without error 00% 57421 - #14 Extended offline Completed without error 00% 56677 - #15 Extended offline Completed without error 00% 56302 - #16 Extended offline Completed without error 00% 55928 - #17 Extended offline Completed without error 00% 55208 - #18 Extended offline Completed without error 00% 54465 - #19 Extended offline Completed without error 00% 53746 - #20 Extended offline Completed without error 00% 53002 - #21 Extended offline Completed without error 00% 52259 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
Yea I guess it's always possible that both my old disk #1 and this one both failed at the same time. When I ran the boot menu disk test yesterday, 1 out of 4 disks reported problems, which I removed from the unit. I ran the disk test again with the 3 remaining drives and does not report problems. I get you that it still might have problems, but I tend to think that I did all the wrong things while the one that failed was failing...and basically put this third disk into some kind of data-state that is confusing ReadyNAS OS6 enough that it won't wipe it and reset it.
I also get you that I if I had a PC I could wipe it, delete all partitions, etc.. even do more extensive disk testing, etc..
Unfortunately I don't have a windows PC available any time soon.
I wonder if I do factory reset with just the drives that don't seem to be a problem, if I can then boot up readynas with just two drives in X-Raid (raid 1), and then hot swap in the third one and use fdisk or parted or something within readynas command line to get rid of the old partition that is blocking the factory reset from working?
Doing another boot menu disk test right now; it will be another hour or two before I can do anything else.
won't be buying any more HDD's for this device, just trying to stretch a few more years of non-mission-critical use out of it.
I wonder if I do factory reset with just the drives that don't seem to be a problem, if I can then boot up readynas with just two drives in X-Raid (raid 1)
You can do that. If you put those disks in slot 1, you should also be able to hot-insert the third disk. The NAS shouldn't add it to the array, but you could use ssh to test the disk with smartctl (using the long test option). If that passed, you should be able to select the disk in the web ui, and then format it. That would add it to the array.
(You could also use dd to zero the disk, and then see if you get any disk errors in the logs).
Are you sure you did a factory default, not an OS reinstall the first time?
You can't put 2 drives into a RAID5 configuration, so it sounds like that reset went as it should. The NAS will convert it to RAID5 when you put in the third drive. You should hot-insert that third drive and format it, after which the NAS should add it to the array (assuming you chose XRAID).
yes I'm sure I did factory reset.
I did a lot of different things trying to get this working so its a little murky now what all I have tried, but I have tried factory reset numerous times including with all three disks and with only two disks.
I first did it with 3 disks inside after having done a boot menu disk test to discover disk#4 had errors and I removed it..
but it failed to reset with the remaining three drives, gave me an error message on the front of the readynas and in raidar a message about corrupt root. I did googling and found out this is normal, readynasOS is designed to not overwrite it if you have one or more other volumes, it will not erase the new third one if it thinks there might be some old valid data on it....ie...detects a root or detects certain partition or something like that.
I tried to also factory reset only with disk#3 and it also failed.
At some point I did it with only first two disks and that worked.
when I try to put disk 3 back in, it complains that in order to use it I must remove the first two "inactive" disks. I don't want to use it, I want to erase it. but readynas will not erase it or reset it.
I have already tried numerous times to DESTROY all known volumes and FORMAT each of the disks... but ultimately this third disk keeps coming back with a status that there is an old 16TB volume associated with it and does not want to be reset or erased.
but it failed to reset with the remaining three drives, gave me an error message on the front of the readynas and in raidar a message about corrupt root.
The factory reset reformats the disk and recreates the root. So either that process failed, or you accidentally did an OS reinstall.
when I try to put disk 3 back in, it complains that in order to use it I must remove the first two "inactive" disks.
No harm in removing them, since your goal is to reformat everything anyway. Then you can go to system->settings and do the factory default from there.
My drive 3 is also suspect. It says passed, but I would appreciate comment on this.
The extended test actually failed with a read error. So it did not pass.
I tried to run dd on disk#4.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 61 02 00 00 00 a0 Device Fault; Error: ABRT"Device Fault", so also a significant problem.
I was w
referring to the word “PASSED”that is included in the report and is also given if using smartcrl -h. What is the meaning of that?
# 1 Extended offline Completed: read failure 60% 60172 1210183120
# 2 Extended offline Completed: read failure 10% 60161 1433936648Error 19443 occurred at disk power-on lifetime: 42602 hours (1775 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 61 02 00 00 00 a0 Device Fault; Error: ABRTI was refering to these reports.
I don't know what you saw in smartctrl -h. Unfortunately, the ReadyNAS software isn't as good at reporting disk errors as it should be.
to avoid confusion, please exclude /dev/sdd from the discussion it is already thrown in the trash.
Regarding /dev/sdc, the report provided above clearly has in all caps the word "PASSED". I see the errors already. What is the meaning of the word "PASSED"? It seems you are in disagreement with that.
Also smartctl -H produces the following:
root@webman:/home/sjs# smartctl -H /dev/sdc smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.218.x86_64.1] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Please note the following marginal Attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 154 001 051 Pre-fail Always In_the_past 2292so two questions are, what is the meaning of the word PASSED? It seems you feel it is not passed, but rather failed, due to the raw_read_error_rate error listed. It also says it was in the past, whatever that means. Is I possible that this error was reported a long time ago but hasn't been reported in some time? Why does smartctl still consider it PASSED?
is it possible for one failing disk to cause other disks to have errors reported, even though they are not actually in the process of dying like the other one (disk 4 is clearly dead, that's why I throw it away already.
My only question is whether to throw the entire readynas away once and for all or keep using it as a plex server. I really don't know the answer to that question. Not buying any more HDD's for it. Once they are done, I'm getting rid of this thing and getting something more modern.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
