Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Still have problem with LSI conroller

Featured Replies

I am still having problems with the AOC-USAS2_L8i controller.

 

My system is:

Supermicro X9SCM-F-O

8 GB ram

Antec case with 4 Supermicro CSE-M35T Cages

2 AOC-USAS2-L8i controllers flashed with LSI firmware

6x Seagate 3tb drives

Corsair TX-850 Pwr supply

 

It is still the spin up/down problem, I can spin up/down the drives manually all day long, no problems, but let the system set for several hours and then spin up the drives I get the dreaded red ball(s), wrong drive, missing drive message.

 

I have had this problem even with the beta 12a software, it is still there even with rc2 software. I have tried moving all drives to the mainboard controller with no success, (this would seem to indicate no problem with the LSI driver), also have moved the drives to different combinations of controllers to try and isolate bad cables.

 

The attached syslog shows several plugins installed, these plugins were not installed when I was testing with beta 12a, also ingore the duplicate file messages they have been taken care of, I just happened to have unmenu running when the problem occured so I was finally able to get a syslog.

syslog-2012-05-05.txt

If you're having the problem even with Beta12a and RC3 then you're having much larger issues than what is the LSI issue so you should perhaps start examining other items in your mix.

1. Your BIOS is old - dated 06/30/2011

 

Since you are using relatively new hardware one should take care to upgrade the motherboard BIOS as there will be many problems early on that could be fixed by BIOS upgrades later in the product life-cycle.

 

Coincidentally it looks like SM released a new BIOS just few days ago - dated May 8, 2012

 

2. Your LSI firmware may not be up to date - the latest being 13.00.57.00 when yours are with 13.00.01.00

 

3. You are using a server grade components but are missing the last one needed for reliable "server" operation - UPS.

 

1. Your BIOS is old - dated 06/30/2011

 

Since you are using relatively new hardware one should take care to upgrade the motherboard BIOS as there will be many problems early on that could be fixed by BIOS upgrades later in the product life-cycle.

 

Coincidentally it looks like SM released a new BIOS just few days ago - dated May 8, 2012

 

2. Your LSI firmware may not be up to date - the latest being 13.00.57.00 when yours are with 13.00.01.00

 

3. You are using a server grade components but are missing the last one needed for reliable "server" operation - UPS.

 

For supermicro, that is not old. bios upgrades from them are rare and not always "good".

but upgrading to the latest Bios is not always the best option. for those running ESXi on an X9 board, the new bios breaks ESXi. The PCIe slots and the NIC stop working (sort of the whole point of a mother board...)

 

many people have gone back to the 1.0c bios

 

I am still having problems with the AOC-USAS2_L8i controller.

 

My system is:

Supermicro X9SCM-F-O

8 GB ram

Antec case with 4 Supermicro CSE-M35T Cages

2 AOC-USAS2-L8i controllers flashed with LSI firmware

6x Seagate 3tb drives

Corsair TX-850 Pwr supply

 

It is still the spin up/down problem, I can spin up/down the drives manually all day long, no problems, but let the system set for several hours and then spin up the drives I get the dreaded red ball(s), wrong drive, missing drive message.

 

I am running one AOC-USAS2-L8i.  I can assure you that the spinup problem does not manifest itself in my system on either RC2 or RC3.

 

However, I only have a single card so this is one, possibly significant, difference.  Would it be possible for you to re-configure your system with only a single USAS2-L81 installed?  I have not tried with the P13 firmware, but with P11 and P13.5 (released a couple of weeks ago).  However, I find it difficult to believe that you are suffering from a bug introduced, and removed again, between those releases.

 

I'm afraid that I don't have a preserved log from when I experienced the spinup problem on b13.  If someone has a log, can it be confirmed that the entries you see in your log are similar to the spinup problems that the rest of us experienced?

I am still having problems with the AOC-USAS2_L8i controller.

 

My system is:

Supermicro X9SCM-F-O

8 GB ram

Antec case with 4 Supermicro CSE-M35T Cages

2 AOC-USAS2-L8i controllers flashed with LSI firmware

6x Seagate 3tb drives

Corsair TX-850 Pwr supply

 

It is still the spin up/down problem, I can spin up/down the drives manually all day long, no problems, but let the system set for several hours and then spin up the drives I get the dreaded red ball(s), wrong drive, missing drive message.

 

I have had this problem even with the beta 12a software, it is still there even with rc2 software. I have tried moving all drives to the mainboard controller with no success, (this would seem to indicate no problem with the LSI driver), also have moved the drives to different combinations of controllers to try and isolate bad cables.

 

The attached syslog shows several plugins installed, these plugins were not installed when I was testing with beta 12a, also ingore the duplicate file messages they have been taken care of, I just happened to have unmenu running when the problem occured so I was finally able to get a syslog.

 

This might sound odd.

pull the second SAS card and put all 6 drives on one card.

when I ran multi LSI cards with 3 TB drives. I would drop one every now and then. It was like they took to long to  spin up and unraid gave up. this has been discussed a few times. when all drives were on card, the problems went away. if that fixes that immediate problem, then you have a direction to look in.

  • Author

I may have solved the problem, some time ago i attempted to disable  int 13 on the controllers, after that when the card booted up I got a message the adapter had been disabled by the user, I managed to renable the controllers and have been trying to reproduce the problem, so far so good, so this may have been operator error after all.

 

Thank you all for you help.

  • Author

Looks like I spoke to soon, still have the same problem. I tried copying a file to the server and it crashed. I am going to reconfig the array to run off the MB ports only and see what happens.

syslog-2012-05-16.zip

As pointed out earlier, did you update the Firmware on your LSI card?

  • Author

It worked running off the MB ports, I am going to try the suggestion to pull one of the controllers and put all drives on the other one, I will try the firmware update after that.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.