tucansam

Guys, I am in the middle of reading a ton of forum posts and unraid topics/notes regarding both wake-on-lan and rsync. I have two unraid servers, a primary that runs 24/7 and a smaller system I intend to use for backups. What I would like to do is put the backup server to sleep, and then have it wake up (with a magic packet presumably) when the primary server decides its time to rsync critical files over to the backup. Then, once the backup is complete, I'd like the backup server to go back to sleep. Is this something that should be fairly straight forward? Back to reading I go...

Got this board up and running with 2GB RAM and some older disks.... Runs like a champ and draws 60w during a parity check with six drives, including two older 7200rpm drives that average 36-40 degrees C. Satisfied since this will be a backup server to be used once a week, but I am getting 40-60MB/s during parity checks. Not sure if the lightweight CPU is to blame (load average during parity check is 1.96/1.97/2.04) So far its a great little board and aside from slow disk performance I'm happy. The NIC has dropped a few times, mostly when writing to the machine. I upgraded unraid and copied bzimage and bzroot and the NIC puked, came back on its own after a few minutes but the files didn't copy all the way. I am letting a parity check finish and then I will write some data to it to test. Its running on a powerline ethernet adapter at the moment, which I am liking less and less these days, but I'm waiting on a few small parts to finish the build before I put it in my equipment cabinet on gig ethernet. Hopefully that will fix things.

I am just now learning how to get rsync working. I have a primary server that has several users and user shares based on those usernames. Family's "My Documents" folders from various machines in the house redirect to said user shares. I am planning on setting up my backup server identically in terms of users and shares. My plan is for my primary server to rsync data to the backup server, say weekly. Any failure of the primary would be assumed to be catastrophic enough to require me to change the IP address of the backup server to the primary's, and essentially become a failover server, while I work the issue on the primary. I hope this makes sense the way I wrote it. I'm wondering if this is a solid plan. I'm also wondering if I rsync data as root (or any other user for that matter) either via a cron job or directly from the command line, will permissions be copied? Or will they be inherited? In other words, if "root" runs the rsync command and copies three users' files to the backup server, will root then own those files? Or will users be able to access their data on the backup server without issue? I would actually just like to keep it simply and have one share, called "backup," on my backup server, and dump all user share folders there... But I'm thinking this would end up causing me a lot more work down the road, should I ever have to recover the files, or bring up the backup in place of the primary. Comments and advice welcome. Thanks.

