NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN312 random volume degraded with no indication why
RN312 (2x 2TB RAID1) now reporting volume degraded, but interface gives no clues as to why. I can see a picture of two drives, one grey, one blue, both with green "leds". Hovering over both shows bot...
Regis-IT wrote:
Many thanks StephenB, PM sent.
dmesg.log (among others) is flooded with unrecoverable read errors on disk 1 (sda, serial # WD-WCC4N7VXZF16)
[Mon Jul 8 11:07:43 2024] do_marvell_9170_recover: ignoring PCI device (8086:3a22) at PCI#0 [Mon Jul 8 11:07:43 2024] ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x0 [Mon Jul 8 11:07:43 2024] ata1.00: irq_stat 0x40000008 [Mon Jul 8 11:07:43 2024] ata1.00: failed command: READ FPDMA QUEUED [Mon Jul 8 11:07:43 2024] ata1.00: cmd 60/01:70:4f:00:90/00:00:00:00:00/40 tag 14 ncq 512 in res 41/40:00:4f:00:90/00:00:00:00:00/40 Emask 0x409 (media error) [Mon Jul 8 11:07:43 2024] ata1.00: status: { DRDY ERR } [Mon Jul 8 11:07:43 2024] ata1.00: error: { UNC } [Mon Jul 8 11:07:43 2024] ata1.00: configured for UDMA/133 [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 Sense Key : Medium Error [current] [descriptor] [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 CDB: Read(16) 88 00 00 00 00 00 00 90 00 4f 00 00 00 01 00 00 [Mon Jul 8 11:07:43 2024] blk_update_request: I/O error, dev sda, sector 9437263So you need to replace this disk.
WD no longer makes WD30EFRX. If you want to stick with WD 3 TB, then good options are the WD30EFPX or WD30EFZX (WD Red Plus drives that replace the WD30EFRX). Avoid the WD Red version (WD30EFAX) as this is SMR, and not a good option for RAID.
There's no problem with mixing WD and Seagate in the same array so you can also get the Seagate Ironwolf (ST3000VN006).
If you get a larger drive, you won't get additional space until you replace sdb with one of the same size.
Netgear recommends making sure you have an up-to-date backup before manipulating disks, and I agree. At the moment your array is unprotected, and that will continue until the problem drive is replaced and synced to drive 2.
Regis-IT wrote:
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid1 sdb3[1]
2925414784 blocks super 1.2 [2/1] [_U]
This is telling you that the first disk (sda with serial WD-WCC4N7VXZF16) has dropped out of the array.
It's not enough to tell you why that happened (or exactly when). There could be more information on that in
- dmesg.log
- kernel.log
- readynasd.log
- status.log
- system.log
- systemd-journal.log
but as you say, it can be hard to interpret. If you want me to take a look, you could put the entire zip into cloud storage and send me the link in a PM (private message) using the envelope icon in the upper right of the forum page. Make sure the permission is set so anyone with the link can download.
Regis-IT wrote:
Many thanks StephenB, PM sent.
dmesg.log (among others) is flooded with unrecoverable read errors on disk 1 (sda, serial # WD-WCC4N7VXZF16)
[Mon Jul 8 11:07:43 2024] do_marvell_9170_recover: ignoring PCI device (8086:3a22) at PCI#0 [Mon Jul 8 11:07:43 2024] ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x0 [Mon Jul 8 11:07:43 2024] ata1.00: irq_stat 0x40000008 [Mon Jul 8 11:07:43 2024] ata1.00: failed command: READ FPDMA QUEUED [Mon Jul 8 11:07:43 2024] ata1.00: cmd 60/01:70:4f:00:90/00:00:00:00:00/40 tag 14 ncq 512 in res 41/40:00:4f:00:90/00:00:00:00:00/40 Emask 0x409 (media error) [Mon Jul 8 11:07:43 2024] ata1.00: status: { DRDY ERR } [Mon Jul 8 11:07:43 2024] ata1.00: error: { UNC } [Mon Jul 8 11:07:43 2024] ata1.00: configured for UDMA/133 [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 Sense Key : Medium Error [current] [descriptor] [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed [Mon Jul 8 11:07:43 2024] sd 0:0:0:0: [sda] tag#14 CDB: Read(16) 88 00 00 00 00 00 00 90 00 4f 00 00 00 01 00 00 [Mon Jul 8 11:07:43 2024] blk_update_request: I/O error, dev sda, sector 9437263So you need to replace this disk.
WD no longer makes WD30EFRX. If you want to stick with WD 3 TB, then good options are the WD30EFPX or WD30EFZX (WD Red Plus drives that replace the WD30EFRX). Avoid the WD Red version (WD30EFAX) as this is SMR, and not a good option for RAID.
There's no problem with mixing WD and Seagate in the same array so you can also get the Seagate Ironwolf (ST3000VN006).
If you get a larger drive, you won't get additional space until you replace sdb with one of the same size.
Netgear recommends making sure you have an up-to-date backup before manipulating disks, and I agree. At the moment your array is unprotected, and that will continue until the problem drive is replaced and synced to drive 2.
Many thanks - much appreciated. Would be more helpful if this was exposed on the interface rather than buried in log files! Along with logs marrying up so one doesn't say it's clean while another says it's failing! 🙂
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
