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.

P5B-VM DO does not recognize AOC-SASLP-MV8 [SOLVED]

Featured Replies

Hi!

 

I'm installing my HDDs in my new Unraid Tower. My Mobo is the P5B-VM DO and have 2 PCI-E cards: 1 x AOC-SASLP-MV8 (in the x16 slot) & 1 x Adaptec 1430SA (in the x4 slot).

At the beggining, I only change in the BIOS the SATA controler to AHCI to recognize the USB with DOS (I've change several Samsung 2TB HD204UI HDDs with the new firm). I've changed the JMicron Controler to AHCI too (I don't know if it's correct or I have to put it in RAID or BASIC mode).

I entered once in the AOC-SASLP-MV8 and disable the INT 13 option (I read about it somewhere and did it).

Since that, when I star the tower the Adaptec card lights and it's recognized in the Bios but the Supermicro only shine a second and it's not recognized at all. I press CTRL + M but I can go into the Supermicro Bios again.

 

Maybe someone with the same configuration can help me. Must I change anything in the Asus Mobo Bios?

I've tried to change in the BIOS Internal Graphics Adapter to IGD (default is PEG/PCI) but the problem continues.

 

I've read this in the Supermicro Manual:

 

"Problem:

The AOC-SASLP-MV8 add-on card's BIOS does not show up in DOS.

Recommended Solutions:

1 - Make sure that the system has enough expansion ROM to initialize the card.

Remove other add-in cards if possible.

2 - Make sure that the card is properly and fully seated in its PCI slot.

3 - Check if the motherboard's BIOS is updated. (You can download an updated BIOS

from our web site at: www.supermicro.com.)"

 

1 - I don't know what is this: "enough expansion ROM to initialize the card". Someone can explain it to me?

2 - I'm sure the card is properly seated in the x16 PCI-E slot. The lights shine one second when I start the tower but after that nothing more.

3 - The mobo is new, so I dont think I must update the BIOS. And if the Mobo recognizes the Adaptec in the x4 slot, why not the same with the Supermicro in the x16 slot?

 

 

Another question:

 

I've read in the BIOS Hardware monitor that the CPU Temperature is 73.5 ºC. Is that too much?

I've a Celeron 430 processor and I use the stock Intel CPU fan cooler. Maybe I must change the cooler for a better one?

 

Thanks in advance.

 

 

 

 

Hi,

 

what happens when you try to boot, do you get a black screen?

 

Has anyone else with this board run the supermicro card in the x16 slot? Try it in the x4 slot. Some motherboards won't support anything but a graphics card in the x16 slot.

 

The other thin about the initiazing ROM thing, have a read of this post:

 

http://lime-technology.com/forum/index.php?topic=9488.0

 

The option rom is needed to load the bios of other items like the supermicro card. The .21 firmware of that card uses more option rom and on my asus board freezes it. Downgrade the firmware or try the motherboard settings in IDE. I've also had someone with the same board but a different card do the same and found changing to RAID worked. I suspect that AHCI uses more of the option ROM and doesn't leave enough for the supermicro card to boot.

 

Josh

 

I have a similar configuration.  I don't think I ever disabled Int 13 on the SASLP.  I beleive the reason for this was the limit the number of disks that show up in the BIOS.  If there are too many, the USB drive can disappear and then you can't boot.  I was able to configure my USB stick as a forced floppy and boot off of it as a removable disk.  This avoids all of the headaches with the disk count.  I would recommend that configuration to keep you from having to keep playing with the boot options every time you change disks.

 

Are the drives attached to the SASLP controller showing up in unRAID?

 

I think my JMB is in "BASIC" mode, not RAID mode.  AHCI is right.

 

I would say that 73C is too hot for your CPU.  40C - 50C is more typical.  Did you install the heat sink fan (HSF) yourself?  If so, perhaps you did not install it correctly and there is poor contact between the CPU and the HSF.  That would cause high temps.

 

If your SASLP is not responding in this computer, I would suggest trying to install it in another computer.

  • Author

Hi!

 

