This might be of interest.. I had turned the drive off for about 20
minutes, then turned it back on. ata1.03 is now partially there, it is
recognized as a device, but of 0MB in size.

All of this is done with the 4726 turned on..

Bootlog11.txt -> I unplugged the 4726, waited 10 seconds, and plugged it
into the second port on the 3124. All 4 drives are there.

Bootlog12.txt -> I unplugged the 4726 again, waited 10 seconds, plugged
it back into the first (original) port, and ata1.03 is back..

Bootlog13.txt -> I powered the 4726 off, waited 10 seconds, turned it
back on. The same drive is missing now.

Bootlog14.txt -> I unplugged, waited 10 seconds, and re-plugged the 4726
into the same port (first eSATA port) and now ata1.03 is recognized and
accessible.


I'll make sure to turn on the timestamping for you tomorrow. Would want
me to redo this testing so you can have the timestamps also?

Thanks


Tejun Heo wrote:
> Andrew Ryder wrote:
>   
>> Tejun,
>>
>> I rebooted with the 4726 online during bootup, verified everything was
>> there by re-formatting the fs on each drive. I powered off the 4726 for
>> approx 15 seconds, turned it back on, and repeated the power on/off
>> again about 1 minute later.
>>
>> The first 3 drives are accessible, but the 4th drive on ata1.03 failed
>> to be recognized.
>>     
>
> Hmmm... That's interesting.  The fourth drive seemed to have gone out
> for lunch.  If you can, does connecting the drive to another port (be it
> PMP port or not) without removing power make the drive work again?  If
> you can't do that, does removing the drive and re-plugging revives it?
> Please try to determine who went out for lunch - the PMP port or the
> drive.  Also, can you please turn on CONFIG_PRINTK_TIME so that I can
> tell what's happening when?
>
> Thanks.
>
>