Tyler

Here's my config (with a few things redacted, and IPv6 stuff removed / disabled to make it a bit simpler). I've had it running for quite a while now, so it's far from a fresh install. If you haven't already, I'd recommend reading the config guide on Docker Hub: https://hub.docker.com/r/pihole/pihole Particularly the Important Upgrade Notes and Environment Variables sections, as they explain in more detail the various "DNS" entries. Repository: pihole/pihole:latest Docker Hub URL: https://hub.docker.com/r/pihole/pihole Icon URL: https://i.imgur.com/OWkNcEn.png WebUI: http://[IP]:[PORT:80]/admin Extra Parameters: --cap-add=NET_ADMIN --dns 127.0.0.1 --dns 1.1.1.1 Network Type: 'Custom: br0' Fixed IP address (optional): 10.1.1.100 Privileged: Off Variables ('Key'='Value') 'ServerIP'='10.1.1.100' 'WEBPASSWORD'='my password' 'DNS1'='1.1.1.1' 'DNS2'='1.0.0.1' 'IPv6'='False' 'INTERFACE'='eth0' 'DNSMASQ_LISTENING'='all' Ports (host port : connection type) 53 : TCP 53 : UDP 80 : TCP Paths ('container path' : 'host path' : 'access mode') '/etc/pihole/' : '/mnt/cache/appdata/pihole/pihole/' : 'Read/Write' '/etc/dnsmasq.d/': '/mnt/cache/appdata/pihole/dnsmasq.d/' : 'Read/Write'

Might be worth trying to change the “LAN Networks” setting in Plex under Network (enable advanced settings). They’re entered in the format: 127.0.0.1,192.168.1.0/255.255.255.0 More details here: https://support.plex.tv/articles/200430283-network/

I noticed something that could be the cause of your issue, in the Docker run command you posted in your GitHub issue that you've set the variable: 'INTERFACE'='br0' I believe this variable needs to refer to the name of the container's internal interface which is 'eth0', rather than the name of UnRaid network interface the container is running on which in your case is 'br0' @bonienl posted instructions a few pages back on how to re-configure this If you haven't tried this already it might be worth giving this a shot

Try mapping the /config path to a cache or disk share, rather than the user share. Will depend on where your “appdata” is stored, e.g. /mnt/cache/appdata/plex or /mnt/disk1/appdata/plex See this post for some details why:

I had the same issue with nothing in the Query Log or data in the graphs. diginc posted a fix in an issue raised for this on GitHub, and it worked for me. Although the only step I had to do was edit the config file /dnsmasq.d/01-pihole.conf and change the line from "log-queries" to "log-queries=extra", then restart the container.

Have a look at this help article: https://support.plex.tv/hc/en-us/articles/201370363-Move-an-Install-to-Another-System I’ve used this method successfully to move my library around in the past. The first step to disable the emptying of trash is important, but sounds like this may already be too late unless you’ve got a backup of the appdata from your Win10 system.

Thanks @CHBMB and @sparklyballs! Now working for me with the fping IPV4 only build. You've gone above and beyond to get this working with v6.3

Thanks for the replies guys. Yes and with multiple browsers (Firefox, Safari, Chrome), still nothing on the graphs. Me too, only using IPV4. Running unRAID 6.3.5

