Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rob_uk]

Hi all,

I've just got a DIR-505, probably one of the first batch in the UK, and it has FW 1.03 installed.

I also have a couple of Buffalo ministation USB drives (320gb) and one of these doesn't power up from the USB port, but fortunately the other one does. This presumably is down to the power requirements being close to the maximum amount and individual component tolerances etc. A Y cable has been ordered from Amazon

The drive which does power up has worked ok for streaming and transferring videos to my ipad and I have used the d-link app and a browser. The drive was formatted to FAT 32.

I also installed the d-link app on an android phone and had a good degree of sucess uploading small files, photos / vidoes.  However I hit a point when a file upload failed and every subsequent upload both on android and the ipad app caused an error.  On the ipad d-link app the error code was 413.  Nothing else was able to upload and i was stuck with a partial file.  When I plugged the drive into a PC I could not delete the offending file as Windows 7 reported it as corrupt.

Does anyone have an explanation of error 413, why a file would become corrupted and why this would then stop any further uploads to the 505?

I decided to reformat the drive to NTFS and I hope this might make it less likely to corrupt.  It does seem to still play up a bit with uploads and crashed this morning.  When it does crash it just appears like the drive is no longer there.  It was available after a reboot and files could still be streamed and writtenm, so not a total crash.

Anyone else had much experience of using a USB HDD wiht the 505?

Cheers
Robin

[FurryNutz]

Does it only crash or fail when using the Android app? And to clarify, if the Android crashes the 505, no other devices work on it until a reboot or power cycle? Can you access it's web page after a crash?

I would email DLink with this information and see what they say. I presume if only the Adroid is causing this, might me the app that needs to be looked at.

[holmes4]

I suggest you try it again when you get the Y cable. You may find it makes a difference.  In the past I have seen devices that spun up, but did not work reliably until really sufficient power was supplied.