AOC-SASLP-MV8 & Motherboard=AHCI results in not booting


Recommended Posts

unRAID 4.7

Motherboard = Gigabyte GA-880GMA-UD2H (latest FW)

HDDs = Hitachi 5k3000 2TB x 6

RAID CARD = SUPERMICRO AOC-SASLP-MV8 (FW=3.1.0.21) x 2

CABLES = 3WARE CBL-SFF8087OCF-05M x 4 & Sata x 2

PSU = CORSAIR CMPSU-850HX 850W

 

1) With the SASLPs in the x16 and x16(x4) slots and 4 x 5k3000 connected (one to each P0 cable) then unRaid boots successfully.

2) With the SASLPs in the x16 and x16(x4) slots and 4 x 5k3000 connected (one to each P0 cable) and a 2 x 5K3000 also connected to the Motherboards on-board SATA (and set as RAID or IDE) then unRaid boots successfully.

3) With the SASLPs in the x16 and x16(x4) slots and 4 x 5k3000 connected (one to each P0 cable) and 2 x 5K3000 also connected to the Motherboard's on-board SATA (and set as AHCI) then the PC freezes before it gets to the unRaid boot screen and I am left with a flashing "_".

4) With the SASLPs in the x16 and x16(x4) slots and 4 x 5k3000 connected (one to each P0 cable) and no HDDs connected to the Motherboard's on-board SATA (although it is set as AHCI) then unRaid boots successfully

 

i.e. I am unable to boot the PC and load unRaid with the motherboard onboard Sata in AHCI mode and HDDs connected to the on-board Sata.

 

I have:

a) disabled INT 13h on both SASLPs (and also tried booting with just 1 SASLP and the results are the same - as soon as I connect a HDD to the motherboard's on-board SATA and set it to AHCI the PC fails to boot.

 

b) Tried to access the BIOS of the PC when it is booting in AHCI mode and the motherboard's BIOS screens are "blank" - see below:

 

Normal Bios Screen

 

unraid10b_thumb.jpg

 

'blank' Bios Screen

 

unraid10a_thumb.jpg

 

c) Tried to select a different boot device (press F12) when it is booting in AHCI mode and the resulting boot menu is "garbled" - see below:

 

Normal boot device Screen

 

unraid11b_thumb.jpg

 

'garbled' boot device Screen

unraid11a_thumb.jpg

 

Additional Information:

d) I have also noticed that SASLP Adapter 0 states RAID Mode: "RAID 0 RAID 1 RAID 10" whereas Adapter 1 states RAID Mode: "JBOD". Is this normal for when using 2 x SASLP (see below)?

 

Adapter 0 showing RAID

 

unraid12a_thumb.jpg

 

Adapter 1 showing RAID

 

unraid12b_thumb.jpg

 

e) I have also noticed that when looking at the Main menu that the 2 x HDDs connected to one of the SASLP are showing as 'scsi-SATA_' whereas the other 2 x HDDs connected to the other SASLP are not. I am assuming this is also related to point d) above.

 

unraid13_thumb.jpg

 

syslog also attached - and the lines included below are those highlighted in orange or red in the syslog.

 

Mar 31 19:35:05 NAS-03 kernel: ACPI Warning: Package List length (0x1) larger than NumElements count (0x0), truncated (Minor Issues)

...

Mar 31 19:35:05 NAS-03 kernel: scst: ***WARNING***: Patch io_context was not applied on your kernel. SCST will be working with not the best performance. (Minor Issues)

...

Mar 31 19:35:05 NAS-03 kernel: ------------[ cut here ]------------

Mar 31 19:35:05 NAS-03 kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b() (Minor Issues)

Mar 31 19:35:05 NAS-03 kernel: Hardware name: GA-880GMA-UD2H

Mar 31 19:35:05 NAS-03 kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered (Drive related)

Mar 31 19:35:05 NAS-03 kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas (Drive related)

Mar 31 19:35:05 NAS-03 kernel: Pid: 811, comm: modprobe Not tainted 2.6.32.9-unRAID #8 (Errors)

Mar 31 19:35:05 NAS-03 kernel: Call Trace: (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c10244e9>] warn_slowpath_fmt+0x24/0x27 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c109cf0e>] proc_register+0x11c/0x14b (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c109d0cc>] proc_mkdir_mode+0x2f/0x43 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c109d0ef>] proc_mkdir+0xf/0x11 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<f83f6a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst] (Routine)

Mar 31 19:35:05 NAS-03 kernel:  [<f83ddca9>] __scst_register_target_template+0x16c/0x3af [scst] (Routine)

Mar 31 19:35:05 NAS-03 kernel:  [<f845bd5d>] mvst_init+0x3b/0x5b [mvsas] (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<f8460895>] mvs_pci_init+0xaa5/0xaf7 [mvsas] (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1142050>] local_pci_probe+0xe/0x10 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c11426ad>] pci_device_probe+0x48/0x66 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1194956>] driver_probe_device+0x79/0xed (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1194a0d>] __driver_attach+0x43/0x5f (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c11940a7>] bus_for_each_dev+0x39/0x5a (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c119482f>] driver_attach+0x14/0x16 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c11949ca>] ? __driver_attach+0x0/0x5f (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c119451c>] bus_add_driver+0x9f/0x1c5 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1194ccf>] driver_register+0x7b/0xd7 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1142882>] __pci_register_driver+0x39/0x8c (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<f8468000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<f8468030>] mvs_init+0x30/0x45 [mvsas] (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1001139>] do_one_initcall+0x4c/0x131 (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1042e6e>] sys_init_module+0xa7/0x1dd (Errors)

