limetech Posted November 26, 2009 Author Share Posted November 26, 2009 The release notes for beta-8/9/11 state: - Upgrade pkgtools in order to support slackware packages which have .txz extension. To use that capability, the "xz" compression utility needs to be included as well. Currently, in beta-11, it is not. I'm guessing this is an oversight. Joe L. I am already able to install packages with .txz extension using -beta11 Quote Link to comment
dvd.collector Posted November 26, 2009 Share Posted November 26, 2009 Hi all, I thought I'd give this new version a try, however i seem to be having a problem when stopping the array. (Cache_dirs related?) The web interfaces shows the drives as "unmounting", and nothing i can do can seemingly get them to unmount. So I resorted to the power button. That of course started a parity check when it booted up, and uplon pressing "stop", i got the same situation. Is there any way to avoid this? Nov 26 15:09:04 Tower emhttp: shcmd (58): /etc/rc.d/rc.samba stop | logger Nov 26 15:09:04 Tower emhttp: shcmd (59): /etc/rc.d/rc.nfsd stop | logger Nov 26 15:09:05 Tower emhttp: Spinning up all drives... Nov 26 15:09:06 Tower emhttp: shcmd (60): sync Nov 26 15:09:11 Tower emhttp: shcmd (61): umount /mnt/user >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (62): rmdir /mnt/user >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (63): umount /mnt/user0 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (64): rmdir /mnt/user0 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (65): umount /mnt/disk1 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (65): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (66): rmdir /mnt/disk1 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (66): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (67): umount /mnt/disk2 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (67): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (68): rmdir /mnt/disk2 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (68): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (69): umount /mnt/disk3 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (69): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (70): rmdir /mnt/disk3 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (70): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (71): umount /mnt/disk4 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (71): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (72): rmdir /mnt/disk4 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (72): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (73): umount /mnt/disk5 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (73): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (74): rmdir /mnt/disk5 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (74): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (75): umount /mnt/disk6 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (75): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (76): rmdir /mnt/disk6 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (76): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (77): umount /mnt/disk7 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (77): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (78): rmdir /mnt/disk7 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (78): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (79): umount /mnt/disk8 >/dev/null 2>&1 The above just repeats forever.. [update] I disabled cache_dirs and the issue goes away. Quote Link to comment
Joe L. Posted November 26, 2009 Share Posted November 26, 2009 Hi all, I thought I'd give this new version a try, however i seem to be having a problem when stopping the array. (Cache_dirs related?) The web interfaces shows the drives as "unmounting", and nothing i can do can seemingly get them to unmount. So I resorted to the power button. That of course started a parity check when it booted up, and uplon pressing "stop", i got the same situation. Is there any way to avoid this? Nov 26 15:09:04 Tower emhttp: shcmd (58): /etc/rc.d/rc.samba stop | logger Nov 26 15:09:04 Tower emhttp: shcmd (59): /etc/rc.d/rc.nfsd stop | logger Nov 26 15:09:05 Tower emhttp: Spinning up all drives... Nov 26 15:09:06 Tower emhttp: shcmd (60): sync Nov 26 15:09:11 Tower emhttp: shcmd (61): umount /mnt/user >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (62): rmdir /mnt/user >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (63): umount /mnt/user0 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (64): rmdir /mnt/user0 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: shcmd (65): umount /mnt/disk1 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (65): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (66): rmdir /mnt/disk1 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (66): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (67): umount /mnt/disk2 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (67): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (68): rmdir /mnt/disk2 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (68): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (69): umount /mnt/disk3 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (69): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (70): rmdir /mnt/disk3 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (70): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (71): umount /mnt/disk4 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (71): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (72): rmdir /mnt/disk4 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (72): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (73): umount /mnt/disk5 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (73): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (74): rmdir /mnt/disk5 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (74): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (75): umount /mnt/disk6 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (75): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (76): rmdir /mnt/disk6 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (76): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (77): umount /mnt/disk7 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (77): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (78): rmdir /mnt/disk7 >/dev/null 2>&1 Nov 26 15:09:11 Tower emhttp: _shcmd: shcmd (78): exit status: 1 Nov 26 15:09:11 Tower emhttp: shcmd (79): umount /mnt/disk8 >/dev/null 2>&1 The above just repeats forever.. [update] I disabled cache_dirs and the issue goes away. Download and install the newest version of cache_dirs and the issue will also go away It is coded to look for the lines in the syslog showing the array attempt to stop, and will terminate itself accordingly. . The newest beta versions of unRAID will no longer partially stop the array showing you "Unformatted" where it has un-mounted disks. This same issue will occur with ANY add-on process or terminal session that is keeping a disk busy. unRAID will now wait for the process to terminate before continuing its shutdown. If you log in via telnet and change directory to /mnt/disk1, it will be "busy" because it is your current working directory. You will not be able to stop unRAID until you change directory off of a data disk. This is expected now, and far better than terminating processes improperly, or showing you "Unformatted" when your disks really have data. Joe L. Quote Link to comment
lionelhutz Posted November 26, 2009 Share Posted November 26, 2009 Tom; Here is the output of v /sys/block total 0 lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop0 -> ../devices/virtual/block/loop0/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop1 -> ../devices/virtual/block/loop1/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop2 -> ../devices/virtual/block/loop2/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop3 -> ../devices/virtual/block/loop3/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop4 -> ../devices/virtual/block/loop4/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop5 -> ../devices/virtual/block/loop5/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop6 -> ../devices/virtual/block/loop6/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 loop7 -> ../devices/virtual/block/loop7/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 md1 -> ../devices/virtual/block/md1/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 md2 -> ../devices/virtual/block/md2/ lrwxrwxrwx 1 root root 0 Nov 26 13:44 md3 -> ../devices/virtual/block/md3/ lrwxrwxrwx 1 root root 0 Nov 26 07:21 sda -> ../devices/pci0000:00/0000:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/ lrwxrwxrwx 1 root root 0 Nov 25 19:45 sdb -> ../devices/pci0000:00/0000:00:11.0/host1/target1:0:0/1:0:0:0/block/sdb/ lrwxrwxrwx 1 root root 0 Nov 26 07:22 sdc -> ../devices/pci0000:00/0000:00:11.0/host2/target2:0:0/2:0:0:0/block/sdc/ lrwxrwxrwx 1 root root 0 Nov 26 07:21 sdd -> ../devices/pci0000:00/0000:00:11.0/host3/target3:0:0/3:0:0:0/block/sdd/ lrwxrwxrwx 1 root root 0 Nov 26 07:20 sde -> ../devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0/block/sde/ I get what you define as a freeze when accessing a user share which will spin up either of the unused data drives using Windows Explorer. The tests were done on the same machine as the video file is playing on. Just trying to help here. Typically, I'm not accessing the server when watching video, I'm watching the video but it does happen on my system. 1. Attempt to access any disk/user share on the same Windows PC that is currently also playing the media on the already-spun-up disk. This is a problem with Windows & I have not tried to find a fix for it yet. I think this happens in Mac OS as well. Can you give a link to describe this problem? I've never seen it posted or read about it before so I'm curious what the issue is. Peter Quote Link to comment
Kaygee Posted November 26, 2009 Share Posted November 26, 2009 I want to try and clear up some confusion regarding stutter/freeze of media data being read off the unRAID server. First let's define some terms: "stutter" refers to a momentary (less than 1 second) 'glitch' in the displayed video/audio (or just audio if media stream is audio-only). Also included would be a series of "stutters". I think both a freeze and a stutter could be related. Depending on how much information is needed to be retrieved from the disk or disks and how much is retained in the system cache. With drop_caches I can trun a stutter into a stop for the streaming media even to an external hardware streamer. Also I can reproduce this across controllers with disks on separate controllers. Without forcing drop_caches and 4GB RAM installed I had previously never noticed the issue. Quote Link to comment
BRiT Posted November 26, 2009 Share Posted November 26, 2009 I get what you define as a freeze when accessing a user share which will spin up either of the unused data drives using Windows Explorer. The tests were done on the same machine as the video file is playing on. What you are experiencing is not an unRAID problem, but a CLIENT SIDE OS problem. I've seen this exist even when playing media files from a WinOS server to a WinOS client. Quote Link to comment
hgeorges Posted November 26, 2009 Share Posted November 26, 2009 Hello; Can someone coach me how to migrate from latest stable version 4.4.2 pro, to the latest beta. Over time I've tried to install quite a few packages/add-ons, and I have a bit of a mess left, which I'd try to clean up with this upgrade. Which are the original/mandatory files I should keep, and discard everything else? Thanks for your time. HG Quote Link to comment
lionelhutz Posted November 27, 2009 Share Posted November 27, 2009 What you are experiencing is not an unRAID problem, but a CLIENT SIDE OS problem. I've seen this exist even when playing media files from a WinOS server to a WinOS client. That's why I asked for a link explanaing it or with possible solutions. If Windows can't play a network video and access files at the sanme time with Internet Explorer then it must be something common that others have seen and documented. Besides, if you read through the thread others claim it's not a Windows problem.... Peter Quote Link to comment
BRiT Posted November 27, 2009 Share Posted November 27, 2009 Others may not be experiencing the windows problem, but it does exist in a pure Windows EcoSystem involving 2 PCS total, one client and one server. As Tom/Limetech stated, there are several different issues. Some were confusing the Windows client issue with the unRAID server issues. Quote Link to comment
iwens Posted November 27, 2009 Share Posted November 27, 2009 I get what you define as a freeze when accessing a user share which will spin up either of the unused data drives using Windows Explorer. The tests were done on the same machine as the video file is playing on. What you are experiencing is not an unRAID problem, but a CLIENT SIDE OS problem. I've seen this exist even when playing media files from a WinOS server to a WinOS client. I do not believe this is a client side os problem, as i also see it on my popcorn hour. The thing is i use 4 gig in my unraid server so let's say i use 1 gig as cache this will mean even after all drives are for some reason in accessible there will be enough data in cache to feed my popcorn hour for at least 15 min on a standard sd stream. I know this is only theoretically but the fact remains that when unraid spins up a drive the complete unraid server is unresponsive, on a spin up of a drive my media player or any other source cannot receive any data from the server. Now the popcorn hour has a very limited cache build in, so it may survive maybe a 1 sec freeze but it seems a 2 sec data break will confuse the player enough to get a stutter in the playout. So i am interested why the unraid server seems to freeze completely when a drive is spun up, to be clear it could be a hardware/os limit and maybe this can not be avoided. That will be a disappointment as then i will need to avoid any write actions to the server when i am watching on my popcorn hour. Or spin-up all drives when i read data from my video share which will mean increased spin-up and down actions on drive's. Quote Link to comment
daniel.boone Posted November 27, 2009 Share Posted November 27, 2009 I get what you define as a freeze when accessing a user share which will spin up either of the unused data drives using Windows Explorer. The tests were done on the same machine as the video file is playing on. What you are experiencing is not an unRAID problem, but a CLIENT SIDE OS problem. I've seen this exist even when playing media files from a WinOS server to a WinOS client. I do not believe this is a client side os problem, as i also see it on my popcorn hour. The thing is i use 4 gig in my unraid server so let's say i use 1 gig as cache this will mean even after all drives are for some reason in accessible there will be enough data in cache to feed my popcorn hour for at least 15 min on a standard sd stream. I know this is only theoretically but the fact remains that when unraid spins up a drive the complete unraid server is unresponsive, on a spin up of a drive my media player or any other source cannot receive any data from the server. Now the popcorn hour has a very limited cache build in, so it may survive maybe a 1 sec freeze but it seems a 2 sec data break will confuse the player enough to get a stutter in the playout. So i am interested why the unraid server seems to freeze completely when a drive is spun up, to be clear it could be a hardware/os limit and maybe this can not be avoided. That will be a disappointment as then i will need to avoid any write actions to the server when i am watching on my popcorn hour. Or spin-up all drives when i read data from my video share which will mean increased spin-up and down actions on drive's. I'm with you on this one. Lionelhutz is probably experiencing the combination of Win OS and unRaid issue. Those of us that have hardware players see the distinction. I would think if unRaid is corrected Windows only enviroments would continue to experience video freezing. Quote Link to comment
Joe L. Posted November 27, 2009 Share Posted November 27, 2009 I get what you define as a freeze when accessing a user share which will spin up either of the unused data drives using Windows Explorer. The tests were done on the same machine as the video file is playing on. What you are experiencing is not an unRAID problem, but a CLIENT SIDE OS problem. I've seen this exist even when playing media files from a WinOS server to a WinOS client. I do not believe this is a client side os problem, as i also see it on my popcorn hour. The thing is i use 4 gig in my unraid server so let's say i use 1 gig as cache this will mean even after all drives are for some reason in accessible there will be enough data in cache to feed my popcorn hour for at least 15 min on a standard sd stream. I know this is only theoretically but the fact remains that when unraid spins up a drive the complete unraid server is unresponsive, on a spin up of a drive my media player or any other source cannot receive any data from the server. Now the popcorn hour has a very limited cache build in, so it may survive maybe a 1 sec freeze but it seems a 2 sec data break will confuse the player enough to get a stutter in the playout. So i am interested why the unraid server seems to freeze completely when a drive is spun up, to be clear it could be a hardware/os limit and maybe this can not be avoided. That will be a disappointment as then i will need to avoid any write actions to the server when i am watching on my popcorn hour. Or spin-up all drives when i read data from my video share which will mean increased spin-up and down actions on drive's. I'm with you on this one. Lionelhutz is probably experiencing the combination of Win OS and unRaid issue. Those of us that have hardware players see the distinction. I would think if unRaid is corrected Windows only enviroments would continue to experience video freezing. Most of the "hardware players" run Linux of their own. They don't often have a lot of extra buffering. It could as easily be that the disk I/O is blocking network I/O, and regardless of how you access it, it has to rely upon the buffers. On my MG-35 media players, the ISO files on shares are simply mounted through a loop device, yet another possible point of buffering being too small. If I spin up the drives I know I can interrupt the stream enough to have to reset the MG-35. My personal feeling is that there are several causes of the network freeze. It is what is making it difficult to diagnose and determine the cause, as our different hardware is buffering differently, and different hardware drivers handling interrupts differently. Tom's spin-up groups will work for me for most of my media playing, at the expense of a little more power used. Eventually, I feel the causes will be identified and addressed where possible. Joe L. Quote Link to comment
peter_sm Posted November 29, 2009 Share Posted November 29, 2009 This info is copied from the 4.4 forum I can't see my files on the server using W7 or vista, this files are moved to the server using smbmount from the unraid. I can see all my files from my tvix using NFS protocol. I have Export (SMB): set to Export read only Below is a example of a new file copied to my server drwxr-xr-x 1 root root 3440 Nov 21 16:27 ../ -rwxr-xr-x 1 root root 138351 Nov 28 17:13 tvix.jpg* -rwxr-xr-x 1 root root 56805 Nov 28 17:13 front_cover.tvixie* -rwxr-xr-x 1 root root 7914 Nov 28 17:13 folder.jpg* -rwxr-xr-x 1 root root 11736332875 Nov 28 17:13 xxx-xxxxx.mkv* -rwxr-xr-x 1 root root 1998 Nov 28 17:13 MovieInfo.tvixie* Is something wrong ? Using version: 4.5-beta11 OBS, My very first files that was moved to the server is fine , its all my latest files I can't see, so I think it could be some of the latest beta that have doing something wrong with the permission ?? EDIT This files are OK, look at the permission ? it's a capital S in there. -rwxrwSrwx 1 root root 39468 Sep 17 2008 xxxxx.srt* -rwxrwSrwx 1 root root 4700504201 Sep 17 2008 xxxx.mkv* -rwxrwSrwx 1 root root 104225 Sep 17 2008 front_cover.tvixie* -rwxrwSrwx 1 root root 9280 Sep 17 2008 folder.jpg* -rwxrwSrwx 1 root root 118541 Sep 17 2008 TViX.jpg* -rwxrwSrwx 1 root root 1513 Sep 17 2008 MovieInfo.tvixie* -rwxrwSrwx 1 root root 11776 Jul 20 08:56 Thumbs.db* EDIT Added my syslog.... EDIT 2 I think I have solved it, i have done this on one disc chmod -R 766 * And now I can see all my files in W7 Have I done it right?, if so what have cause this problem ? My files now have this permission -rwxrw-rw- 1 root root 8527295020 Jan 2 2009 xxxxxxxx.mkv* -rwxrw-rw- 1 root root 46445 Jan 2 2009 front_cover.tvixie* -rwxrw-rw- 1 root root 9108 Jan 2 2009 folder.jpg* -rwxrw-rw- 1 root root 127035 Oct 4 16:04 TViX.jpg* -rwxrw-rw- 1 root root 2089 Oct 4 16:04 MovieInfo.tvixie* drwxrw-rw- 2 root root 280 Oct 28 20:34 ./ drwxrw-rw- 63 root root 3440 Nov 21 16:27 ../ -rwxrw-rw- 1 root root 24064 Nov 29 2009 Thumbs.db* //Peter Quote Link to comment
BRiT Posted November 29, 2009 Share Posted November 29, 2009 See the previous posts dealing with "map hidden" SAMBA options [ http://lime-technology.com/forum/index.php?topic=4674.msg43584#msg43584 ] Quote Link to comment
peter_sm Posted November 30, 2009 Share Posted November 30, 2009 Thanks, how could I miss that So now I need to change manually using chmod -R 766 for all my files I add to the server. Or is it samething I can do different to avoid this problem wih hidden files ? Quote Link to comment
yp_1 Posted November 30, 2009 Share Posted November 30, 2009 Thanks, how could I miss that So now I need to change manually using chmod -R 766 for all my files I add to the server. Or is it samething I can do different to avoid this problem wih hidden files ? I described a permanent workaround here: http://lime-technology.com/forum/index.php?topic=4674.msg43603#msg43603 Just run this in telnet session. Quote Link to comment
CaptainSpalding Posted December 1, 2009 Share Posted December 1, 2009 I have the 4.4.2 stable, how can I update it to this beta? Quote Link to comment
prostuff1 Posted December 1, 2009 Share Posted December 1, 2009 I have the 4.4.2 stable, how can I update it to this beta? Read the directions in the first post of this thread Quote Link to comment
Joe L. Posted December 1, 2009 Share Posted December 1, 2009 I have the 4.4.2 stable, how can I update it to this beta? Step 1. Read the first post in this thread. Step 2. Follow the upgrade directions given in it. Quote Link to comment
CaptainSpalding Posted December 1, 2009 Share Posted December 1, 2009 Ahh.. I thought that was just changes / bug fixes all the way. Thanks you both! EDIT: Did not even have to reassign the drives, maybe it's because I only have 2? Quote Link to comment
prostuff1 Posted December 1, 2009 Share Posted December 1, 2009 Ahh.. I thought that was just changes / bug fixes all the way. Thanks you both! EDIT: Did not even have to reassign the drives, maybe it's because I only have 2? You usually don't have to reassign drives but every once in a while you might if they get detected in a different order. Quote Link to comment
limetech Posted December 2, 2009 Author Share Posted December 2, 2009 As for freezing... This is always caused by spinning up a disk other than the one you are currently reading media from. I know of two causes of this: 1. Attempt to access any disk/user share on the same Windows PC that is currently also playing the media on the already-spun-up disk. This is a problem with Windows & I have not tried to find a fix for it yet. I think this happens in Mac OS as well. This is what happens to me but its not happening on any PC. My popcorn hour freezes when I force sleeping drives to spin up via user share access. Please try 4.5-beta12 to see if this issue is resolved. Quote Link to comment
RobJ Posted December 2, 2009 Share Posted December 2, 2009 Interrupts are assigned exactly the same way in "failure mode", i.e., when a reboot yields only a 100Mb/s connection. So I'm beginning to feel less and less that it is a linux issue and more and more that the hardware is simply flaky. I pulled the network cable and reconnected and it negotiated 1000Mb/s. (14:41:17 in attached syslog). Went into S3 sleep, then WOL and reconnected A-OK at 1000 (@15:31:41). Once it's working it seems stable. Problem occurs only on startup - I think! Maybe all the different behaviors I noted between beta 6, 8, 10-11 were just random and had nothing to do with the linux core or driver changes. Seemed to me I repeat tested enough to be sure, but now I'm having second thoughts. I did not check back into all of your posts, to see how repeatable the problem is. That is, whether it *always* sets 100Mbps in a particular circumstance. But this sounds to me like a speed negotiation issue, because the negotiated speed seems inconsistent, mostly 1000Mbps but occasionally 100Mbps. When a network connection is first initialized, it tests the line, whether it can support gigabit speed, and if at that moment it does not think it can, then it 'falls back' to 100Mbps. I would have to suspect either the cable is marginal for gigabit support, or the cable is good but there are sources of noise or interference affecting the signal on the cable. Can you try a different network cable, a Cat5e or Cat6 cable known to be good? Then look for sources of interference, such as power lines running very close to it. I apologize for being off-topic to the beta release. Quote Link to comment
kapperz Posted December 6, 2009 Share Posted December 6, 2009 Why do I see files created like ".fuse_hidden0000023900000007" in some directories? Its about 10megs. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.