"Andreas Neumann"  wrote in message
news:pntb3o$ak7$1@gioia.aioe.org...
> NY wrote:
>
>> It's happened with a different disk (Transcend) so it looks as if it's
>> the
>> Pi that's doing it. I wonder whether it's a power supply issue, as
>> someone
>> suggested.
>
> If it actually is a hardware issue, it is of course better to resolve
> that.
>
>> I'll try linking /mnt/recordings to /media/pi/ - is it better
>> to make a hard link or a symbolic one?
>
> I have never used hard links, all my linking works fine being soft :-)
>
>> I've not heard of bind-mounting.
>> I'll research it.
>
> It is a way to mount an already mounted resource simultaneously at another
> place, the manpage should suffice for explanation as it is easy to do.

Sounds an excellent idea to be able to mount a device in two places in the
filesystem.

>> I'll also get a powered USB hub.
>
> That might help, as stability depends on peak current consumption of the
> drive.
> OTOH I am running an SSD off the Pi without any problems, current uptime
> is
> 158 days.


I've just checked the voltage at the +5V and GND pins on the GPIO and *at
the time of testing* I'm getting 5.1V, so definitely not below spec. It is
interesting that with the drive in a different USB port (bottom left rather
than bottom left, looking with the Ethernet port to the left of the USBs)
the new drive hasn't bombed out yet.

But I think a powered hub might be useful - or else a HDD with its own power
supply. I have one somewhere - but I can't think where that "somewhere"
might be :-)

--- SoupGate-Win32 v1.05