Thanks. I should have checked the scripts to make sure I was running the correct command. When running this with the --debug option I still see the same error with fping. FPing: Got fping output: '(null): can't create raw socket (must run as root?) : Address family not supported by protocol' Also tried running the same fping command directly and also same result. Can someone who has everything working try running fping to see if they get this same error? root@c381ec688e22:/$ s6-setuidgid abc /usr/bin/smokeping --config="/etc/smokeping/config" --nodaemon --debug ### assuming you are using an fping copy reporting in milliseconds ### Compiling alert detector pattern 'someloss' ### >0%,*12*,>0%,*12*,>0% my $d = shift; sub { my $y = $d->{loss}; for(1){ my $imax2 = min(@$y - 3, 12); my $imax1 = min(@$y - 3, 12); my $minlength = 3; my $maxlength = 27; next if scalar @$y < $minlength ; my $i1; for($i1=0; $i1 < min($maxlength,$imax1); $i1++){ my $i2; for($i2=0; $i2 < min($maxlength-$i1,$imax2); $i2++){ next unless defined $y->[-3-$i1-$i2] and $y->[-3-$i1-$i2] =~ /^\d/ and $y->[-3-$i1-$i2] > 0 ; last; } return 0 if $i2 >= min($maxlength-$i1-$i2,$imax2); next unless defined $y->[-2-$i1] and $y->[-2-$i1] =~ /^\d/ and $y->[-2-$i1] > 0 ; last; } return 0 if $i1 >= min($maxlength-$i1,$imax1); next unless defined $y->[-1] and $y->[-1] =~ /^\d/ and $y->[-1] > 0 ; return 1; } return 0; } Smokeping version 2.006011 successfully launched. Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that. FPing: probing 20 targets with step 300 s and offset 294 s. FPing: Executing /usr/sbin/fping -C 20 -q -B1 -r1 -i10 cam.ac.uk facebook.com web.mit.edu linuxserver.io 208.67.220.220 al.ktz.me www.ucsd.edu 208.67.222.222 www.berkley.edu 8.8.4.4 google.com www.telefonica.de jupiterbroadcasting.com youtube.com www.indiana.edu www.uea.ac.uk 8.8.8.8 cixp.web.cern.ch FPing: Got fping output: '(null): can't create raw socket (must run as root?) : Address family not supported by protocol' Calling RRDs::update(/data/DNS/OpenDNS2.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/DNS/GoogleDNS2.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/DNS/OpenDNS1.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/DNS/GoogleDNS1.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/Europe/UK/UEA.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/Europe/UK/CambridgeUni.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/Europe/UK/IBNorwich.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/Europe/Germany/TelefonicaDE.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/Europe/Switzerland/CernIXP.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/Europe/Switzerland/SBB.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/InternetSites/JupiterBroadcasting.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/InternetSites/GoogleSearch.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/InternetSites/Facebook.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/InternetSites/Youtube.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/InternetSites/linuxserverio.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/USA/MIT.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/USA/UCSD.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/USA/IU.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/USA/Sun.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/USA/UCB.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500804998:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) root@c381ec688e22:/$ s6-setuidgid abc /usr/sbin/fping -C 20 -q -B1 -r1 -i10 cam.ac.uk facebook.com web.mit.edu linuxserver.io 208.67.220.220 al.ktz.me www.ucsd.edu 208.67.222.222 www.berkley.edu 8.8.4.4 google.com www.telefonica.de jupiterbroadcasting.com youtube.com www.indiana.edu www.uea.ac.uk 8.8.8.8 cixp.web.cern.ch (null): can't create raw socket (must run as root?) : Address family not supported by protocol

