panic ehci_abort_xfer on rsync to mirror or stripe

[jptechnical]

I have a Dell Dim8400, embedded usb thumbdrive of Muad'Dib. Onboard SATA ports, 2x seagate 1tb drives in raid1, seagate 1.5tb + .5tb in raid0. Also an ext3 hd in a BlackX external dock

I was rsync'ing the external drive to the stripe array. It ran for quite a while, then it locked up. I was running the rsync -urvh from the shell (f2 terminal) and was tailing the system.log in the shell (option from main menu). I was watching the files pass by then it stopped, I didn't see it stop, just saw the bold panic message.

Before this occurred, I was rsync'ing over the network, moving about 40gigs, and it locked up, but I couldn't see the error and hadn't figured out how to look in the log far enough back to see the cause. I restarted the rsync after a power-cycle and resumed the rsync and it completed ok.

I know that ext is not directly supported, and I am ok with that, since I was only reading it. The ext partition would not mount after restart, so I am fsck'ing it, which completed ok and mounted again.

The system actually rebooted automatically, but it was after about 30mins or so. During this time, the system was unresponsive to any access, the services were there, but they would not respond (i.e. webui continually loading, kybd not working, smb waiting for response, ssh never got to login but didn't ask for creds).

So, what am I doing wrong? I intend to use this nas box with rsync pretty extensively. If rsync is not stable, then I would be ok putting a full os on this system, as that is what it is otherwise replacing.

panic: ehci_abort_xfer
cpuid=0
uptime: 2hr45min


btw, I played with freenas a couple few years ago, but it didn't like the ide cards and drives I was using. I am pleased to see the HUGE leaps it has grown since I last tried it. Very good work everyone!

Thanks!