page3

noob questions I'm afraid, but I'm going round in circles. I'm trying to set up a facility to backup various directories in my array to an external HDD. I've been recommended crashplan. Installed the community crashplan docker and crashplan desktop docker and configured as per page one of this thread. crashplan log: *** Running /etc/my_init.d/config.sh... Current default time zone: 'Europe/London' Local time is now: Mon Jul 20 17:28:07 BST 2015. Universal Time is now: Mon Jul 20 16:28:07 UTC 2015. *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 64 Desktop log: *** Running /etc/my_init.d/config.sh... Current default time zone: 'Europe/London' Local time is now: Mon Jul 20 17:40:06 BST 2015. Universal Time is now: Mon Jul 20 16:40:06 UTC 2015. cp: cannot stat ‘/root/wallpapers/*’: No such file or directory Err, what do I do now? I don't seem to have any GUI. I was expecting a web-based GUI but reading between the lines I need to remote desktop to port 4243 on my server. Tried VLC on my Mac, but no go. I don't have a Windows box. Am I on the right track? Documentation for crash plan is unfortunately all over the place and quite obscure unless you know exactly what to ask! Help appreciated TO UPDATE: Installed Microsoft Remote Desktop on my Mac and seem to be able to log in. Now to give it a go. Leaving this post here because it just might help other noobs!

Thanks for the very useful post. I'm also running plex as a plugin (as I've only just upgraded from 5 to 6) so this information is very welcome.

Just a quick update to say I purchased a licence and upgraded without any issues. Only took a half hour or so Now to experiment with XFS / Dockers etc etc...

Thank you. Former sounds like the best plan.

Hi all, Done a search but cannot find an answer, but please excuse me if I've missed it somewhere. I'm current running version 5 and am finally going to upgrade to 6. Currently I am using the free version as my modest microserver only has four drives. To upgrade to version 6 'basic' do I upgrade first, then purchase the key or is there a preferred method? Obviously, I don't want to lose access to any of my data due to being unregistered. Thanks.

Thanks - useful info. At current Gen8 prices I think this is the way to go over a self-build.

I agree. A RSync GUI would be a great addition to Unraid. The easier it is to backup, the more lightly it is that people will.

Hi all, I've been running a small unRAID server on a HP Microserver Gen 7. Very happy with it and unRAID, but am looking for improved performance and am tempted by the current offers on a Gen 8 Microserver. Is anyone running a Gen 8, preferably with v.6 (using v.5 on my gen 7, but thinking of taking the opportunity to upgrade). Simply requirements - NAS plus Plex mainly. Found a few threads via search, but nothing recent.

That worked great, thanks.

I have this too. Plex plugin (1.5.2) will not update Plex to the latest version. Installed Version: 0.9.10.1.585-f31034e? Update to Version: 0.9.11.0.672-bf09ab7? When I click update it goes through the motions, but remains on 0.9.10.

Smart report looks good. So OFF-TOPIC: How did you produce that smart report? I have never seen one that gives percentages. External USB3 caddy and DriveDX tool on my Mac. (http://binaryfruit.com/drivedx). Thanks for the time, once again. I'll run with the new drive and see what happens. At the very least it should help me diagnose drive or other hardware issue.

Hi My drive array is full so it has taken me a few days to get time to produce this for you - apologies. SMART report attached. smart_report_WD_Green.txt

Syslog as requested. Thanks. syslog.zip

First time using the drive in anger today, and it red balled again. This time I have the following in the log: Oct 5 15:03:23 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:03:23 Tower afpd[3336]: enumerate(vid:5, did:103554, name:'.'): error adding dir: 's8M2dLV+RKC2BT0GHDVXgA' Oct 5 15:03:52 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:03:52 Tower afpd[3336]: cname(did:103499, name:'20061224-185040', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:03:57 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 5 15:03:57 Tower kernel: ata2.00: failed command: FLUSH CACHE EXT Oct 5 15:03:57 Tower kernel: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Oct 5 15:03:57 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 5 15:03:57 Tower kernel: ata2.00: status: { DRDY } Oct 5 15:03:57 Tower kernel: ata2: hard resetting link Oct 5 15:04:07 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:04:07 Tower kernel: ata2: hard resetting link Oct 5 15:04:17 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:04:17 Tower kernel: ata2: hard resetting link Oct 5 15:04:20 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:04:20 Tower afpd[3336]: cname(did:103499, name:'20061224-185040', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:04:47 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:04:47 Tower afpd[3336]: cname(did:103499, name:'20061224-185051', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:04:52 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:04:52 Tower kernel: ata2: limiting SATA link speed to 1.5 Gbps Oct 5 15:04:52 Tower kernel: ata2: hard resetting link Oct 5 15:04:57 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 5 15:04:57 Tower kernel: ata2.00: link online but device misclassified Oct 5 15:05:02 Tower kernel: ata2.00: qc timeout (cmd 0xec) Oct 5 15:05:02 Tower kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 5 15:05:02 Tower kernel: ata2.00: revalidation failed (errno=-5) Oct 5 15:05:02 Tower kernel: ata2: hard resetting link Oct 5 15:05:12 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:05:12 Tower kernel: ata2: hard resetting link Oct 5 15:05:16 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:05:16 Tower afpd[3336]: cname(did:103499, name:'20061224-185051', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:05:22 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:05:22 Tower kernel: ata2: hard resetting link Oct 5 15:05:44 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:05:44 Tower afpd[3336]: cname(did:103499, name:'20061224-185055', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:05:57 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:05:57 Tower kernel: ata2: hard resetting link Oct 5 15:06:02 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 5 15:06:02 Tower kernel: ata2.00: link online but device misclassified Oct 5 15:06:11 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:06:11 Tower afpd[3336]: cname(did:103499, name:'20061224-185055', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:06:12 Tower kernel: ata2.00: qc timeout (cmd 0xec) Oct 5 15:06:12 Tower kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 5 15:06:12 Tower kernel: ata2.00: revalidation failed (errno=-5) Oct 5 15:06:12 Tower kernel: ata2: hard resetting link Oct 5 15:06:22 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:06:22 Tower kernel: ata2: hard resetting link Oct 5 15:06:32 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:06:32 Tower kernel: ata2: hard resetting link Oct 5 15:06:39 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:06:39 Tower afpd[3336]: cname(did:103499, name:'20061224-185115', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:07:07 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:07:07 Tower kernel: ata2: hard resetting link Oct 5 15:07:07 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:07:08 Tower afpd[3336]: cname(did:103499, name:'20061224-185115', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:07:13 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 5 15:07:13 Tower kernel: ata2.00: link online but device misclassified Oct 5 15:07:36 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:07:36 Tower afpd[3336]: cname(did:103499, name:'20061224-185127', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:07:43 Tower kernel: ata2.00: qc timeout (cmd 0xec) Oct 5 15:07:43 Tower kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 5 15:07:43 Tower kernel: ata2.00: revalidation failed (errno=-5) Oct 5 15:07:43 Tower kernel: ata2.00: disabled Oct 5 15:07:43 Tower kernel: ata2: hard resetting link Oct 5 15:07:53 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:07:53 Tower kernel: ata2: hard resetting link Oct 5 15:08:03 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:08:03 Tower kernel: ata2: hard resetting link Oct 5 15:08:04 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:08:04 Tower afpd[3336]: cname(did:103499, name:'20061224-185127', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:08:32 Tower afpd[3336]: transmit: Request to dbd daemon (db_dir /mnt/user/Aperture) timed out. Oct 5 15:08:32 Tower afpd[3336]: cname(did:103499, name:'20061224-185131', cwd:'/mnt/user/Aperture/Vault 2014.apvault/Database/Versions/2006/12/24'): failed to add dir Oct 5 15:08:38 Tower kernel: ata2: softreset failed (1st FIS failed) Oct 5 15:08:38 Tower kernel: ata2: hard resetting link Oct 5 15:08:43 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 5 15:08:43 Tower kernel: ata2.00: link online but device misclassified Oct 5 15:08:43 Tower kernel: ata2: EH complete Oct 5 15:08:43 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Oct 5 15:08:43 Tower kernel: sd 2:0:0:0: [sdc] Oct 5 15:08:43 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Oct 5 15:08:43 Tower kernel: sd 2:0:0:0: [sdc] CDB: Oct 5 15:08:43 Tower kernel: cdb[0]=0x28: 28 00 00 00 c1 38 00 00 48 00 Oct 5 15:08:43 Tower kernel: end_request: I/O error, dev sdc, sector 49464 Oct 5 15:08:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49400 Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49408 Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49416 Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49424 Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49432 Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49440 Oct 5 15:08:43 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49448 Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49456 Oct 5 15:08:43 Tower kernel: md: disk2 read error, sector=49464 Oct 5 15:08:43 Tower kernel: sd 2:0:0:0: [sdc] Oct 5 15:08:43 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Oct 5 15:08:43 Tower kernel: sd 2:0:0:0: [sdc] CDB: Oct 5 15:08:43 Tower kernel: cdb[0]=0x2a: 2a 00 ae 08 00 40 00 00 08 00 Oct 5 15:08:43 Tower kernel: end_request: I/O error, dev sdc, sector 2919759936 Oct 5 15:08:43 Tower kernel: md: disk2 write error, sector=2919759872 Oct 5 15:08:43 Tower kernel: md: recovery thread woken up ... Oct 5 15:08:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Oct 5 15:08:43 Tower last message repeated 3 times Oct 5 15:08:43 Tower kernel: md: recovery thread has nothing to resync Oct 5 15:08:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Oct 5 15:08:43 Tower last message repeated 6 times Oct 5 15:08:52 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Oct 5 15:08:52 Tower kernel: sd 2:0:0:0: [sdc] Oct 5 15:08:52 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Oct 5 15:08:52 Tower kernel: sd 2:0:0:0: [sdc] CDB: Oct 5 15:08:52 Tower kernel: cdb[0]=0x2a: 2a 00 00 00 c1 38 00 00 48 00 Oct 5 15:08:52 Tower kernel: end_request: I/O error, dev sdc, sector 49464 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49400 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49408 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49416 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49424 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49432 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49440 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49448 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49456 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=49464 Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] Oct 5 15:08:53 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] CDB: Oct 5 15:08:53 Tower kernel: cdb[0]=0x2a: 2a 00 aa e5 89 88 00 00 08 00 Oct 5 15:08:53 Tower kernel: end_request: I/O error, dev sdc, sector 2867169672 Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] Oct 5 15:08:53 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] CDB: Oct 5 15:08:53 Tower kernel: cdb[0]=0x2a: 2a 00 00 cc 00 40 00 00 08 00 Oct 5 15:08:53 Tower kernel: end_request: I/O error, dev sdc, sector 13369408 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=2867169608 Oct 5 15:08:53 Tower kernel: md: disk2 write error, sector=13369344 Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] Unhandled error code Oct 5 15:08:53 Tower kernel: sd 2:0:0:0: [sdc] errors repeated loads of time until: Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2867149856 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2160859568 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2161063824 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2576090168 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2576090216 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2576090224 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2576090248 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2576090288 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2659975168 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2659975184 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2659975200 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2691441872 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2735472656 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2735472664 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2308440064 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2308440072 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2507145216 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2575564800 Oct 5 15:08:56 Tower kernel: md: disk2 write error, sector=2575564808 and then another 100 times or so. Analysis appreciated! I have a spare drive this time, I intend to replace this drive with.

Wow. Thanks for the detailed reply.

Keep an eye on the high-fly-writes. The normalized value has dropped quite a bit and is getting closer to its affiliated failure threshold. It has not failed SMART, but it will be something for you to watch on that drive. Thanks. I've just read up on "high-fly-writes" and it does seem opinion is divided on if this actually means anything or not. If given the option, would you advise putting data on the drive and simply monitoring it, or perhaps running another couple of preclears?

Hi All, New Seagate NAS 2Tb drive. Preclear looks 'ok' to me, but I'd appreciate confirmation from someone more knowledgeable. Thanks. preclear_results.txt

The smart extended scan completed overnight, with no errors. I then re-added the drive to the array and it rebuilt fine, with no errors. I then ran another parity check, which completed fine. So, all seems ok. I'll keep an eye on the disk and have ordered a spare, just in case.

That is rather different - you actually stated that you were running a parity check Oops. You're right, I did. Must engage brain before keyboard, especially when doing this sort of stuff!

Thanks for the detailed reply. I know you're not sure running SMART extended is worth it, but it's concerning that is still hasn't got past 10% after a couple of hours.

Thank you for the reply. I've been reading all the FAQs and WiKi while the drive runs an extended SMART test. I've managed NOT TO PANIC, as the most important thing - my son can still access the programmes he needs to. This may sound ridiculous, but he's Autistic and a sudden change away from the norm can (and often does) result in a meltdown!! I've also dismantled my server (HP Microserver) and disconnect/reconnected all the cables I can get to. I'm 20 years out of date with PC technology, used to fix Toshiba/Compaq machines but that was a loooooong time ago. The HP Microserver is quite packed inside so not easy to work on and not familiar with these new-fangled connectors! My plan is to: 1. complete extended parity check and see what it says. 2. wait for some nice fellow to comment on the original smart results, to see if they look 'ok'. 3. If 1 and 2 are ok then I'll put the drive back unassign/reassign+build parity as per the WiKi and see if it red-balls again. 4. If I get another red-ball then it is time to either replace the drive, or perhaps first swap the position of a working drive, if that is possible, just to confirm all is ok with the cables etc. Anyway, many thanks - this forum is one of the things that makes UnRaid so great. The community is so helpful even with people like myself who don't always know the right questions to ask!

I have removed the disk and connected it to my Mac running linux via VMWare. It appears to read the disk fine. Now running an extended SMART test. Not sure what to do after that...?

Unraid 5.0.4 HP Microserver 1 Parity drive. Two data Drives. 1 SSD outside the array for Plex. syslog now included as per FAQ. Help appreciated! Just got a red ball on one of my drive (WD Green, not the parity disc) Alert: Disk 2 in error state ST1500DL003-9VT16L_5YD9GJDV (sdc) Disk quick self test gives: Short offline Completed without error 00% 54304 None SMART gives: 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 0 3 Spin Up Time 0x0003 093 092 000 Pre-fail Always Never 0 4 Start Stop Count 0x0032 089 089 020 Old age Always Never 11438 5 Reallocated Sector Ct 0x0033 100 100 036 Pre-fail Always Never 0 7 Seek Error Rate 0x000f 069 060 030 Pre-fail Always Never 8979960 9 Power On Hours 0x0032 039 038 000 Old age Always Never 54304 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 52 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 1 189 High Fly Writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow Temperature Cel 0x0022 068 060 045 Old age Always Never 32 (0 4 32 32 0) 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 13 193 Load Cycle Count 0x0032 095 095 000 Old age Always Never 11441 194 Temperature Celsius 0x0022 032 040 000 Old age Always Never 32 (128 0 0 0 0) 195 Hardware ECC Recovered 0x001a 033 005 000 Old age Always Never 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 42292542972014 241 Total LBAs Written 0x0000 100 253 000 Old age Offline Never 3006156173 242 Total LBAs Read 0x0000 100 253 000 Old age Offline Never 2803909810 I'm at a loss to what to do next, other than order a new drive! syslog.txt

A shame that as backups are handled so badly by UnRAID one can only assume that LimeTech don't consider them important! We really do need a GUI interface for an easy backup solution, direct from an UnRaid box to an internal and/or external drive(s). Should be easy to set when and what is backed up and how. The fact that we don't have any sort of interface right now had lead me to consider other solutions many times, and is really the only area of UnRaid for which I am distinctly unhappy. Command line simply doesn't cut it for backups - we need a clear, easy to use interface that encourages them. I've tried many a time to get something up and running using existing command line magic, but never succeeded. My array remains without backup, not through lack of trying. I cannot be the only one?

Good call, next day it started spitting out loads more errors. New drive has arrived today (from amazon). Think I'll give it a soak test as it was 'packaged' loose in a box with no padding at all!