Hi all, I'm trying to use this docker app too, but can't seem to get it working. I use a bunch of other Linuxserver.io containers without any issues (thanks guys!). Here's my docker run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="smokeping" --net="bridge" -e TZ="Australia/Sydney" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8050:80/tcp -v "/mnt/cache/appdata/smokeping/data":"/data":rw -v "/mnt/cache/appdata/smokeping/config":"/config":rw linuxserver/smokeping In my unRAID network config I have bonding and bridging both disabled, I tried enabling bridging without any difference. I've tried to do some troubleshooting and I think @ziggie216 was onto something with this. How I arrived at this was checking the in-built Smokeping troubleshooting from within the Smokeping docker's shell. There does seems to be an inconsequential issue with the basic Smokeping troubleshooting saying the config file can't be found. But the config is definitely being picked-up because I can see all the (empty) graphs for each of the targets configured by the docker container. root@212bb2c07243:/$ smokeping --check ERROR: can't open /usr/bin/../etc/smokeping/config: No such file or directory root@212bb2c07243:/$ smokeping --debug ERROR: loading smokeping configuration file /usr/bin/../etc/smokeping/config: No such file or directory Running the Smokeping debug command against the actual config file gives this result: root@212bb2c07243:/$ smokeping --config /etc/smokeping/config --debug ### assuming you are using an fping copy reporting in milliseconds ### Compiling alert detector pattern 'someloss' ### >0%,*12*,>0%,*12*,>0% sub { my $d = shift; my $y = $d->{loss}; for(1){ my $imax2 = min(@$y - 3, 12); my $imax1 = min(@$y - 3, 12); my $minlength = 3; my $maxlength = 27; next if scalar @$y < $minlength ; my $i1; for($i1=0; $i1 < min($maxlength,$imax1); $i1++){ my $i2; for($i2=0; $i2 < min($maxlength-$i1,$imax2); $i2++){ next unless defined $y->[-3-$i1-$i2] and $y->[-3-$i1-$i2] =~ /^\d/ and $y->[-3-$i1-$i2] > 0 ; last; } return 0 if $i2 >= min($maxlength-$i1-$i2,$imax2); next unless defined $y->[-2-$i1] and $y->[-2-$i1] =~ /^\d/ and $y->[-2-$i1] > 0 ; last; } return 0 if $i1 >= min($maxlength-$i1,$imax1); next unless defined $y->[-1] and $y->[-1] =~ /^\d/ and $y->[-1] > 0 ; return 1; } return 0; } Smokeping version 2.006011 successfully launched. Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that. FPing: probing 20 targets with step 300 s and offset 212 s. FPing: Executing /usr/sbin/fping -C 20 -q -B1 -r1 -i10 www.uea.ac.uk www.ucsd.edu 208.67.220.220 8.8.4.4 google.com web.mit.edu youtube.com 8.8.8.8 www.telefonica.de www.indiana.edu www.berkley.edu 208.67.222.222 jupiterbroadcasting.com al.ktz.me cam.ac.uk facebook.com linuxserver.io cixp.web.cern.ch FPing: Got fping output: '(null): can't create raw socket (must run as root?) : Address family not supported by protocol' Calling RRDs::update(/data/USA/IU.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500781590:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/USA/UCSD.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500781590:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) Calling RRDs::update(/data/USA/UCB.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1500781590:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U) ... continues for each target (site/IP) ... If I try to run "fping" from within the docker's shell I get: root@212bb2c07243:/$ /usr/sbin/fping 8.8.8.8 (null): can't create raw socket (must run as root?) : Address family not supported by protocol So from what I can see "fping" doesn't run due to come sort of permission error, and possibly why no data is getting into the Smokeping RRD files / graphs. Searching for a solution only really turns up results relating to user/file permissions of "fping". So I tried messing with various file permissions and ownership with no result. Does anyone have any ideas or suggestions? Thanks!

No problem, glad it helped. Just a suggestion for the Home Assistant config, you probably want to enable the configuration option for "use_x_forwarded_for" so the client's IP address is passed to Home Assistant rather than the IP of the Nginx docker. This also allows you to use the IP Ban options. More details on the Home Assistant HTTP config page: https://home-assistant.io/components/http/ Here's a sample config for Home Assistant: http: api_password: MyPassWord base_url: SUB.MYDOMAIN.com:8123 use_x_forwarded_for: True ip_ban_enabled: True login_attempts_threshold: 5 And on the Nginx config side you've already got the relevant Proxy setting enabled: server { ... location / { ... proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; ... } } That being said, if you're security conscious you're likely far better off managing things at the Nginx layer. And it's great that this docker already has Fail2ban built in.

Hi ritalin I have this Letsencrypt / Nginx docker, and the Home Assistant docker setup working. Just wanted to check if you've had a read of the Home Assistant team's guide for setting up Nginx: https://home-assistant.io/ecosystem/nginx/ Specifically their sample config in step 8 (looks like you've already done the rest). This is what I based my config on, and having a quick look over your config it seems to be missing a few settings/parameters. I'm by no means an expert with Nginx or docker, but if you're still having issues I can post a copy of my configs.

The updated Plex container is working well for me. Grabbing the current Plex Pass version (0.9.16.4) using "VERSION=latest". Thanks lonix and to all the Linuxserver.io team for your great work!

I've swapped the the stock fans in my Norco SS-500 for non-PWM Noctua NF-R8 fans. I run them at full speed, so don't use the included fan speed controllers. Take a look at this review, gives a really good run-down of the cages and the process for swapping the fan. http://greenleaf-technology.com/new-norco-ss-500-5-in-3-drive-cage-review/

