Any hardware diagnostics available

[wde]

My 10 year old AS602T is dying. It's no longer getting updates (except a few security updates re ransomeware).
2-bay nas configured Raid1, 2X3TB WD RED
About 2 months ago, one of the disks became unavailable, Raid was degraded.
Disk Doctor and DR Asustor shows everything good.
Tried using each disk in each of the two drives. A few times it would start up and run for a while, then each of the disks would be unavailable in either drive.
After Asustor suggested running test on both drives (both showed good) and looking at Health Record they couldn't determine the problem.
I bit the bullet and bought 2 new WD RED Plus drives. I had backups so just initialized the new drives in Raid1 and reset up everying as if new.
This worked great for one week. First 1 drive, and then 2 drives show as inaccessible. System degraded then System error.
Tried setting up one of the new drives as JOBD in slot one. Worked for a few days then inaccessible, System error
Tried setting up the other new drive as JOBD in slot two. Worked for a day then inaccessible. System error.

I've looked at the exported heath records but could see no hardware errors.
Are there any hardware diagnostics I could run that might pinpoint the problem?.

Or, now that I have 4 disks, probably all just fine, should I upgarde to a Lockerstore 4 Gen 2 ?
10 years was a good run.

[Nazar78]

Could it be some dirty/worn-out sata slot connectors?

When the issue happen, SSH as root then check the status of:

Code: Select all

dmesg|grep -Ei '(error|warning)'

[wde]

Could it be some dirty/worn-out sata slot connectors?

When the issue happen, SSH as root then check the status of:

Code: Select all

dmesg|grep -Ei '(error|warning)'

Code: Select all

/volume1$ dmesg|grep -Ei '(error|warning)'
[    0.000000] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20130725/tbfadt-653)
[    8.050276] GPT: Use GNU Parted to correct GPT errors.
[   38.585865] iscsi-scst: ***WARNING***: CONFIG_TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION not enabled in your kernel. ISCSI-SCST will be working with not the best performance. Refer README file for details.
[23478.821654] ata7: SError: { RecovComm PHYRdyChg 10B8B Dispar }

**sorry** this is the status right now. If I get the error again I'll run it again if I can get in using SSH.
Thanks

[wde]

Ran for a day. Beeping again, front flashing red.
One brand new disk in slot 1 using JOBD
I've tried single new disks in both slots.

Code: Select all

/volume1$ dmesg|grep -Ei '(error|warning)'
[    0.000000] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20130725/tbfadt-653)
[    8.050276] GPT: Use GNU Parted to correct GPT errors.
[   38.585865] iscsi-scst: ***WARNING***: CONFIG_TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION not enabled in your kernel. ISCSI-SCST will be working with not the best performance. Refer README file for details.
[23478.821654] ata7: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[77920.909539] ata7: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[77934.736501] ata7: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[77941.528269] ata7: SError: { RecovComm PHYRdyChg CommWake 10B8B Dispar Handshk DevExch }
[77945.242797] ata7: SError: { PHYRdyChg CommWake DevExch }
[77946.138901] ata7: SError: { PHYRdyChg CommWake 10B8B Dispar DevExch }
[77947.902028] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[77953.968245] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[77959.201989] md: super_written gets error=-5, uptodate=0
[77959.417252] md: super_written gets error=-19, uptodate=0
[77962.896519] ata7: SError: { CommWake DevExch }
[77963.569572] md: super_written gets error=-19, uptodate=0
[77963.579539] Buffer I/O error on device md0, logical block 196608
[77963.585606] lost page write due to I/O error on md0
[77963.590535] JBD2: Error -5 detected when updating journal superblock for md0-8.
[77963.780419] md: super_written gets error=-19, uptodate=0
[77964.248166] ata7: SError: { PHYRdyChg CommWake DevExch }
[77969.937721] ata7: SError: { RecovComm PHYRdyChg 10B8B Dispar Handshk }
[77969.949472]          res 40/00:c0:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[77971.735208] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[77980.822138] ata7.00: irq_stat 0x48000000, interface fatal error
[77980.828128] ata7: SError: { 10B8B Dispar Handshk TrStaTrns }
[77980.839041]          res 40/00:20:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[77983.130420] ata7.00: irq_stat 0x48000000, interface fatal error
[77983.136416] ata7: SError: { 10B8B Dispar Handshk TrStaTrns }
[77983.147266]          res 40/00:28:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[77984.180356] ata7.00: irq_stat 0x48000000, interface fatal error
[77984.186322] ata7: SError: { Handshk TrStaTrns }
[77984.196098]          res 40/00:30:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[77992.629289] ata7: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[77999.276205] ata7: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[78007.205226] md: super_written gets error=-19, uptodate=0
[78007.210704] Buffer I/O error on device md0, logical block 0
[78007.216318] lost page write due to I/O error on md0
[78007.221253] EXT4-fs error (device md0): ext4_journal_check_start:56: Detected aborted journal
[78007.235409] EXT4-fs (md0): previous I/O error to superblock detected
[78007.241842] Buffer I/O error on device md0, logical block 0
[78007.247432] lost page write due to I/O error on md0
[78007.441963] md: super_written gets error=-19, uptodate=0
[78016.853788] ata7: SError: { CommWake DevExch }
[78017.855346] ata7: SError: { PHYRdyChg CommWake DevExch }
[78018.740523] ata7: SError: { PHYRdyChg CommWake DevExch }
[78059.729198] ata7: SError: { PHYRdyChg CommWake DevExch }

[Nazar78]

Looks like hardware issues. As mentioned check your sata connections. It also could be fault with the new disks, yes I had two new sealed disks getting bad sectors after about a month in-between.

[wde]

I was getting this error on the older disk - bought 2 new and reinitialized to try and solve the problem.
How do I check the sata connections?

[Nazar78]

Try booting your NAS using Live USB or any modern Linux installers like Ubuntu Desktop (choose the try option). Then monitor again, this is to eliminate any OS/firmware software issues but I doubt it is.

As for the connectors, probably the same way you would clean a typical motherboard. I would dust off with compressed air. If the connectors are oxidized, you can carefully use cotton buds with electrical contact cleaners. Also check if any of them are loose or bent pin contacts. Turn off the NAS before cleaning.