Cannot access eSata enclosure

[greenbeast]

when running IDE reset i get:

Code:

Reset IDE:
Marvell Serial ATA Adapter
Warning Integrated SATA is Powered Off
no device found

The enclosure does work when connected to my win7 laptop

any ideas?
i've done some searching but it's difficult to know which leads to follow given the change in devices, uboots and kernels over time

[greenbeast]

Tried to update kernel using these instructions.

Kernel stayed the same???

[Confusticated]

Please post the output of the 'version' command from the u-boot Marvell prompt.
I am looking for the u-boot version and compile date.

[greenbeast]

Code:

Marvell>> version

U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

[greenbeast]

how positively frustrating!

i've tried following these instructions. i forgot the

Code:

flash-kernel

now it doesn't boot correctly, although the esata does appear to be initialised and 'working'

now i'm left here :

Code:

[   85.829896] Kernel panic - not syncing: Fatal exception in interrupt
[   85.836291] [<c002cee4>] (unwind_backtrace+0x0/0xdc) from [<c02bd110>] (panic+0x34/0x128)
[   85.844529] [<c02bd110>] (panic+0x34/0x128) from [<c002abd8>] (die+0x248/0x284)
[   85.851888] [<c002abd8>] (die+0x248/0x284) from [<c002de78>] (__do_kernel_fault+0x68/0x80)
[   85.860208] [<c002de78>] (__do_kernel_fault+0x68/0x80) from [<c002e064>] (do_page_fault+0x1d4/0x1ec)
[   85.869397] [<c002e064>] (do_page_fault+0x1d4/0x1ec) from [<c0026280>] (do_DataAbort+0x34/0x94)
[   85.878150] [<c0026280>] (do_DataAbort+0x34/0x94) from [<c0026a8c>] (__dabt_svc+0x4c/0x60)
[   85.886462] Exception stack(0xc107fba8 to 0xc107fbf0)
[   85.891542] fba0:                   df9c0000 c1090b80 c107e000 00000100 df9c0000 df477d80
[   85.899775] fbc0: c1090b80 df9c0000 00000000 df815580 c0440f30 df527200 df527200 c107fbf0
[   85.908002] fbe0: bf2542e0 bf2542e0 a0000013 ffffffff
[   85.913157] [<c0026a8c>] (__dabt_svc+0x4c/0x60) from [<bf2542e0>] (ipv6_sock_mc_close+0xf4/0x10c [ipv6])
[   85.922815] [<bf2542e0>] (ipv6_sock_mc_close+0xf4/0x10c [ipv6]) from [<bf2350c4>] (inet6_release+0x2c/0x44 [ipv6])
[   85.933278] [<bf2350c4>] (inet6_release+0x2c/0x44 [ipv6]) from [<c0233734>] (sock_release+0x24/0x8c)
[   85.942474] [<c0233734>] (sock_release+0x24/0x8c) from [<c02337c0>] (sock_close+0x24/0x34)
[   85.950792] [<c02337c0>] (sock_close+0x24/0x34) from [<c00cd518>] (__fput+0x114/0x1f0)
[   85.958760] [<c00cd518>] (__fput+0x114/0x1f0) from [<c00c9fc0>] (filp_close+0x70/0x7c)
[   85.966729] [<c00c9fc0>] (filp_close+0x70/0x7c) from [<c0045d74>] (put_files_struct+0x80/0xe0)
[   85.975387] [<c0045d74>] (put_files_struct+0x80/0xe0) from [<c0047730>] (do_exit+0x1f8/0x64c)
[   85.983969] [<c0047730>] (do_exit+0x1f8/0x64c) from [<c002abe0>] (die+0x250/0x284)
[   85.991592] [<c002abe0>] (die+0x250/0x284) from [<c002de78>] (__do_kernel_fault+0x68/0x80)
[   85.999911] [<c002de78>] (__do_kernel_fault+0x68/0x80) from [<c002e064>] (do_page_fault+0x1d4/0x1ec)
[   86.009100] [<c002e064>] (do_page_fault+0x1d4/0x1ec) from [<c0026280>] (do_DataAbort+0x34/0x94)
[   86.017853] [<c0026280>] (do_DataAbort+0x34/0x94) from [<c0026a8c>] (__dabt_svc+0x4c/0x60)
[   86.026157] Exception stack(0xc107fe88 to 0xc107fed0)
[   86.031244] fe80:                   00000000 ffffffd0 00000000 00000000 00000000 00000000
[   86.039477] fea0: 00000000 00000000 c0027048 c107e000 00000000 bee98c3c 00000000 c107fed4
[   86.047705] fec0: 00000000 c01a7b18 00000013 ffffffff
[   86.052787] [<c0026a8c>] (__dabt_svc+0x4c/0x60) from [<c01a7b18>] (__memzero+0x78/0xc0)

best course of action?

[greenbeast]

i've upgraded the uBoot version

Code:

Marvell>> version

U-Boot 2011.03 (Apr 26 2011 - 21:50:07)
Marvell-Sheevaplug - eSATA - SD/MMC
gcc (Debian 4.5.2-8) 4.5.2
GNU ld (GNU Binutils for Debian) 2.21.0.20110327

it's now not booting my usb kernel at all.

More playing needed to get it working again...

[Confusticated]

To use a new u-boot with an old kernel (if that is what you are trying to do) you will need to set the 'machid' variable in u-boot (search this forum).

[greenbeast]

Confusticated, i feel like crying right now.

the current situation is that i have an eSata Sheeva that i can get to a marvell prompt, version as below:

Code:

Marvell>> version

U-Boot 2011.03 (Apr 26 2011 - 21:50:07)
Marvell-Sheevaplug - eSATA - SD/MMC
gcc (Debian 4.5.2-8) 4.5.2
GNU ld (GNU Binutils for Debian) 2.21.0.20110327

what is the best course of action regarding uboots and kernels and all that jazz, to get debian working again and able to access esata?

I feel like i've been through the mill with this device.

i just tried running the v1.0 installer but i just get an OpenOCD error:

Code:

Open On-Chip Debugger 0.2.0 (2009-07-26-14:56) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
Unknown command: adapter_khz 2000
 **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug

I've spent dozens of hours on this device since monday and don't appear any better off!?

[greenbeast]

ok back at a working debian login.

Code:

root@debian:~# uname -a
Linux debian 2.6.32-5-kirkwood #1 Thu Nov 3 18:29:02 UTC 2011 armv5tel GNU/Linux

getting no esata

[Confusticated]

dmesg -c

to clear the kernel message buffer, then hotplug the enclosure

Code:

dmesg

to see what the kernel found

[greenbeast]

I get nothing.

Code:

root@debian:~# dmesg
root@debian:~#

i don't know about other enclosures but this one doesn't stay powered up unless actively connected to something.

If i interrupt the boot process at uboot and do 'ide reset' it will power up and detect the enclosure.
But debian doesn't want to know

[Confusticated]

doesn't stay powered up

No experience of this, I would forget the enclosure and connect an eSATA drive directly to the plug.
After I have that working, I would then go back to trying with the enclosure.

[greenbeast]

ok, i just spent £60 on it to have a nice RAID1 array, so i can't not use it.

I guess i could test another drive to see if esata works.

i have an esata to sata cable, can i connect a bare sata drive up using this if i power the drive separately?

[greenbeast]

might just have to use it on USB2
at least got that working for now.

[Confusticated]

can i connect a bare sata drive up using this

Yes

might just have to use it on USB2

much slower than eSATA

to have a nice RAID1 array, so i can't not use it

Get the lone drive working first, then find a way to stop the enclosure powering down.