Phil C. Posted December 17, 2011 Share Posted December 17, 2011 Frank1940, The two seconds after pausing (and spinning down) is your player's buffer running out. Then you have a short pause while the drives spin back up and the movie continues from where the buffer left off. All of what you have identified is normal behavior that I see through AFP or SMB. In short, enjoy unRAID - you don't have a problem. Quote Link to comment
Frank1940 Posted December 17, 2011 Share Posted December 17, 2011 Frank1940, The two seconds after pausing (and spinning down) is your player's buffer running out. Then you have a short pause while the drives spin back up and the movie continues from where the buffer left off. All of what you have identified is normal behavior that I see through AFP or SMB. In short, enjoy unRAID - you don't have a problem. Your explanation is exactly what I thought was the cause of the pause in my playback. What I was attempting to point out was that I am not NORMALLY having the issue that I surmise (from their description) that other people are experiencing with NFS--These are the people who are complaining that NFS is 'broke'. However, I can create those problems by spinning down the array while in a paused playback situation. What I don't know is that is their problem or not. Was their array spun down and a buffer somewhere contained a few seconds of content? I don't know exactly what their problem is but I was hoping that one of the people with the problem would take an hour or so and look at what is happening on their system. And provide enough details so that the root cause of the problem could be uncovered. Quote Link to comment
PeterB Posted December 17, 2011 Share Posted December 17, 2011 What I don't know is that is their problem or not. Was their array spun down and a buffer somewhere contained a few seconds of content? I don't know exactly what their problem is but I was hoping that one of the people with the problem would take an hour or so and look at what is happening on their system. And provide enough details so that the root cause of the problem could be uncovered. What I experience is that when I copy files from unRAID, unto the disk of a client computer (running Ubuntu) - and the problem occurs if it is an application reading the file(s) - the file transfer hangs after a few seconds. It never restarts, and the only way to regain control over nfs appears to be to reboot both computers. I see no evidence linked to this event in the syslog. If you would care to tell me what I should be looking at during this 'hour or so', I will gladly do it. I have to believe that the problem lies with unRAID/kernel 3.x, because I do not experience this problem when running unRAID 5.0 beta 11. Quote Link to comment
Frank1940 Posted December 18, 2011 Share Posted December 18, 2011 What I don't know is that is their problem or not. Was their array spun down and a buffer somewhere contained a few seconds of content? I don't know exactly what their problem is but I was hoping that one of the people with the problem would take an hour or so and look at what is happening on their system. And provide enough details so that the root cause of the problem could be uncovered. What I experience is that when I copy files from unRAID, unto the disk of a client computer (running Ubuntu) - and the problem occurs if it is an application reading the file(s) - the file transfer hangs after a few seconds. It never restarts, and the only way to regain control over nfs appears to be to reboot both computers. I see no evidence linked to this event in the syslog. If you would care to tell me what I should be looking at during this 'hour or so', I will gladly do it. I have to believe that the problem lies with unRAID/kernel 3.x, because I do not experience this problem when running unRAID 5.0 beta 11. At this point, I am a little confused about exactly what the process is. Are you copying a file from the unRAID server directly to the Hard Disk on the Unbuntu computer? Where are you starting the transfer from? What is this comment about " the problem occurs if it is an application reading the file(s)"? How can an application be reading a file which is being transferred? Normally, a program that wants to use a file will open it for either reading or read/write. In any case, I would be looking at the "Device Status" on the main page of the browser interface to see what the disk status is before I initiated the start of the transfer. If they are spun down prior to the start of the transfer, do they spin up? (You have to 'refresh' the browser to see if the status changes.) If the drives are spun down, you can force a spin up and see if the transfer works as it should. You can also force a spin down from that same page. Understand that you are trying to figure out exactly what is not working correctly. If you can find some action that makes it work correctly, than whoever will have to fix the issue will have a leg up on what will have to be done. The point, I was trying to make is that not everyone has a problem with NFS transfers. I certainly do not mean to imply that you are imagining things. To give the developer(s) a hand in the solution, those people with a problem have to describe in great detail exactly what they are doing, what the state of the unRAID server is, how does it change (Example, does it completely lock up) and any other observations that you might have. (f I were to hazard a guess as to cause of the problem , I would tend to suspect that some piece of hardware (or hardware driver) is not working quite correctly with the version 3 kernel. BUT I really don't know...) Quote Link to comment
peter_sm Posted December 18, 2011 Share Posted December 18, 2011 The issue I have are when I have a folder on unraid with about 15 MKV files with sub files for each mkkv (.srt), when streaming of a mkv from tvix (media player) the subtitles only show first line, when moving that MKV and srt file to a own folder the subtitles works thru entire movie. Streaming using samba to the folder with 15 mkv all subs are OK //Peter Quote Link to comment
PeterB Posted December 18, 2011 Share Posted December 18, 2011 What I don't know is that is their problem or not. Was their array spun down and a buffer somewhere contained a few seconds of content? I don't know exactly what their problem is but I was hoping that one of the people with the problem would take an hour or so and look at what is happening on their system. And provide enough details so that the root cause of the problem could be uncovered. What I experience is that when I copy files from unRAID, unto the disk of a client computer (running Ubuntu) - and the problem occurs if it is an application reading the file(s) - the file transfer hangs after a few seconds. It never restarts, and the only way to regain control over nfs appears to be to reboot both computers. I see no evidence linked to this event in the syslog. If you would care to tell me what I should be looking at during this 'hour or so', I will gladly do it. I have to believe that the problem lies with unRAID/kernel 3.x, because I do not experience this problem when running unRAID 5.0 beta 11. At this point, I am a little confused about exactly what the process is. Are you copying a file from the unRAID server directly to the Hard Disk on the Unbuntu computer? Where are you starting the transfer from? Sorry not to be explicit, but I'm doing the natural thing - I'm sitting on the Ubuntu desktop, attempting to fetch a file from the unRAID server to save it to a local disk on the workstation. What is this comment about " the problem occurs if it is an application reading the file(s)"? How can an application be reading a file which is being transferred? Normally, a program that wants to use a file will open it for either reading or read/write. Sorry ... I left the word 'also' out from my sentence. I first encountered the problem when I was attempting to open the flac file on the server, with a sound converter running in Ubuntu, attempting to create an mp3 file. The sound converter process hung, so I thought 'No problem', I'll simply copy the file to a local device and do the conversion from there. This was when I discovered that even the simple file copy (using Nautilus on the desktop) was also failing. In any case, I would be looking at the "Device Status" on the main page of the browser interface to see what the disk status is before I initiated the start of the transfer. If they are spun down prior to the start of the transfer, do they spin up? (You have to 'refresh' the browser to see if the status changes.) If the drives are spun down, you can force a spin up and see if the transfer works as it should. Yes, the drive does spin up, because the first few megabytes of the file do get transferred. You can also force a spin down from that same page. Understand that you are trying to figure out exactly what is not working correctly. If you can find some action that makes it work correctly, than whoever will have to fix the issue will have a leg up on what will have to be done. I have not found anything which will make the copy succeed (apart from starting with beta11 on the server - 12, 12a, 13 and 14 all fail. The point, I was trying to make is that not everyone has a problem with NFS transfers. I've been waiting to hear from someone who says something like: "I use nfs all the time, and I've never seen this problem.", but I don't recall having seen such a post. I certainly do not mean to imply that you are imagining things. To give the developer(s) a hand in the solution, those people with a problem have to describe in great detail exactly what they are doing, what the state of the unRAID server is, how does it change (Example, does it completely lock up) and any other observations that you might have. Sure, I understand that. I have worked in software/systems development for 30 years. I have even been known to identify a coding error in a SCSI device driver, written in ARM assembler. Purely from observing symptoms, I predicted precisely what instruction was wrong, searched the binary, found the instruction, patched it and fixed the driver. (f I were to hazard a guess as to cause of the problem , I would tend to suspect that some piece of hardware (or hardware driver) is not working quite correctly with the version 3 kernel. BUT I really don't know...) Perhaps, but the most likely drivers to cause this problem would be the disk host controller, and have observed the problem with both the motherboard host controller, and with a PCIe host controller. The other likely candidate would be the NIC driver, but I'm using an Intel e1000 which is supposed to be one of the most solidly supported devices. I first reported the problem here. I realise that the one test I ought to perform is to see whether the disk share can still be accessed from another Ubuntu client, after the fault has been provoked. Perhaps I should return the drive to a mobo port, and retest with 12, 12a, 13, 14 and the 14/latest kernel combination, and in each case provoke the fault and then attempt access from another client. Other suggestions for further investigation would be appreciated. Quote Link to comment
Frank1940 Posted December 18, 2011 Share Posted December 18, 2011 Quote from PeterB: "...I first encountered the problem when I was attempting to open the flac file on the server, with a sound converter running in Ubuntu, attempting to create an mp3 file. The sound converter process hung, so I thought 'No problem', I'll simply copy the file to a local device and do the conversion from there. This was when I discovered that even the simple file copy (using Nautilus on the desktop) was also failing." OK, my Netgear NTV550 is running Linux kernel 2.6.22.19. (Of course,this kernel is only the foundation and Netgear has added a lot of their proprietary code.) I think you should now realize that I am playing a media file on the NTV550 which is using an application running under Linux. It is working! But as I said in my original post, this unRAID system is using really, really old hardware! The disks are all IDE disks and the 20GB HD has a manufacturing date of Feb 2002. BUT the hardware and software are working, and apparently quite satisfactorily. I am not the one who is going to solve this problem. What has to happen is for more people with both working and non-working systems to chime is and contribute their experiences. IF this were to happen, a pattern of hardware usage might evolve that would contain the key to the solution. Unfortunately, Limetech's license agreement and the way that the Plus and Pro software are keyed to a single USB memory stick make it difficult to run a quick test with beta software on systems that have more than three disks on them. I would venture that many people are testing beta versions are using test setups cobbled together with parts from their junk boxes--- just as I did! And their signature line containing their setup would not necessarily reflect their beta testing setup. PS: Note to all users of media players and streamers: I believe that all of these devices are using Linux as the core of their operating system. Its usage is free of any licensing fees. In fact, my Toshiba HD-DVD and Panasonic Blu-ray players use an Linux core! Quote Link to comment
joshpond Posted December 18, 2011 Share Posted December 18, 2011 Hi PeterB, Have you had a look around other forums? If NFS is broken with kernal 3.xxxx then I suspect a lot of people running the newer ubuntu etc flavours would see a few other issues pop up? (I'm assuming the latest ubuntu builds have the 3.xxx kernal, been a while since I've looked.) Josh Quote Link to comment
gfjardim Posted December 18, 2011 Share Posted December 18, 2011 Hi PeterB, Have you had a look around other forums? If NFS is broken with kernal 3.xxxx then I suspect a lot of people running the newer ubuntu etc flavours would see a few other issues pop up? (I'm assuming the latest ubuntu builds have the 3.xxx kernal, been a while since I've looked.) Josh Seems that the issue is related to the combination of NFS and fuse-mounted file system (the "/mnt/user" mount). Quote Link to comment
Frank1940 Posted December 18, 2011 Share Posted December 18, 2011 Hi PeterB, Have you had a look around other forums? If NFS is broken with kernal 3.xxxx then I suspect a lot of people running the newer ubuntu etc flavours would see a few other issues pop up? (I'm assuming the latest ubuntu builds have the 3.xxx kernal, been a while since I've looked.) Josh Seems that the issue is related to the combination of NFS and fuse-mounted file system (the "/mnt/user" mount). Sorry to report that is not true in my case. My mount point is /mnt/user/Media. And I have had no problems. Josh, (if you are running either beta 13 or 14), Will you describe your experience and any problems you may have had? A complete description of your test bed might also help. Quote Link to comment
PeterB Posted December 18, 2011 Share Posted December 18, 2011 Seems that the issue is related to the combination of NFS and fuse-mounted file system (the "/mnt/user" mount). Sorry to report that is not true in my case. My mount point is /mnt/user/Media. And I have had no problems. ... and I'm experiencing the problem with /mnt/disk2/Music/... Quote Link to comment
spants Posted December 20, 2011 Share Posted December 20, 2011 (I'm using 5b13 with a mix of NFS (media streaming music, avi and bluray rips on openelec linux xbmc) from user mnts and smb with no transfer issues) Quote Link to comment
Frank1940 Posted December 20, 2011 Share Posted December 20, 2011 (I'm using 5b13 with a mix of NFS (media streaming music, avi and bluray rips on openelec linux xbmc) from user mnts and smb with no transfer issues) What is your equipment setup? Quote Link to comment
joshpond Posted December 20, 2011 Share Posted December 20, 2011 Josh, (if you are running either beta 13 or 14), Will you describe your experience and any problems you may have had? A complete description of your test bed might also help. Sorry, I don't run the betas at the moment, using 4.7. It was just a thought, trying to pinpoint the issue. If it was purely a kernel issue I would have thought a lot of people would have had issues. Josh Quote Link to comment
Interstellar Posted December 20, 2011 Share Posted December 20, 2011 Getting segfaults with this release, never had the issue before IIRC. This is what happens if I try and manually start it: Dec 20 23:04:40 Tower emhttp: unRAID System Management Utility version 5.0-beta14 (Lime Tech) Dec 20 23:04:40 Tower emhttp: Copyright (C) 2005-2011, Lime Technology, LLC (Lime Tech) Dec 20 23:04:40 Tower emhttp: Plus key detected, GUID: 0781-5530-2444-13111DE05C32 (Other emhttp) Dec 20 23:04:40 Tower emhttp: rdevName.22 not found (Other emhttp) Dec 20 23:04:41 Tower emhttp: diskFsStatus.1 not found (Other emhttp) Dec 20 23:04:41 Tower kernel: emhttp[12455]: segfault at 0 ip b763b760 sp bfe332b0 error 4 in libc-2.11.1.so[b75c2000+15c000] (Errors) Dec 20 23:05:04 Tower emhttp: unRAID System Management Utility version 5.0-beta14 (Lime Tech) Dec 20 23:05:04 Tower emhttp: Copyright (C) 2005-2011, Lime Technology, LLC (Lime Tech) Dec 20 23:05:04 Tower emhttp: Plus key detected, GUID: 0781-5530-2444-13111DE05C32 (Other emhttp) Dec 20 23:05:05 Tower emhttp: rdevName.22 not found (Other emhttp) Dec 20 23:05:05 Tower emhttp: diskFsStatus.1 not found (Other emhttp) Dec 20 23:05:05 Tower kernel: emhttp[12481]: segfault at 0 ip b753b760 sp bf9f4c90 error 4 in libc-2.11.1.so[b74c2000+15c000] (Errors) Dec 20 23:05:31 Tower logger: Tue Dec 20 14:41:45 GMT 2011 - Hard Drives active, resetting counter Dec 20 23:06:31 Tower logger: Tue Dec 20 14:41:45 GMT 2011 - Hard Drives active, resetting counter Dec 20 23:08:31 Tower last message repeated 2 times Dec 20 23:09:02 Tower emhttp: unRAID System Management Utility version 5.0-beta14 (Lime Tech) Dec 20 23:09:02 Tower emhttp: Copyright (C) 2005-2011, Lime Technology, LLC (Lime Tech) Dec 20 23:09:02 Tower emhttp: Plus key detected, GUID: 0781-5530-2444-13111DE05C32 (Other emhttp) Dec 20 23:09:02 Tower emhttp: rdevName.22 not found (Other emhttp) Dec 20 23:09:02 Tower emhttp: diskFsStatus.1 not found (Other emhttp) Dec 20 23:09:02 Tower kernel: emhttp[12721]: segfault at 0 ip b74e5760 sp bfbb37f0 error 4 in libc-2.11.1.so[b746c000+15c000] (Errors) Dec 20 23:09:31 Tower logger: Tue Dec 20 14:41:45 GMT 2011 - Hard Drives active, resetting counter root@Tower:~# /usr/local/sbin/emhttp & [1] 12721 root@Tower:~# ps -C emhttp PID TTY TIME CMD [1]+ Segmentation fault /usr/local/sbin/emhttp root@Tower:~# Machine is in the middle of a parity check and correct if it helps. HOWEVER, I do have extensions installed, but nothing I didn't have before b14. I will remove the Smartfeatures GUI when the server is finished. Rebooting fixes the issue when it happened before tho. Edit: Found this thread: http://lime-technology.com/forum/index.php?topic=16379.0 Did that, GUI came back showing cache disk as unformatted, which I assume because it was asleep. Restarted, GUI is back and i've set the parity check and correct off again. Wonder what causes the GUI to fall over/give a seg fault!? Quote Link to comment
jdog09 Posted December 21, 2011 Share Posted December 21, 2011 Any update on the NFS issue? I have used Unraid for a couple of years as a NFS store for VMWare and XenCenter. I can't keep a NFS from going stale. Usually 12-24 hours something happens. I drop and remount the client (XenCenter) and I can restart my VM. The NFS mount point on Private Only.. NO SMB or AFP enabled. Private Security Rule 192.168.1.199(rw,no_root_squash) Any other ideas.. Quote Link to comment
jbrodriguez Posted December 21, 2011 Share Posted December 21, 2011 i believe limetech is waiting for a new linux kernel, to release a beta15. Quote Link to comment
JackBauer Posted December 22, 2011 Share Posted December 22, 2011 This beta is based on kernel 3.1.1. 3.1.6 has been out for like a couple weeks now I think? So it's likely Tom is working on an update, just a matter of when. I'm hoping for an early xmas present Quote Link to comment
peter_sm Posted December 22, 2011 Share Posted December 22, 2011 The issue I have are when I have a folder on unraid with about 15 MKV files with sub files for each mkkv (.srt), when streaming of a mkv from tvix (media player) the subtitles only show first line, when moving that MKV and srt file to a own folder the subtitles works thru entire movie. Streaming using samba to the folder with 15 mkv all subs are OK //Peter My issue is on user share, using Disk share no issues. //Peter Quote Link to comment
peter_sm Posted December 22, 2011 Share Posted December 22, 2011 Kernel 3.1.6 Some FUSE fix http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.1.6 Quote Link to comment
Joe L. Posted December 22, 2011 Share Posted December 22, 2011 Kernel 3.1.6 Some FUSE fix http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.1.6 Looks promissing... One bug was when seeking. The other when buffering pages of data. Either could explain the issue with subtitles. Quote Link to comment
flixxx Posted December 22, 2011 Share Posted December 22, 2011 Hi, I get random ethernet drops with version 5b14. An issue I never had with V4.7 Dec 20 04:09:48 kenny kernel: e1000e 0000:03:00.0: eth0: Reset adapter Dec 20 04:09:48 kenny dhcpcd[1020]: eth0: carrier lost Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: carrier acquired Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: rebinding lease of 192.168.1.110 Dec 20 04:09:51 kenny kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: acknowledged 192.168.1.110 from 192.168.1.1 Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: checking for 192.168.1.110 Dec 20 04:09:56 kenny dhcpcd[1020]: eth0: leased 192.168.1.110 for infinity Dec 20 04:10:11 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: I have an Asus P5WD2 Premium board, but I tested a PCI Ethernet card with the same issue (I don't recall which one at the moment). Here are the logs before and after the drop; Dec 20 04:07:30 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:07:30 kenny kernel: TDH Dec 20 04:07:30 kenny kernel: TDT <38> Dec 20 04:07:30 kenny kernel: next_to_use <38> Dec 20 04:07:30 kenny kernel: next_to_clean Dec 20 04:07:30 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:07:30 kenny kernel: time_stamp <3d2c935> Dec 20 04:07:30 kenny kernel: next_to_watch Dec 20 04:07:30 kenny kernel: jiffies <3d2c9ec> Dec 20 04:07:30 kenny kernel: next_to_watch.status <0> Dec 20 04:07:30 kenny kernel: MAC Status <80080783> Dec 20 04:07:30 kenny kernel: PHY Status <796d> Dec 20 04:07:30 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:07:30 kenny kernel: PHY Extended Status <3000> Dec 20 04:07:30 kenny kernel: PCI Status <10> Dec 20 04:07:32 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:07:32 kenny kernel: TDH Dec 20 04:07:32 kenny kernel: TDT <38> Dec 20 04:07:32 kenny kernel: next_to_use <38> Dec 20 04:07:32 kenny kernel: next_to_clean Dec 20 04:07:32 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:07:32 kenny kernel: time_stamp <3d2c935> Dec 20 04:07:32 kenny kernel: next_to_watch Dec 20 04:07:32 kenny kernel: jiffies <3d2cab4> Dec 20 04:07:32 kenny kernel: next_to_watch.status <0> Dec 20 04:07:32 kenny kernel: MAC Status <80080783> Dec 20 04:07:32 kenny kernel: PHY Status <796d> Dec 20 04:07:32 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:07:32 kenny kernel: PHY Extended Status <3000> Dec 20 04:07:32 kenny kernel: PCI Status <10> Dec 20 04:07:34 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:07:34 kenny kernel: TDH Dec 20 04:07:34 kenny kernel: TDT <38> Dec 20 04:07:34 kenny kernel: next_to_use <38> Dec 20 04:07:34 kenny kernel: next_to_clean Dec 20 04:07:34 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:07:34 kenny kernel: time_stamp <3d2c935> Dec 20 04:07:34 kenny kernel: next_to_watch Dec 20 04:07:34 kenny kernel: jiffies <3d2cb7c> Dec 20 04:07:34 kenny kernel: next_to_watch.status <0> Dec 20 04:07:34 kenny kernel: MAC Status <80080783> Dec 20 04:07:34 kenny kernel: PHY Status <796d> Dec 20 04:07:34 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:07:34 kenny kernel: PHY Extended Status <3000> Dec 20 04:07:34 kenny kernel: PCI Status <10> Dec 20 04:07:36 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:07:36 kenny kernel: TDH Dec 20 04:07:36 kenny kernel: TDT <38> Dec 20 04:07:36 kenny kernel: next_to_use <38> Dec 20 04:07:36 kenny kernel: next_to_clean Dec 20 04:07:36 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:07:36 kenny kernel: time_stamp <3d2c935> Dec 20 04:07:36 kenny kernel: next_to_watch Dec 20 04:07:36 kenny kernel: jiffies <3d2cc44> Dec 20 04:07:36 kenny kernel: next_to_watch.status <0> Dec 20 04:07:36 kenny kernel: MAC Status <80080783> Dec 20 04:07:36 kenny kernel: PHY Status <796d> Dec 20 04:07:36 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:07:36 kenny kernel: PHY Extended Status <3000> Dec 20 04:07:36 kenny kernel: PCI Status <10> Dec 20 04:07:38 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:07:38 kenny kernel: TDH Dec 20 04:07:38 kenny kernel: TDT <38> Dec 20 04:07:38 kenny kernel: next_to_use <38> Dec 20 04:07:38 kenny kernel: next_to_clean Dec 20 04:07:38 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:07:38 kenny kernel: time_stamp <3d2c935> Dec 20 04:07:38 kenny kernel: next_to_watch Dec 20 04:07:38 kenny kernel: jiffies <3d2cd0c> Dec 20 04:07:38 kenny kernel: next_to_watch.status <0> Dec 20 04:07:38 kenny kernel: MAC Status <80080783> Dec 20 04:07:38 kenny kernel: PHY Status <796d> Dec 20 04:07:38 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:07:38 kenny kernel: PHY Extended Status <3000> Dec 20 04:07:38 kenny kernel: PCI Status <10> Dec 20 04:07:39 kenny kernel: e1000e 0000:03:00.0: eth0: Reset adapter Dec 20 04:07:40 kenny dhcpcd[1020]: eth0: carrier lost Dec 20 04:07:42 kenny dhcpcd[1020]: eth0: carrier acquired Dec 20 04:07:42 kenny dhcpcd[1020]: eth0: rebinding lease of 192.168.1.110 Dec 20 04:07:42 kenny kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Dec 20 04:07:42 kenny dhcpcd[1020]: eth0: acknowledged 192.168.1.110 from 192.168.1.1 Dec 20 04:07:43 kenny dhcpcd[1020]: eth0: checking for 192.168.1.110 Dec 20 04:07:48 kenny dhcpcd[1020]: eth0: leased 192.168.1.110 for infinity Dec 20 04:09:39 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:09:39 kenny kernel: TDH <92> Dec 20 04:09:39 kenny kernel: TDT Dec 20 04:09:39 kenny kernel: next_to_use Dec 20 04:09:39 kenny kernel: next_to_clean <91> Dec 20 04:09:39 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:09:39 kenny kernel: time_stamp <3d2fb6f> Dec 20 04:09:39 kenny kernel: next_to_watch <92> Dec 20 04:09:39 kenny kernel: jiffies <3d2fbec> Dec 20 04:09:39 kenny kernel: next_to_watch.status <0> Dec 20 04:09:39 kenny kernel: MAC Status <80080783> Dec 20 04:09:39 kenny kernel: PHY Status <796d> Dec 20 04:09:39 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:09:39 kenny kernel: PHY Extended Status <3000> Dec 20 04:09:39 kenny kernel: PCI Status <10> Dec 20 04:09:41 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:09:41 kenny kernel: TDH <92> Dec 20 04:09:41 kenny kernel: TDT Dec 20 04:09:41 kenny kernel: next_to_use Dec 20 04:09:41 kenny kernel: next_to_clean <91> Dec 20 04:09:41 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:09:41 kenny kernel: time_stamp <3d2fb6f> Dec 20 04:09:41 kenny kernel: next_to_watch <92> Dec 20 04:09:41 kenny kernel: jiffies <3d2fcb4> Dec 20 04:09:41 kenny kernel: next_to_watch.status <0> Dec 20 04:09:41 kenny kernel: MAC Status <80080783> Dec 20 04:09:41 kenny kernel: PHY Status <796d> Dec 20 04:09:41 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:09:41 kenny kernel: PHY Extended Status <3000> Dec 20 04:09:41 kenny kernel: PCI Status <10> Dec 20 04:09:43 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:09:43 kenny kernel: TDH <92> Dec 20 04:09:43 kenny kernel: TDT Dec 20 04:09:43 kenny kernel: next_to_use Dec 20 04:09:43 kenny kernel: next_to_clean <91> Dec 20 04:09:43 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:09:43 kenny kernel: time_stamp <3d2fb6f> Dec 20 04:09:43 kenny kernel: next_to_watch <92> Dec 20 04:09:43 kenny kernel: jiffies <3d2fd7c> Dec 20 04:09:43 kenny kernel: next_to_watch.status <0> Dec 20 04:09:43 kenny kernel: MAC Status <80080783> Dec 20 04:09:43 kenny kernel: PHY Status <796d> Dec 20 04:09:43 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:09:43 kenny kernel: PHY Extended Status <3000> Dec 20 04:09:43 kenny kernel: PCI Status <10> Dec 20 04:09:45 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:09:45 kenny kernel: TDH <92> Dec 20 04:09:45 kenny kernel: TDT Dec 20 04:09:45 kenny kernel: next_to_use Dec 20 04:09:45 kenny kernel: next_to_clean <91> Dec 20 04:09:45 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:09:45 kenny kernel: time_stamp <3d2fb6f> Dec 20 04:09:45 kenny kernel: next_to_watch <92> Dec 20 04:09:45 kenny kernel: jiffies <3d2fe44> Dec 20 04:09:45 kenny kernel: next_to_watch.status <0> Dec 20 04:09:45 kenny kernel: MAC Status <80080783> Dec 20 04:09:45 kenny kernel: PHY Status <796d> Dec 20 04:09:45 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:09:45 kenny kernel: PHY Extended Status <3000> Dec 20 04:09:45 kenny kernel: PCI Status <10> Dec 20 04:09:47 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:09:47 kenny kernel: TDH <92> Dec 20 04:09:47 kenny kernel: TDT Dec 20 04:09:47 kenny kernel: next_to_use Dec 20 04:09:47 kenny kernel: next_to_clean <91> Dec 20 04:09:47 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:09:47 kenny kernel: time_stamp <3d2fb6f> Dec 20 04:09:47 kenny kernel: next_to_watch <92> Dec 20 04:09:47 kenny kernel: jiffies <3d2ff0c> Dec 20 04:09:47 kenny kernel: next_to_watch.status <0> Dec 20 04:09:47 kenny kernel: MAC Status <80080783> Dec 20 04:09:47 kenny kernel: PHY Status <796d> Dec 20 04:09:47 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:09:47 kenny kernel: PHY Extended Status <3000> Dec 20 04:09:47 kenny kernel: PCI Status <10> Dec 20 04:09:48 kenny kernel: e1000e 0000:03:00.0: eth0: Reset adapter Dec 20 04:09:48 kenny dhcpcd[1020]: eth0: carrier lost Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: carrier acquired Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: rebinding lease of 192.168.1.110 Dec 20 04:09:51 kenny kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: acknowledged 192.168.1.110 from 192.168.1.1 Dec 20 04:09:51 kenny dhcpcd[1020]: eth0: checking for 192.168.1.110 Dec 20 04:09:56 kenny dhcpcd[1020]: eth0: leased 192.168.1.110 for infinity Dec 20 04:10:11 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:10:11 kenny kernel: TDH <80> Dec 20 04:10:11 kenny kernel: TDT Dec 20 04:10:11 kenny kernel: next_to_use Dec 20 04:10:11 kenny kernel: next_to_clean <7d> Dec 20 04:10:11 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:10:11 kenny kernel: time_stamp <3d30749> Dec 20 04:10:11 kenny kernel: next_to_watch <80> Dec 20 04:10:11 kenny kernel: jiffies <3d3086c> Dec 20 04:10:11 kenny kernel: next_to_watch.status <0> Dec 20 04:10:11 kenny kernel: MAC Status <80080783> Dec 20 04:10:11 kenny kernel: PHY Status <796d> Dec 20 04:10:11 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:10:11 kenny kernel: PHY Extended Status <3000> Dec 20 04:10:11 kenny kernel: PCI Status <10> Dec 20 04:10:13 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:10:13 kenny kernel: TDH <80> Dec 20 04:10:13 kenny kernel: TDT Dec 20 04:10:13 kenny kernel: next_to_use Dec 20 04:10:13 kenny kernel: next_to_clean <7d> Dec 20 04:10:13 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:10:13 kenny kernel: time_stamp <3d30749> Dec 20 04:10:13 kenny kernel: next_to_watch <80> Dec 20 04:10:13 kenny kernel: jiffies <3d30934> Dec 20 04:10:13 kenny kernel: next_to_watch.status <0> Dec 20 04:10:13 kenny kernel: MAC Status <80080783> Dec 20 04:10:13 kenny kernel: PHY Status <796d> Dec 20 04:10:13 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:10:13 kenny kernel: PHY Extended Status <3000> Dec 20 04:10:13 kenny kernel: PCI Status <10> Dec 20 04:10:15 kenny kernel: e1000e 0000:03:00.0: eth0: Detected Hardware Unit Hang: Dec 20 04:10:15 kenny kernel: TDH <80> Dec 20 04:10:15 kenny kernel: TDT Dec 20 04:10:15 kenny kernel: next_to_use Dec 20 04:10:15 kenny kernel: next_to_clean <7d> Dec 20 04:10:15 kenny kernel: buffer_info[next_to_clean]: Dec 20 04:10:15 kenny kernel: time_stamp <3d30749> Dec 20 04:10:15 kenny kernel: next_to_watch <80> Dec 20 04:10:15 kenny kernel: jiffies <3d309fc> Dec 20 04:10:15 kenny kernel: next_to_watch.status <0> Dec 20 04:10:15 kenny kernel: MAC Status <80080783> Dec 20 04:10:15 kenny kernel: PHY Status <796d> Dec 20 04:10:15 kenny kernel: PHY 1000BASE-T Status <7c00> Dec 20 04:10:15 kenny kernel: PHY Extended Status <3000> Dec 20 04:10:15 kenny kernel: PCI Status <10> Quote Link to comment
Auggie Posted December 22, 2011 Share Posted December 22, 2011 b15 has been relatively stable so far, until now. Web GUI is unresponsive but unMENU still is accessible. syslog-2011-12-22.txt.zip Quote Link to comment
elkay14 Posted December 22, 2011 Share Posted December 22, 2011 I have a 3.1.6 kernel ready to test with beta14: You'll find the bzroot and bzimage here: http://blueskyhorizon.com/unraid/kernel/v5/3.1.6/ The files are much smaller than stock because I used xz compression for them instead of gzip. Tom should do this to save on his bandwidth bill! Please only download these if you intend to actually test them; they are hosted at home over my cable internet connection. Quote Link to comment
Frank1940 Posted December 22, 2011 Share Posted December 22, 2011 I have a 3.1.6 kernel ready to test with beta14: You'll find the bzroot and bzimage here: http://blueskyhorizon.com/unraid/kernel/v5/3.1.6/ The files are much smaller than stock because I used xz compression for them instead of gzip. Tom should do this to save on his bandwidth bill! Please only download these if you intend to actually test them; they are hosted at home over my cable internet connection. How are these files used since you changed the compression scheme? Or does the boot process 'know' how to handle xz as well as gzip? 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.