joeshmoe1

I'm not sure if this is best practice but I'll tell you how mine is set up. Under container volume I have /mnt and under host I have that pointed to /mnt/cache/docker/emby/mnt/ (a folder I made on my cache). Then for my media, I point container volumes to host paths like /mnt/movies (container) to /mnt/user/movies/ (host). I have /config set to /mnt/cache/docker/emby/. Good luck.

Still no luck. Are other folks able to add smb locations in the media library > add media folder section of emby's settings? Since it doesn't work for me there, I'm assuming (maybe incorrectly) that the path substitution setting is also not working. EDIT - NM. DVD's are working on my kodi client now. Not sure what changed but path substitution seems to be functioning. Thanks

I believe you need to run the container with the network option set to host and within emby you need to setup path substitution I've got it set to host and path substitution is what I'm trying to setup. I'm "testing" it by trying to add various paths in the folder section. The network button doesn't find anything and adding smb:\\ or \\IP address doesn't seem to work either.

I've been testing out the Emby docker (thanks for the great work) and have a similar question to one of the other posters. I've set the volume mappings and most things work well but I can't play older dvd vidoe_ts or iso files through kodi. The Emby forum suggests that providing a network path so the files can be played directly would help but I can't seem to get smb to work. Is a network folder something a docker should be able to access? If so what path would I use?

It's only for vmware.

Got it. Thanks.

Should I run a parity-check before replacing it?

One of my disks shows two errors on the main gui but the disk is still green. No errors in the syslog. Got the following result from a smart report. What should I do next. Run parity? Replace the disk then run parity? Thanks for the help. smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: W1F28VTN Firmware Version: CC24 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Nov 23 16:25:34 2013 MST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 584) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 82650208 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 557 5 Reallocated_Sector_Ct 0x0033 093 093 010 Pre-fail Always - 8672 7 Seek_Error_Rate 0x000f 056 056 030 Pre-fail Always - 47249594215 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3517 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 6 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 061 051 045 Old_age Always - 39 (Min/Max 21/44) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 6 193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 4910 194 Temperature_Celsius 0x0022 039 049 000 Old_age Always - 39 (0 21 0 0) 197 Current_Pending_Sector 0x0012 099 099 000 Old_age Always - 320 198 Offline_Uncorrectable 0x0010 099 099 000 Old_age Offline - 320 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 229991203734438 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 16315713208 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 59358290954 SMART Error Log Version: 1 ATA Error Count: 2 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 2 occurred at disk power-on lifetime: 3311 hours (137 days + 23 hours) When the command that caused the error occurred, the device was active or idle . After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 28d+17:43:28.470 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:28.468 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:28.417 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:28.338 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:28.331 READ FPDMA QUEUED Error 1 occurred at disk power-on lifetime: 3311 hours (137 days + 23 hours) When the command that caused the error occurred, the device was active or idle . After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 28d+17:43:13.496 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:13.488 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:13.478 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:13.468 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 28d+17:43:13.458 READ FPDMA QUEUED SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

CEMCWWXP23

That version works.

You can probably just copy to the flash share and reboot. Some folks have had to run make_bootable again. If your using a VDMK then http://lime-technology.com/forum/index.php?topic=26639.msg255826#msg255826. Back up the flash share before you start.

Not sure why I'm posting this other than the fact that for some reason this guy specifically decided to pick on unRAID. http://www.avsforum.com/t/1457880/a-first-look-at-nzfs-and-replacing-unraid-with-nzfs-s-transparent-raid-traid

Thanks Zeron. The tools work great.

Flexraid. Flexraid is a software layer that bolts onto existing operating systems including both Windows and Unix. This is the current main unraid competitor. Flexraid used to be free, but early this year, the Author made a decision to start charging for the software for reasons he has thoroughly explained on his own forum and website. It is still very reasonably priced and similar in costings to unraid. Licencing is not bound to a single USB drive. Flexraid when I looked at it a year or two ago, was in its infancy and was unstable and not polished. The author has changed all this now and a full product is released which looks to be very nice. His forum is buzzing and he constantly replies and updates people from what I can see. He also has a wiki. I haven't looked into it enough recently to know how it compares to unraid, but it is based on the same concept and parity ideas. The Author of flexraid is now looking towards the future and is trying to bring NZFS (Not ZFS) to "compliment" his existing Flexraid products, using some of the exciting features and ideas you may be fimiliar with from ZFS, but in a different way. I probably explained that quite badly and people who know more on Flexraid can please amend any of the above. This is just me trying to give an idea of it. it basically does a similar job to unraid but is not it's own bundled OS....yet....apparently I have read that this may happen. Flexraid is also a one man show that has experienced similar communication issues in the past.

