Not sure, but try this -- use uuid in fstab. First get the uuid designation of your esata hdd by attaching it to a booted machine. In linux you can use the command "blkid" or if that is not available

Code:

ls -l /dev/disk/by-uuid

Not sure how to do this in windows though.

Mount your SD card on your booted machine and open /etc/fstab with your editor (nano, vi etc) and change your line to something like this:

Code:

uuid=the-output-from-above /srv ext4 defaults,noatime 0 1

The older way to indicate a device, like "/dev/sda1" can be inconsistent, but the uuid is unique and can only mean that one device. Frankly, I'm not sure if this is the root of your problem, but it might be, and in any case, couldn't hurt.

I had a similar problem (also with esata sheevaplug) where the fsck of the root fs failed. It would run fsck.ext4 but the rootfs s ext3. So it would choke.You don't specify which disk is failing so this might be your problem.I 'fixed' it by adding a line in fstab mounting roots with 0 0 options at the end (copy the entry out of fstab).I don't know why that should affect it, but it worked after that and I didn't do anything else.

I had a similar problem (also with esata sheevaplug) where the fsck of the root fs failed. It would run fsck.ext4 but the rootfs s ext3. So it would choke.You don't specify which disk is failing so this might be your problem.I 'fixed' it by adding a line in fstab mounting roots with 0 0 options at the end (copy the entry out of fstab).I don't know why that should affect it, but it worked after that and I didn't do anything else.

Normally the "defaults" option should mount the partition, but since it's not, maybe the extra "auto" will force it. Also try putting the actual fs (ext4) rather than "auto" might help and couldn't hurt. Also I noticed that you used a bold font on your "auto fs" entry. If that's what's actually in your fstab, it shouldn't be. Hope it helps.

And if it were me, I would use "uuid=xxxxx...." instead of /dev/sda1" but you already tried that

First, you should seek assistance with this problem from NewIT. eSATA SheevaPlugs are hard to come by in the U.S., but even if they weren't, we can only speculate about the layout of the card, the contents of your u-Boot environment and what changes may have been made to the 6.0 (unstable) branch of Debian since the SD card was manufactured.