User(s) browsing this thread: 1 Guest(s)
|
Cannot write over network to internal 3 TB drive
|
|
12-20-2011, 12:17 AM
(This post was last modified: 12-20-2011 01:10 AM by drummer.)
|
|||
|
|||
|
Cannot write over network to internal 3 TB drive
A-300 with 3 TB WD HDD installed and formatted via the PH. Latest firmware.
I can connect to the share with my XP and my Mac Book, however, I cannot write a file to the share. It's as if the share is read-only but I was able to create new directories. I tried FTP and cannot do that either. I had a PH A-100 and didn't have this problem with my 1 TB drive. Am I doing something wrong? Thanks for any help. I'm really looking forward to filling up this new drive. EDIT: When I say cannot write, I mean that I drag within Finder or Explorer and get the copy dialog but it never shows progress. On Windows, I will eventually get a "the path is too deep" type error. Mac doesn't error (at least for quite a while). I'm UNC'ing to the directory. i.e. \\192.168.1.113\share\video\comedy I attached a 250 GB MyBook with movies, photos and music and it works fine. I can navigate and play but am also not able to copy files to this "share"/drive. /drummer |
|||
|
01-04-2012, 07:08 PM
|
|||
|
|||
|
RE: Cannot write over network to internal 3 TB drive
No responses to my post but here's an update:
I moved the popcorn hour and connected it to the linksys with a purchased network cable. Where it had been is behind my TV with a network cable that had been terminated at a wall plate. Inspecting the cable shows it's not the best wiring - where the twists are maintained right up to the terminal block. Anyway, I had formatted the drive as NTFS and that worked fine. Trying to rule out bad drive here. I then put back in the popcorn and let it re-format and then was able to transfer across the network to the drive. No problem. Placing the popcorn back behind the TV I have the same problem when trying to copy files to or from it across the network. The thing is, i DIDN'T have problems with my previous popcorn A-110. I'm going to test with a wireless n USB to see if that fixes my problems. I never stream across the network, only xfer files. /drummer |
|||
|
01-04-2012, 08:10 PM
|
|||
|
|||
|
RE: Cannot write over network to internal 3 TB drive
I dont know if 3Tb internal HDD is supported. I know that if you tried to format it with the player then you will only get 2.19Tb out of it. So you have to format elsewhere and then place inside to get full 3Tb.
That means if you want to transfer content via a network you need a USB stick and the NMT Apps installed on it. A400: SSD+SD Card(Apps), HDMI A300: USB(Apps), HDMI C200: USB(Apps), BD SH-B083L(SB01), HDMI CAT6 Wired Network: TV TX-P42G20, HP ProCurve 1400-8G, Netgear GS-608/605, Synology CS407 |
|||
|
01-06-2012, 04:56 PM
|
|||
|
|||
|
RE: Cannot write over network to internal 3 TB drive
I didn't know about the size limit. I have a 2 TB drive I can swap (my original popcorn hour internal HDD) and then use the 3 TB as an attached USB drive.
Is there a way to see the free space/total space of the drive from the popcorn interface? Thanks. |
|||
|
01-07-2012, 02:43 AM
|
|||
|
|||
|
RE: Cannot write over network to internal 3 TB drive
Just out of curiousity, if you telnet into your popcorn ip address from your PC, then issue a "ls -l" command, what does it say the permissions are?
What I mean is, based on your stated path of "\\192.168.1.113\share\video\comedy", I'd do the following: Run a command prompt (type "command") type "telnet 192.168.1.113" inside the telnet prompt, type "cd /share/video" <--- note the slashes are forward /. This is linux, not windows! type "ls -l" if you see something like drwxr-xr-x 4 root root 4096 comedy Then you don't have write rights to the comedy directory. |
|||
|
01-10-2012, 02:43 AM
(This post was last modified: 01-12-2012 04:45 AM by drummer.)
|
|||
|
|||
|
RE: Cannot write over network to internal 3 TB drive
Thanks for your kind reply.
Both the share and the directory have full rights for root. The share is: lrwxrwxrwx 1 root root 41 Jan 4 20:36 share -> /opt/sybhttpd/localhost.drives/SATA_DISK/ The directory is: drwxrwxrwx 12 root root 4096 Jan 3 08:29 Video A little bit more info about the drive: sh-3.00# hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: WD30EZRX-00MMMB0 Firmware Revision: Standards: Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 5860533168 device size with M = 1024*1024: 2861588 MBytes device size with M = 1000*1000: 3000592 MBytes (3000 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 DMA: *mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns - snip - |
|||
|
01-30-2012, 08:57 PM
|
|||
|
|||
RE: Cannot write over network to internal 3 TB drive
(12-20-2011 12:17 AM)drummer Wrote: A-300 with 3 TB WD HDD installed and formatted via the PH. Latest firmware. YOu may want to try some software that will help you to fix these problems. There are many in the market and they save you time, and therefore money. I personally recommend Long Path Tool |
|||
|
01-30-2012, 10:02 PM
(This post was last modified: 01-30-2012 10:10 PM by dax40.)
|
|||
|
|||
RE: Cannot write over network to internal 3 TB drive
(01-04-2012 07:08 PM)drummer Wrote: Anyway, I had formatted the drive as NTFS and that worked fine. Trying to rule out bad drive here. I then put back in the popcorn and let it re-format and then was able to transfer across the network to the drive. No problem. Hi there, dunno if this helps, but I also have a A-300 with a 3TB WD drive (WD30EZRX) which work fine together. I had read a bit about preparing the drive before installing it, so here's what I did: I installed the HDD in my PC (win7; SATA-port from Mainboard) and let windows format the drive as one NTFS system, but with "quick format" disabled. That took about 6 hours. Then plugged a 8GB USB Stick into the poppy and let it install the NMT apps onto it. Then filled the HDD with some TV recs and DVD and BD isos to check if these would be recognized and played. After I installed the drive in the poppy they would all play rightaway, so I tested some more. I have so far been able to do all I want to do, write files over Ethernet to the poppy, creating directories, put some nfo's next to the files, and even dump isos on it directly. At the moment I am busy filling the HDD with my movies, but switched to USB connection (with desktop docking station), as the transfer speed over my wired net is too slow for my liking - just about max. 100mbit, but this topic has risen elsewhere and I do not fret about it much. So, maybe you can try my config, to start from scratch and use a USB stick for the NMT apps and the HDD as one big NTFS drive. Perhaps you should then refrain from letting the poppy format it again? This is definitely a good question for the more experienced users to answer, as I have only started to fall in love with my A-300 a few days ago. But apart from the lots and lots of threads to read and small obstacles to overcome (to get NMJ and YAMJ working -->renaming helps! ) I am quite happy with everything more or less working so far.Hope you get your issues solved soon. regards, dax40 /.edit: Just read that you only have problems whilst connected to a particular network socket in your wall? Sorry, then my post will not really help. But then you should double check your ethernet cables (especially the connectors for correct alignment of the wires) as well as your wall bracket. Try attaching a long cable to see if this resolves the problem. Then you will rule out the poppy and the drive and other network settings etc. |
|||
|
« Next Oldest | Next Newest »
|

Twitter
Facebook
NMT Wiki
Search
Member List
Help
A-400 [13 May 2013]






![[+]](images/collapse_collapsed.gif)



) I am quite happy with everything more or less working so far.