Thanks to both, joshpond & bjp999. I've mada some pics (sorry, but I could not capture the screen) of the BIOS screens:

 

1. This is the Adaptec screen. Everything seems ok and when I connect a HDDs it does appear in the Screen.

 

http://img5.imageshack.us/i/adaptec.jpg/

 

2. This is the JMicron. It seems OK too and recognized a HDD when I plug one to it.

 

http://img856.imageshack.us/i/jmicron.jpg/

 

3. These are (I guess) the 1 & 2 Supermicro's screens. As it can be seen in the pics, It has the .21 firmware Version and It's recognized by the Bios. I don't know if there would be 2 Controllers & Groups as the Micro has 2 MiniSas ports for 4 SATA each one.

Even a HDDs is installed, it can be seen in the pic that "No Physical Disk" is recognized.

 

http://img816.imageshack.us/i/supermicro1.jpg/

http://img718.imageshack.us/i/supermicro2.jpg/

 

4. These are pics of the two cards, first one when I start the tower and last one when the Dos Promt is still ready. At firs, every light in the Adaptec are on and I can observe that one light lights on green a second in the Supermicro. When the DOS system is ready, there is only a green light in the Adaptec and no light in the Supermicro. Both cards are well fitted in the MOBO.

 

http://img860.imageshack.us/i/cards1.jpg/

http://img848.imageshack.us/i/cards2.jpg/

 

I have set in the BIOS the SATA to IDE (as default), the JMICRON to RAID and the Internal Graphics Adapter to IGD or PCI/IGD (default is PEG/PCI), but the Supermicro still doesnot recognized any HDDs.

Since I disabled the INT 13 option in the Supermicro BIOS I can enter in it with CTRL + M again.

 

I was thinking about this two options:

 

A - I should change the Supermicro Firm to the .15 one (to save ROM). But it should work with the .21. I can give it a try to the .15 downgrade, I dont know...

B - The MiniSAS-Sata cable is not the right one. I bought this one:

 

http://www.planetronic.es/cable-interno-mini-sas-36p-sff8087-sata-05m-p-20598.html

 

I've read in this post about "forward or reverse" breakout cables. Mine's reference is SFF8087, so I supposed it's a forward one. This is the post:

 

http://lime-technology.com/forum/index.php?topic=5840.0

 

Maybe I must buy these SFF8087OCF-05 3Ware cables.

 

About the CPU high Temperature (73.5 ºC) with the Celeron 430 processor and the stock Intel CPU fan cooler (it doesn't fit well in the Asus mobo, maybe that's the problem), I'll buy this one:

 

Scythe Big Shuriken Low Profile (29 Euros). It doesn't cost a lot, it will fit in the case/mobo and seems to be very quiet:

 

http://www.scythe-eu.com/en/products/cpu-cooler/big-shuriken.html

 

Any suggestions for the same price?

 

Hope you can help me to solve this. My next step is pleclear 15 Samsung HDDs and install Unraid + UnMenu, and after that copy all my files (+ or - 24TB to the tower). There's still a lot of job to do.... ;)

 

The SASLP is in the x16 slot, the Adaptec in the x4 slot.

 

And the Adaptect, MB, and JMicron ports all work.

 

But the SASLP ports do not work.

 

Can you confirm these are the facts?

 

Are you sure you have the SAS to SATA forward breakout cables.  Also, make sure the SAS plug is securely plugged until it clicks in place.

 

 

  • Author

The SASLP is in the x16 slot, the Adaptec in the x4 slot.

 

And the Adaptect, MB, and JMicron ports all work.

 

But the SASLP ports do not work.

 

Can you confirm these are the facts?

 

Yes, that's it.

 

Are you sure you have the SAS to SATA forward breakout cables.  Also, make sure the SAS plug is securely plugged until it clicks in place.

 

