RN102 broken after OS 6.10.4 update

---

StephenB wrote:

---

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 1721199976

 I 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.

---

Do you think the NAS will boot up with Disk 1 taken out? Did you observe similar errors in Disk 2? How likely do you think the problem with the NAS hanging when reading/writing multiple files is related to errors in Disk 1?

What is preferred way of posting a file (other than an image) on the forum?