External eSATA drive not recognized on 2nd power up

[Patrick Lists]

Hi,

I have an up-to-date F16 x86_64 box with 2 eSATA ports on the back 
powered by a JMicron JMB362 chip. When I attach an external SATA drive 
to the eSATA port and power up the drive it is recognized fine. But when 
I power down that drive, wait 2 minutes, and power it up again the drive 
is no longer recognized. Also there are no messages related to the 2nd 
power up in /var/log/messages. All SATA controllers are set to AHCI in 
the BIOS. No idea where to go from here. Anyone have any suggestions how 
I can fix this?

Thanks and regards,
Patrick

[Bill Davidsen]

Patrick Lists wrote:
> Hi,
>
> I have an up-to-date F16 x86_64 box with 2 eSATA ports on the back
> powered by a JMicron JMB362 chip. When I attach an external SATA drive
> to the eSATA port and power up the drive it is recognized fine. But when
> I power down that drive, wait 2 minutes, and power it up again the drive
> is no longer recognized. Also there are no messages related to the 2nd
> power up in /var/log/messages. All SATA controllers are set to AHCI in
> the BIOS. No idea where to go from here. Anyone have any suggestions how
> I can fix this?

Will you settle for something easy to give a data point? When powered 
down, unplug the eSATA box and replug. If /var/log/messages tells you 
anything, share it with us, if it suddenly works again, that's a data point.

In the mean time, I have a similar issue, and will try powering up the 
system with the RAID already up and see if it solves one of _my_ 
problems, the eSATA box works with some boxen and not other, so I will 
try all states of power on, off, cable connected, and see what it 
yields. I thought the cheap ATOM system just had an unsupported chip for 
the connect.

[Patrick Lists]

On 03/29/2012 03:14 AM, Bill Davidsen wrote:
> Will you settle for something easy to give a data point? When powered
> down, unplug the eSATA box and replug. If /var/log/messages tells you
> anything, share it with us, if it suddenly works again, that's a data
> point.

No change and no messages at all. Here's what I did: turn off the 
external disk (which was recognized), watch the ata & sd messages in 
/var/log/messages about the disk no longer being there, wait a minute, 
remove eSATA cable, wait a minute, plug eSATA cable back in. Nothing. 
Powering the external disk up also does not make a difference.
> In the mean time, I have a similar issue, and will try powering up the
> system with the RAID already up and see if it solves one of _my_
> problems, the eSATA box works with some boxen and not other, so I will
> try all states of power on, off, cable connected, and see what it
> yields. I thought the cheap ATOM system just had an unsupported chip for
> the connect.

Good luck. Hope you find a way to make it work.

Regards,
Patrick

[James Wilkinson]

Patrick Lists wrote:
> I have an up-to-date F16 x86_64 box with 2 eSATA ports on the back
> powered by a JMicron JMB362 chip. When I attach an external SATA
> drive to the eSATA port and power up the drive it is recognized
> fine. But when I power down that drive, wait 2 minutes, and power it
> up again the drive is no longer recognized. Also there are no
> messages related to the 2nd power up in /var/log/messages. All SATA
> controllers are set to AHCI in the BIOS. No idea where to go from
> here. Anyone have any suggestions how I can fix this?

Does it work with older (pre 3.3) kernels? It might have something to do
with http://lkml.org/lkml/2012/3/4/152

Hope this helps,

James.

[Patrick Lists]

Hi James,

On 03/30/2012 09:30 PM, James Wilkinson wrote:
> Does it work with older (pre 3.3) kernels? It might have something to do
> with http://lkml.org/lkml/2012/3/4/152

I don't have a pre-3.3 kernel as these are kickstart deployments of F16 
+ updates. Thank you for that excellent link. Seems it's a bug so I'll 
just wait for 3.4 or F17 where I hope it will be fixed. Meanhwile I 
reported it here: https://bugzilla.redhat.com/show_bug.cgi?id=808743

