Hi all,

 

I'm coming over from FreeNAS and trying to get off the ground.  I followed the instructions in the startup tutorial videos and all went well, until the parity sync.  One of my drives got a red x next to it and the system said parity failed (or something similar).

 

I thought I'd try from scratch.  Pulled all drives, formatted, ran chkdsk /f and WD Disk Util, passed both.

 

Formatted the SD card, reinstalled unRAID and tried again... but this time a different disk failed (I know it's a different disk as 3 are WD and the first time it was one of those, but my fourth disk (assigned to parity disk) is the same size (3TB) but a HGST.

 

So again, the first time a WD drive got the red x, now its the HGST (less than 1 year old).

 

Anyone have thoughts?

 

Also, the SMART test's aren't working anymore on any of the drives... before I was downloading them and getting normal outputs on all disks... now I get:

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build)

Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

 

=== START OF INFORMATION SECTION ===

Vendor:              /11:0:0:

Product:              0

User Capacity:        600,332,565,813,390,450 bytes [600 PB]

Logical block size:  774843950 bytes

Physical block size:  3166222336 bytes

Lowest aligned LBA:  12346

scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46

scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46

>> Terminate command early due to bad response to IEC mode page

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

And under show SMART error log I get:

scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46

 

I'm NEW to unRAID (48 hours new)... here's the log if that helps.

 

Thank you for your help in advance!

 

John

 

Aug 22 08:43:18 Tower kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Aug 22 08:43:18 Tower kernel: ata10.00: revalidation failed (errno=-5)

Aug 22 08:43:18 Tower kernel: ata10: limiting SATA link speed to 3.0 Gbps

Aug 22 08:43:18 Tower kernel: ata10: hard resetting link

Aug 22 08:43:18 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Aug 22 08:43:18 Tower kernel: ata9.00: revalidation failed (errno=-5)

Aug 22 08:43:18 Tower kernel: ata9: limiting SATA link speed to 3.0 Gbps

Aug 22 08:43:18 Tower kernel: ata9: hard resetting link

Aug 22 08:43:18 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Aug 22 08:43:18 Tower kernel: ata12.00: revalidation failed (errno=-5)

Aug 22 08:43:18 Tower kernel: ata12: limiting SATA link speed to 3.0 Gbps

Aug 22 08:43:18 Tower kernel: ata12: hard resetting link

Aug 22 08:43:18 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320)

Aug 22 08:43:18 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 320)

Aug 22 08:43:18 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 320)

Aug 22 08:43:48 Tower kernel: ata9.00: qc timeout (cmd 0xec)

Aug 22 08:43:48 Tower kernel: ata10.00: qc timeout (cmd 0xec)

Aug 22 08:43:48 Tower kernel: ata12.00: qc timeout (cmd 0xec)

Aug 22 08:43:49 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Aug 22 08:43:49 Tower kernel: ata9.00: revalidation failed (errno=-5)

Aug 22 08:43:49 Tower kernel: ata9.00: disabled

Aug 22 08:43:49 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Aug 22 08:43:49 Tower kernel: ata12.00: revalidation failed (errno=-5)

Aug 22 08:43:49 Tower kernel: ata12.00: disabled

Aug 22 08:43:49 Tower kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Aug 22 08:43:49 Tower kernel: ata10.00: revalidation failed (errno=-5)

Aug 22 08:43:49 Tower kernel: ata10.00: disabled

Aug 22 08:43:49 Tower kernel: ata9: hard resetting link

Aug 22 08:43:49 Tower kernel: ata12: hard resetting link

Aug 22 08:43:49 Tower kernel: ata10: hard resetting link

Aug 22 08:43:50 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320)

Aug 22 08:43:50 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 320)

Aug 22 08:43:50 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 320)

Aug 22 08:43:51 Tower kernel: ata9: EH complete

Aug 22 08:43:51 Tower kernel: ata12: EH complete

Aug 22 08:43:51 Tower kernel: ata10: EH complete

Aug 22 08:47:31 Tower emhttp: mdcmd: write: Input/output error

Aug 22 08:47:31 Tower kernel: mdcmd (38): spindown 0

Aug 22 08:47:31 Tower kernel: md: disk0: ATA_OP e0 ioctl error: -5

 

Attaching diagnostic would help.

 

Also, check your cable / port. Plug the redballed disk to a different SATA port.

 

Thanks for the quick reply!

 

I'll move the SATA cable for that drive over to another port and try again, but before I do, how to I run diagnostics?

 

Attaching diagnostic would help.

 

Also, check your cable / port. Plug the redballed disk to a different SATA port.

Ok, so I've moved the SATA cables onto a different set of ports....... sill me may have hooked them up to a MARVEL controller

 

So far, here is my log while I'm starting the parity check... looks better, I'll update if I need more help.

 

Thanks, your humble noob,

 

John

 

