General NAS-Central Forums

Welcome to the NAS community
It is currently Sat Aug 19, 2017 1:41 am

All times are UTC




Post new topic Reply to topic  [ 40 posts ]  Go to page Previous  1, 2, 3  Next
Author Message
PostPosted: Mon May 03, 2010 7:43 pm 
Offline

Joined: Sat Jul 11, 2009 10:20 pm
Posts: 61
Oh heck, the folder listing when accessing videos now has no folder structure, they all appear twice in one big list.

And there is another set of folders that seems to be system stuff.
I have rebuilt the database before but am doing it again.

OK to confirm what I am seeing, when I use windows explorer it is fine.
When I use the Xbox360 & twonkeyvision what I see is:
All videos - where there are at last 2 of every video - some times more.

THe other folders available are:
oldroot\proc\self\task\1295\fd\ then "no videos found" ...

So I'm wondering what to do next, I have rebuilt the database & rescanned.

I'm wondering if a copy it all to a new drive, reformat & start again may well be required.

OH hang on..... I'm just going into the twonkey config & will se the folders & rebuild the database from there.
BRB.

Yay!!!... folders are back now... :D

_________________
Dumb Windows user & 500gb Network Store owner.
I'm not compatible with Linux :(


Top
 Profile  
 
PostPosted: Mon May 10, 2010 3:12 pm 
Offline

Joined: Mon May 10, 2010 2:53 pm
Posts: 2
Hi all,
I've been following this thread since I have a similar problem on two Lacie network space drives (1TB each). I'm not a linux user but I downloaded Ubuntu 10.04 and after booting and using the live version I recovered the data from both drives. My problem is I would like to delete the log files that got out of control (almost 700MB each!) but after getting to the terminal and trying

sudo apt-get update
sudo apt-get install mc