These are the cables I bought (and I'm sure they are well plugged):

 

http://www.planetronic.es/cable-interno-mini-sas-36p-sff8087-sata-05m-p-20598.html

 

Do you think they are Forward? There is no written info in the cables (the reference when I bought them was SFF8087, so I supposed they were forward ones). The company that bought them to me told me that these are the only MiniSas-Sata cables they have. I've asked about the differences between "forward or reverse", but they don't have this information at all.

 

Should I buy new ones as the SFF8087OCF-05 3Ware cables?

 

http://cgi.ebay.de/AMCC-3ware-Multilane-Breakout-Kabel-CBL-SFF8087OCF-SAS-/170615155302?pt=DE_Technik_Computerzubeh%C3%B6r_Kabel_Adapter&hash=item27b974aa66

 

Or should I try to install the .15 firm in the Supermicro?

 

As you can watch in the pics, I think the SASLP is recognized in the BIOS (at least 1 Controller & Group), but not the HDDS. And I can't enter in the SASLP BIOS anymore since I disabled the INT 13 option. I press "CTRL + M" but nothing happens.

 

The SASLP is in the x16 slot, the Adaptec in the x4 slot.

 

And the Adaptect, MB, and JMicron ports all work.

 

But the SASLP ports do not work.

 

Can you confirm these are the facts?

 

Yes, that's it.

 

Are you sure you have the SAS to SATA forward breakout cables.  Also, make sure the SAS plug is securely plugged until it clicks in place.

 

These are the cables I bought (and I'm sure they are well plugged):

 

http://www.planetronic.es/cable-interno-mini-sas-36p-sff8087-sata-05m-p-20598.html

 

Do you think they are Forward? There is no written info in the cables (the reference when I bought them was SFF8087, so I supposed they were forward ones). The company that bought them to me told me that these are the only MiniSas-Sata cables they have. I've asked about the differences between "forward or reverse", but they don't have this information at all.

 

Should I buy new ones as the SFF8087OCF-05 3Ware cables?

 

http://cgi.ebay.de/AMCC-3ware-Multilane-Breakout-Kabel-CBL-SFF8087OCF-SAS-/170615155302?pt=DE_Technik_Computerzubeh%C3%B6r_Kabel_Adapter&hash=item27b974aa66

 

Or should I try to install the .15 firm in the Supermicro?

 

As you can watch in the pics, I think the SASLP is recognized in the BIOS (at least 1 Controller & Group), but not the HDDS. And I can't enter in the SASLP BIOS anymore since I disabled the INT 13 option. I press "CTRL + M" but nothing happens.

 

 

I don't speak (or read) any language but English.  Sorry :(

 

I know that you need a forward breakout cable like THIS ONE.  I can't read the other one you posted, does it say Forward Breakout in German?

 

I have never heard of a controler that, when you change a firmware setting, it prevents you from re-entering the BIOS.  Leads me to believe something is wrong with it.  Did you try disconnecting the cable and booting with it not connected to any drives?  If the cable is the wrong type, the signal it is getting may be causing the malfunction and interfering with it allowing the BIOS program to run.  Seem like a long shot.

 

You may have the wrong cable, a bad cable, a bad controller, or a bad motherboard.  Your processor could also be frying, but that would not be related to this problem.

 

I think I'd try putting the SASLP in another computer and see if you can get into the BIOS with not cable / no drive attached.  And then see if it will recognize an attached disk.  If it acts exactly like it does in the P5B VM DO, then you have isolated the problem to the controller or the cable.

 

 

  • Author

Yes, both are the same cable, but I'll give a try to your idea and test the card and the cable in other pc. Thanks again a lot.

Why not switch the controllers over - the SM in the x4 slot and the Adaptec in the x16 slot and try it this way. Or remove the Adaptec temporarily and try the SM in the x4 slot.

Alternatively if you have access to another motherboard you can try the SM card there to identify if the cable is the problem.

 

 

  • Author

I've installed Unmenu, and in "PCI Devices" I have this:

 

03:00.0 RAID bus controller: Adaptec Serial ATA II RAID 1430SA (rev 02)

Subsystem: Adaptec Serial ATA II RAID 1430SA

Flags: bus master, fast devsel, latency 0, IRQ 16

Memory at fea00000 (64-bit, non-prefetchable)

I/O ports at e800

Memory at fe900000 (64-bit, non-prefetchable)

Capabilities: [40] Power Management version 2

Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

Capabilities: [60] Express Legacy Endpoint, MSI 00

Capabilities: [100] Advanced Error Reporting

Kernel driver in use: sata_mv

Kernel modules: sata_mv

 

 

01:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01)

Subsystem: Marvell Technology Group Ltd. Unknown device 6480

Flags: bus master, fast devsel, latency 0, IRQ 16

I/O ports at cc00

Memory at fe6f0000 (64-bit, non-prefetchable)

Expansion ROM at fe680000 [disabled]

Capabilities: [48] Power Management version 2

Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

Capabilities: [e0] Express Legacy Endpoint, MSI 00

Capabilities: [100] Advanced Error Reporting

Kernel driver in use: mvsas

Kernel modules: mvsas

 

 

Does it mean that the Supermicro is well pluged and recognized in the Mobo & Unraid?

The HDDs are recognized in the Adaptec, but not in the Supermicro.

Maybe someone could answer me. If it's recognized then the problem are the cables for sure.

 

That's similar to the report I get with my SASLP board. I believe you do have the wrong type cable, or a bad cable.

Post the complete syslog as I do not know how the card will display under the "PCI devices" in Unmenu.

 

The cable could be the reason why they are not recognized.

I do not know Spanish but the description on the vendor "para conexión de dispositivos SAS a dispositivos SATA."  implies the same passive (backplane) connection to SATA connection and this is the wrong "reverse breakout" cable.

 

It is a nice store and I am surprised that they do not have the other "forward breakout" cable. The description should be something as " para conexión de controller SAS a dispositivos SATA." - sorry not sure the propper Spanish word for "controller"

 

  • Author

Thanks to both, ratmice & bcbgboy13. Here it's the complete syslog:

 

PCI Devices

 

00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 02)

  Subsystem: ASUSTeK Computer Inc. Unknown device 81e9

  Flags: bus master, fast devsel, latency 0

  Capabilities: [e0] Vendor Specific Information

 

