Seven

Ah, now I see... thanks for the info!

Nice build but I have a question. I checked the specs for the Asus PRIME Z590-A motherboard just now and it seems to only have 6 SATA ports. Just curious how you were able to get 7x WD Reds connected?

Locky ransomware does scan for mapped and unmapped network shares and will attempt to encrypt any media files it finds. That's what made me take a close look at our home network environment to see about hardening security there. More info about Locky ransomware here, for anyone who is interested. My wife works from home and she's always emailing MS Office and other documents with co-workers. So after the ransomware attack at my workplace I decided to take a closer look at the security settings on our home network as well. Anyways, it sounds like the current method is the best option for setting read-only on my unraid shares. I expected as much but just thought I would check in case there was a faster way to toggle read-only on unraid shares. Thanks for the suggestions....

We had a ransomware attack at the office recently (Locky) and I've learned quite a bit from the experience. The smoke has now cleared and I've had time to assess any potential holes on our home network and I've decided it would be prudent to make our unraid shares read-only to help prevent damage to our precious media files in the event of a future ransomware attack. Currently I am running a stock unraid v6.1.9 install (using Windows7 and Windows8 clients) and was wondering if there's a quick way to toggle the read-write / read-only setting for my unraid shares. The idea is to toggle read-only when there are no file/copy transactions occurring, then toggle read-write whenever I need to copy/move/delete files. I'd like to keep the shares read-only the majority of the time and I will change to read-write only when I need to make changes. Currently, the process I am using requires about 5-steps: Navigate to the main unraid main menu, click shares, click the share name, scroll down and change to read-only, click apply. I was wondering if there is a faster way? Thanks for any advice!

NETGEAR 24 Port Gigabit Business-Class Rackmount Switch - Lifetime Warranty http://www.newegg.com/Product/Product.aspx?Item=N82E16833122058 $149.99 With Promo Code: EMCPDPG29 $30 mail in rebate drops final price to: $119.99

I just got one of these at the Fry's in Los Angeles. It was the last one on the shelf... hopefully they'll get more in soon.

Looks like this slow parity check was caused by a failing disk. I replaced the suspected bad disk with another that I had on hand and kicked off a new parity check. Now it's saying parity check will complete in a much more reasonable 321 minutes. I'll be RMA'ing this bad drive and will update this thread once the parity check completes. Thanks everyone for your help!

I'll let it run for a while so I can build a bigger syslog. Today I also noticed a new clicking / knocking sound coming from one of the hard drives but I'm not sure which one it is yet. I wonder if a drive is about to fail.

SMART status report test results attached. smart.txt

I have attached a screenshot showing the disks I have installed. I'm also running some basic SMART checks now and will post the results shortly.

I trying to run my first parity check after building a new unraid 5.5 server and it's saying it will complete in 77,098 minutes (53 days!). It ran for about 1-hour before reaching 0.5% completed. I canceled it and thought I'd better check with the unraid gurus. On my old unraid server this process only took about 10 hours. Wondering if there's something simple I'm missing here or do I have bigger problems? Motherboard is ASUS M5A97 R2. It also has an Intel NIC, model # EXPI9301CT Any advice would be greatly appreciated! syslog.txt

Parity-sync completed without any issues. I will be running a full parity check next and expect that will go well also. Thanks garycase and CrashnBrn for the help...

I added the old parity drive to my new server and parity-sync is underway. Will report back later today once it completes.

Hello, apologies if this was asked before... I couldn't find anything on this when I searched. My question is this: I'm building a new unraid server and plan to use the old 2TB parity drive from my old system as the parity drive in the NEW system. I don't need to migrate or preserve any data from the old system. The new system does currently have 2 unprotected data drives installed and they do contain data that I need to keep. I'm worried if I simply add the parity drive from the old system to this arrangement that I could trash my new array. Do I need to wipe or re-initialize the old parity drive in any way before adding it as the parity drive to the new system? Thanks

@WeeboTech - You are probably right... I'm not sure but maybe the server awakens on power loss and will do a hard shutdown after X amount of time if main power isn't restored by then. I'll have to test this... Thanks very much for your help!

It was scared!!!! Reality is, the APC is probably sending an alert along the USB/Serial interface so the computer can track it. Thus it's causing wake up. Perhaps a setting in the bios to not allow USB to wake the computer. However, if you do that, how will you wake the computer? I tested all possible combinations in the BIOS related to S3 power management behavior but the server still wakes from S3 sleep when APC-UPS battery backup power kicks in. I would like for the server to wake upon receiving the magic packet on the ethernet interface only, not whenever it detects main power loss by the UPS. It seems I'm the only one experiencing this issue so far?

I still haven't found a resolution for this issue. Every time the power hiccups, the server starts up from S3 sleep. Is it possible something related to apcupsd daemon? Does anyone know if there are tunable settings that control how servers behave on power related events?

Here's the syslog file. The first power event starts at 12:04 PM. syslog-2013-09-12.txt

Today we had a strong thunderstorm pass through and we lost power for a few seconds two separate times throughout the day. Each time the power flickered, the APC UPS beeped then the server spun up from its S3 sleep state. The server is attached to an APC BACK UPS battery via USB (serial?) cable. I'm wondering what could have caused the server to awaken from S3 sleep each time the power flickered. Is there some setting that I have set wrong for the UPS? Can it be something else? I'm hoping it's a simple setting that I have wrong somewhere. It's running unraid version 5.0 final. Any input will be appreciated!

1: That folder name is "TV\ Shows", not "TV". 2: The OP solved his problem two years ago. [*]How do you know that? [*]Where does it say the OP solved his problem 2 years ago?

I'm not sure what the OP is trying to accomplish exactly, but I would try changing the rsync command from this: rsync -av --stats --progress /mnt/user/Media/ rsync://192.168.80.99/mnt/user/TV\ Shows/ to this: rsync -av --stats --progress /mnt/user/Media rsync://192.168.80.99/mnt/user/TV

Thanks for the link! I was able to get my 5.0 servers to sleep by manually entering the following at the command prompt: echo -n mem > /sys/power/state They also wake up successfully via network magic packet. Now I'll need to see if I can somehow incorporate the above command into an automated sleep script that puts the server into S3 sleep after X amount of inactivity.

I also just upgraded to 5.0 final and now I'm trying to get the s3 sleep functionality back. It seems /proc/acpi/sleep is no longer included with the latest unraid distro. That's what I was using to sleep my 4.7 servers. I like to put my servers to sleep when not in use to save power and reduce noise. I don't have any answers/solutions yet but I am searching...

Today I successfully upgraded both of my 4.7 servers to 5.0. No issues at all with the upgrade. A couple of oddities that I'm trying to figure out now that I have completed the upgrade: [*] Do I need to run a parity check after upgrading? I just ran a parity check 2 days ago and there were no sync errors found. Curious if I need to run another one immediately after upgrading to 5.0. [*] It seems S3 sleep program /proc/acpi/sleep is no longer present in 5.0. I googled around and found the /proc/acpi/sleep functionality appears to be deprecated but I'm not sure what is replacing it. [*] In Windows Explorer I'm seeing my shares and also shares to each physical disk, i.e., disk1, disk2, disk3, etc. This was not what I was seeing in Explorer on 4.7. Is there a setting somewhere to disable disk shares from displaying in Windows Explorer? If anyone has any info on any of the above items it would be appreciated. Otherwise I'll keep searching.

I haven't upgraded yet (still on 4.7) so some problems may still be reported! I don't expect there to be any problems but you never know.