NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN102 broken after OS 6.10.4 update
My RN102 appears to be broken after updated to 6.10.4. Not sure which came first, I updated the OS to 6.10.4 and noticed very slow transfer speed when I copied hundreds of JPEG images from the SD card on my PC to the NAS. I know the RN102 is not exctly a speed demon but it was annoying slow, only 25 MB/s as measured by NASTester 1.7. Other posts in the community suggests around 60 to 70 MB/s. The reported negotiated speed is 1 Gps as reported by Windows 10.
To rule out problems with LAN hardware, I connected the PC directly to the NAS with a CAT 6e cable but the speed did not change much. I then ran the same test from a laptop connecting to the LAN via 5GHz WiFi and the reported speed was similar, albeit a bit slower. I concluded the bottle neck is unlikely to be LAN hardware.
I suspect the next step is probably what broke the camel's back. In an attempt to improve read/write speed, I disabled Bit Rot Protection on all Shares and things took a dive from there. The NAS hangs up whenever reading/writing multiple files but single file read/write is fine. When it hangs up, the Admin page is not accessible but I can still ping the NAS. To shut it down requires disconnecting power, it will not respond to the power button shutdown sequence, or it will take so long that I do not bother to wait.
Honeslty I do not know where to go from here. I hate the idea of reinstalling the OS because I will lose all data, as I do not have a back up. The file system appears to be intact and the files are still accessible but they can only be accessed one by one and that is not terribly useful. I have not re-enabled Bit Rot Protection to see what will happen.
Any suggestions are welcomed.
39 Replies
Have you downloaded the log zip file, and looked for btrfs and disk-related errors in system.log and kernel.log?
What apps are installed?
I downloaded the log System_log-nas-36-1C-14-20210429-072924.zip this morning but I don't know exactly what to look for. The Log page in Admin looks fine to me; no error, no warning. By the way, the OS was updated on 25/4 6:39pm but the log was not retrieved until 29/4 4:7:29am so there is big chunk of information missing. The only app installed is Transmission.
dstsui wrote:
I downloaded the log System_log-nas-36-1C-14-20210429-072924.zip this morning but I don't know exactly what to look for. The Log page in Admin looks fine to me; no error, no warning. By the way, the OS was updated on 25/4 6:39pm but the log was not retrieved until 29/4 4:7:29am so there is big chunk of information missing. The only app installed is Transmission.
I redacted your download link (the full log zip shouldn't be posted publicly). But I did take a look.
kernel.log has a lot of errors on disk 1 (sda). For instance, this segement
Apr 27 10:30:23 nas-36-1C-14 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 27 10:30:23 nas-36-1C-14 kernel: ata1.00: irq_stat 0x40000001 Apr 27 10:30:23 nas-36-1C-14 kernel: ata1.00: failed command: READ DMA EXT Apr 27 10:30:23 nas-36-1C-14 kernel: ata1.00: cmd 25/00:40:a8:6d:2b/00:05:67:00:00/e0 tag 26 dma 688128 in res 51/40:0f:d8:70:2b/00:02:67:00:00/e0 Emask 0x9 (media error) Apr 27 10:30:23 nas-36-1C-14 kernel: ata1.00: status: { DRDY ERR } Apr 27 10:30:23 nas-36-1C-14 kernel: ata1.00: error: { UNC } Apr 27 10:30:23 nas-36-1C-14 kernel: ata1.00: configured for UDMA/133 Apr 27 10:30:23 nas-36-1C-14 kernel: sd 0:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 27 10:30:23 nas-36-1C-14 kernel: sd 0:0:0:0: [sda] tag#26 Sense Key : Medium Error [current] [descriptor] Apr 27 10:30:23 nas-36-1C-14 kernel: sd 0:0:0:0: [sda] tag#26 Add. Sense: Unrecovered read error - auto reallocate failed Apr 27 10:30:23 nas-36-1C-14 kernel: sd 0:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 67 2b 6d a8 00 05 40 00 Apr 27 10:30:23 nas-36-1C-14 kernel: blk_update_request: I/O error, dev sda, sector 1730900184 Apr 27 10:30:23 nas-36-1C-14 kernel: md/raid1:md127: sda3: rescheduling sector 1721199976I suggest powering down the NAS and testing it in a Windows PC (either connected with SATA or a USB adapter/dock) with Lifeguard.
Alternatively, you could try rebooting the NAS w/o it, (leaving disk 2 in slot 2), and see if you get a more normal speed.
When you replace the disk, avoid the WD20EFAX - it is an SMR drive. A Red Plus drive (another WD20EFRX or WD20EFZX) would be fine.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