Mar 31 19:35:05 NAS-03 kernel:  [<c1002935>] syscall_call+0x7/0xb (Errors)

Mar 31 19:35:05 NAS-03 kernel: ---[ end trace d0f2ec762b996703 ]---

...

Mar 31 19:35:07 NAS-03 emhttp: shcmd (6): killall -HUP smbd (Minor Issues)

 

Does anyone have any suggestions, pointers, help, tips as to what could be wrong and how to solve it? Is running the motherboard SATA ports as RAID instead of AHCI going to make a difference to performance etc? Setting them to RAID does seem to result in the Temperature not being shown, so does this mean no SMART?

 

And I know I don't need 2 x SASLP-MV8 with only 6 HDDs, I have some more HDDs I will add once I am certain it is all working  :P

 

thanks

 

Alex

 

 

5._syslog-2011-03-31_2xSASLP_4x1_and_2xonboard_Sata_drives_as_RAID.txt

Link to comment

Thanks to Josh for his input on this forum thread where there was a similar issue on an Asus motherboard. The temporary solution was to downgrade the firmware of the SASLP from .21 to .15N and then re-enable AHCI.

 

This took 2 minutes to do (thanks to Josh's instructions) and my motherboard now successfully boots with HDDs attached and in AHCI mode. I will run a pre-clear on the drives and confirm if all is ok.

 

If anyone could take a look at the other errors showing in the syslog then I'd greatly appreciate it.

 

I'll also drop a note to Gigabyte support and see if they can provide a motherboard bios that works with the SASLP .21 firmware.

 

thanks

 

Link to comment

I first would like to state that IMHO this is how everyone should report their problems (hardware plus firmware and a syslog)

 

Suggestions - load the default setting for the BIOS and then:

1. Disable the serial and parallel ports, the floppy, the audio, the firewire and the IDE if you are not going to use the older PATA drives.

Do not forget to check for this Gigabyte feature called "DualBios" - it has to be turned off by default

2. Check the BIOS to see if you can disable (change) the SATA3 ports into a regular SATA2 mode.

 

Then try to change the setting to AHCI and boot.

 

If successful then you are set.

 

3. If not you have a separate USB3 controller. Disable this in the BIOS temporarily and try again to boot into AHCI mode.

 

4. Your SM SASLP-MV8 are with firmware .21

I am not familiar with this one but try to go into the different menus and change the settings to JBOD.

 

Try again - if not successful and you want to play with fire you can try to downgrade the SM firmware to .15 as I do recall some people having problems with ASUS boards and I believe was also 880/890 based chipset - http://lime-technology.com/forum/index.php?topic=9488.0

 

 

Well - it looks like you fixed it yourself while I was looking at the various places.

Link to comment

Hi AlexanderIanHall,

 

I believe it has to do with the 880/890 chips and the lack of option ROM. I don't think a bios update will fix it but my talking to ASUS ended up in a dead end. I remember someone mentioning that with a different board and different card but getting a lack of option ROM as well they managed to get it going with the motherboard drives set to RAID.

 

I haven't had any real problems with the .15 firmware.

I have had issues with trying to preclear whilst watching movies at the same time (doesn't matter which hdd and mobo or SASLP connected) but I can't be sure that is to do with the .15 firmware. The movie I'm watching doesn't load or keeps crashing. I just preclear now on another linux machine or do it when I don't watch anything.

 

Glad it all helped.

 

Josh

Link to comment

I have tried switching the following options of within the BIOS:

 

Bios_thumb.jpg

 

OnChip SATA Controller = Enabled

OnChip SATA Type = AHCI

OnChip SATA Port 4/5 Type = As SATA Type

OnChip SATA3.0 Support = disabled

Onboard IDE Ctrl = disabled

Onboard LAN Function = disabled

Onboard LAN Boot ROM = disabled

Onboard Audio Function = disabled

Onboard 1394 Function = disabled

[/color]Onboard USB 3.0 Controller = disabled

USB Controllers = Enabled

USB Legacy Function = Enabled

USB Storage Function = Enabled

Onboard Serial Port 1 = disabled

 

I still had the same issue, i.e. trying to use the motherboard's onboard SATA controller in AHCI mode with HDD attached resulted in the PC not booting.

 

bcbgboy13 - There are no specific settings within the SASLP to set the connected HDDs to JBOD that I can see. I am assuming that unless you explicitly create a RAID array on the SASLP the default behaviour is JBOD.

 

Josh - I think you may be correct re: it being a limitation of the 880/890 chips. I can confirm that setting the SATA controller as either IDE or RAID works successfully with SASLP firmware .21, it is purely setting as AHCI that causes the issue with firmware .21.

 

I do see one Pre-Clear oddity using the SASLP on firmware .15 that I did not see when the HDDs were connected directly to the onboard SATA. (see below). I see the following error:

Error SMART Status command failed

...

Register values returned from SMART Status command are:

ST = 0x50

ERR=0x00

NS=0x08

SC=0xc0

CL=0x87

CH=0xe0

SEL=0x40

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$

 

I then have to type 'Yes' a second time in order to kick of a pre-clear. Any thoughts?

 

SmartError_thumb.jpg

 

I will contact Gigabyte anyway, and see what they respond with re: the failure to boot.

 

thanks

 

Alex

 

I

Link to comment
  • 11 months later...

Did u get any response from Ggabyte. I have the same sas card and the same mobo resulting in the same issue that you have.

 

I flash the firmware to .15n and i can get it to work when the bios is on IDE mode. When i switch back to AHCI i get stuck at the "_" blinking cursor.

 

Also when i switch to IDE mode UnRAid reports sata3_4 & sata3_5 as missing disk.

 

so AHCI = no sas card

    IDE = sas card + 2 missing disk

 

 

How did you solved this??

 

 

Link to comment

 

I do see one Pre-Clear oddity using the SASLP on firmware .15 that I did not see when the HDDs were connected directly to the onboard SATA. (see below). I see the following error:

Error SMART Status command failed

...

Register values returned from SMART Status command are:

ST = 0x50

ERR=0x00

NS=0x08

SC=0xc0

CL=0x87

CH=0xe0

SEL=0x40

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$

 

I then have to type 'Yes' a second time in order to kick of a pre-clear. Any thoughts?

 

 

This is a problem I have had with SASLP cards in my rig as well. There was some discussion about a year ago in the supermicro motherboard threads. The upshot was preclearing from a SAS card would give that error, whereas using a motherboard port would be fine. My "fix" was to reserve a motherboard (X8SIL-F)  slot for all preclears and use the SAS cards for data drives. someone may have figured out a real fix by now.

Link to comment

1) you sure .15 is installed?  YES

2) does it boot in ide? YES

