NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN104 data recovery with single RAID1 volume
Hello all, I have a ReadyNAS 104 with firmware version 6.5.0 It has 2 x WD Red NAS drives WD30EFRX 3TB. One of the drives started showing degraded errors and by the time I tried to copy my dat...
StephenB wrote:I am confused on your pathway.
The whole point of purchasing ReclaiMe was to use it to recover files from the damaged file system. That doesn't require mounting it.
Sorry for my long-winded post. I have recovered the files from the original 3TB drive from my RN to the new 4TB drive in the DS220+. However, testing my new 4TB drive still shows bad sectors and it cannot be mounted by BRTFS. I am not comfortable ignoring these errors in case I need to recover data again from the new 4TB drive, and I also want to be able to transfer data from it on the Linux box for faster backups in the future.
In short, my question is: Should I try to repair these bad sectors on the new 4TB drive?
My other option B is to copy again everything to a drive I have checked for errors which I hope will be able to be mounted on the Linux box
CircuitBreaker wrote:I have recovered the files from the original 3TB drive from my RN to the new 4TB drive in the DS220+.
Great, I somehow missed that.
CircuitBreaker wrote:
However, testing my new 4TB drive still shows bad sectors and it cannot be mounted by BRTFS. I am not comfortable
I am not seeing any evidence of bad sectors in your posts. Can you give more info on that?
Generally if you are suspecting bad sectors (perhaps seeing them in smart stats, or WD's Dashboard software. or disk errors in the logs), then the best strategy is to exchange the disk with the seller if you are still within the return period. Otherwise pursue a warranty replacement with WD.
If I am reading your post correctly, the drive was formatted/installed on the Synology, correct? Then you copied the data to the Synology data volume with ReclaiMe. If that is correct, then you should see these errors in the Synology logs. Have you looked there?
ReadyNAS volumes (even JBOD) always need to be assembled with mdadm first, and then you mount the mdadm array. I don't own Synology, so I don't know how they handle this. You should make sure you are using the correct mounting procedure in the Synology forum.
I am hoping you didn't purchase a WD Red. Current WD Red drives use SMR (shingled magnetic recording), which often misbehaves in RAID configurations. WD Red Plus and WD Red Pro are CMR, so don't have this issue.
CircuitBreaker wrote:
However, testing my new 4TB drive still shows bad sectors and it cannot be mounted by BRTFS. I am not comfortableI am not seeing any evidence of bad sectors in your posts. Can you give more info on that?
I followed the process as described in this thread with mdadm but did not post all commands before the `mount` attempt. The dmesg output was in one of my previous posts but also adding it here for clarity. It seems that there are some corrupt blocks (leafs) and root flag errors - I am not sure if they can be repaired:
[ 2072.479819] BTRFS info (device dm-1): using crc32c (crc32c-intel) checksum algorithm [ 2072.479832] BTRFS info (device dm-1): using free space tree [ 2072.493260] BTRFS critical (device dm-1): corrupt leaf: root=1 block=163692544 slot=17, invalid root flags, have 0x400000000 expect mask 0x1000000000001 [ 2072.493272] BTRFS error (device dm-1): read time tree block corruption detected on logical 163692544 mirror 1 [ 2072.497822] BTRFS critical (device dm-1): corrupt leaf: root=1 block=163692544 slot=17, invalid root flags, have 0x400000000 expect mask 0x1000000000001 [ 2072.497831] BTRFS error (device dm-1): read time tree block corruption detected on logical 163692544 mirror 2 [ 2072.497854] BTRFS warning (device dm-1): couldn't read tree root [ 2072.498374] BTRFS error (device dm-1): open_ctree failedThe 4TB drive was installed/formatted in Synology but I did not do any error checks. I will check the Synology logs for errors.
It is a WD Red WD40EFRX and I bought it a couple of years ago as a spare for emergencies like this one. I will check it for errors with the WD Dashboard and see if it is still under warranty. Thanks!
CircuitBreaker wrote:
I followed the process as described in this thread with mdadm but did not post all commands before the `mount` attempt. The dmesg output was in one of my previous posts but also adding it here for clarity. It seems that there are some corrupt blocks (leafs) and root flag errors - I am not sure if they can be repaired:Clearly there is a problem here. But unless you have more data you haven't posted, you are leaping to a conclusion when you attribute this to bad sectors on the disk. You aren't reporting any read errors, and you haven't checked for write errors on the Synology. A bad disk is one possibility, but there are others.
FWIW, I always test my own disk using vendor tools before installing them in the NAS. That includes the full long non-destructive diag and when possible, the full write zeros test. (I prefer the older Lifeguard WD software over their Dashboard, as WD removed the write test in Dashboard). I have found some out-of-the-box disks that pass one of thest tests, but fail the others.
As I said, I don't know the steps needed to mount a synology drive. I am thinking the superblock issue you posted before this snippet perhaps needs to be explored first. But first I'd put it back in the Synology and see if it mounts there when you boot the NAS. If it does, then then almost certainly is due to the mounting steps you are using
While the disk is installed, you could also use smartctl on the synology to run the full non-destructive disk test, if that is more convenient than doing that test with WD software on a PC..
Since I installed it, the 4TB drive has mounted without problems on the Synology NAS. I only see issues when trying to mount it on the Linux machine.
I also could not find any problems with the 4TB drive in the Synology logs:
Info System 2024/06/10 00:51:16 xxxxx System starts to optimize [Storage Pool 1]. Info System 2024/06/10 00:51:16 xxxxx System successfully created [Volume 1] on [Storage Pool 1]. Info System 2024/06/10 00:51:16 xxxxx System successfully created [Storage Pool 1](Device Type is [SHR]) with drive [SynologyNAS: 1]. Info System 2024/06/10 00:50:50 xxxxx System starts to create [Volume 1] on [Storage Pool 1]. Info System 2024/06/10 00:50:48 xxxxx System starts to create [Storage Pool 1](Device Type is [SHR]) with drive [SynologyNAS: 1].Now I am running an extended SMART scan and will report back
CircuitBreaker wrote:
Since I installed it, the 4TB drive has mounted without problems on the Synology NAS. I only see issues when trying to mount it on the Linux machine.
Then I think you are just needing to do something different in your commands.
There is a guide here:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
