Array has been running fine for months on my HP Microserver, tried to start today and it gets stuck somewhere - running 5.0 RC2 (was planning to upgrade today!)

 

On the main unRAID page, it just says 'Starting' indefinitely (and I have SimpleFeatures). unMENU thinks that the array has started, and if I browse from Windows I can only access the flash drive.

 

I think the problem is something to do with my cache drive? My Syslog is attached below, hope it is a relatively simple fix? 

 

This is the only error thrown according to unMENU.

 

Jun 18 22:30:45 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Jun 18 22:30:45 Tower kernel: ata1.00: ATA-8: ST2000DL001-9VT156, CC94, max UDMA/133 (Drive related)
Jun 18 22:30:45 Tower kernel: ata1.00: 3907029168 sectors, multi 0: LBA48  (Drive related)
Jun 18 22:30:45 Tower kernel: ata1.00: configured for UDMA/133 (Drive related)
Jun 18 22:30:45 Tower kernel: scsi 0:0:0:0: Direct-Access     ATA      ST2000DL001-9VT1 CC94 PQ: 0 ANSI: 5 (Drive related)
Jun 18 22:30:45 Tower kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) (Drive related)
Jun 18 22:30:45 Tower kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks (Drive related)
Jun 18 22:30:45 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off (Drive related)
Jun 18 22:30:45 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 (Drive related)
Jun 18 22:30:45 Tower kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Jun 18 22:30:45 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Jun 18 22:30:45 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Jun 18 22:30:45 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Jun 18 22:30:45 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Jun 18 22:30:45 Tower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
Jun 18 22:30:45 Tower kernel: ata2.00: ATA-8: ST2000DL001-9VT156, CC94, max UDMA/133 (Drive related)
Jun 18 22:30:45 Tower kernel: ata2.00: 3907029168 sectors, multi 0: LBA48  (Drive related)
Jun 18 22:30:45 Tower kernel: ata5.00: failed to enable AA(error_mask=0x1) (Errors)
Jun 18 22:30:45 Tower kernel: ata5.00: ATA-8: VB0250EAVER, HPG0, max UDMA/100 (Drive related)
Jun 18 22:30:45 Tower kernel: ata5.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32) (Drive related)
Jun 18 22:30:45 Tower kernel: ata6.00: ATA-8: ST2000DL003-9VT166, CC3C, max UDMA/133 (Drive related)
Jun 18 22:30:45 Tower kernel:  sda: sda1 (Drive related)
Jun 18 22:30:45 Tower kernel: ata6.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) (Drive related)
Jun 18 22:30:45 Tower kernel: ata4.00: ATA-8: ST31000528AS, CC38, max UDMA/133 (Drive related)
Jun 18 22:30:45 Tower kernel: ata4.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) (Drive related)
Jun 18 22:30:45 Tower kernel: ata2.00: configured for UDMA/133 (Drive related)
Jun 18 22:30:45 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI disk (Drive related)
Jun 18 22:30:45 Tower kernel: scsi 1:0:0:0: Direct-Access     ATA      ST2000DL001-9VT1 CC94 PQ: 0 ANSI: 5 (Drive related)
Jun 18 22:30:45 Tower kernel: ata5.00: failed to enable AA(error_mask=0x1) (Errors)
Jun 18 22:30:45 Tower kernel: ata5.00: configured for UDMA/100 (Drive related)
Jun 18 22:30:45 Tower kernel: ata6.00: configured for UDMA/133 (Drive related)

syslog-2012-06-18.zip

Disable add-ons and see if the problem goes away. Then enable add-ons one at a time until the add-on or set of add-ons that causes the issue  is determined. Then start a thread in the User Customization forum.