3) rma if doen't boot in ide 

 

Josh

 

I can boot onto UnRAid with the mobo on AHCI mode and the card on the PCIEX4 or PCIEX16 as long as i dont have any drive attached to the SATA card. I have 8 drives attached to the mobo without a problem. As soon as i attach 1 HDD to the card the system hangs.

 

I get the garbled boot option, the blank bios set up and the balck screen, blinking cursor.

 

I have the latest bios on my mobo and downgrade to .15N on the sata card.

 

so?  what now?  im 100% lost.

Link to comment

I can boot onto UnRAid with the mobo on AHCI mode and the card on the PCIEX4 or PCIEX16 as long as i dont have any drive attached to the SATA card. I have 8 drives attached to the mobo without a problem. As soon as i attach 1 HDD to the card the system hangs.

 

I get the garbled boot option, the blank bios set up and the balck screen, blinking cursor.

 

I have the latest bios on my mobo and downgrade to .15N on the sata card.

 

so?  what now?  im 100% lost.

 

I had similar problems with my GA-890GPA-UD3H in ACHI mode and the AOC SASLP. In the end I flashed mine up to .21 and installed it in the second  PCIe slot. I Moved my IBM M1015 (flashed to IT mode) to the first PCIe slot. With this configuration I have ACHI on and the machine boots.

Link to comment
  • 1 month later...

Just a quick update to my old post. I noticed last week that Gigabyte had posted a new BIOS for this motherboard in September 2011 (version F6f) that showed a smaller file size and a couple of features removed. I wondered if this would provide sufficient space for the .21 firmware version on the AOC-SASLP-MV8s so....

 

1. I flashed the Motherboard BIOS from F5 to F6f. UnRaid successfully booted.

2. I removed one SASLP-MV8 and flashed the remaining SASLP-MV8 to .21. Server successfully booted

3. I removed the .21 SASLP-MV8 and flashed the remaining SASLP-MV8 to .21. Server successfully booted

4. I installed both .21 SASLP-MV8, confirmed motherboard was set to AHCI and server successfully booted

 

Looks like the F6f Gigabyte BIOS for this specific motherboard has resolved the issue and I can now successfully use .21 firmware (and hence 3TB/4TB support)

 

note: I haven't actually tried a 3TB or 4TB HDD yet, however others have used them successfully with firmware .21

 

YEAH YEAH YEAH - this removed my only issue with the GA-880GMA-UD2H

 

Alex

 

 

 

Link to comment
  • 3 years later...

Had the exact same problem (Gigabyte GA-880GMA-UD2H), which was solved after updating the BIOS to F6f.

It took me a while to locate this beta BIOS update, so here it is.

 

EDIT: I had some on-screen horizontal lines with random colors appear occasionally in Windows when using the onboard GPU with BIOS version F6e / F6f, the problem was solved when I reverted back to version F5. (perhaps this is the reason this BIOS version never made it past beta).

I found out I can work-around the issue by using an external GPU.

Edited by tal.aloni
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.