SATA link down?

[gorbachev]

I just built an unraid server with 5 disks (6th is still preclearing). One cache drive and four data drives. Not assigning parity drive yet, because I don't want to build parity while I copy files from old disks.

 

I'm using a Supermicro AOC-SASLP-MV8 controller card to hook the drives up (20 drive build...not using onboard SATA slots yet).

 

This is what I get in dmesg:

 

ata7: SATA max UDMA/133 abar m2048@0xfbdf0000 port 0xfbdf0100 irq 28

ata8: SATA max UDMA/133 abar m2048@0xfbdf0000 port 0xfbdf0180 irq 28

ata9: SATA max UDMA/133 abar m2048@0xfbdf0000 port 0xfbdf0200 irq 28

ata10: SATA max UDMA/133 abar m2048@0xfbdf0000 port 0xfbdf0280 irq 28

ata11: SATA max UDMA/133 abar m2048@0xfbdf0000 port 0xfbdf0300 irq 28

ata12: SATA max UDMA/133 abar m2048@0xfbdf0000 port 0xfbdf0380 irq 28

ata7: SATA link down (SStatus 0 SControl 300)

ata8: SATA link down (SStatus 0 SControl 300)

ata9: SATA link down (SStatus 0 SControl 300)

ata10: SATA link down (SStatus 0 SControl 300)

ata11: SATA link down (SStatus 0 SControl 300)

ata12: SATA link down (SStatus 0 SControl 300)

 

Why are my SATA links showing down?

 

The drives are recognized by the controller at bootup, unraid sees them correctly, I'm able to preclear them just fine, I was able to assign them to the drive array, they formatted just fine, and I'm currently copying files on them just fine.

 

I just finished copying the initial set of files, and am moving them from the cache drive to the data drive(s). Everything is working fine.

 

What's with the SATA link down messages? Can I ignore them or have I set up something wrong?

[Rajahal]

Most likely the SATA links are reported as 'up' again later in the syslog.  Post a full syslog (zip it if too large to attach) and we can confirm for you.

 

The SASLP cards have kind of an odd initialization sequence.  The first thing they do (which you can watch in their boot screens) is load, then they reboot, then load again.  Not sure why, that's just what they do.  So I think it is normal that the syslog will report the links being down for a bit, then back up shortly after.

 

If you are able to preclear, copy files, etc. then clearly the links aren't actually down.

[gorbachev]

Most likely the SATA links are reported as 'up' again later in the syslog.  Post a full syslog (zip it if too large to attach) and we can confirm for you.

 

Nope. Grepped the living daylights out of the log file. The links are never reported as up.

 

Could the disks be hooked up in IDE mode for some reason?

 

Another problem appears to be that if I connect a monitor to my unraid box with a VGA cable and then unhook the cable, I get errors with IRQ 16 and at least one of the hard drives stops responding.

 

The errors are:

 

irq 16: nobody cared (try booting with the "irqpoll" option) (Errors)

<couple of lines of call trace info goes here>

Disabling IRQ #16

 

 

I wonder if the PCI port settings aren't quite right.

[bcbgboy13]

Why you do not post your complete syslog and hardware confuguration, otherwise the Yurui Dolgorukii will get you.

[gorbachev]

Why you do not post your complete syslog and hardware confuguration, otherwise the Yurui Dolgorukii will get you.

 

I'm lazy

 

I'll do it over the weekend if I can't solve this on my own before that.

[PeterB]

Why you do not post your complete syslog and hardware confuguration,

 

I'm lazy

 

I'm not sure that this goes down well when requesting help from unpaid volunteers!

[Kaygee]

That is showing the onboard sata ports. Notice only six ports. Since no drives attached wont show sata links as up because thewy arent. You havent plugged any drives into them.

[gorbachev]

That is showing the onboard sata ports. Notice only six ports. Since no drives attached wont show sata links as up because thewy arent. You havent plugged any drives into them.

 

Hmm...that would explain things. Actually, I think you're absolutely right.

 

I've attached the complete syslog. Just above the SATA link down messages, there're messages about the drives attached to the controller card getting discovered on ata1 - ata6 interfaces, e.g.:

 

Apr 30 07:43:31 unraid1 kernel: sas: sas_ata_phy_reset: Found ATA device.

Apr 30 07:43:31 unraid1 kernel: ata1.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

Apr 30 07:43:31 unraid1 kernel: ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

Apr 30 07:43:31 unraid1 kernel: ata1.00: configured for UDMA/133

Apr 30 07:43:31 unraid1 kernel: scsi 0:0:0:0: Direct-Access    ATA      WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

syslog-2011-05-01.txt