NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN104 Remove inactive volumes Disk 3,4
Hi everyone, one of my 4 2TB drives (#2) failed in my RN104. I went ahead and bought a replacement, but after insertion it looks like i get the "remove inactive volumes disk 3,4"; with some of my dr...
schtroumpfmoi wrote:
Sep 22 13:17:49 NAS mdadm[2171]: Fail event detected on md device /dev/md0, component device /dev/sdc1
[Fri Sep 22 13:50:34 2023] sd 3:0:0:0: [sdd] tag#13 Add. Sense: Unrecovered read error - auto reallocate failed
So both sdc and sdd are detected as failed. Unfortunately not a good sign. It'd have been better if one of the disks was just out of sync.
I'm not sure if either of these is disk 1, you might want to double-check that by looking at disk-info.log.
schtroumpfmoi wrote:
I guess my main question now is: is there still a way i can force a rebuild / should i try to remove/readd the faulty disk ?
With single redundancy, you need three working disks to rebuild the fourth. You don't have that.
If the disks can be read at all, you could try cloning one or both. That might help with recovery.
RAID recovery software like ReclaiMe might be able to recover some data from the two remaining disks - not sure. You can download it and see before you pay for it. You would need a way to connect the disks to a PC (directly with SATA, or using a USB adapter/dock).
Hi again,
Here is the extract of mdadm errors from system.log:
Sep 22 13:17:49 NAS mdadm[2171]: Fail event detected on md device /dev/md0, component device /dev/sdc1
Sep 22 13:17:50 NAS disk_event_handler[19813]: mdadm: set 8:34 faulty in /dev/md1
Sep 22 13:17:50 NAS mdadm[2171]: Fail event detected on md device /dev/md1, component device /dev/sdc2
Sep 22 13:18:00 NAS mdadm[2171]: NewArray event detected on md device /dev/md1
Sep 22 13:18:06 NAS mdadm[2171]: RebuildStarted event detected on md device /dev/md1, component device resync
Sep 22 13:18:58 NAS mdadm[2171]: RebuildFinished event detected on md device /dev/md1, component device resync
Sep 22 13:29:16 NAS disk_event_handler[31784]: mdadm: hot removed 8:33 from /dev/md0
Sep 22 13:29:16 NAS disk_event_handler[31784]: mdadm: hot removed 8:35 from /dev/md127
Sep 22 13:37:50 NAS mdadm[2119]: NewArray event detected on md device /dev/md0
Sep 22 13:37:51 NAS mdadm[2119]: DegradedArray event detected on md device /dev/md0
Sep 22 13:37:51 NAS mdadm[2119]: NewArray event detected on md device /dev/md1
Below are some items i thought would be relevant from the other logs, the main one being
[Fri Sep 22 13:36:22 2023] md/raid:md127: not enough operational devices (2/4 failed)
I guess my main question now is: is there still a way i can force a rebuild / should i try to remove/readd the faulty disk ?
Or is it just trying to reclaim data off the two valid disks and pray something is still readable ?
Many thanks for any insights...
DMESG [Fri Sep 22 13:36:18 2023] Buffer I/O error on dev sdd3, logical block 1, async page read —> 20 of these
[Fri Sep 22 13:50:34 2023] sd 3:0:0:0: [sdd] tag#13 Add. Sense: Unrecovered read error - auto reallocate failed
[Fri Sep 22 13:36:18 2023] blk_update_request: I/O error, dev sdd, sector 9437257
[Fri Sep 22 13:36:22 2023] md/raid:md127: device sda3 operational as raid disk 0
[Fri Sep 22 13:36:22 2023] md/raid:md127: device sdb3 operational as raid disk 1
[Fri Sep 22 13:36:22 2023] md/raid:md127: not enough operational devices (2/4 failed)
SYSTEM
Mostly « THROW: open failed path:/data/Pictures errno:2 (No such file or directory) » (and others errors related to my top folders being missing)
KERNEL
Lots of these:
Sep 22 13:44:07 NAS kernel: sd 3:0:0:0: [sdd] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 22 13:44:07 NAS kernel: sd 3:0:0:0: [sdd] tag#15 Sense Key : Medium Error [current] [descriptor]
Sep 22 13:44:07 NAS kernel: sd 3:0:0:0: [sdd] tag#15 Add. Sense: Unrecovered read error - auto reallocate failed
Sep 22 13:44:07 NAS kernel: sd 3:0:0:0: [sdd] tag#15 CDB: Read(10) 28 00 00 90 00 48 00 00 08 00
Sep 22 13:44:07 NAS kernel: blk_update_request: I/O error, dev sdd, sector 9437257
Sep 22 13:44:07 NAS kernel: Buffer I/O error on dev sdd3, logical block 1, async page read
SYSTEMD JOURNAL
Mostly « open failed » on the top folders
STATUS:
[23/07/22 20:40:07 CEST] warning:disk:LOGMSG_SMART_ATA_ERR_30DAYS_WARN Detected increasing ATA error count: [62418] on disk 1 (Internal) [WDC WD20EFRX-68EUZN0, WD-WCC4M6EZU2XC] 20733 times in the past 30 days. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data
schtroumpfmoi wrote:
Sep 22 13:17:49 NAS mdadm[2171]: Fail event detected on md device /dev/md0, component device /dev/sdc1
[Fri Sep 22 13:50:34 2023] sd 3:0:0:0: [sdd] tag#13 Add. Sense: Unrecovered read error - auto reallocate failed
So both sdc and sdd are detected as failed. Unfortunately not a good sign. It'd have been better if one of the disks was just out of sync.
I'm not sure if either of these is disk 1, you might want to double-check that by looking at disk-info.log.
schtroumpfmoi wrote:
I guess my main question now is: is there still a way i can force a rebuild / should i try to remove/readd the faulty disk ?
With single redundancy, you need three working disks to rebuild the fourth. You don't have that.
If the disks can be read at all, you could try cloning one or both. That might help with recovery.
RAID recovery software like ReclaiMe might be able to recover some data from the two remaining disks - not sure. You can download it and see before you pay for it. You would need a way to connect the disks to a PC (directly with SATA, or using a USB adapter/dock).
Quick update to say that after scanning the drives with R-Studio (one by one linked with a USB to SATA adapter) i could not see the files i was looking for... So I am rebuilding the NAS clean and I fixed the email issue that had caused me not to be notified of the first signs back in July.
Thanks a lot for the insights anyways !
schtroumpfmoi wrote:
Quick update to say that after scanning the drives with R-Studio (one by one linked with a USB to SATA adapter) i could not see the files i was looking for...
You chose the wrong RAID recovery tool. OS-6 uses BTRFS for the data volume, and R-Studio doesn't support that file system.
ReclaiMe might have worked.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