00:01.0 PCI bridge: Intel Corporation 82Q963/Q965 PCI Express Root Port (rev 02) (prog-if 00 [Normal decode])

  Flags: bus master, fast devsel, latency 0

  Bus: primary=00, secondary=01, subordinate=01, sec-latency=0

  I/O behind bridge: 0000c000-0000cfff

  Memory behind bridge: fe600000-fe6fffff

  Capabilities: [88] Subsystem: Intel Corporation Unknown device 277d

  Capabilities: [80] Power Management version 3

  Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+

  Capabilities: [a0] Express Root Port (Slot+), MSI 00

  Capabilities: [100] Virtual Channel

  Capabilities: [140] Root Complex Link

  Kernel driver in use: pcieport

 

00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81e9

  Flags: bus master, fast devsel, latency 0, IRQ 11

  Memory at fe500000 (32-bit, non-prefetchable)

  Memory at e0000000 (64-bit, prefetchable)

  I/O ports at bc00

  Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-

  Capabilities: [d0] Power Management version 2

 

00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network Connection (rev 02)

  Subsystem: ASUSTeK Computer Inc. Unknown device 8268

  Flags: bus master, fast devsel, latency 0, IRQ 27

  Memory at fe4c0000 (32-bit, non-prefetchable)

  Memory at fe4fa000 (32-bit, non-prefetchable)

  I/O ports at b880

  Capabilities: [c8] Power Management version 2

  Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+

  Kernel driver in use: e1000e

  Kernel modules: e1000e

 

00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [uHCI])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0, IRQ 16

  I/O ports at b480

  Kernel driver in use: uhci_hcd

 

00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02) (prog-if 00 [uHCI])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0, IRQ 17

  I/O ports at b800

  Kernel driver in use: uhci_hcd

 

00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02) (prog-if 20 [EHCI])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0, IRQ 18

  Memory at fe4fb800 (32-bit, non-prefetchable)

  Capabilities: [50] Power Management version 2

  Capabilities: [58] Debug port: BAR=1 offset=00a0

  Kernel driver in use: ehci_hcd

 