Worked great! Thanks Madburg.

I noticed when I did a trail install of ESXI 5.1 that "32bit FreeBSD" was not one of the operating systems available when creating a VM. What are folks using? Would "other linux 86" work?

If your MB controller shows up as two separate controllers then you could pass a portion of it to a VM but the SIL3132 cannot be used for datastores as far as I know. Also you might be limited to ESXi 4 as according to this post there aren't ESXi drivers for 5 yet. That was back in Jan-Apr time frame so that could have changed but I don't believe ESXi can use a third party driver as a datastore drive. For future reference I tried this on my X8SIL with esxi 5.1. The sil3132 seemed to work fine as a datastore but when I tried to start the vm with the onboard controller passed through everything crashed. It shows up as one six port intel ibex peak. I'm guessing the network card and other components are also dependent on that controller. Now to get a M1015.

Deleted everything from extra and went through the steps above with the same result. If I telnet in and install individually it works perfectly.

I used the files in the zip. I finally just grabbed the tgz files manually and put them in the extra folder. Most things seems to be working OK although there are some icons missing.

It's not working for me. Log says "bad download, deleting". Sep 29 06:00:00 SERVER logger: installing plugin: simpleFeatures.activity.monitor-1.0.5-noarch-1 Sep 29 06:00:00 SERVER logger: file /boot/config/plugins/simpleFeatures/simpleFeatures.activity.monitor-1.0.5-i486-1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.activity.monitor-1.0.5-i486-1.tgz ... bad download, deleting Sep 29 06:00:00 SERVER logger: installing plugin: simpleFeatures.core.webGUI-1.0.5-noarch-1 Sep 29 06:00:00 SERVER logger: file /boot/config/plugins/simpleFeatures/simpleFeatures.core.webGUI-1.0.5-i486-1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.core.webGUI-1.0.5-i486-1.tgz ... bad download, deleting Sep 29 06:00:00 SERVER logger: installing plugin: simpleFeatures.disk.health-1.0.5-noarch-1 Sep 29 06:00:00 SERVER logger: file /boot/config/plugins/simpleFeatures/simpleFeatures.disk.health-1.0.5-i486-1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.disk.health-1.0.5-i486-1.tgz ... bad download, deleting Sep 29 06:00:00 SERVER logger: installing plugin: simpleFeatures.log.viewer-1.0.5-noarch-1 Sep 29 06:00:00 SERVER logger: file /boot/config/plugins/simpleFeatures/simpleFeatures.log.viewer-1.0.5-i486-1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.log.viewer-1.0.5-i486-1.tgz ... bad download, deleting Sep 29 06:00:00 SERVER logger: installing plugin: simpleFeatures.system.info-1.0.5-noarch-1 Sep 29 06:00:00 SERVER logger: file /boot/config/plugins/simpleFeatures/simpleFeatures.system.info-1.0.5-i486-1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.system.info-1.0.5-i486-1.tgz ... bad download, deleting Sep 29 06:00:00 SERVER logger: installing plugin: simpleFeatures.system.stats-1.0.5-noarch-1 Sep 29 06:00:00 SERVER logger: file /boot/config/plugins/simpleFeatures/simpleFeatures.system.stats-1.0.5-i486-1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.system.stats-1.0.5-i486-1.tgz ... bad download, deleting Sep 29 06:00:00 SERVER logger: installing plugin: simpleFeatures.web.server-1.0.5-noarch-1 Sep 29 06:00:00 SERVER logger: file /boot/config/plugins/simpleFeatures/simpleFeatures.web.server-1.0.5-i486-1.tgz: downloading from http://unraid-simplefeatures.googlecode.com/files/simpleFeatures.web.server-1.0.5-i486-1.tgz ... bad download, deleting

For future reference I recently purchased a CyberPower CP825LCD and it seems to work fine with the APCUPSD plugin.

Thanks

Can someone please tell me the difference in these two cards? One is part number 46M0861 and the other is 46M0831. Obviously I'd prefer to buy the cheaper one if they're comparable. http://www.compuvest.com/Desc.jsp?iid=1637642 http://www.compuvest.com/Desc.jsp?iid=1559372 Thanks

I'm happy to update the wiki but I think my hardware is fairly common and the issue doesn't seem widespread. I've sent Tom a pm so I'm hoping he can provide some input.

Parity - Western Digital Caviar Green 2TB Disk 1 - WDC WD20EARX 2TB Disk 2 - Hitachi 2TB Disk 3 - SAMSUNG SpinPoint F2 EG series 1.5TB Disk 4 - Western Digital Caviar Green 1TB Cache - Seagate Barracuda 7200.11 1TB I'm running reiserfsck --check on them now since I can't think of anything else to try. So far everything looks good.