I get an error - update not available (or something similar. can't recall exact message)

Is there any other way (standard terminal commands?) that I can use to have proper rights to delete files?

Any help greatly appreciated.
Thanks.


Top
 Profile  
 
PostPosted: Mon May 10, 2010 3:25 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6022
cheburashka wrote:
Hi all,
I've been following this thread since I have a similar problem on two Lacie network space drives
Really? Then you are the 3th one within a month on this forum.
There must be a serious bug in the Lacie/Twonky combination.
Quote:
Is there any other way (standard terminal commands?) that I can use to have proper rights to delete files?
Sure. Do the 'df' trick to find the mountpoint. Let's say it's /media/sdb9. Open a terminal and type
Code:
cd /media
cd sdb9
cd snaps
cd 00
cd user
cd local
cd twonkeyvision
or
Code:
cd /media/sdb9/snaps/00/usr/local/twonkeyvision

and then
Code:
sudo rm twonkymediaserver-logtxt
Of course your exact path and/or filename could be different. When a command is rejected, type 'ls' to see the contents of the current directory.


Top
 Profile  
 
PostPosted: Mon May 10, 2010 5:59 pm 
Offline

Joined: Sat Jul 11, 2009 10:20 pm
Posts: 61
I didn't do that.

I used the gui, I think it may have been a terminal - not sure.
I could right click int the r/h window & set permissions.
That allowed me to delete the file.

Sorry I cannot remember exactly what I ran though.

_________________
Dumb Windows user & 500gb Network Store owner.
I'm not compatible with Linux :(


Top
 Profile  
 
PostPosted: Mon May 10, 2010 11:50 pm 
Offline

Joined: Mon May 10, 2010 2:53 pm
Posts: 2
Thanks a zillion, Mijzelf!

I followed your instructions, removed the log and now it's back in the box and connected. Although very unstable at the moment. I can see it on my network places and have access but the web interface went blank (Firefox 3.6.3). I had tried rebuilding the database (web interface -> media -> rebuild) and can't tell if it did it or not. It went back to the same message - Troubleshooting: rebuilt database advised...

I had to restart the drive (power off/on) to get back to "normal". Web interface available now and the message still there (rebuilt database advised) so I don't know what to make of it.

<rant>
Extremely poor software I must say. And writing to the log file endlessly without checking for available space? Just brilliant! Fortunately the drive inside the box is listed as compatible with the Synology NAS I'm going to get. And they seem to know how to write software, so the all looking good designed by whoever crap box will meet the plastic police soon. LaCie? Never again. I can only blame myself after getting LaCie Cinema (media player) with its buggy crappy software. I gave them another chance. I should've known better.
</rant>

I also have a friend in the office with the same problem. Btw, firmware is 1.1.8

mattylad, I don't know how you did it but using the graphic interface (Gnome?) "Move to trash" was disabled. Anyway, I felt comfortable using the terminal commands since I've been using PCs long before there was a graphic interface.


Top
 Profile  
 
PostPosted: Tue May 11, 2010 7:01 am 
Offline

Joined: Sat Jul 11, 2009 10:20 pm
Posts: 61
I have a very muzzy headache at the mo & cannot remember but your sorted brill.

You may also want to go into the twonky config pages & trun off some logging & the drive scanning
that causes it to have a lot of activity when its not in use.

After this I have lost trust in it so am going to be backing it all up & keeping a constant 2nd copy of everything on it.

If only there was a community firmware available.... :D

_________________
Dumb Windows user & 500gb Network Store owner.
I'm not compatible with Linux :(


Top
 Profile  
 
PostPosted: Tue May 11, 2010 7:41 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6022
@mattylad; Did you analize the logfile? I can hardly imagine that this file is growing that big by design, so I expect it's due to some (unexpected) interaction with a client, or, because both you and cheburashka have problems rebuilding the database, due to some incompatible filenames or so.
Quote:
After this I have lost trust in it so am going to be backing it all up & keeping a constant 2nd copy of everything on it.
Of course. Even if you fully trust your NAS, you should have a 2nd copy. The NAS contains a harddisk, so it *will* fail, some day. BTW, I don't think these logfile issues put your data in danger. It's on a different partition.
Quote:
If only there was a community firmware available....
There is. Have a look here. (I'm sorry, you'll have to register before you can read that forum.)

cheburashka wrote:
Thanks a zillion
You're welcome.


Top
 Profile  
 
PostPosted: Wed May 12, 2010 6:51 pm 
Offline

Joined: Sat Jul 11, 2009 10:20 pm
Posts: 61
How can I read the logfile?
600+mb does not want to open in Notepad :D

_________________
Dumb Windows user & 500gb Network Store owner.
I'm not compatible with Linux :(


Top
 Profile  
 
PostPosted: Wed May 12, 2010 7:21 pm 
Offline

Joined: Sat Jul 11, 2009 10:20 pm
Posts: 61
OK I have managed to read it using WimVI

Although its not very helpful for me, it does not appear to contain any dates on what it logs.
The end got cut off doing what looks like a scan of the files.
Quote:
15:05:47:615 LOG_DB:upnp_folder_watch_add_dir /home/openshare/Movies
15:05:47:616 LOG_DB:watch wd=1 added on /home/openshare/Movies


and there is a lot of this sort of entries. (makes no sense to me).

Quote:
0:33:16:021 LOG_SYSTEM:upnp_get_interfaces get_interface_addresses 127.0.0.1
00:33:16:022 LOG_SYSTEM:check_NIC_change IP count: 1 / 1
00:33:16:023 LOG_SYSTEM:check_NIC_change IP verify: 127.0.0.1
00:33:46:321 LOG_SYSTEM:upnp_get_interfaces get_interface_addresses 127.0.0.1
00:33:46:322 LOG_SYSTEM:check_NIC_change IP count: 1 / 1
00:33:46:323 LOG_SYSTEM:check_NIC_change IP verify: 127.0.0.1
00:34:11:331 LOG_SSDP:SSDP_notify_packet ### SSDP sending:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=1810
LOCATION: http://127.0.0.1:9000/DeviceDescription.xml
NT: uuid:7076436f-6e65-1063-8074-424242424242
NTS: ssdp:alive
SERVER: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0
USN: uuid:7076436f-6e65-1063-8074-424242424242


00:34:11:333 LOG_SSDP:SSDP_notify_packet ### SSDP sending:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=1810
LOCATION: http://127.0.0.1:9000/DeviceDescription.xml
NT: upnp:rootdevice
NTS: ssdp:alive
SERVER: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0
USN: uuid:7076436f-6e65-1063-8074-424242424242::upnp:rootdevice


00:34:11:335 LOG_SSDP:SSDP_notify_packet ### SSDP sending:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=1810
LOCATION: http://127.0.0.1:9000/DeviceDescription.xml
NT: urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:alive
SERVER: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0
USN: uuid:7076436f-6e65-1063-8074-424242424242::urn:schemas-upnp-org:device:MediaServer:1


00:34:11:337 LOG_SSDP:SSDP_notify_packet ### SSDP sending:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=1810
LOCATION: http://127.0.0.1:9000/DeviceDescription.xml
NT: urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:alive
SERVER: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0
USN: uuid:7076436f-6e65-1063-8074-424242424242::urn:schemas-upnp-org:service:ContentDirectory:1


00:34:11:339 LOG_SSDP:SSDP_notify_packet ### SSDP sending:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=1810
LOCATION: http://127.0.0.1:9000/DeviceDescription.xml
NT: urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:alive
SERVER: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0
USN: uuid:7076436f-6e65-1063-8074-424242424242::urn:schemas-upnp-org:service:ConnectionManager:1


00:34:16:621 LOG_SYSTEM:upnp_get_interfaces get_interface_addresses 127.0.0.1
00:34:16:622 LOG_SYSTEM:check_NIC_change IP count: 1 / 1
00:34:16:623 LOG_SYSTEM:check_NIC_change IP verify: 127.0.0.1
00:34:46:921 LOG_SYSTEM:upnp_get_interfaces get_interface_addresses 127.0.0.1
00:34:46:922 LOG_SYSTEM:check_NIC_change IP count: 1 / 1
00:34:46:923 LOG_SYSTEM:check_NIC_change IP verify: 127.0.0.1
00:35:16:211 LOG_SYSTEM:upnp_get_interfaces get_interface_addresses 127.0.0.1
00:35:16:212 LOG_SYSTEM:check_NIC_change IP count: 1 / 1
00:35:16:213 LOG_SYSTEM:check_NIC_change IP verify: 127.0.0.1
00:35:17:331 LOG_SSDP:SSDP_notify_packet ### SSDP sending:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=1810
LOCATION: http://127.0.0.1:9000/DeviceDescription.xml
NT: uuid:7076436f-6e65-1063-8074-424242424242
NTS: ssdp:alive
SERVER: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0
USN: uuid:7076436f-6e65-1063-8074-424242424242


00:35:17:333 LOG_SSDP:SSDP_notify_packet ### SSDP sending:
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=1810
LOCATION: http://127.0.0.1:9000/DeviceDescription.xml
NT: upnp:rootdevice
NTS: ssdp:alive
SERVER: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0
USN: uuid:7076436f-6e65-1063-8074-424242424242::upnp:rootdevice

_________________
Dumb Windows user & 500gb Network Store owner.
I'm not compatible with Linux :(


Top
 Profile  
 
PostPosted: Mon May 24, 2010 12:00 pm 
Offline

Joined: Wed Jul 22, 2009 8:47 pm
Posts: 3
Mijzelf wrote:
cheburashka wrote:
Hi all,
I've been following this thread since I have a similar problem on two Lacie network space drives

Really? Then you are the 3th one within a month on this forum.

Guess that makes me number 4 :cry:

My network space wasn't even assigned an IP-address anymore, so it was completely unreachable.
Also it could not be powered off with the switch anymore, a reset to factory defaults therefore didn't work either.
LaCie would repair it under warranty, but they say they format the drive when they repair it and I wanted to try and save some of the data.

I've transplanted the drive in a USB drive casing and after downloading, burning and booting the Ubuntu CD, I've been able to copy all my files to my PC's harddisk.
The PC's harddisk is shown as "Boot" in nautilus, the network space shows as two filesystems, one 999 GB and one 691 MB.
The 999 GB contains myshare and openshare and has 285,8 GB used and 644,6 GB free.
The 691 MB contains EDMINI, lost+found and snaps and has 648,5 MB used and 0 bytes free.

My 616 MB large twonkymediaserver-log.txt was in snaps/01/usr/local/TwonkyVision.
The logfile contains lots of similar entries as mattylad's and ends in a couple of dozens of hh:mm:ss:ddd scanned /home/openshare/.... entries.
The last line has just a time "22:03:44:513", no more room for the "scanned ..." part apparently.

I executed "sudo nautilus" in a terminal window (I didn't have an internet connection, so couldn't get Midnight Commander) and was able to delete the culprit.
Had to mount the 691 MB Filesytem in another (not sudo-ed) nautilus window to see it in the sudo-ed window though (which may make perfectly good sense to a Linux adept, but beats me, another Linoob).
After unmounting and clearing the Trash, the 691 MB has 64,8 MB used and 583,7 MB free :D

The power off problem remained :(
Dis- and reconnecting the power would start it, and if switched off quickly enough would power it off but wouldn't reset to factory defaults when powering on again, and when waiting too long (more than about 2 to 3 seconds) it wouldn't switch off.
After several tries, I managed to get the timing just right and succeeded in resetting the device to factory defaults.
It went back to version 1.1.6, so I had to redo the upgrade to 1.1.8.

It seems to be operating all right, only every couple of minutes the LaCie Network Assistant reports a new LaCie Ethernet disc was found :?
Any ideas on why that is, and more importantly, how to fix this :?:


Top
 Profile  
 
PostPosted: Mon May 24, 2010 12:06 pm 
Offline

Joined: Sat Jul 11, 2009 10:20 pm
Posts: 61
Just before I went away on holiday, I found that I could no longer access it & so my house sitter has had no movies to watch :(

I cannot access the drive & now it does not turn off at all.

I will investigate further when I get access to a PC, I think I need to back it all up to another drive.

_________________
Dumb Windows user & 500gb Network Store owner.
I'm not compatible with Linux :(


Top
 Profile  
 
PostPosted: Sun May 30, 2010 8:56 pm 
Offline

Joined: Sat Jul 11, 2009 10:20 pm
Posts: 61
OK now I have started to back it up to a bigger drive.
Tomorrow I start copying the movies off, that will take the best part of 8 hrs.

Methinks its time to start it again, format it & start again.

I will be trying the replacement drive stuff mentioned here once it's ready for it.

Although, now is also a good time to look for a replacement media serving drive.
Can anyone recommend and good NAT drives other than this? (somehting stable without screw ups like this has).

Cheers.

_________________
Dumb Windows user & 500gb Network Store owner.
I'm not compatible with Linux :(


Top
 Profile  
 
PostPosted: Mon Jun 21, 2010 1:49 pm 
Offline

Joined: Sun Jun 20, 2010 1:10 pm
Posts: 3
I had the same 'drive full' problem. The media server never failed though, and I could resolve it temporarily by removing the logs at the Twonky config pages. At first I still had FTP access so at that point it wasn't that much of an issue since I use my NetworkSpace mainly as a media server. But then the FTP went too, and without the ability to put new files on, the media server suddenly wasn't very functional any more.

So I decided to be brave and take the drive out of its box. I put it into USB case, and indeed, there was a huge log file clogging up the 691 MB filesystem, leaving 0 bytes on the drive:

Image
(the 'myshare on networkspace' and 'openshare on networkspace' folders you see in the bottom left of the screen are just bookmarks from back when everything still worked)

Note it's in /snaps/02/usr/local/twonkyvision (rather than mattylad's /snaps/00/)

I copied the 591.8 MB log file to a safe place, then deleted it using Midnight Commander (sudo rm or sudo nautilus would have probably been quicker, but and yeah, I am -just- old enough to remember Norton Commander, and was feeling nostalgic...), put the drive back in the box, and kept my fingers crossed all would be well now.

BUT, unfortunately, I'm worse of now than I was before my drive's adventure outside the box: my NetworkSpace doesn't seem to be booting up. When I turn it on, the drive spins up seemingly as normal, the blue light flickers a bit, but then instead of the blue light turning off as the drive becomes visible, it now stays on continuously - even when I power down the NetworkSpace. The Lacie Network Assistant reports there are 'No Ethernet Disks Available'.

I tried a factory reset (power off, power on for 3 sec, power off and right back on again), but that didn't change anything.

Edit:
I tried a few more factory resets, and finally one took. First it looked like I was right back where I started (media player worked, but no shares), but a couple of restarts later even the openshare and myshare reappeared. Hurray!
Many thanks for all your advise!

PS- because of the factory reset, my system version is now back to 1.1.6 instead of 1.1.8, and I think I'll leave it at that for now. I don't know if the new firmware was the cause, and it's not as if problems started immediately when I upgraded to 1.18, but I do know that in 1.1.6, there weren't any problems at all.


Top
 Profile  
 
PostPosted: Mon Jun 21, 2010 6:44 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6022
Quote:
Note it's in /snaps/02/usr/local/twonkyvision (rather than mattylad's /snaps/00/)

On the networkspace2 there is a script which at boottime creates a unionfs, existing of sda8 and sda9/snaps/nn, where nn stands for all available directories which names are two digits.
The name 'snaps' implies that those directories are snapshots, and indeed you can go back to a previous state by deleting the last directory or -ies.
I couldn't find a way to create such a snapshot, (didn't try very hard, I don't own a NS2, so I could only search the scripts).
Now I see you went back 2 firmware versions by applying a factory reset. Assuming you upgraded twice, it seems that a snapshot is created when a new firmware is loaded.


Top
 Profile  
 
PostPosted: Mon Jun 21, 2010 7:43 pm 
Offline

Joined: Sun Jun 20, 2010 1:10 pm
Posts: 3
Mijzelf wrote:
On the networkspace2 there is a script which at boottime creates a unionfs, existing of sda8 and sda9/snaps/nn, where nn stands for all available directories which names are two digits.
The name 'snaps' implies that those directories are snapshots, and indeed you can go back to a previous state by deleting the last directory or -ies.
I couldn't find a way to create such a snapshot, (didn't try very hard, I don't own a NS2, so I could only search the scripts).
Now I see you went back 2 firmware versions by applying a factory reset. Assuming you upgraded twice, it seems that a snapshot is created when a new firmware is loaded.


I don't think I ever upgraded to 1.1.7, but leapfrogged from from 1.1.6 to 1.1.8. But I had snapshots going up to 04, so five in total. Though I may well have 'upgraded' four times, because when the drive started going wonky, I tried if reloading the firmware might fix things (ie, I upgraded from 1.1.8 to 1.1.8).

So I suppose it's a good idea to clear logs before upgrading, right?
Though I know keep all the 'log level' boxes on the Twonky media Maintenance page unticked, so no logs are created.

(And just to be clear: I don't own a NS2 either; mine's the old plain NetworkSpace)


Last edited by iris on Wed Jun 23, 2010 8:45 am, edited 1 time in total.

Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 40 posts ]  Go to page Previous  1, 2, 3  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group