I recently picked up a IBM BR10i and got it installed. The device itself seems to be working, however, since installing it, unRAID has been behaving very strangely. The first thing I noticed was an audible 'beep' coming from the machine, seemingly from the card. The beep comes every 10 seconds or so. Additionally, my Syslog is being spammed with a repeating set of lines very frequently. My Syslog is included below. A number of other issues have arisen, the most troubling of which is a "filesystem read-only" error, which I've discovered is caused by corruption on a disk (Reiserfsck advised that I run it with the --rebuild-tree option, which I have not done yet). I believe that my current set of issues, however, is related to the BR10i card, though I have no idea how to ensure that it is the issue.

 

The bit that I'm concerned about in my Syslog is this:

Feb 21 20:15:34 Apollo kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen (Errors)
Feb 21 20:15:34 Apollo kernel: ata3: irq_stat 0x00400040, connection status changed (Drive related)
Feb 21 20:15:34 Apollo kernel: ata3: SError: { PHYRdyChg 10B8B DevExch } (Errors)
Feb 21 20:15:34 Apollo kernel: ata3: hard resetting link (Minor Issues)
Feb 21 20:15:39 Apollo kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3.00: configured for UDMA/33 (Drive related)
Feb 21 20:15:39 Apollo kernel: ata3: EH complete (Drive related)

 

 

Currently running unRAID version 5.0rc11. I was also having similar issues with 5.0b11 as well.

 

My entire Syslog is too large to be attached. Instead, the log has been uploaded to Pastebin. I can provide other logs, if need be.

 

http://pastebin.com/qTH0CCNv

 

Thank you for the assistance.

Reseat the SATA cable. Try a new SATA cable. Do not tightly zip-tie SATA cables. Do not route the SATA cables adjacent to a power cable.

Reseat the SATA cable. Try a new SATA cable. Do not tightly zip-tie SATA cables. Do not route the SATA cables adjacent to a power cable.

 

I'm currently zip-tying my twenty something extra sata cables pretty close together of my shelf, can I ask why I shouldn't and if it only matters if they're in the build?

I'm currently zip-tying my twenty something extra sata cables pretty close together of my shelf, can I ask why I shouldn't and if it only matters if they're in the build?

You can store disconnected SATA cables any way you wish, as long as you don't crimp them. When they are in use they need separation so the signal flowing through one doesn't bleed across to the other.

I'm currently zip-tying my twenty something extra sata cables pretty close together of my shelf, can I ask why I shouldn't and if it only matters if they're in the build?

You can store disconnected SATA cables any way you wish, as long as you don't crimp them. When they are in use they need separation so the signal flowing through one doesn't bleed across to the other.

 

Well, in my build (Both unraid and desktop) the sata cables are really close coming out of the mobo, like, literally just enough space to fit the head of the sata cables and no room in between.

 

Oh well, my desktop has been running fine for years, I doubt it's really much of an issue.

I'm currently zip-tying my twenty something extra sata cables pretty close together of my shelf, can I ask why I shouldn't and if it only matters if they're in the build?

You can store disconnected SATA cables any way you wish, as long as you don't crimp them. When they are in use they need separation so the signal flowing through one doesn't bleed across to the other.

 

Well, in my build (Both unraid and desktop) the sata cables are really close coming out of the mobo, like, literally just enough space to fit the head of the sata cables and no room in between.

1/4" separation is plenty. Bundling them so they are continously touching over several inches in parallel is bad. Touching each other incidentally at an angle is fine, the closer to 90 degrees they are, the better.

Reseat the SATA cable. Try a new SATA cable. Do not tightly zip-tie SATA cables. Do not route the SATA cables adjacent to a power cable.

 

Thanks for the suggestion. That appears to have fixed the disk issue that I was having, however, I'm still getting a read-only filesystem error. Reiserfsck suggested that I used the --rebuild-tree option. Is this a relatively safe option to go ahead and use, or do I need to do something prior to running it? I have uploaded a log of what Reiserfsck provided when running the --check option on Disk 3, in case that helps.

 

http://pastebin.com/6jzfYMLP

 

 

Thank you again.

Reseat the SATA cable. Try a new SATA cable. Do not tightly zip-tie SATA cables. Do not route the SATA cables adjacent to a power cable.

 

Thanks for the suggestion. That appears to have fixed the disk issue that I was having, however, I'm still getting a read-only filesystem error. Reiserfsck suggested that I used the --rebuild-tree option. Is this a relatively safe option to go ahead and use, or do I need to do something prior to running it? I have uploaded a log of what Reiserfsck provided when running the --check option on Disk 3, in case that helps.

 

http://pastebin.com/6jzfYMLP

 

 

Thank you again.

 

Run with --rebuild-tree.