aim60

For experimentation, I'm running two Plex dockers (one LinuxServer and one Binhex), using different appdata folders. Since you can't change the port that Plex listens on (38400), I needed to assign a different IP address to one of the dockers. So the Binhex docker is running on Custom:br0, and a fixed IP address. br0 is a Linux bridge, not a Docker bridge, so port mappings are not required. Its like Host mode. I'm still on 6.6.7, but that shouldn't matter.

I believe that within unraid you can only use vlans for dockers and vms. See if you can configure your switchport to send vlan 10 traffic as untagged, while sending the other vlans as tagged.

Make sure all shares are set to COW. Any problem converting the system share containing the docker and libvirt images to COW?

I'm planning on adding a new SSD to my cache pool, and was wondering if and how Unraid users test new SSDs. I give spinners a SMART long test, and 3 Preclear passes.

While testing the "Virtual Machine Wake On Lan" plugin, I discovered that I had two VMs using the same MAC address (sloppy editing of the XML's). It would be useful if Fix Common Problems could scan the docker configs and VM configs for duplicate MACs, and the docker configs for duplicate IP's.

Hi Thanks for the great work. Could you please add md5deep. Compiled version here: http://packages.slackonly.com/pub/packages/14.2-x86_64/system/md5deep/md5deep-4.4-x86_64-2_slonly.txz Thanks

Request: Please implement Safe Powerdown so it can be activated from the console/telnet session. Reason: For the past several years I have been using only Cyberpower PFC UPS's. They are the reasonably affordable and designed for PFC power supplies. Unfortunately, they don't work correctly with APCUPSD when "Power Down UPS After Shutdown" is set to yes. I would like the ability to run Cyberpower's UPS software in a Docker container or VM, and have it initiate a power down via a scripted telnet session to UnRAID. Thinking ahead. Still on UnRAID 5.

+1 Feature Request - The option for Automatically Created (the way it works now) or Manually Created Only user shares Would rather not have to start directory names with a "." to have unRaid ignore them. Why not put those directories on a disk that is excluded from user shares? I keep the contents of each disk categorized by function. Its not a big deal either way, but the sysadmin in me would like to have the choice. Been wanting to throw this one out there for years. Just chimed in now because I discovered that I'm not the only one who would like this. Tom, there are many other things with higher priority. I'm just requesting that you keep this on your list of things to consider for a rainy day when you have nothing else to do.

+1 Feature Request - The option for Automatically Created (the way it works now) or Manually Created Only user shares Would rather not have to start directory names with a "." to have unRaid ignore them. Why not put those directories on a disk that is excluded from user shares? I keep the contents of each disk categorized by function. Its not a big deal either way, but the sysadmin in me would like to have the choice.

+1 Feature Request - The option for Automatically Created (the way it works now) or Manually Created Only user shares Would rather not have to start directory names with a "." to have unRaid ignore them.

dgaschk One disk has 4 pending sectors, but they're the same 4 that have been there for years. And the parity check (with all new cables) shows no hardware errors. garycase I will definitely look into check-summing the files. A backup server is also worth thinking about, as is segregating the really important files so a copy can be taken off-site. I've also been slowly coming to the conclusion that the only way forward is to do a correcting parity check. And I've realized that 3000 blocks with errors is only about 3MB of data, so damage may be minimal. Thanks guys for the input.

As a result of Black Friday purchases, I’ve been upgrading disks, and retiring the oldest ones. I’ve had a few disk problems in the last 9 months, which turned out to be sata cable related. My plan was to disturb things as little as possible, do all of the disk upgrades, and when things were stable replace all of the sata cables. Bad decision. I replaced disk6, a ST31500341AS 1.5TB, with a 2TB WDC_WD20EARX-00PASB0, and initiated a rebuild. The result was many disk read errors on disk2. I canceled the rebuild. From the errors in the syslog I concluded that all of the errors were related to the sata cables. I replaced all of the older sata cables. While I was in the case, I also noticed that the power connector to disk2 was not fully seated, and fixed it. Before continuing, I successfully ran smartctl short disk tests on all disks. I re-initiated the rebuild on disk6. This time the result was many read errors on disk5, and unraid marked disk5 as missing. The syslog again indicated to me that the errors were cable/power related. Disk5 still had one of the older sata cables, and in hindsight, it was on the loose side. So I replaced the remaining sata cables in the system. At this point, I needed to establish confidence in the hardware. I re-installed the original disk6, and replaced super.dat with the one from before the first disk6 replacement. The array was set to not auto-start, and I powered up the hardware. I successfully read over 1GB from each disk with dd if=/dev/sdx of=/dev/null bs=65536 count=20000, then initiated a nocorrect parity check. The hardware seems stable. The results of the parity check were: 49 sync errors within 1 second (housekeeping area?) 1 sync error sometime later 3000+ sync errors after sector 2930245632 If my calculations are correct, the 3000+ errors all occurred within 16GB of the end of a 1.5TB drive (disk6). An fdisk of disk6 is attached. My Question - Since the parity disk reflects the rebuild of a 1.5TB disk6 onto a 2.0TB disk6, might the 3000+ errors all reflect the reiserfs housekeeping of increasing the size of the disk? Or do I have corrupted data? In other words, can I run a correcting parity check and be reasonably confident that I have no data corruption? I have no backups and would l like as much as possible to avoid further corruption. Any suggestions on how to proceed would be greatly appreciated. I’m thinking that once things are stable, I’ll run a reiserfsck on all of the data drives. An observation – anyone running a server without removable drive bays, that does a fair amount of moving/replacing drives, should strongly consider replacing their sata cables regularly. The ones I just installed are Monoprice sata3 cables, and they seem more secure than any other cables I’ve used. 5.0.2RC1, C2SEE, Celeron 1400, 4GB, Corsair VX450, (1) SIL3132 PCIx SATA controller, Intel PCI NIC, 7 drives in total. Syslogs_etc.zip

Same price on Amazon. http://www.amazon.com/Seagate-SATA-Cache-Drive-ST4000VN000/dp/B00D1GYO4S/ref=sr_1_1?ie=UTF8&qid=1385609553&sr=8-1&keywords=4tb+nas+hard+drive

For the people who can resolve the by host name when the server is using dhcp, but not with it is static, this is expected behavior. Your router is able to resolve the host name as long as the dhcp lease is active. The following works for me using a DD-WRT router, but it may not work for everybody: See if your router will allow you to assign a static DHCP address. That's enough for DD-WRT to permanently resolve the host name. Since you now know what IP would always be assigned to your nic by dhcp, you can go ahead and assign the address statically.

TRENDnet TEG-S82g Unmanaged 10/100/1000Mbps 8-Port Gigabit GREENnet Switch $19.99 after promo code EMCYTZT4089, Ends 8/20 11:59PM PT http://www.newegg.com/Product/Product.aspx?Item=33-156-448&nm_mc=EMC-GD082813&cm_mmc=EMC-GD082813-_-index-_-Item-_-33-156-448&

Hi Joe, found a quirk. Running unRaid 5.0-rc16c and preclear 1.13. In the unRaid disk settings, set Enable Auto Start to No, then reboot. Run preclear_disks.sh -l. All disks, whether assigned to the array or not, are listed as available for clearing. Start the array. Only the correct disks are listed for clearing. Stop the array. The correct disks are still listed.

If you are planning on using the APCUPSD plugin with a CyberPower, read this. http://lime-technology.com/forum/index.php?topic=13411.msg127182#msg127182 The plugin shuts down unraid without a problem. Suggest setting "Power Down UPS after shutdown" to NO, and dedicating the UPS to unraid. On my CP1500PFCLCD, if you set it to YES, the UPS doesn't shutdown when you would expect it to. At power fail, it sets an internal 60 minute timer, and shuts down the UPS when the timer expires. And the timer doesn't reset if utility power is restored! If you power up the server before it expires, be prepared for an unexpected server crash. A manual power cycle of the UPS will clear the timer. There's an alternative to APCUPSD that seems to have Cyberpower compatibility. No idea what it would take to get it running under unraid. http://www.networkupstools.org

Another syslog server program worth trying http://www.kiwisyslog.com/free-edition.aspx

I had the same problem with preclear , cach_dirs, and drives spinning up. Most of my storage is large video recordings, with one share containing many small files. I excluded the share with the small files from cache_dirs, and it fixed the problem.

Thanks

But the real question is: If you have a flash drive with a fully functional 4.7, labeled UNRAID, license key, disks configured, shares set up, etc. And a flash with a fully functional 5.x,labeled UNRAID, license key, disks configured, shares set up, etc. Can you shutdown a server under one OS, pull the flash, copy super.dat to the other flash, insert the other flash, and bring up the server under the other OS. The goal is that both OS's are happy, no irregularities, and no rebuilding of the raid drive required under either OS. Is the super.dat file the only thing that needs to change when switching flash drives? I would like to be able to switch back and forth several times before committing to 5.x, with minimal impact.

Got 2 keys when I bought my license.

Still running 4.7. I'd like to start building a 5.0 environment on a separate flash drive, and have the ability to go back and forth between releases. Is copying super.dat when switching flash drives all that's necessary? I seem to remember that Tom said that it wasn’t a problem going back to 4.7 after newperms has been run.

Rob Thanks for the great feedback. Just for the record, I've included the previous syslog. A power outage from Hurricane Sandy forced the server down after 9 months. Other than a few media errors and a sporatic "frozen" error from the unresolved Barracuda 7200.11 firmware issues, nothing noteworthy. UnRaid 4.7 has been so incredibly stable that I haven't wanted to upgrade. The price I paid was having to purchase another small (2TB) drive, and not having the luxury to wait for a good sale. I'm looking forward to an equally stable 5.0 release. Syslog_2012-10-29.zip

It's in the zip file