00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])

  Flags: bus master, fast devsel, latency 0

  Bus: primary=00, secondary=03, subordinate=03, sec-latency=0

  I/O behind bridge: 0000e000-0000efff

  Memory behind bridge: fe800000-feafffff

  Prefetchable memory behind bridge: 0000000080000000-00000000801fffff

  Capabilities: [40] Express Root Port (Slot+), MSI 00

  Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+

  Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Capabilities: [a0] Power Management version 2

  Capabilities: [100] Virtual Channel

  Capabilities: [180] Root Complex Link

  Kernel driver in use: pcieport

 

00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02) (prog-if 00 [Normal decode])

  Flags: bus master, fast devsel, latency 0

  Bus: primary=00, secondary=02, subordinate=02, sec-latency=0

  I/O behind bridge: 0000d000-0000dfff

  Memory behind bridge: fe700000-fe7fffff

  Prefetchable memory behind bridge: 0000000080200000-00000000803fffff

  Capabilities: [40] Express Root Port (Slot+), MSI 00

  Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+

  Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Capabilities: [a0] Power Management version 2

  Capabilities: [100] Virtual Channel

  Capabilities: [180] Root Complex Link

  Kernel driver in use: pcieport

 

00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [uHCI])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0, IRQ 23

  I/O ports at b000

  Kernel driver in use: uhci_hcd

 

00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02) (prog-if 00 [uHCI])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0, IRQ 19

  I/O ports at b080

  Kernel driver in use: uhci_hcd

 

00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02) (prog-if 00 [uHCI])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0, IRQ 18

  I/O ports at b400

  Kernel driver in use: uhci_hcd

 

00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02) (prog-if 20 [EHCI])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0, IRQ 23

  Memory at fe4fb400 (32-bit, non-prefetchable)

  Capabilities: [50] Power Management version 2

  Capabilities: [58] Debug port: BAR=1 offset=00a0

  Kernel driver in use: ehci_hcd

 

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2) (prog-if 01 [subtractive decode])

  Flags: bus master, fast devsel, latency 0

  Bus: primary=00, secondary=04, subordinate=04, sec-latency=32

  Memory behind bridge: feb00000-febfffff

  Capabilities: [50] Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

 

00:1f.0 ISA bridge: Intel Corporation 82801HO (ICH8DO) LPC Interface Controller (rev 02)

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, medium devsel, latency 0

  Capabilities: [e0] Vendor Specific Information

 

00:1f.2 SATA controller: Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) 6 port SATA AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0])

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 28

  I/O ports at a880

  I/O ports at a800

  I/O ports at a480

  I/O ports at a400

  I/O ports at a080

  Memory at fe4f9800 (32-bit, non-prefetchable)

  Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/4 Enable+

  Capabilities: [70] Power Management version 3

  Capabilities: [a8] SATA HBA

  Kernel driver in use: ahci

  Kernel modules: ahci

 

00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)

  Subsystem: ASUSTeK Computer Inc. Unknown device 81eb

  Flags: medium devsel, IRQ 18

  Memory at fe4fb000 (32-bit, non-prefetchable)

  I/O ports at 0400

  Kernel driver in use: i801_smbus

  Kernel modules: i2c-i801

 

01:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01)

  Subsystem: Marvell Technology Group Ltd. Unknown device 6480

  Flags: bus master, fast devsel, latency 0, IRQ 16

  I/O ports at cc00

  Memory at fe6f0000 (64-bit, non-prefetchable)

  Expansion ROM at fe680000 [disabled]

  Capabilities: [48] Power Management version 2

  Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

  Capabilities: [e0] Express Legacy Endpoint, MSI 00

  Capabilities: [100] Advanced Error Reporting

  Kernel driver in use: mvsas

  Kernel modules: mvsas

 

02:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0])

  Subsystem: ASUSTeK Computer Inc. P5B [JMB363]

  Flags: bus master, fast devsel, latency 0, IRQ 16

  Memory at fe7fe000 (32-bit, non-prefetchable)

  Expansion ROM at fe7e0000 [disabled]

  Capabilities: [68] Power Management version 2

  Capabilities: [50] Express Legacy Endpoint, MSI 01

  Kernel driver in use: ahci

  Kernel modules: ahci

 

02:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03) (prog-if 85 [Master SecO PriO])

  Subsystem: ASUSTeK Computer Inc. P5B [JMB363]

  Flags: bus master, fast devsel, latency 0, IRQ 17

  I/O ports at dc00

  I/O ports at d880

  I/O ports at d800

  I/O ports at d480

  I/O ports at d400

  Capabilities: [68] Power Management version 2

  Kernel driver in use: JMicron IDE

  Kernel modules: pata_jmicron, jmicron

 

03:00.0 RAID bus controller: Adaptec Serial ATA II RAID 1430SA (rev 02)

  Subsystem: Adaptec Serial ATA II RAID 1430SA

  Flags: bus master, fast devsel, latency 0, IRQ 16

  Memory at fea00000 (64-bit, non-prefetchable)

  I/O ports at e800

  Memory at fe900000 (64-bit, non-prefetchable)

  Capabilities: [40] Power Management version 2

  Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

  Capabilities: [60] Express Legacy Endpoint, MSI 00

  Capabilities: [100] Advanced Error Reporting

  Kernel driver in use: sata_mv

  Kernel modules: sata_mv

 

04:01.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])

  Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard

  Flags: bus master, medium devsel, latency 64, IRQ 5

  Memory at febff800 (32-bit, non-prefetchable)

  Memory at febf8000 (32-bit, non-prefetchable)

  Capabilities: [44] Power Management version 2

 

 

Still thinking that the cable is the reason why they are not recognized?

I'll buy 2 of these cables:

 

http://cgi.ebay.de/AMCC-3ware-Multilane-Breakout-Kabel-CBL-SFF8087OCF-SAS-/170615155302?pt=DE_Technik_Computerzubeh%C3%B6r_Kabel_Adapter&hash=item27b974aa66

 

Just some shorts questions:

 

1 - My unraid towers lasts more than 5 minutes to be ready:

 

1' minute to load the MOBO + Adaptec + Supermicro BIOS

10'' to load bzimage

3' 30'' to load bzroot

1' to load Unraid's rest

 

Is that normal? more than 5 to be ready? If it's always that way I would think about suspend instead of powerdown. Is that possible? How?

 

2 - Is it possible to auto log in? I mean, switch on the tower and don't have to write "root" to get in the Unraid console. Maybe I must change something in the config/go file?

 

3 - This is my CPU info. Take a look about Temp. Is it right?

 

Sensor info (from /usr/bin/sensors)

 

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +55.0 C  (high = +82.0 C, crit = +100.0 C) 

 

I'm pleclearing 3 HDDs and the Temp has increased a lot. Now it's 72.0 C...

 

The more I investigate and complete my Unraid, the more questions I have... 

 

Thanks in advance for your time and help.

 

It sounds as if your USB port is running at USB 1.0 speeds when booting.  Look for a BIOS option to enable 2.0 speed.

  • Author

Thanks, Joe. I've changed to USB 2.0 (High Speed 480Mbps) and now it lasts 2 min to start and 1 min to shutdown. Much better.

I'll change the CPU fan today (the CPU Temp must decrease a lot; now it's 55º C & 72-75ºC when pleclearing) and hope have this week the new and properly Minisas cables. I'll report.

 

What does "`proftpd' uses 32-bit capabilities (legacy support in use)" mean? Is it important? How can it be fixed?

Artagnan any update on the cards with the right cables ?

does it work now ?

 

  • Author

Yes, I received the new cables yesterday and they work properly. Good luck for me ;)

Yes, I received the new cables yesterday and they work properly. Good luck for me ;)

 

Does the BIOS screen for the controller come up and allow you to enter to firmware program to change parameters with the right cables in place?

  • Author

Yes, I received the new cables yesterday and they work properly. Good luck for me ;)

 

Does the BIOS screen for the controller come up and allow you to enter to firmware program to change parameters with the right cables in place?

 

Yes, I entered to the controller Bios without a problem.

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.