jbone

That was indeed the problem, thanks Joe. Out of curiosity, why wasn't I seeing this problem with the old version?

Hello, I have been running unRAID 4.7 for a few years now without issue. I am about to run out of space though, so I've purchased some 4TB drives to upgrade my old set with. I read that support for drives > 2TB requires upgrading to unRAID 5, so this is what I am trying to do. After upgrading, my box boots normally, but is not grabbing an IP address. I am using an Intel Pro 1000. I have reverted to unRAID 4.7 and everything is working fine again. I have tried: unRAIDServer-5.0 and unRAIDServer-5.0.5 but I see the same network issue in both. I have attached my syslog from unRAIDServer-5.0.5 Thanks syslog.txt

Fair enough. Thanks for the info.

Hello, Recently my unraid server has started acting up when streaming media. Intermittently the media will freeze and my user share's will briefly drop off my network. In the syslogs, I found the following corresponding entries: Nov 6 21:20:38 jNAS kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Nov 6 21:20:38 jNAS kernel: Tx Queue <0> Nov 6 21:20:38 jNAS kernel: TDH <43> Nov 6 21:20:38 jNAS kernel: TDT <47> Nov 6 21:20:38 jNAS kernel: next_to_use <47> Nov 6 21:20:38 jNAS kernel: next_to_clean <40> Nov 6 21:20:38 jNAS kernel: buffer_info[next_to_clean] Nov 6 21:20:38 jNAS kernel: time_stamp <46f85> Nov 6 21:20:38 jNAS kernel: next_to_watch <43> Nov 6 21:20:38 jNAS kernel: jiffies <47245> Nov 6 21:20:38 jNAS kernel: next_to_watch.status <0> Nov 6 21:20:39 jNAS ifplugd(eth0)[1314]: Link beat lost. Nov 6 21:20:42 jNAS kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Nov 6 21:20:43 jNAS ifplugd(eth0)[1314]: Link beat detected. Doing some research online, I found the following thread among a bunch of not as useful suggestions: http://blog.bradiceanu.net/2010/11/28/netdev-watchdog-eth0-transmit-timed-out/ What caught my eye here is that these problems just started occurring recently and, in fact, coincide with me upgrading the machine to 4GBs of RAM. (Which that thread identifies as a potential problem point.) The suggested solution says that I will require Intel’s e1000 driver version 8.0.25 or higher. I am running unRaid version 4.7 and my driver version is as follows: jNAS:/var/log# ethtool -i eth0 driver: e1000 version: 7.3.21-k5-NAPI Is it possible to upgrade this driver, or am I stuck either removing some RAM or finding a new NIC? Thanks.

I too am stuck with the same issue. I've edited the settings.json file for my IP address a dozen times, and it never "sticks". It seems when I stop and start Transmission using the unMenu script, it overwrites it and resets it back to: "rpc-whitelist": "127.0.0.1", "rpc-whitelist-enabled": true If I go into custom/tranmission/tranmission_conf, I can find the correct settings.json file that unmenu establishes, but the trouble is, I can't make it "take" those settings. Is something wrong with the startup script "transctl"? I noticed another thread where this was mentioned, but it looks like that bug was fixed. Or should the settings file be in a different directory? Any help is much appreciated! I was having the same problem at first, until I realized I was trying to modify the settings while Transmission was running. I found that Transmission writes to the conf file again on shutdown (overwriting all the changes I'd made). Once I discovered that, I made all my changes with Transmission shut down, then started it back up. Settings took that time.

This is the list from a private tracker I am using, which I believe is also well known and respected: Transmission/1.22 (6228) Transmission/1.51 (79*) Transmission/1.53 Transmission/1.54 Transmission/1.60 Transmission/1.61 Transmission/1.76 Transmission/1.77 Transmission/1.90 Transmission/1.92 STABLE † (This indicates this version will soon be banned) Transmission/1.93 STABLE Transmission/2.04 Transmission/2.12 Transmission/2.13 Transmission/2.22 Transmission/2.31

Not for a while. I am busy reworking the airvideo package and the 2.01 version in the package works fine for me. I don't have much motivation to fix something that is not broken, especially when I have other packages that need attention. It does work well, I was impressed how easy it was to get setup. I only asked because a couple of the private trackers I am on don't allow Transmission versions earlier than 2.04. Thanks for the great package though!

Any chance the Transmission version will be upgraded beyond 2.01 in this package?

Thanks Joe.

I sent this thread to [email protected], is that who you were referring to?

Disk history is as folllows: This was a brand new HDD. I added it and the parity drive to my array before adding anything else (or reading enough documentation, apparently). I did not pre-clear it, I just added it, then formatted through the Web UI. Afterwards, I realized that this had added it as MBR:unaligned, and that I wanted MBR:4k-aligned. I switched my default setting to MBR:4k-aligned. At that point, I removed it from the array, ran preclear (specifying -A) then dropped it back in the array and formatted through the UI once again. cat /sys/block/sdb/size 3907029168 dd status=noxfer count=1 if=/dev/sdb | od -Ad -t x1 1+0 records in 1+0 records out 0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000448 00 00 00 00 00 00 40 00 00 00 70 88 e0 e8 00 00 0000464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 * 0000496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa 0000512

Here's the screenshot and syslog: syslog.txt

But in the Web UI, the parity drive is listed as sda: parity device: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) WDC_WD20EARS-22MVWB0_WD-WCAZA4035730

Hello, I am brand new to UnRaid. Just set up my first array with UnRaid version: 4.7. I pre-cleared each of my disks, then added them to the array and formatted. I've copied over all my data and everything seems to be working fine, but I'm curious about the output of fdisk -l. Here is my Parity drive: Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 2 62016336 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. and here is one of my data drives: Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. but here is my other data drive: Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 243202 1953514552 0 Empty Partition 1 does not end on cylinder boundary. It reports ID 0 and System 'Empty'?? I can see and access all the data that has gone to that drive, so everything appears to be in order. But is that something I need to be worried about? Thanks.