Aug 22 09:36:03 Tower logger: naming =version 2 bsize=4096 ascii-ci=0 ftype=1

Aug 22 09:36:03 Tower logger: log =internal bsize=4096 blocks=357698, version=2

Aug 22 09:36:03 Tower logger: = sectsz=512 sunit=0 blks, lazy-count=1

Aug 22 09:36:03 Tower logger: realtime =none extsz=4096 blocks=0, rtextents=0

Aug 22 09:36:03 Tower emhttp: shcmd (106): mkdir -p /mnt/disk3

Aug 22 09:36:03 Tower emhttp: shcmd (107): set -o pipefail ; mount -t auto -o noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

Aug 22 09:36:03 Tower kernel: XFS (md3): Mounting V5 Filesystem

Aug 22 09:36:03 Tower kernel: XFS (md3): Ending clean mount

Aug 22 09:36:03 Tower emhttp: shcmd (108): xfs_growfs /mnt/disk3 |& logger

Aug 22 09:36:03 Tower logger: meta-data=/dev/md3 isize=512 agcount=4, agsize=183141659 blks

Aug 22 09:36:03 Tower logger: = sectsz=512 attr=2, projid32bit=1

Aug 22 09:36:03 Tower logger: = crc=1 finobt=1

Aug 22 09:36:03 Tower logger: data = bsize=4096 blocks=732566633, imaxpct=5

Aug 22 09:36:03 Tower logger: = sunit=0 swidth=0 blks

Aug 22 09:36:03 Tower logger: naming =version 2 bsize=4096 ascii-ci=0 ftype=1

Aug 22 09:36:03 Tower logger: log =internal bsize=4096 blocks=357698, version=2

Aug 22 09:36:03 Tower logger: = sectsz=512 sunit=0 blks, lazy-count=1

Aug 22 09:36:03 Tower logger: realtime =none extsz=4096 blocks=0, rtextents=0

Aug 22 09:36:03 Tower emhttp: shcmd (109): sync

Aug 22 09:36:03 Tower emhttp: shcmd (110): mkdir /mnt/user

Aug 22 09:36:03 Tower emhttp: shcmd (111): /usr/local/sbin/shfs /mnt/user -disks 14 -o noatime,big_writes,allow_other -o remember=0 |& logger

Aug 22 09:36:03 Tower emhttp: shcmd (112): rm -f /boot/config/plugins/dynamix/mover.cron

Aug 22 09:36:03 Tower emhttp: shcmd (113): /usr/local/sbin/update_cron &> /dev/null

Aug 22 09:36:03 Tower kernel: mdcmd (37): check CORRECT

Aug 22 09:36:03 Tower kernel: md: recovery thread woken up ...

Aug 22 09:36:03 Tower kernel: md: recovery thread syncing parity disk ...

Aug 22 09:36:03 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks.

Aug 22 09:36:05 Tower emhttp: shcmd (114): :>/etc/samba/smb-shares.conf

Aug 22 09:36:05 Tower avahi-daemon[2273]: Files changed, reloading.

Aug 22 09:36:05 Tower emhttp: Restart SMB...

Aug 22 09:36:05 Tower emhttp: shcmd (115): killall -HUP smbd

Aug 22 09:36:05 Tower emhttp: shcmd (116): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service

Aug 22 09:36:05 Tower avahi-daemon[2273]: Files changed, reloading.

Aug 22 09:36:05 Tower avahi-daemon[2273]: Service group file /services/smb.service changed, reloading.

Aug 22 09:36:05 Tower emhttp: shcmd (117): pidof rpc.mountd &> /dev/null

Aug 22 09:36:05 Tower emhttp: shcmd (118): /etc/rc.d/rc.atalk status

Aug 22 09:36:05 Tower emhttp: Starting Docker...

Aug 22 09:36:05 Tower logger: /usr/bin/docker not enabled

Aug 22 09:36:06 Tower avahi-daemon[2273]: Service "Tower" (/services/smb.service) successfully established.

Thanks for the quick reply!

 

but before I do, how to I run diagnostics?

 

 

Go to 'Tools' Then click on the 'Diagnostics'.  It will save the file in your download directory/folder of your browser.  You can then attach that file to your next post.

WELL, thank you sir.  All good.

 

Appreciate the help.

 

I'm sure I'll be back in here asking more questions again soon haha!

 

John

More often than not a red X is caused by a bad connection to the drive rather than the drive itself being bad. And the bogus SMART report you showed is a symptom of not being able to communicate with the drive.

 

The red X means unRAID has disabled the drive due to a write error. It is disabled because its contents are no longer in sync with parity. unRAID will emulate all reads and writes to the drive using the rest of the parity array until the drive is rebuilt. The drive contents are wrong, but the drive data is in the parity array and can be read and even written to the emulated drive.

 

See this wiki:

 

What do I do if I get a red X next to a hard disk?