Richard Jacobsen
2010-Dec-17 19:29 UTC
[zfs-discuss] Supermicro AOC-SAT2-MV8 and 1TB Seagate Barracuda ES.2
Hi all, I''m getting a very strange problem with a recent OpenSolaris b134 install. System is: Supermicro X5DP8-G2 BIOS 1.6a 2x Supermicro AOC-SAT2-MV8 1.0b 11 Seagate Barracuda 1TB ES.2 ST31000340NS drives If I have any of the 11 1TB Seagate drives plugged into the controller, the AOC-SAT2-MV8 BIOS appears to detect them just fine, but I get the following problems: 1. Grub takes a long time to findroot 2. Once Grub finally finds the OS disk, OpenSolaris sits and hangs at the splash screen (verbose doesn''t even work) If I boot the system without any of these drives attached and then attach one, I get "Device failed to power up", and I can''t configure them with cfgadm or use them to create a pool. Every other disk I''ve tried in the box appears to work perfectly fine, so it appears to only be these ES.2s which are having a problem. Anyone have any ideas? Thanks, Richard
Richard Elling
2010-Dec-19 17:25 UTC
[zfs-discuss] Supermicro AOC-SAT2-MV8 and 1TB Seagate Barracuda ES.2
On Dec 17, 2010, at 11:29 AM, Richard Jacobsen wrote:> Hi all, > > I''m getting a very strange problem with a recent OpenSolaris b134 install. > > System is: > Supermicro X5DP8-G2 BIOS 1.6a > 2x Supermicro AOC-SAT2-MV8 1.0b > 11 Seagate Barracuda 1TB ES.2 ST31000340NS drives > > If I have any of the 11 1TB Seagate drives plugged into the controller, the AOC-SAT2-MV8 BIOS appears to detect them just fine, but I get the following problems: > > 1. Grub takes a long time to findrootIn cases where I''ve seen this, the cause was some sort of firmware bug or BIOS/firmware configuration. Some good configuration choices are: 1. disable power management 2. disable plug-n-play 3. set AHCI/IDE mode to AHCI 4. disable system controller (iDRAC, iLO, etc) over LAN HTH, -- richard> 2. Once Grub finally finds the OS disk, OpenSolaris sits and hangs > at the splash screen (verbose doesn''t even work) > > If I boot the system without any of these drives attached and then attach one, I get "Device failed to power up", and I can''t configure them with cfgadm or use them to create a pool. > > Every other disk I''ve tried in the box appears to work perfectly fine, so it appears to only be these ES.2s which are having a problem. > > Anyone have any ideas? > > Thanks, > Richard > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Marc Bevand
2010-Dec-21 08:51 UTC
[zfs-discuss] Supermicro AOC-SAT2-MV8 and 1TB Seagate Barracuda ES.2
Richard Jacobsen <richard <at> unixboxen.net> writes:> > Hi all, > > I''m getting a very strange problem with a recent OpenSolaris b134 install. > > System is: > Supermicro X5DP8-G2 BIOS 1.6a > 2x Supermicro AOC-SAT2-MV8 1.0bAs Richard pointed out this is a bug in the AOC-SAT2-MV8 firmware 1.0b. It incorrectly associates itself with other Marvell SATA controllers in the system, based on PCI IDs, causing all sort of strange issues: http://opensolaris.org/jive/message.jspa?messageID=254150#254150 I reverse engineered and patched 2 bytes in the firmware to fix the bug in my case. But I would recommend to simply exchange your cards with newer ones running a firmware labelled "3.x.x.x". I don''t think Richard''s suggestions will work (disabling AHCI or PnP) because even though it may disable onboard SATA controllers contributing to the PCI ID confusion, you have 2 x AOC-SAT2-MV8 so I suspect the 2 firmwares may not even correctly associate themselves to their own card (eg. it might attempt to initialize the same card during POST, leaving the other uninitialized.) -mrb