Rebel

Just an insight into how I do it in the house here, we use a common "backup" share but everyone uses crashplan (free for PC to PC use) and then everyone has different archive keys everything is encrypted in such a way only the data owner can see / recover their files. It was simply choice for me though as I run crashplan on unraid anyhow as I carry a sub to backup the unraid servers to their cloud, 10 years+ DSLR photos, vids I've made and just plain work file backup as an offsite.

You also get that sort of behaviour if the key file gets corrupt / missing...

The logs will say why it's failing, sometimes you can get data errors that can flag the disk that the drives own smart doesn't alarm out on. Can you pull the disk and run something like spinrite on it?

Spin up a syslog-ng docker if one exists?

Hi Frank, I scraped it to here for you

Hi Guys, I used to use the unmenu parity check and smtp packages to do checks and email reports on the older versions, I stopped using the unmenu and moved to the schedule checks (first day of the month) when it moved into unraid main (on 6.2 now) last week I got round to doing email notifications in the settings and started to get "Resync Notification - Status: The unRaid array is resync/rebuilding parity." emails every hour even when it's not checking, I then unticked array status email notification but still getting it and have since unticked ALL email and I'm STILL getting erroneous notifications! Any ideas guys? Chris.

I: 2016/02/19 17:31:57 unbalance.go:28: unBALANCE v1.3.4-482.221ac38 starting up ... I: 2016/02/19 17:31:57 unbalance.go:38: No config file exists yet. Using app defaults ... I: 2016/02/19 17:31:57 server.go:45: Starting service Server ... I: 2016/02/19 17:31:57 server.go:62: Serving files from /usr/local/emhttp/plugins/unbalance I: 2016/02/19 17:31:57 server.go:93: Server started listening on :6237 I: 2016/02/19 17:31:57 core.go:76: starting service Core ... F: 2016/02/19 17:31:57 unbalance.go:46: Unable to find unRAID mdcmd (/usr/local/sbin, /root) root@LSpace:/boot/logs#

Hi, I don't get it, it just says stopped.

Hi, Selected enable but it doesn't start? Last few log lines.... Feb 19 00:08:07 LSpace php: /usr/local/emhttp/plugins/unbalance/scripts/start Feb 19 00:08:07 LSpace sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/bin/bash -c /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 Feb 19 00:08:41 LSpace kernel: mdcmd (88): spindown 2 Feb 19 00:13:14 LSpace emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1

Thanks for the reply It was running the monthly parity check (a throwback from unmenu when I was on 4.6, I left it on as I thought it was a good idea) it went to 768 errors and disabled I can't get it to run smart tests on the disk (do I need to stop the array?) and I didn't want to stop the array or do anything more intrusive until I had a clear plan of safe action. I agree actually the safe course of action would be to just get the array safe and worry about the conversion after. I get free next day from scan, their 4T Hitachi offering is this one if you think that's the one to get. https://www.scan.co.uk/products/4tb-hgst-0s03665-deskstar-nas-35-hdd-24x7-use-sata-iii-6gb-s-7200rpm-64mb-cache-8ms-ncq-retail-box

Hi Guys, One of my 3TB WD Red's failed on the monthly scan, I've seen that I can replace it with a 4 (which is my parity disk size) and / or I can flip from the old RFS to XFS but not using the rebuild. I don't have a spare on hand (silly I know) but I can get one next day from scan, so here's my plan please tell me if I am wrong / about to **** things up royally here. Plan: Disk 5 has failed with 2.3TB on it, array has about 4TB spare but no single disk can take all data: Activate the disk 5 SMB share and disk shares on other disks to cover the footprint. Move data from disk5 share (I Assume parity ghost here) to other disk shares Shut array down Take failed disk out of array shut system down Swap failed disk for new 4TB reboot and start without disk 5 preclear disk and format for XFS and introduce disk back into array next week Feedback please? Also should I get WD Red, seagate or HGST 4TB ? EDIT: Am I overthinking this? Should I just go with the replacement and worry about XFS later (conversion has been on my todo list for a while so it's not like it's a super urgent must have thing right no)

Thanks, Can I give you Karma / Thumbs up etc?

Hi guys, I am currently preclearing my first 2 4TB drives, I want to put the (current) 3T parity drive back in a data disk, can I just move it to a worker disk when I put the 4 worker and 4 parity in? Or am I best of putting the 4parity and worker in letting it rebuild parity and then putting it in or do I even need to preclear it? --EDIT: Subject title clarity.

Seems reseating it has brought it back into identification although it's not happy happy about the disk so I am running another 5 preclears on it to see if I can prompt a read / write failure. Thanks guys (this can be marked solved)

It's cable 2 on a supermicro AOC-SAS2LP-MV8 card. I'll get it powered down after 8 tonight and try a reset. The really odd thing was it precleared fine and has been okay right up until the parity check on the 1st Feb (that said it was only put in last month so that was it's first month and fortunatly it's still empty)

Thats not good then

I recently commissioned some WD red 3TB drives, I ran preclear multiple times without issues before inserting into the array. My array does a parity check 1st of the month and this month it disabled one of the new 3T drives with the following error although I don't know if I'm looking at a drive / controller / other issue. This is a brand new drive (Still empty fortunatly) out of set of 5 that's been put in (parity drive + drives 5 - 8 ) disks 1 - 4, parity and cache are onboard sata then I have a supermicro 8 port sata card if that is important Feb 3 00:14:37 LSpace kernel: md: disk6: ATA_OP e0 ioctl error: -5 (Errors) WDC_WD30EFRX-68AX9N0_WD-WMC1T1014384 (sdh) 2930266532 * 3 TB 3 TB 11450152 16 768<<== errors