Drive Becomes Un-Accessible After short use

[Dickstar]

That's a very interesting observation, thanks for sharing. I have a torrent program installed (Transmission), and it happens every few hours. I think downloading Torrents is pretty heavy for this thing as well, with all the connections and stuff.

I'm not an expert  when it comes to Linux, or any coding stuff. But, I noticed in the Twonky server info thingy, that it almost had no memory to work with. I could be talking complete nonsense of course, but it might be something to look at.

I completely agree with you though. This is a NAS, and it should work as advertised.  It doesn't matter that it's cheaper than the average NAS, it should do what it promises.

[enter666]

Today I observe a strange behavior of the WD. After I shutdown the PC, and I left to work, I cud access only the Trasnmission torrent from work, FTP and GUI interface still don't work so first I believe it was from router configuration, but when I arrived at home and start the PC I couldn't access it from here the FTP & GUI, only Transmission.

So in conclusion I can access HDD if i put my PC in standby. And defenetly it is something on firmwere softwere. I don't know linux but I'm realy good on MCU programing so i can't realise when a infinite loop happens.

[Dickstar]

Have you found anything more yet, dzentai?

[CrashHouse]

Same problem here with certain accounts for instance account 'Passie' is generating this error:

 01/24 16:19:06  MyBookWE daemon.info afpd[10667]: logout Passie
 01/24 16:19:05  MyBookWE daemon.info afpd[10667]: Setting uid/gid to 0/1000
 01/24 16:19:05  MyBookWE daemon.warn afpd[10667]: Warning: No CNID scheme for volume /DataVolume/Download. Using default.
 01/24 16:19:05  MyBookWE daemon.info afpd[10667]: CNID DB initialized using Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003)
 01/24 16:19:05  MyBookWE daemon.info afpd[10667]: Setting uid/gid to 0/1000
 01/24 16:19:05  MyBookWE daemon.warn afpd[10667]: Warning: No CNID scheme for volume /DataVolume/Public. Using default.
 01/24 16:19:05  MyBookWE daemon.info afpd[10667]: login Passie (uid 504, gid 1000) AFP3.2
 01/24 16:19:05  MyBookWE daemon.info afpd[10667]: dhx login: Passie

I can only acces the drive with my initial account.

[dzentai]

So far I found one very strange thing. Mionet is still running even though I disabled it.

Not just that it is running, but it creates hundreds of such processes:

5176 root      12820 S   /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/lib

So now I deleted the mionet start script from init.d, and also the twonky media server. I'm not using either of them.

I will get back if I have any results.

[ivanpudic]

well i'm facing exactly the same problem

we have purchased 4 x WD4000H2NC and they all face the same issue.

after a couple of minutes/hours, the device is completely unaccessible.

we need to shutdown the device and power up again to make it work.

piece of crap

[image1]

Add another person to the count of those with this issue.

<set-up: wired connection from Win 7 box to switch, flat network with DHCP server all devices on static leases>

I just received my 1.5 TB MBWE white light a few days ago and all was fine till today. I have successfully done a 36 GB and 546 GB batch file transfer (from Win 7 explorer). I then attempted to transfer another 16GB of files and it has hung after 1 or two files on three tests. The 36GB transfer was composed of 500mb to 2GB files. The 546 GB transfer was composed of 1 to 10 mb files.  I can still ping the drive and after doing a forced shutdown was able to copy ~300mb of 1 -5mb files to the drive. It then failed when trying to copy a 2GB file.

Other things I have noticed:

Mionet does not stay "off" if I uncheck "start at boot) or even if I manually turn it off and then come back to see it's status a few minutes later.

Even if I do a reboot or shutdown from the Web GUI, on restart Twonky rebuilds the database (I have scan set to -1)

I've not had this or similar issues with my HP MediaVault NAS over the past 2 years.

[ivanpudic]

i think i got it fixed.

i managed thru SSH to disable mionet completely.

mionet doesn't start anymore and my NAS has been copying files for 24hours (without interruption)

4 to 5MBps , it's slow, but it's copying

[dzentai]

I can also confirm, that after completly disabling (removing init.d startup scripts using SSH)  Mionet and Twonky server my NAS is still up and working for 4 days now. But I'm still not sure, lets wait a week!

[ivanpudic]

could you confirm your trasnfer speed (writing)?