Thanks again.

Regards,
Patrick

[James Wilkinson]

I asked Patrick:
> Does it work with older (pre 3.3) kernels?

Patrick Lists wrote:
> I don't have a pre-3.3 kernel as these are kickstart deployments of
> F16 + updates.

http://koji.fedoraproject.org/koji/packageinfo?packageID=8 has links to
all the recent kernel builds, including the last 3.2 Fedora kernels.

You should be able to just download and install a suitable kernel.

Hope this helps,

James.

[Dr J Austin]

On Sat, 2012-03-31 at 19:09 +0100, James Wilkinson wrote:
> I asked Patrick:
> > Does it work with older (pre 3.3) kernels?
>
> Patrick Lists wrote:
> > I don't have a pre-3.3 kernel as these are kickstart deployments of
> > F16 + updates.
>
> http://koji.fedoraproject.org/koji/packageinfo?packageID=8 has links to
> all the recent kernel builds, including the last 3.2 Fedora kernels.
>
> You should be able to just download and install a suitable kernel.
>
> Hope this helps,
>
> James.
>
> -- 
> E-mail:     james@ |     “Sir, they’ve taken Mr. Rimmer!”
> aprilcottage.co.uk |     “Quick, let’s get out of here before they bring him
>                    | back!”
>                    |     -- Kryten and Cat, ‘Red Dwarf’

Just to say this problem still appears to be present with

ja@minix ~ 1$ uname -a
Linux minix 3.3.1-3.fc16.x86_64 #1 SMP Wed Apr 4 18:08:51 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux

where it is meant to have been cured

I have added details to
https://bugzilla.redhat.com/show_bug.cgi?id=806676

I hope it gets solved soon as I use eSATA hotplug often each day !

John

[Dr J Austin]

On Sun, 2012-04-08 at 12:34 +0100, John Austin wrote:
> On Sat, 2012-03-31 at 19:09 +0100, James Wilkinson wrote:
> > I asked Patrick:
> > > Does it work with older (pre 3.3) kernels?
> >
> > Patrick Lists wrote:
> > > I don't have a pre-3.3 kernel as these are kickstart deployments of
> > > F16 + updates.
> >
> > http://koji.fedoraproject.org/koji/packageinfo?packageID=8 has links to
> > all the recent kernel builds, including the last 3.2 Fedora kernels.
> >
> > You should be able to just download and install a suitable kernel.
> >
> > Hope this helps,
> >
> > James.
> >
> > -- 
> > E-mail:     james@ |     “Sir, they’ve taken Mr. Rimmer!”
> > aprilcottage.co.uk |     “Quick, let’s get out of here before they bring him
> >                    | back!”
> >                    |     -- Kryten and Cat, ‘Red Dwarf’
>
> Just to say this problem still appears to be present with
>
> ja@minix ~ 1$ uname -a
> Linux minix 3.3.1-3.fc16.x86_64 #1 SMP Wed Apr 4 18:08:51 UTC 2012
> x86_64 x86_64 x86_64 GNU/Linux
>
> where it is meant to have been cured
>
> I have added details to
> https://bugzilla.redhat.com/show_bug.cgi?id=806676
>
> I hope it gets solved soon as I use eSATA hotplug often each day !
>
> John

Not fixed for me using
ja@minix ~ 1$ uname -a
Linux minix 3.3.1-5.fc16.x86_64

but it looks as if this may be the problem

http://www.spinics.net/lists/linux-ide/msg43173.html
(Date: Fri, 13 Apr 2012 09:24:07 +08002012_04_13)

"...
> The fundamental problem with this patch is that all SATA ports are 
> hotpluggable... even the ones the firmware/silicon failed to mark as 
> hotpluggable via AHCI's PORT_CMD_MPSP | PORT_CMD_HPCP

So the acceptable solution is to add runtime pm support for hotpluggable
port.

I'll send new patches.

Thanks,
Lin Ming"

John