NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Readynas 104 - Cannot access data - remove inactive volumes to use the disk
Hi,
I'm in trouble.
My ReadyNAS had a problem with the power plug not connecting fully after moving house.
Have fixed it and it is working, but Windows 10 won't read the data.
Logged into the NAS via the web interface,
ReadyNAS reports it is healthy, but the drives are all in Red.
Each drive shows between 40 and 180 ATA errors - but Ive had this for 10 years.
Device date says 7 April even though it is 23 April.
My entire 60 years of life is on this - my kids pics, tax returns.... I have some backups but they are all eyars out of date. Went to ReadyNAS after a string of Seagate HDD fails.
Tried to get onto support but all the options are unavailable (except Community).
I am in Australia in a small country town - would need to drive 4 hours in a car each way just to get near someone.
Hoping there is a way that this can be diagnosed and fixed ?
Log file here https://drive.google.com/file/d/11EX8jKzK5WrerfsfIpC-jGEYuDadMxKS/view?usp=sharing
Help? đ
xfixiate wrote:
Each drive shows between 40 and 180 ATA errors - but Ive had this for 10 years.
smart_history.log shows these counts beginning on 21 Dec 2024, though nothing new since 8 Feb 2025.. Worth keeping a close eye on.
xfixiate wrote:
Device date says 7 April even though it is 23 April.
If you click on the settings wheel next to the time in the NAS admin page, is "synchronize time with an internet server" checked?
xfixiate wrote:
My ReadyNAS had a problem with the power plug not connecting fully after moving house.
I am seeing this from last December
[24/12/21 23:40:38 AEDT] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Inactive. [24/12/21 23:42:36 AEDT] err:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 3 (Internal) changed state from ONLINE to FAILED. [24/12/21 23:46:52 AEDT] err:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from ONLINE to FAILED.This might be a side effect of your power problem.
I'm not seeing errors on those disks now, but the NAS is choosing not to add them to your RAID array.
[Mon Apr 7 11:22:33 2025] md: md127 stopped. [Mon Apr 7 11:22:33 2025] md: bind<sdd3> [Mon Apr 7 11:22:33 2025] md: bind<sdb3> [Mon Apr 7 11:22:33 2025] md: bind<sda3> [Mon Apr 7 11:22:33 2025] md: bind<sdc3> [Mon Apr 7 11:22:33 2025] md: kicking non-fresh sda3 from array! [Mon Apr 7 11:22:33 2025] md: unbind<sda3> [Mon Apr 7 11:22:33 2025] md: export_rdev(sda3) [Mon Apr 7 11:22:33 2025] md: kicking non-fresh sdb3 from array! [Mon Apr 7 11:22:33 2025] md: unbind<sdb3> [Mon Apr 7 11:22:33 2025] md: export_rdev(sdb3) [Mon Apr 7 11:22:33 2025] md/raid:md127: device sdc3 operational as raid disk 0 [Mon Apr 7 11:22:33 2025] md/raid:md127: device sdd3 operational as raid disk 1 [Mon Apr 7 11:22:33 2025] md/raid:md127: allocated 4294kB [Mon Apr 7 11:22:33 2025] md/raid:md127: not enough operational devices (2/4 failed) [Mon Apr 7 11:22:33 2025] RAID conf printout:The RAID system puts a transaction count on each disk, and updates that on every write to the disk. The "non-fresh" status means that some writes were missed on these two disks. That could be a result of the issue on 21 December, or it could have happened if the NAS wasn't properly shut down when you were troubleshooing the power problem.
Either way, it is possible to force the array to mount from tech support mode. If you want to pursue that path, let me know and I can give you advice over private message (using the envelope icon in the upper right of the forum page). There could be some damage to some files, since some writes were lost. But it is likely slight.
The other path would is RAID recovery. You'd have to buy some equipment and software to do that yourself, or you'd need to find a recovery service. You could mail them the disks to avoid the travel complexity. This is lower risk, but would cost. (And I do think the risk is slight if you are careful to follow my instructions).
xfixiate wrote:
My entire 60 years of life is on this - my kids pics, tax returns....As Sandshark says, you need a backup plan. Any device can fail at any time. After your data access is restored, we can provide some advice there. Options include a USB disk (either attached to the NAS or a PC), Cloud Storage, or some combination of both.
US pricing for 2 TB of cloud storage is about $10 USD per month, and that is likely enough to hold your most important files.
6 Replies
I recommend that you remove the log zip from your cloud storage, as there is some privacy leakage when you post the logs publicly.
I have downloaded the log zip, and will post back in a bit.
Since you came here before you tried anything on your own, potentially making things worse, there is a good chance you can recover most or all of your data with StephenB's help or the use of recovery software. But you are probably going to need some place to which to copy the data. You also need to have a backup plan for your irreplaceable data so you don't have to go through this again, so that device can also serve for the basis for doing that.
As you have found out the hard way, RAID and hardware can fail in ways that make all the data inaccessible, though it's better than just individual drives. True backup (on another device) is the only way to make sure your data is protected. There is an old IT saying that still applies: "If you have only one copy of something, you must not think it's very important." For the best protection, that backup is off-site so fire, theft, etc. can't cause the loss of both.
So while StephenB looks for a way to recover your data, you need to start thinking about what that backup method is going to be. Cloud storage, USB drive(s), and another NAS are all options and what you choose can depend on how much data is involved, amount of risk you are comfortable retaining, and budget. StephenB and I both use other NAS as our primary backup. I believe he also uses cloud backup for the most important stuff, as that is both off-site and further backed up by the cloud operator. I have a NAS located at my brother's house in another state, but have also recently started putting some things in the cloud.
If you decide on another NAS, then you also need to decide if you want to buy a used ReadyNAS since you are already familiar with it, or one from another company who's still supporting theirs. If you choose another brand, you'd most likely want to make it your main NAS and relegate the ReadyNAS to backup duty.
xfixiate wrote:
Each drive shows between 40 and 180 ATA errors - but Ive had this for 10 years.
smart_history.log shows these counts beginning on 21 Dec 2024, though nothing new since 8 Feb 2025.. Worth keeping a close eye on.
xfixiate wrote:
Device date says 7 April even though it is 23 April.
If you click on the settings wheel next to the time in the NAS admin page, is "synchronize time with an internet server" checked?
xfixiate wrote:
My ReadyNAS had a problem with the power plug not connecting fully after moving house.
I am seeing this from last December
[24/12/21 23:40:38 AEDT] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Inactive. [24/12/21 23:42:36 AEDT] err:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 3 (Internal) changed state from ONLINE to FAILED. [24/12/21 23:46:52 AEDT] err:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from ONLINE to FAILED.This might be a side effect of your power problem.
I'm not seeing errors on those disks now, but the NAS is choosing not to add them to your RAID array.
[Mon Apr 7 11:22:33 2025] md: md127 stopped. [Mon Apr 7 11:22:33 2025] md: bind<sdd3> [Mon Apr 7 11:22:33 2025] md: bind<sdb3> [Mon Apr 7 11:22:33 2025] md: bind<sda3> [Mon Apr 7 11:22:33 2025] md: bind<sdc3> [Mon Apr 7 11:22:33 2025] md: kicking non-fresh sda3 from array! [Mon Apr 7 11:22:33 2025] md: unbind<sda3> [Mon Apr 7 11:22:33 2025] md: export_rdev(sda3) [Mon Apr 7 11:22:33 2025] md: kicking non-fresh sdb3 from array! [Mon Apr 7 11:22:33 2025] md: unbind<sdb3> [Mon Apr 7 11:22:33 2025] md: export_rdev(sdb3) [Mon Apr 7 11:22:33 2025] md/raid:md127: device sdc3 operational as raid disk 0 [Mon Apr 7 11:22:33 2025] md/raid:md127: device sdd3 operational as raid disk 1 [Mon Apr 7 11:22:33 2025] md/raid:md127: allocated 4294kB [Mon Apr 7 11:22:33 2025] md/raid:md127: not enough operational devices (2/4 failed) [Mon Apr 7 11:22:33 2025] RAID conf printout:The RAID system puts a transaction count on each disk, and updates that on every write to the disk. The "non-fresh" status means that some writes were missed on these two disks. That could be a result of the issue on 21 December, or it could have happened if the NAS wasn't properly shut down when you were troubleshooing the power problem.
Either way, it is possible to force the array to mount from tech support mode. If you want to pursue that path, let me know and I can give you advice over private message (using the envelope icon in the upper right of the forum page). There could be some damage to some files, since some writes were lost. But it is likely slight.
The other path would is RAID recovery. You'd have to buy some equipment and software to do that yourself, or you'd need to find a recovery service. You could mail them the disks to avoid the travel complexity. This is lower risk, but would cost. (And I do think the risk is slight if you are careful to follow my instructions).
xfixiate wrote:
My entire 60 years of life is on this - my kids pics, tax returns....As Sandshark says, you need a backup plan. Any device can fail at any time. After your data access is restored, we can provide some advice there. Options include a USB disk (either attached to the NAS or a PC), Cloud Storage, or some combination of both.
US pricing for 2 TB of cloud storage is about $10 USD per month, and that is likely enough to hold your most important files.
A huge shoutout to Stephen who has helped me get my NAS data back.
LIterally "saved" my life.
I could not be more grateful for his help and for the community here.
Cheers,
John W
Australia
I have a very similar if not identical issue as Johns above. If there is anyone out there who could help me get access to my data it would be much appriciated.
GG
If there is anyone out there who could help me get access to my data it would be much appriciated.
Start by downloading the full log zip file from the logs page.
If you want me to help, then put the full zip into cloud storage (dropbox, google drive, etc) and send me a private message (PM) with a link. Make sure the permissions are set so anyone with the link can download. You send a PM using the envelope icon in the upper right of forum page.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
