PDA

View Full Version : Boxee sends my NAS to sleep, never to return until powered off and on!


Skillip-Evolver
April 28th, 2010, 07:29 PM
This is a pretty crazy one. :confused:

I've recently started using Boxee again. Got all my movies scanned (bar two which the scraper just refused to find). Wanted to scan my music next. So I added the shares. Shortly after, I noticed an "X" by the shares (disconnected).

I checked back in win explorer, sure enough, it had been disconnected. Tried to re-map the drive, windows error. I also noticed the swirling blue LED light on the NAS (it's a WesternDigital MyBookWorld 500GB), stopped moving (still lit up however).

I can only map to the drive again, if I unplug it and re-plug it.

Basically Boxee seems to be 'knocking it out'! The drive IS slow so one theory I had was that Boxee was trying to libraritise the music so quickly that the drive caved in. Having said that, it's been no problem in xbmc for years n years.

The NAS drive basically has a NIC inside it where upon sits a stripped down variety of Linux of some kind, which gives it its 'brain', kinda like a mini OS. The drive inside can still be heard (fan also running) after the problem happens, but perhaps Boxee is codding the OS of the drive in some way?

It's very peculiar, but it only happens with Boxee, I've tried other apps (xbmc, winamp).

Can anyone help? :(

Last vital info:
System: ASRock330, 2gb ram, 1.6GHz Atom, ION graphics. Windows 7 Ultimate. 100mbps router connection. Not sure what else to add?

Silverlock
April 28th, 2010, 07:40 PM
Just as a data point; we have one of the networked WD drives at work, and I've seen it "go to sleep" just by leaving it alone for several minutes. The only way to wake it up seems to be to cycle the power. So it might not be Boxee's fault.

Skillip-Evolver
April 29th, 2010, 04:54 AM
I have never witnessed that behaviour with mine. Mine never sleeps at all. Which I like.

But this definitely is happening only with Boxee. Believe me I've tested it tens of times now.

rsava
April 29th, 2010, 08:04 AM
This is not a Boxee issue. I have 5 of these running stuff for me for Boxee. I have 3 500GB (Blue Ring), 1 1TB (Blue Ring), and 1 2TB (White Ring) and they never "go to sleep". I moved them to a new rack over a month ago and they have never "disconnected" from Win 7 for me. Before that the longest one of them were up and connected to a computer was over 200 days straight.
I have hacked and modded them using the instructions here: http://mybookworld.wikidot.com/hacks-and-howto
and there are some great people over there on the forums. Perhaps they can offer some help. It can sometimes take a couple of days to get a response but they always helped me while I was learning how to mod the drives.

darcilicious
April 29th, 2010, 10:11 AM
Would it be possible it's not going to "sleep" as much as possible being locked up while Boxee tries to index media from it??

Knifeyspoony
April 29th, 2010, 10:42 AM
Possibly the drive is killing the power for safety reasons. It may be encountering a bad sector while reading from the disk. It couldn't hurt to run chkdsk on it and eliminate that as a possibility.

Skillip-Evolver
April 29th, 2010, 06:04 PM
rsava, all due respect I don't think its right to state 'this is not a boxee issue'. What I'm saying happens to me may not be happening to yourself but that dosen't mean it's not happening for me. Thanks for the link though, I'd seen it before but it requires more linux skill than I have.

Darcilicious, yes that's a good point, I will let it go on overnight with the attempted scan and see what happens (however both boxee and win explorer show 'disconnected') :( definitely worth a go though.
Result: Tried this, checked in the morning, same result unfortunately.

Knifeyspoony, this sounds like a good thought. The drive is a few years old now so it could be damaged you're right. I tried to run chkdsk in a dos prompt but it said windows cannot run chkdsk on a networked drive. There doesn't seem to be any checking tools in the properties of the drive either, so maybe I'll have to get some custom software?

thanks for the idea. I will look into it.

rsava
May 3rd, 2010, 07:15 PM
rsava, all due respect I don't think its right to state 'this is not a boxee issue'. What I'm saying happens to me may not be happening to yourself but that dosen't mean it's not happening for me. Thanks for the link though, I'd seen it before but it requires more linux skill than I have.



You are right, I should have said "I don't think Boxee is causing this...." and listed my reasons why. Sorry about that.
Have you had any success in getting around this? Is it still happening, have you found any other clues as to why?

keeleyt83
May 20th, 2010, 11:49 PM
Happens to me too. I'm running the latest boxee, acer revo 3610, win 7. I was able to run versions of boxee alpha without incident. Just started boxee, it saw my library, and tried to have it rescan my library for some new stuff when it broke. Not sure what is up. I'll post again if i figure it out.

Skillip-Evolver
June 20th, 2010, 05:31 AM
Happens to me too. I'm running the latest boxee, acer revo 3610, win 7. I was able to run versions of boxee alpha without incident. Just started boxee, it saw my library, and tried to have it rescan my library for some new stuff when it broke. Not sure what is up. I'll post again if i figure it out.

just wondered if you had any news? It's been suggested in this thread that I scan the drive for errors. But as of yet, I've not found any software which can do that to this (mybook500gb lan) nas drive. It's also hard to get into the case (because I would like to remove the drive, and attach it somehow to another pc directly and try to error-check that way).

keeleyt83
July 2nd, 2010, 10:38 AM
just wondered if you had any news? It's been suggested in this thread that I scan the drive for errors. But as of yet, I've not found any software which can do that to this (mybook500gb lan) nas drive. It's also hard to get into the case (because I would like to remove the drive, and attach it somehow to another pc directly and try to error-check that way).

Nope, no news. I will update my version of Boxee soon and see if that helps.

Would it be possible it's not going to "sleep" as much as possible being locked up while Boxee tries to index media from it??

It would seem that this is the case, darcilicious. I can see my shared music on the NAS from boxee, but only for about 30 seconds. It is like it starts to index or something and then breaks. I can't explain it. Does boxee have logging of some kind? Would that help? Thanks.

darcilicious
July 2nd, 2010, 10:59 AM
Yes, you can up the logging level in Settings / System (set the Debug level to Debug), I believe and the boxee.log file in your Userdata folder is the logfile. I suggest that you start Boxee, remove the NAS from your media source list, set the Debug log level to Debug, stop Boxee and then start up Boxee and the NAS back as a media source. After the NAS is locked up, exit Boxee and copy off the boxee.log file somewhere (only the current and previous copies of the .log file are kept) and send it along with a description of the problem to http://support.boxee.tv

And please do this with the latest publicly available version of Boxee -- it's not very helpful to work on bugs from previous versions ;)

keeleyt83
July 10th, 2010, 01:19 PM
Yes, you can up the logging level in Settings / System (set the Debug level to Debug), I believe and the boxee.log file in your Userdata folder is the logfile. I suggest that you start Boxee, remove the NAS from your media source list, set the Debug log level to Debug, stop Boxee and then start up Boxee and the NAS back as a media source. After the NAS is locked up, exit Boxee and copy off the boxee.log file somewhere (only the current and previous copies of the .log file are kept) and send it along with a description of the problem to http://support.boxee.tv

And please do this with the latest publicly available version of Boxee -- it's not very helpful to work on bugs from previous versions ;)

Thanks, darcilicious. Turns out I am running the most recent version. :( I was hoping it might have been fixed. Oh well. I'll try to submit a bug with my log file this weekend.

darcilicious
July 10th, 2010, 01:37 PM
Just to be sure, a new version was released yesterday :)

keeleyt83
July 10th, 2010, 02:14 PM
Just to be sure, a new version was released yesterday :)

LOL ok, I'll get that one. Thanks.

keeleyt83
July 10th, 2010, 02:25 PM
Just to be sure, a new version was released yesterday :)

Well, it works now! I'm not sure if it was the boxee update or the network and sharing settings I changed in win7, but it works. I tend to think it was the boxee update because I changed the network and sharing settings (none of which looked like they would affect anything) and it still wouldn't work with the older version of boxee. Anyway, thanks for your help.

Skillip-Evolver
August 16th, 2010, 05:43 AM
Just wanted to ditto the last comment, it's working for me now too.

Thanks for the fix.