snsumner

Bump

Yes, I have two identical NICs in different PCIe slots. However, in ESXi settings both are assigned as VM DirectPathIO and I'm only added one NIC to my UnRAID 6 VM. I only see eth0 and there is no indication in syslog that a second NIC is detected.

Hello, I'm a long time UnRAID power user and have be running 5.0.5 stable under ESXi 5.5 for well over a year with zero issues. I tried upgrading to UnRAID 6.0-beta15 and cannot get my NIC to work with it. I'm using VM DirectPathIO + ESXi 5.5 u2e and it does bind to eth0 but there is no RX/TX traffic when I run ethtool eth0 it says the link is down. I don't see any error messages in the /var/log/syslog keyword "tg3". I'm using BCM5751 because they are officially supported by ESXi 5.x for VM DirectPathIO and it works just fine with UnRAID 5.0.5 but no joy with UnRAID 6.0-beta15. I can quickly switch between 5.0.5 and 6.0-beta15 because I have two VM + two UnRAID keys + two USB drive. This is obviously an issue specific to UnRAID 6.0-beta15 with the Broadcom BCM5751 NIC using tg3 drivers 3.1.37 which come with that version of UnRAID. Any suggestions or workarounds greatly appreciated. Regards, Scott

I tried using this vmdk but I'm unable to get it to work properly. I added my USB drive that has my key but when unRAID 6 boots up it says "No flash (-4)". It looks like the flash is showing up as the virtual disk instead of my USB drive. How did you configure this to work properly with the unraid license key?

I found this link showing how to change the locale to UTF-8 with UnRAID: http://lime-technology.com/forum/index.php?topic=4700.msg112848;topicseen#msg112848 Maybe this will fix my issue?

I have been using Sickbeard and SABnzbd on unRAID 4.7 for a few days now and for the most part its working great. However, I've ran into a problem where the sabToSickBeard.py script is failing because it appears to not be able to handle non-ascii characters. Here is the error I'm getting from sabToSickBeard.py: 500 Internal Server Error The server encountered an unexpected condition which prevented it from fulfilling the request. Traceback (most recent call last): File "/mnt/disk1/.sickbeard/cherrypy/_cprequest.py", line 660, in respond response.body = self.handler() File "/mnt/disk1/.sickbeard/cherrypy/lib/encoding.py", line 193, in __call__ self.body = self.oldhandler(*args, **kwargs) File "/mnt/disk1/.sickbeard/cherrypy/_cpdispatch.py", line 25, in __call__ return self.callable(*self.args, **self.kwargs) File "/mnt/disk1/.sickbeard/sickbeard/webserve.py", line 1371, in processEpisode result = processTV.processDir(dir, nzbName) File "/mnt/disk1/.sickbeard/sickbeard/processTV.py", line 97, in processDir process_result = processor.process() File "/mnt/disk1/.sickbeard/sickbeard/postProcessor.py", line 705, in process ep_obj.createMetaFiles() File "/mnt/disk1/.sickbeard/sickbeard/tv.py", line 1265, in createMetaFiles self.createNFO(force) File "/mnt/disk1/.sickbeard/sickbeard/tv.py", line 1277, in createNFO result = cur_provider.create_episode_metadata(self) or result File "/mnt/disk1/.sickbeard/sickbeard/metadata/generic.py", line 195, in create_episode_metadata return self.write_ep_file(ep_obj) File "/mnt/disk1/.sickbeard/sickbeard/metadata/tivo.py", line 287, in write_ep_file data = self._ep_data(ep_obj) File "/mnt/disk1/.sickbeard/sickbeard/metadata/tivo.py", line 235, in _ep_data data += ("vActor : " + str(actor) + "\n") UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 8: ordinal not in range(128) I did some searching around the internet and found this thread: http://sickbeard.com/forums/viewtopic.php?f=4&t=1102&p=4926&hilit=ascii%27+codec+can%27t+encode+character#p4926 So I tried running some python command to figure out what locale python is using and this is the output I got: Python 2.6.4 (r264:75706, Dec 5 2009, 21:18:28) [GCC 4.3.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import locale >>> locale.setlocale(locale.LC_ALL, '') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.6/locale.py", line 513, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting >>> locale.getpreferredencoding(); 'ANSI_X3.4-1968' From what I've read ANSI_X3.4-1968 can't handle non-ASCII characters. I need to use something like UTF-8 I also found this discussion thread within SABnzbd forum: http://forums.sabnzbd.org/viewtopic.php?t=6912 Where somebody running sabnzbd on unRAID is having a similar issue and somebody made this comment: I'm afraid your Python installation is incomplete or somehow not connected to the language settings of the OS. Possibly the locale package for your OS is missing. On Ubuntu Linux you would do something like this: apt-get install locales-all Does anyone have any suggestions of how I can fix this problem?