First, I didn't even realize 5.0.2 was so new until I started reading a few posts... I have been running 5.0-rc5 forever on my primary system, and just brought a new system up tonight. I wasn't sure how the upgrade process worked, so I tried it on my new (yet unfilled) server to test. Unraid upgraded fine, but both unmenu and simplefeatures (both installed under the original 5.0-rc5 load that lingered on that particular USB stick from ages ago) are now broken, mostly. I'm sure its too early to expect everything to work with this new version... Are the differences between the two versions so great that stuff will break? Openssl/ssh was installed/ran fine under 5.0-rc5, now broken, and unmenu's package manager shows incorrect version errors when trying to reinstall them. Most other packages are this way. Simplefeatures works, after an initial boot that took almost 15 minutes and included numerous 404 errors on the console. Now, most of the pages give me something like this: Warning: parse_ini_file(/simpleFeatures.system.stats.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 12 (stats page) or this: Warning: file_get_contents(): Unable to find the wrapper "http" - did you forget to enable it when you configured PHP? in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 159 Warning: file_get_contents(http://lime-technology.com/wiki/index.php/UnRAID_Plugins): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 159 Warning: strpos(): Offset not contained in string in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 166 Warning: strpos(): Offset not contained in string in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 170 (plugins page) I'd like to run either/or/both simplefeatures and unmenu on this new system. Should I downgrade to a prior release of unraid? Wait for the authors of unmenu and simplefeatures to release new versions? Or should all work fine and I have screwed something up along the way? As an aside, generally strange behavior is occuring... Like setting a root password, and then not having that change persist beyond a reboot. Or having it persist for a while, and then suddenly root no longer needs a password. Taking it one problem at a time, trying to get unmenu upgraded to see if it upgrades the package versions when I try to install them.... Here's what happens: -- root@ffs2:/boot/unmenu# ./unmenu_install -u Downloading hdparm-9.37-unmenu-package-1.conf rev $Revision: 252 $ $Date: 2012-05-09 08:13:45 -0400 (Wed, 09 May 2012) $ Installed hdparm-9.37-unmenu-package-1.conf Downloading myMain_local.conf rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$ 5a0630afc49c196a23db71a5d02bf18f != a5d02879e3d52eb0dffda20f12d0111c or 7799da8e 46bf08d7a328617cb1a48442, /tmp/unmenu_tmp/myMain_local.conf not installed root@ffs2:/boot/unmenu# -- Also, I just realized this should be in the user customizations forum, so my apologies. Thanks to all.

Awesome. Learn something every day. Thanks.

Not a show stopper but more of a point of curiosity for me. In just shy of 48 hours I will have precleared a 4TB disk. When I started, I was getting 108MB/s. Now I'm at 80MB/s (a few hours ago I was at 96MB/s). Is the slower speed because the heads are running on the very edge of the platters, where they are physically spinning slower?

I know the favorite unraid controllers (LSI/M1505/Supermicro) can be had on ebay from time to time for cheap. I'm not a huge fan of "trying" them in various motherboards until I find one that I can use to flash the right firmware (if necessary) and the guy(s) who sell the "correct for unraid" versions seem to come and go. So I'm looking at an alternative. http://www.amazon.com/IO-Crest-Profile-Bracket-SI-PEX40064/dp/B00AZ9T3OU (appears to be the same at this) http://www.newegg.com/Product/Product.aspx?Item=N82E16816124064 (Don't know if its bad taste to link to a retailer here so I'm leaving it cold) These seem to work with unraid (read reviews). I have three PCI-e slots in my unraid server. I need to be able to address ten additional drives, but plan on adding them over time (right now upgrading my existing drives to 4TB drives is cheaper than buying a new 5-disk cage, controller, etc). I like this four port card because I can add one, and when I have added four more a drives, add another. I can spread the 16 drives (max) in my server across these cards and the MB to maximize performance (not really necessary as its just a simple file server but a nice option to have nonetheless). Plus they're inexpensive... If I find one of the typically-recommended 8-port cards on ebay, for say $100, that's a good deal to be sure, but three of these cards is still cheaper. Or, I can buy two 8-port cards, and move all the drives off my motherboard (would this be better for performance?) So I'm at a crossroads here. Any opinion on the card in the above link? Pros and cons going with a few of these vs one or two of the 8-port variants the community has had so much success with? Thanks.

I have a Conner that was made in the early 90s that still spins up and has no bad sectors. Its 80MB. Makes a noise like my coffee grinder, always has. Have a few Maxtor 254MB drives made shortly thereafter, spin up and work just fine. I have SCSI-1 and SCSI-2 drives that came out of workstations built almost two decades ago, all work fine. Those disks probably spun for 5-8 years straight (Sun and SGI workstations, always on, no such thing as sleep mode back then!) I've had new laptop hard disks that failed inside a year (kids' computers, they like to move around with their laptops while their disks are spinning, against my advice). Guess it all comes down to how you treat them!

None of my member disks were spinning down a few months ago, so I turned off folder caching. I have a huge number of files and folders (several users' "My Documents" are redirected to the server, and mine in particular contains some 25 years of files organized into folder trees to keep me sane). Browsing with windows explorer was so painfully slow. I turned folder caching back on, and my speed is back, but only my parity and cache disks stay spun down.... What are the preferred settings for folder caching? I'd like to maintain my file browsing speed, but having these disks spun up all the time (like when I'm at work and away from my desktop) is a problem. Thanks,

Last checked on Wed Oct 16 22:52:14 2013 MST (today), finding 0 errors. * Duration: 12 hours, 20 minutes, 46 seconds. Average speed: 90.0 MB/sec Hopefully this means I'm good to go? Should I be doing automatic correction parity checks monthly? My system is set up for parity checks on the first of every month -- I don't believe its correcting errors by default.

Parity check with correction complete: Last checked on Tue Oct 15 21:46:19 2013 MST (today), finding 58 errors. * Duration: 12 hours, 18 minutes, 33 seconds. Average speed: 90.3 MB/sec I will now run a parity check without correction and post back.

Will do. Is this something that I should be concerned about, or is this just the cost of doing business? I had errors on the parity drive itself a few weeks ago (red balled and blinking I think) and had started a thread about it, replaced the SATA cable and life was good again. Am I looking at data corruption or are the errors largely a non-issue? Thanks again to all.

Last two. A non-correcting check is running now. I'll check syslog again tomorrow when its done. Thanks again for the help! sde.txt sdf.txt

Syslog is full of thousands of dupe file error messages, talk about the mover running, and spindown commands. Here are the first four disks smart reports sda.txt sdb.txt sdc.txt sdd.txt

From the main status page, I see this: Last checked on Tue Oct 1 13:14:21 2013 MST (thirteen days ago), finding 58 errors. I have never had any errors reported with parity checks before. What does it mean?

Great. Many thanks to all for the help and advice!!!

Cool. So probably a bad/unseated cable after all?

Thanks to all for the replies. I finally got the command to work: root@ffs1:~# /usr/sbin/smartctl -A /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === 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 117 099 006 Pre-fail Always - 155874392 3 Spin_Up_Time 0x0003 092 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 203 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 1813923 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1579 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 10 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 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 068 057 045 Old_age Always - 32 (Min/Max 32/41) 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 100 100 000 Old_age Always - 834 194 Temperature_Celsius 0x0022 032 043 000 Old_age Always - 32 (0 25 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 198539158226121 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 23794604480 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 53856634739 Interesting to see the the "head flying hours" show 22.66 BILLION years. Ha! The self test is still running, but parity check is almost done, so maybe that's why its going so slow. The "short test" has now been running for hours and hours. If its not finished in the morning I'm not sure what I'm going to do. Probably reboot the server and cross my fingers. I don't have twins, and my kids are older. The server sits next to the entertainment center, across from the dog's bed. So any number of things could have bumped the server, although it is unlikely as the kids know better and the dog is lazy and sleeps a lot. Still not exactly sure what happened initially, but assuming parity completes and all looks good, I'll likely watch it for a few days and see what happens. Still will probably order another drive to use as a spare though.

I have no idea if this will mean anything, but here's what I get from the Health -> Disk Attributes tab: Attached to port: sdc ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x000f 117 099 006 Pre-fail Always Never 155874392 3 Spin Up Time 0x0003 092 091 000 Pre-fail Always Never 0 4 Start Stop Count 0x0032 100 100 020 Old age Always Never 203 5 Reallocated Sector Ct 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek Error Rate 0x000f 062 060 030 Pre-fail Always Never 1743018 9 Power On Hours 0x0032 099 099 000 Old age Always Never 1575 10 Spin Retry Count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power Cycle Count 0x0032 100 100 020 Old age Always Never 10 183 Runtime Bad Block 0x0032 100 100 000 Old age Always Never 0 184 End-to-End Error 0x0032 100 100 099 Old age Always Never 0 187 Reported Uncorrect 0x0032 100 100 000 Old age Always Never 0 188 Command Timeout 0x0032 100 100 000 Old age Always Never 0 189 High Fly Writes 0x003a 098 098 000 Old age Always Never 2 190 Airflow Temperature Cel 0x0022 067 057 045 Old age Always Never 33 (Min/Max 33/41) 191 G-Sense Error Rate 0x0032 100 100 000 Old age Always Never 0 192 Power-Off Retract Count 0x0032 100 100 000 Old age Always Never 6 193 Load Cycle Count 0x0032 100 100 000 Old age Always Never 834 194 Temperature Celsius 0x0022 033 043 000 Old age Always Never 33 (0 25 0 0) 197 Current Pending Sector 0x0012 100 100 000 Old age Always Never 0 198 Offline Uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x003e 200 200 000 Old age Always Never 0 240 Head Flying Hours 0x0000 100 253 000 Old age Offline Never 104728482546885 241 Total LBAs Written 0x0000 100 253 000 Old age Offline Never 21661333656 242 Total LBAs Read 0x0000 100 253 000 Old age Offline Never 53856634739 The command you listed to run resulted in "no such device" being returned. Thanks for the followup replies. I may end up with a new disk anyway just to have a spare on hand, this morning's sheer panic feeling tells me I need a spare handy. Hang on, I'll run the short test now. ETA the short test has been at 90% for about 15 minutes.... is that normal?

System didn't move, but its a floor-sitting server, and the kids could have easily bumped it with the vacuum cleaner etc. The old cable was locking -- the new cable is too. I've got a drive cage (iStarUSA) but I believe the drive was seated fine in it. Frankly, when I removed the old cable, both ends were locked up tight. But I had an extra NIB cable laying around so what the heck.

Interesting. I replaced the cable and the system told me "new parity disk found" (my old one) and now a parity check is in progress. Thanks for the help. Hopefully that fixes things and its not a failing disk. syslog showed nothing related to disk errors. Assuming it was just a bad cable (the system has been up for 62 days with this parity drive) -- its interesting how a cable can just go bad. Thanks again.

Looks like my parity disk is disabled: Not sure what is going on. Under health, the parity disk shows it failing a SMART command. Where do I start? This is totally new to me. Thanks.

Thanks so much for taking the time to report back! Sorry it didn't work in the end.

That would be great!!!! Thanks!!!!

I'm usually a huge hater of LEDs and those who like them, so the LEDs will probably get cut off the fans in the end, but the blue glow is sorta... ominous. Disregard the white caulk that I used to fasten the screen to the side of the can, that will be trimmed off. I am just doing test fitting right now while I decide if I am going to do the ASUS C60M1-I or something else. PS is a 300w SPX (is that right?) Gonna get an ethernet punch down port like you'd find in a home outlet plug style and cut a hole in the back of the case next to the power supply so I can run ethernet directly without having to pop the lid. It was also difficult getting an exact measurement for the power supply since the case has rounded corners. Next build I will be either mounting it directly to the longer side wall of the case, or at least measuring a little more precisely so I have room for the plexi drive cage. Having the drives mounted directly to the case isn't a huge deal (and might even help wick away heat) but I am really going for a ten-second-or-less drive swap here, and this sure isn't it. Gotta get some 90 degree SATA and power cables and start testing for length, or build a custom single ribbon power connector that runs all of the drives.