Hello,

I checked my dashboard and I have 3 driver that have a triangle with an !.  One drive has a "Command Timeout line that is orange.  One has a Current Pending sector in orange and the 3rd has reallocated sector count in orange.

 

Is this something to be concerned about?  Of the 3 drives only one has data on it.

 

Thanks for your help,

 

Oscar

 

Post your diagnostics file.  'Tools'  >>>  'Diagnostics'

The Diag. file is too large to post  358KB  What do I do Now?

 

thanks for your help.

Two suggestions:

 

First, post it up to a file sharing service and provide a link to it.

 

Second, split the original file into two pieces and post them up in two different posts.  Add -pt1 and -pt2 to the file name to differentiate them.  (The limit for each post is 320kB and your current file is only a bit over that.)

Ok, Lets see if this works.

 

Here is the link on Google Drive

 

https://drive.google.com/file/d/0B16tu1qcTZmzNUZSazlZd1ZZNDA/view?usp=sharing

 

 

Quick look at SMART Data:

 

Device Model:    Hitachi HDS723020BLA642

Serial Number:    MN1221F3028N8A

  and

Device Model:    WDC WD30EZRX-00SPEB0

Serial Number:    WD-WCC4E1744917

 

Both of these disks each have 3  UDMA_CRC_Errors.  (This is usually caused by a hardware error controller, SATA cable, etc.)  I don't believe a small number of these are any indication of a major problem.

===================

 

Device Model:    ST3500630AS

Serial Number:    5QG0AH59

 

This disk has 6  Reallocated_Sectors on it.  (These are sectors that have been removed from service because of reading errors on those sectors.  When these sectors were re-written at some point in the past, new sectors were assigned to replaced them.  This is somewhat expected but keep an eye on this disk.)

===================

 

Device Model:    WDC WD20EARS-00MVWB0

Serial Number:    WD-WCAZA0088586

 

This disk has 2 Current_Pending_Sectors that should be moved to the Reallocated sectors the next time they are written to.  They were marked this way because the disk drive's on-board controller had to invoke special data recovery procedures to be able to read them.  In other words, they are just short of being unreadable! 

 

If you have another disk fail and you have to rebuild it and these sectors at that time can't be read, the rebuild will fail. 

 

I personally would replace this disk and then discard it or subject to rigorous  testing program. 

===================

 

Which disks are you seeing that have an indication of problems? 

Frank,

I am not really having any problems yet, Disks 5,8, and 9 have the triangle with !.  All others have green thumbs up.  Only Disk 5  has data (ST2000DL003-9VT166) and my concern is that my user interface has been glitchy and was wondering if this may be the reason.

 

Should I have any concern with what you saw in my array?  These errors would not cause the GUI and file management to be glitchy and slow, would it?

 

The Disk that has the 6 errors, is a 500Gb disk that was from an older computer and decided to place in the array, knowing O would replace in the future with a larger disk.

 

Thanks,

 

oscar

 

You have hundreds of lines that look like this:

 