Nope, I basically just took it out of the packaging hooked it up. Assigned it as the parity drive. Click the button to start the parity-sync. The error went away and haven't came back and I'm 44% done with the parity sync.

Just a quick update, the parity is at 5.7% and I'm no longer seeing these errors. The errors where coming from the brand new parity drive but stopped. Weird. ;-(

Hello, I'm helping a friend rebuild his UNRAID system and we just put a brand new 2 TB HDD (ST2000DL003) for the parity drive. I just kicked off the parity-sync and its running fine and I see no errors on the Web interface. However in the /var/log/syslog I'm getting the following message every 30 seconds or so: Apr 13 18:24:19 manuel-nas kernel: ata5: irq_stat 0x00400000, PHY RDY changed Apr 13 18:24:19 manuel-nas kernel: ata5: SError: { PHYRdyChg } Apr 13 18:24:19 manuel-nas kernel: ata5: hard resetting link Apr 13 18:24:23 manuel-nas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 13 18:24:23 manuel-nas kernel: ata5.00: configured for UDMA/33 Apr 13 18:24:23 manuel-nas kernel: ata5: EH complete Apr 13 18:24:24 manuel-nas kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen I'm using a total of six SATA ports connected to the onboard controller of the ASUS P5B motherboard. I have it in AHCI mode within the BIOS. The motherboard support up to SATA 3.0 Gb/s. Does anyone have any ideas of what might be causing this? I've also attached the entire syslog for reference. Thanks, Scott syslog.txt

Yes, I'm very familar with this thread. The following command: MegaCli64 -PDMakeJBOD -PhysDrv [0:0] -aAll Doesn't work for the model of RAID card I have. I had to use the command mention above that makes a virtual disk against to one physical disk in raid0 without a mirror. And the card I have will not go into IT-mode it only support IR-mode and I haven't found a firmware which works to switch it to IT-mode. I'm able to access each disk via /dev/sd* using megaraid_sas but Unraid doesn't include this module even in the latest 5.0 beta. So basically I need to find a firmware that will convert it to IT-mode so it will use the mptsas module included with 5.0 beta or create a custom kernel of unraid which includes megaraid_sas or replace this controller with the Supermicro SAS x8 card. Those are pretty much my options as it stands right now.

I have a Dell PERC 6/i Integration Controller which uses the LSI 1078 chipset. I have each disk setup as JBOD using the following command: ./MegaCli -CfgEachDskRaid0 -aAll The issue I'm having is that this card appears to only work with the megaraid_sas module which is loaded automatically with my Knoppix v6.2.1 Live DVD. However, the latest version of unRAID 5.0b6 does not include the megaraid_sas module only the mptsas and mpt2sas modules which do not appears to work with this card. I'm guessing this is because the card is in IR mode and not IT mode. There doesn't appears to be a firmware availability to switch it to IT mode so unless I want to create a custom kernel of UnRAID that includes megaraid_sas I can't uses this controller. I'm curious if anyone else hit this problem and came up with a solution.

Hello, I was under the impression that unRAID plus allows you to have up to 6 drives + a cache drive. However, I'm unable to add the cache drive to my configuration. I'm running unRAID v4.7 I see in the release notes for 5.0 beta that it appears to support this. Maybe 4.7 doesn't support this? Regards, Scott

Thank you so much for your help, and too everyone else that provide advice. The parity-sync is about 20% from complete I'm able to access all my files. It doesn't appears I lost any data which is absolutely amazing considering that my parity drive failed and my FS on disk4 got corrupted (there doesn't appear to be any hardware issue with that HDD too). Once the Parity-Sync is completed successfully I will change this thread to SOLVED in the subject line.

Just to make double sure when I click start it will not erase or format disk1-5, it will just rebuild the parity drive? I don't want to take any chances.

Ok, I successfully recover disk4 and was able to mount and backup all files to another disk. I ran initconfig and answer Yes. It renamed super.dat to super.bak and created a new config. Now all my disks are showing up blue! Shouldn't disk1-disk5 be green and parity be blue? What should I do now, I'm afraid of losing data by starting parity-sync? I've attached a screenshot of what I'm seeing. I have all my data sitting on disk1-disk5 and I can mount them all successfully and they all passed reiserfsk --check.