Thanks for the reply. That makes sense. I probably should have read up on what the script actually does in detail. Just to give things more of a test, I ran a 2nd preclear on the same 1TB WD Black disk, and it went significantly faster the 2nd time: 11:43 vs 24:16 The only thing I did between the 2 runs was power down the box for about an hour to re-route some cabling and install a few new fans. I've now precleared a total of 5 disks, and this was the only run that was slow. Fingers crossed this was just one of those weird occurrences.

Hi guys I'm new to unRAID, so setting things up for the first time (running v5 RC11), and running my first lot of pre-clears. I'm currently pre-clearing 4 drives: new 1TB WD Black (WD1002FAEX), connected to MB SATA3 port - I plan to use this as a cache drive new 3TB WD Red (WD30EFRX), connected to M1015 new 3TB WD Green (WD30EZRX), connected to M1015 old 1.5TB WD Green (WD15EADS), connected to M1015 - I started the 1.5TB drive about 12 hours after the other 3 All the pre-clears are still in progress, and everything seemed to be going ok. As expected the 1TB Black was well ahead of the other 2 to begin with, but it now seems to have slowed down massively on the post-read phase. I've got email notifications going, so here are the snippets from them: Pre Read finished on /dev/sda ( 1,000,194,048,000 of 1,000,204,886,016 bytes read) Pre Read Elapsed Time: 3:05:54 Total Elapsed Time: 3:05:55 Disk Temperature: 37C, Using Block size of 8,225,280 Bytes Calculated Read Speed - 89 MB/s Zeroing Disk /dev/sda Done. Zeroing Elapsed Time: 8:28:02 Total Elapsed Time: 11:33:57 Disk Temperature: 33C, Calculated Write Speed: 32 MB/s Post Read in progress on /dev/sda: 25% complete. ( 251,693,568,000 of 1,000,204,886,016 bytes read )at 27.3 MB/s Disk Temperature: 36C, Using Block size of 8,225,280 Bytes Next report at 50% Calculated Read Speed: 18 MB/s Elapsed Time of current cycle: 3:41:28 Total Elapsed time: 15:16:25 And here's a current snapshot of the SMART status: === START OF INFORMATION SECTION === Device Model: WDC WD1002FAEX-00Z3A0 Serial Number: WD-WCATRA787309 Firmware Version: 05.01D05 User Capacity: 1,000,204,886,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Mar 12 11:44:38 2013 EST 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. 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: (16260) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 189) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 183 179 021 Pre-fail Always - 3841 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 14 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 18 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 6 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 7 194 Temperature_Celsius 0x0022 110 107 000 Old_age Always - 37 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged 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. For comparison these are the email snippets for the progress the 3TB Red: Pre Read finished on /dev/sdc ( 3,000,582,144,000 of 3,000,592,982,016 bytes read) Pre Read Elapsed Time: 7:55:51 Total Elapsed Time: 7:55:51 Disk Temperature: 31C, Using Block size of 8,225,280 Bytes Calculated Read Speed - 105 MB/s Zeroing Disk /dev/sdc Done. Zeroing Elapsed Time: 7:17:05 Total Elapsed Time: 15:12:56 Disk Temperature: 36C, Calculated Write Speed: 114 MB/s It's now 6% into its post-read phase and running at ~65MB/s. So it'll likely finish at about the same time as the 1TB disk. The only obvious difference between this drive and the others is that it's connected to a SATA port on the MB, the others are connected to an M1015. But the pre-read speeds and zeroing for the drive were fine, and nothing else has changed. I had a search in the forums for issues with post-read and couldn't find anything. Has anyone got any ideas what cause this? Or is it something I shouldn't be concerned about.

A big thanks to madburg for the method to do this. I successfully flashed my M1015 to SAS2008 P11 IT mode. Not sure if people are still doing this, but I've attached SBR file for reference. I'm using an ASRock Z77 Extreme4-M motherboard that has EFI, so I had to use a slightly different method for steps 5 & 6, details in this thread. Thanks goes to newbie_dude! I also upgraded my card from P11 to P15 as described in this post. Thanks goes to binhex! SBRM1015.BIN.zip