Nov 13 00:50:11 Tower shfs/user: shfs_ftruncate: ftruncate: (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_write: write: (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_write: write: (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_write: write: (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_create: open: /mnt/disk1/Pictures/MAC BOOK Time machine/Oscar's Time Machine/TimeMachine.sparsebundle/bands/59bc (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_write: write: (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_create: open: /mnt/disk1/Pictures/MAC BOOK Time machine/Oscar's Time Machine/TimeMachine.sparsebundle/bands/59bc (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_write: write: (28) No space left on device
Nov 13 00:50:11 Tower shfs/user: shfs_write: write: (28) No space left on device
Nov 1

 

I am not really sure what is going on here, but I suspect that something is trying to write to disk1 and it is full.

 

Now here are how actual drives are assigned to the disk# that you see on the Dashboard and the Main page: 

 

Nov  7 15:54:57 Tower kernel: mdcmd (1): import 0 8,96 3907018532 WDC_WD40PURX-64GVNY0_WD-WCC4E6RX8N51
Nov  7 15:54:57 Tower kernel: md: import disk0: [8,96] (sdg) WDC_WD40PURX-64GVNY0_WD-WCC4E6RX8N51 size: 3907018532
Nov  7 15:54:57 Tower kernel: mdcmd (2): import 1 8,160 1953514552 Hitachi_HDS723020BLA642_MN1221F3028N8A
Nov  7 15:54:57 Tower kernel: md: import disk1: [8,160] (sdk) Hitachi_HDS723020BLA642_MN1221F3028N8A size: 1953514552
Nov  7 15:54:57 Tower kernel: mdcmd (3): import 2 8,80 2930266532 WDC_WD30EZRX-00SPEB0_WD-WCC4E1744917
Nov  7 15:54:57 Tower kernel: md: import disk2: [8,80] (sdf) WDC_WD30EZRX-00SPEB0_WD-WCC4E1744917 size: 2930266532
Nov  7 15:54:57 Tower kernel: mdcmd (4): import 3 8,176 3907018532 WDC_WD40PURX-64GVNY0_WD-WCC4E2NH5573
Nov  7 15:54:57 Tower kernel: md: import disk3: [8,176] (sdl) WDC_WD40PURX-64GVNY0_WD-WCC4E2NH5573 size: 3907018532
Nov  7 15:54:57 Tower kernel: mdcmd (5): import 4 8,32 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA9131314
Nov  7 15:54:57 Tower kernel: md: import disk4: [8,32] (sdc) WDC_WD20EARX-00PASB0_WD-WMAZA9131314 size: 1953514552
Nov  7 15:54:57 Tower kernel: mdcmd (6): import 5 8,0 1953514552 ST2000DL003-9VT166_6YD1WW2F
Nov  7 15:54:57 Tower kernel: md: import disk5: [8,0] (sda) ST2000DL003-9VT166_6YD1WW2F size: 1953514552
Nov  7 15:54:57 Tower kernel: mdcmd (7): import 6 8,64 3907018532 WDC_WD40EFRX-68WT0N0_WD-WCC4E0NDDR22
Nov  7 15:54:57 Tower kernel: md: import disk6: [8,64] (sde) WDC_WD40EFRX-68WT0N0_WD-WCC4E0NDDR22 size: 3907018532
Nov  7 15:54:57 Tower kernel: mdcmd (: import 7 8,144 1953514552 ST2000DL003-9VT166_5YD79Z54
Nov  7 15:54:57 Tower kernel: md: import disk7: [8,144] (sdj) ST2000DL003-9VT166_5YD79Z54 size: 1953514552
Nov  7 15:54:57 Tower kernel: mdcmd (9): import 8 8,192 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA0088586
Nov  7 15:54:57 Tower kernel: md: import disk8: [8,192] (sdm) WDC_WD20EARS-00MVWB0_WD-WCAZA0088586 size: 1953514552
Nov  7 15:54:57 Tower kernel: mdcmd (10): import 9 8,112 488386552 ST3500630AS_5QG0AH59
Nov  7 15:54:57 Tower kernel: md: import disk9: [8,112] (sdh) ST3500630AS_5QG0AH59 size: 488386552
Nov  7 15:54:57 Tower kernel: mdcmd (11): import 10 8,48 976762552 WDC_WD1001FALS-00J7B0_WD-WMATV1041839
Nov  7 15:54:57 Tower kernel: md: import disk10: [8,48] (sdd) WDC_WD1001FALS-00J7B0_WD-WMATV1041839 size: 976762552
Nov  7 15:54:57 Tower kernel: mdcmd (12): import 11 8,128 1953514552 WDC_WD20EFRX-68AX9N0_WD-WMC301052837
Nov  7 15:54:57 Tower kernel: md: import disk11: [8,128] (sdi) WDC_WD20EFRX-68AX9N0_WD-WMC301052837 size: 1953514552

 

What I suspect is that the symbols on the Dashboard are warnings of potential issues on each  of those drives. 

 

Upon a further look at the Dashboard, I found it you left click on the Smart Status symbol for each drive will bring up a menu.  If you look the display for each drive, you will find a list of things you can look at in detail.  Open any of them.  Now at the down of that display click on the 'Disk# Settings' tab.  Look at the 'SMART attribute notifications:' section.  I suspect that one of those attributes is the reason that you have the warning.  Looking at the 'Attribute' tab and you can find the actual value of any of those attributes.