It's good to hear someone is working on this.
With all due respect I have no idea who is presently on the SATA group.
Frankly I gave up trying to keep track of who is in what groups, because
every time I send a message about a problem, I find the engineer has
changed groups. This is exactly why we need one unified bug tracking system
to replace both b.o.o and SMI's internal one. It would also help those of
us outside SMI to at least post patches, even if the (laudable) goal of
having us able to do putbacks is still incomplete.
Andrew Hettinger
http://Prominic.NET || [EMAIL PROTECTED]
Tel: 866.339.3169 (toll free) -or- +1.217.356.2888 x.110 (int'l)
Fax: 866.372.3356 (toll free) -or- +1.217.356.3356 (int'l)
Mobile direct: 1.217.621.2540
CompTIA A+, CompTIA Network+, MCP
[EMAIL PROTECTED] wrote on 06/20/2008 10:08:18 AM:
> Andrew M. Hettinger wrote:
> >
> > See below.
> >
> > Andrew Hettinger
> > http://Prominic.NET || [EMAIL PROTECTED]
> > Tel: 866.339.3169 (toll free) -or- +1.217.356.2888 x.110 (int'l)
> > Fax: 866.372.3356 (toll free) -or- +1.217.356.3356 (int'l)
> > Mobile direct: 1.217.621.2540
> > CompTIA A+, CompTIA Network+, MCP
> >
> > [EMAIL PROTECTED] wrote on 06/19/2008 08:03:54
PM:
> >
> > > I have two AOC-SAT-MV8 cards running on a SuperMicro X7DBE+ board
> > > which uses the Intel 5000P chipset and I've had a few problems with
my
> > > setup (and most likely some user error or misunderstanding of how
> > > things should work) and it was suggested that I try asking on this
> > > forum. The drives are connected to a SuperMicro SAS backplane
(BPN-
> > > SAS-836TQ). I apologize for the lengthy post but I wasn't sure if
the
> > > problems were all related or separate.
> > >
> > > The first problem I am seeing is that when I plug in a new drive into
> > > my system, the drives are detected and they show up in cfgadm but
they
> > > aren't automatically configured. I have to first run "cfgadm -c
> > > configure" for the drive to be fully set up and accessible. I have
> > > noticed this behavior when using a Seagate 750GB SATA II drive. If I
> > > then execute "cfgadm -c unconfigure" and remove the drive and re-
> > > insert it then it seems to (at least I think it did but I could be
> > > losing my mind) automatically configure it just fine. It seems to me
> > > that the drive should be automatically configured when it is
> > > inserted. This scenario seemed to work just fine with the Areca
> > > controller card that I was using at one point.
> > >
> > > The first time I insert the drive into a drive slot I only see
> > > messages like the following:
> > >
> > > Jun 19 17:59:39 storage-1 sata: [ID 801593 kern.warning] WARNING: /
> > > [EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL
> > > PROTECTED]/pci8086,[EMAIL PROTECTED]/pci808
> > > 6,[EMAIL PROTECTED],2/pci11ab,[EMAIL PROTECTED]:
> > > Jun 19 17:59:39 storage-1 SATA device detected at port 6
> > > Jun 19 17:59:39 storage-1 sata: [ID 663010 kern.info] /[EMAIL
> > > PROTECTED],0/
> > > pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL
> > > PROTECTED]/pci8086,[EMAIL PROTECTED],2/pc
> > > i11ab,[EMAIL PROTECTED] :
> > > Jun 19 17:59:39 storage-1 sata: [ID 761595 kern.info] SATA disk
> > > device at port 6
> > > Jun 19 17:59:39 storage-1 sata: [ID 846691 kern.info] model
> > > ST3750640AS
> > > Jun 19 17:59:39 storage-1 sata: [ID 693010 kern.info] firmware
3.AAE
> > > Jun 19 17:59:39 storage-1 sata: [ID 163988 kern.info] serial
> > > number 5QD52N2B
> > > Jun 19 17:59:39 storage-1 sata: [ID 594940 kern.info] supported
> > > features:
> > > Jun 19 17:59:39 storage-1 sata: [ID 981177 kern.info] 48-bit LBA,
> > > DMA, Native Command Queueing, SMART, SMART self-test
> > > Jun 19 17:59:39 storage-1 sata: [ID 643337 kern.info] SATA Gen2
> > > signaling speed (3.0Gbps)
> > > Jun 19 17:59:39 storage-1 sata: [ID 349649 kern.info] Supported
> > > queue depth 32
> > > Jun 19 17:59:39 storage-1 sata: [ID 349649 kern.info] capacity =
> > > 1465149168 sectors
> > >
> > >
> > > After I run "cfgadm -c configure" I see the following messages:
> > >
> > > Jun 19 18:09:20 storage-1 scsi: [ID 193665 kern.info] sd46 at
> > > marvell88sx1: target 6 lun 0
> > > Jun 19 18:09:20 storage-1 genunix: [ID 936769 kern.info] sd46 is /
> > > [EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL
> > > PROTECTED],3/pci11ab,[EMAIL PROTECTED]/[EMAIL PROTECTED],0
> > > Jun 19 18:09:20 storage-1 genunix: [ID 408114 kern.info] /[EMAIL
> > > PROTECTED],0/
> > > pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL PROTECTED],3/pci11ab,[EMAIL
> > > PROTECTED]/[EMAIL PROTECTED],0 (sd46) online
> > > Jun 19 18:09:23 storage-1 scsi: [ID 193665 kern.info] sgen27 at
> > > marvell88sx1: target 6 lun 0
> > > Jun 19 18:09:23 storage-1 genunix: [ID 936769 kern.info] sgen27 is /
> > > [EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL
> > > PROTECTED],3/pci11ab,[EMAIL PROTECTED]/[EMAIL PROTECTED],0
> > >
> >
> > This is a known limit^H^H^H^H^Hfeature. I believe RFEs have been filed
> > on it (because it is something I have complained about in the past).
> > The rest I have not seen, and am unsure of.
> >
> There were recent changes to the configuration behavior. I think you
> are running Solaris Nevada (OpenSolaris)
> and if so, you can update to a more recent release. Also, you might get
> more response if you
> make sure someone in the SATA group is CC'ed to your messages. I am no
> longer with that group.
>
> Regards,
> Lida
> >
> >
> > >
> > > The second problem I am having is that if I connect the Seagate drive
> > > and can see the disk in cfgadm and then run "devfsadm -C -c disk"
then
> > > the port disappears from cfgadm and any attempt to execute "cfgadm -c
> > > configure" on that port fails saying that it can't identify the
device
> > > or port (I don't have the exact error message in front of me). If I
> > > remove the drive, then it shows up in the cfgadm list as empty.
> > > However, if I re-insert it, that port disappears from the cfgadm list
> > > and I am still unable to issue a "cfgadm -c configure" command. The
> > > only way that I've figured out how to recover from this is to reboot.
> > > It seems to me that in this scenario that I should be able access the
> > > drive without having to reboot.
> > >
> > >
> > > The third problem that I've been having is that with Samsung drives,
> > > if I boot with the Samsung drives plugged in, they work just fine.
> > > However, if I try to insert a Samsung drive after I've already booted
> > > (or remove it and try to reinsert it), then when I issue the command
> > > "cfgadm -c configure" it returns successfully but any attempt to run
> > > any command that attempts to access the drive (cfgadm, format,
> > > devfsadm -C -c disk) all hang until I remove the drive which then
> > > causes a few "Command failed to complete...Device is gone" error
> > > messages. The Seagate drives do not exhibit this behavior as far as
I
> > > can tell so I'm not sure if it is a bug in the driver, a bug in the
> > > drives, a bug in the controller card, or what but if there are
> > > suggestions for getting additional debug information to narrow down
> > > the problem I'd appreciate any help.
> > >
> > > When I connect the Samsung drive, I see the following messages:
> > >
> > > Jun 19 18:09:11 storage-1 sata: [ID 801593 kern.warning] WARNING: /
> > > [EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL
> > > PROTECTED],3/pci11ab,[EMAIL PROTECTED]:
> > > Jun 19 18:09:11 storage-1 SATA device detected at port 6
> > > Jun 19 18:09:11 storage-1 sata: [ID 663010 kern.info] /[EMAIL
> > > PROTECTED],0/
> > > pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL PROTECTED],3/pci11ab,[EMAIL
> > > PROTECTED] :
> > > Jun 19 18:09:11 storage-1 sata: [ID 761595 kern.info] SATA disk
> > > device at port 6
> > > Jun 19 18:09:11 storage-1 sata: [ID 846691 kern.info] model SAMSUNG
> > > HD753LJ
> > > Jun 19 18:09:11 storage-1 sata: [ID 693010 kern.info] firmware
> > > 1AA01107
> > > Jun 19 18:09:11 storage-1 sata: [ID 163988 kern.info] serial number
> > > S13UJ1KQ112894
> > > Jun 19 18:09:11 storage-1 sata: [ID 594940 kern.info] supported
> > > features:
> > > Jun 19 18:09:11 storage-1 sata: [ID 981177 kern.info] 48-bit LBA,
> > > DMA, Native Command Queueing, SMART self-test
> > > Jun 19 18:09:11 storage-1 sata: [ID 643337 kern.info] SATA Gen2
> > > signaling speed (3.0Gbps)
> > > Jun 19 18:09:11 storage-1 sata: [ID 349649 kern.info] Supported
> > > queue depth 32
> > > Jun 19 18:09:11 storage-1 sata: [ID 349649 kern.info] capacity =
> > > 1465149168 sectors
> > >
> > >
> > > Any help and guidance is appreciated!
> > >
> > > _______________________________________________
> > > storage-discuss mailing list
> > > [email protected]
> > > http://mail.opensolaris.org/mailman/listinfo/storage-discuss
> >
> >
------------------------------------------------------------------------
> >
> > _______________________________________________
> > storage-discuss mailing list
> > [email protected]
> > http://mail.opensolaris.org/mailman/listinfo/storage-discuss
> >
>
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
