Update 2022.10.07: Never mind, after extensive testing of the disk with smartctl and badblocks with no errors found, I am now fairly confident that the errors originated from failing electronics or SATA contacts issues in the WD case. Discarding and replacing with a new NAS.
Hi, and thanks for all the great help and knowledge about the WD My Book Live here that has helped me a lot over the years!!
The last couple of days my aging WBL(10+ years) has started eliciting new and odd behavior. Almost every night it ends up not being reachable anymore either by ssh, the web admin interface or any of the shares. It only responds to pings, and I have to cut and reenable power to get it back online again.
The actual hard drive inside my MBL is pretty new, around 6 months old, and the combination has been working well until the last couple of days.
The last messages from the logs before a new reboot typically are, maybe indicating something with the sata connection, which I am unable to interpret, find any information about or fix:
Sep 21 23:17:13 SviskeNAS logger: exit standby after 365 (since 2022-09-21 23:11:08.860949593 +0200)
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect errors: DIAGN DIAGW DIAGX
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:16:47 SviskeNAS kernel: ata2: Freeze port with 1 QCs aborted
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect errors: ERRM DIAGN DIAGW DIAGX
Sep 22 00:16:47 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:16:47 SviskeNAS kernel: sata-dwc 4bffd1800.sata: Detect recovered communication error
Sep 22 00:16:47 SviskeNAS kernel: ata2: Freeze port with 0 QCs aborted
Sep 22 00:16:47 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:16:53 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:16:56 SviskeNAS kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0310)
Sep 22 00:16:56 SviskeNAS kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x40)
Sep 22 00:17:01 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:05 SviskeNAS kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0310)
Sep 22 00:17:05 SviskeNAS kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x40)
Sep 22 00:17:05 SviskeNAS kernel: ata2.00: limiting speed to UDMA/133:PIO2
Sep 22 00:17:10 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:16 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:17:20 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:26 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect errors: DIAGN DIAGW DIAGX
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:17:27 SviskeNAS kernel: ata2: Freeze port with 0 QCs aborted
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect errors: ERRM DIAGN DIAGW DIAGX
Sep 22 00:17:27 SviskeNAS kernel: ata2: Detect hot plug signal
Sep 22 00:17:27 SviskeNAS kernel: sata-dwc 4bffd1800.sata: Detect recovered communication error
Sep 22 00:17:27 SviskeNAS kernel: ata2: Freeze port with 0 QCs aborted
Sep 22 00:17:30 SviskeNAS kernel: ata2: hard resetting link
Sep 22 00:17:36 SviskeNAS kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 22 00:17:48 SviskeNAS kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0310)
Sep 22 00:17:49 SviskeNAS kernel: ata2.00: configured for UDMA/133
Sep 22 00:17:49 SviskeNAS kernel: ata2: EH complete
Sep 22 00:17:49 SviskeNAS logger: exit standby after 3032 (since 2022-09-21 23:27:17.132949579 +0200)
Sep 22 03:00:16 SviskeNAS logger: exit standby after 9083 (since 2022-09-22 00:28:52.992950114 +0200)I also noticed for the first time this message, where I was able to unmount and fix the data partition with fsck, but I am unable to forcfsck on boot the /dev/md0 raid partition:
Sep 21 16:02:23 SviskeNAS kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommendedJust wondering if anyone here has experience with something similar, and whether it is fixable, something wrong with my hard drive, or if it is finally the end of the line for my WD MBL case this time?
