August 1, 201510 yr Trying to upgrade to the new version, all goes well except that a single drive is labeled as missing, but when reverting back to 5.0.6 all drives are seen and the array is fine
August 1, 201510 yr Please see Need help? Read me first!, and attach the diagnostics zip. One idea, perhaps the drive is attached to one of the suspect cards in this report. That would explain why it works in v5 but not v6. If it's on one of the suspect cards, you can confirm by turning off IOMMU.
August 1, 201510 yr Author The suspected drive is also attached to the onboard SATA along with these other 4 [*]ST2000VN000W1H25L8G (sdk) (2.0TB) WD20EFRX WCC4MC0SYP7T (sdm) (2.0TB) ST2000VN000b W1H25HFA (sdi) (2.0TB) ST2000DL0035YD4P5YS (sdj) Parity (2.0TB) [*]
August 4, 201510 yr Author Any idea on this? Switching back to 5.0.6 all drives are online and the array is fine, but going to 6.0.1 the one drive is missing. I have tried going back and forth a few times and its always the same issue. Should I remove the drive from the array in 5.0.6 and try adding it as a new drive in 6.0.1?
August 4, 201510 yr Community Expert One thing that occurred to me - I wonder how easy it would be to get a version of the diagnostics script that could be used on v5 systems. It would certainly make it easier to troubleshoot issues if the same basic set of files could be obtained for diagnostic purposes on both v5 and v6.
August 4, 201510 yr Community Expert Any idea on this? Switching back to 5.0.6 all drives are online and the array is fine, but going to 6.0.1 the one drive is missing. I have tried going back and forth a few times and its always the same issue. Should I remove the drive from the array in 5.0.6 and try adding it as a new drive in 6.0.1? You do know that unRAID will clear the drive if you add it, don't you?
August 4, 201510 yr Sorry, I've been dealing with flooding, and flood damage, and driving many hours through high water. But you've great help here, no need for me. As stated above, we need the syslog/diagnostics from v6.0.1, where it's not working, to see what the kernel is seeing (or not seeing). You provided a syslog from v5.0.6, where everything is working. That's still useful, for comparison. Off to work again ...
August 4, 201510 yr Author Yes I do know unraid will clear it when added. I will boot up 6.0.1 and grab a diag as requested
August 4, 201510 yr Author Diagnostics attached, oddly enough this time all disks are seen in the array devices listing, was able to start the array with no issues. Not sure if anything can be looked at in the diagnostics to see what happened the last couple times media-diagnostics-20150804-1311.zip
August 5, 201510 yr Diagnostics attached, oddly enough this time all disks are seen in the array devices listing, was able to start the array with no issues. Not sure if anything can be looked at in the diagnostics to see what happened the last couple times Always best to see the syslog that covers the period when the problem occurs. However, the new syslog does show something possibly mis-configured on that drive, perhaps causing inconsistent setup of it. From v5.0.6 - Aug 1 10:47:00 MEDIA kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 1 10:47:00 MEDIA kernel: ata4.00: ATA-9: WDC WD20EFRX-68EUZN0, WD-WCC4MC0SYP7T, 82.00A82, max UDMA/133 Aug 1 10:47:00 MEDIA kernel: ata4.00: 3907029168 sectors, multi 1: LBA48 NCQ (depth 31/32) Aug 1 10:47:00 MEDIA kernel: ata4.00: configured for UDMA/133 Aug 1 10:47:00 MEDIA kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD20EFRX-68E 82.0 PQ: 0 ANSI: 5 Aug 1 10:47:00 MEDIA kernel: sd 5:0:0:0: Attached scsi generic sg4 type 0 Aug 1 10:47:00 MEDIA kernel: sd 5:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Aug 1 10:47:00 MEDIA kernel: sd 5:0:0:0: [sde] 4096-byte physical blocks Aug 1 10:47:00 MEDIA kernel: sd 5:0:0:0: [sde] Write Protect is off Aug 1 10:47:00 MEDIA kernel: sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00 Aug 1 10:47:00 MEDIA kernel: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 1 10:47:00 MEDIA kernel: sde: sde1 Aug 1 10:47:00 MEDIA kernel: sd 5:0:0:0: [sde] Attached SCSI disk From v6.0.1 - Aug 4 13:08:45 MEDIA kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 4 13:08:45 MEDIA kernel: ata4.00: ATA-9: WDC WD20EFRX-68EUZN0, WD-WCC4MC0SYP7T, 82.00A82, max UDMA/133 Aug 4 13:08:45 MEDIA kernel: ata4.00: 3907029168 sectors, multi 1: LBA48 NCQ (depth 31/32) Aug 4 13:08:45 MEDIA kernel: ata4.00: n_sectors mismatch 3907029168 != 268435455 Aug 4 13:08:45 MEDIA kernel: ata4.00: revalidation failed (errno=-19) Aug 4 13:08:45 MEDIA kernel: ata4: limiting SATA link speed to 1.5 Gbps Aug 4 13:08:45 MEDIA kernel: ata4.00: limiting speed to UDMA/133:PIO3 ...[snipped, unrelated] Aug 4 13:08:45 MEDIA kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 4 13:08:45 MEDIA kernel: ata4.00: configured for UDMA/133 Aug 4 13:08:45 MEDIA kernel: scsi 4:0:0:0: Direct-Access ATA WDC WD20EFRX-68E 0A82 PQ: 0 ANSI: 5 Aug 4 13:08:45 MEDIA kernel: sd 4:0:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Aug 4 13:08:45 MEDIA kernel: sd 4:0:0:0: Attached scsi generic sg8 type 0 Aug 4 13:08:45 MEDIA kernel: sd 4:0:0:0: [sdi] 4096-byte physical blocks Aug 4 13:08:45 MEDIA kernel: sd 4:0:0:0: [sdi] Write Protect is off Aug 4 13:08:45 MEDIA kernel: sd 4:0:0:0: [sdi] Mode Sense: 00 3a 00 00 Aug 4 13:08:45 MEDIA kernel: sd 4:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 4 13:08:45 MEDIA kernel: sdi: sdi1 Aug 4 13:08:45 MEDIA kernel: sd 4:0:0:0: [sdi] Attached SCSI disk Except for the part in bold it's essentially identical, should work fine but possibly a bit slower. I have no idea why a reported sector count mismatch (reported vs actual, I believe) should cause a speed drop, they're unrelated. Since it failed to set up in time once, and only succeeded this time after a delay and with a minor issue, I'm not sure you can count on the drive yet. Further testing should determine how reliably it shows up. You might try an hdparm option that reports most drive parameters, hdparm -I /dev/sd*, and compare it with the identical model, Disk 11.
August 6, 201510 yr Don't know what to say, looks identical. Might as well use and test it, but confidence in that drive is not high. Last option is give it a kick!
August 6, 201510 yr Author Thanks Rob for all the help, I will keep an eye on the drive and continue to use version 6. Ill mark the topic as solved
Archived
This topic is now archived and is closed to further replies.