WorriedAboutDataLoss

Thanks SlrG!! That resolved the issue !!

OK. So I was able to resolve the access perms (to lock user to their home dir) I had to add the DefaultRoot ~ property to proftpd.conf to do that. So the only issue remaining is that my proFTPd config screen still shows the status as STOPPED even though the process is running and accepting FTP connections (see attached image)

Thanks Joe! Will keep that in mind. I'll build parity on this drive for now but will replace it as soon as I receive my new drives and have them precleared. Maybe I'll repurpose this drive to a cache drive after that

I hope this is the right place to post ProFTPD related questions. I downloaded the .plg file and set it up. Added a user (shrek) with description (ftpuser /mnt/disk1/FTP) Shows like this in /ets/passwds shrek:x:1000:100:ftpuser /mnt/disk1/FTP:/mnt/disk1/FTP:/bin/false 2 issues I'm facing: 1st Issue : On the ProFTP setting page : Status shows as STOPPED even though the service is running (I can login via FTP): Connected to 192.168.1.100. 220 ProFTPD 1.3.5rc3 Server (ProFTPD Default Installation) [192.168.1.100] 2nd Issue: If I login with that user : I'm still able to browse to a higher level (all the way up to root and anywhere I want). How do I restrict the user to that particular folder? Attaching my proftpd.conf file here proftpd.conf

Thanks Gary! As suggested I ran another preclear on the disk. The final report (diff) doesn't show the ECC recovered value - so I'm guessing it hasn't changed from start -> finish. I'm attaching all 3 reports here (start, finish and rpt). Any suggestions welcome!! preclear_start__2.txt preclear_finish_2.txt preclear_rpt__2.txt

I just ran a preclear (report attached) on a 2TB old disk that I have (pulled out of external enclosure). I ran just 1 cycle as I had been using this disk without errors for almost 4 years now. I did notice that there was a Hardware_ECC_Recovered SMART attribute reports which I've not seen when preclearing previous disks. Is this anything to be concerned about. I'm planning to use this as a parity disk till I get a new WD Red 3 TB put in. Thanks! preclear.txt

Aargh!! So - before waiting for a reply I assigned the disk to the array and as I was impatient and wanted to play around with disk / user shares etc to see how everything behaves - so that disk has some data on it now. So I'm guessing steps for me would be to : - Stop array - Unassigned disk - Run preclear -C (I understand the data on the disk will be lost but will it be a quick preclear as you suggested OR will it take as long as the original preclear ?) - Assign disk back to array - Restart the array I thought that the latest version of the pre-clear script would, when run on a system with UnRAID v5, automatically always use sector 64 => but perhaps that's not the case. So I'd change the second disk to start on sector 64. You can make this change without a long pre-clear run by running preclear with the -C 64 option. ... i.e. if the disk is sdb the command would be: preclear_disk.sh /dev/sdb -C 64

Thx Gary!! I just finished preclearing another 2TB disk and the results look the same! So 2 data disks down - now just waiting for the 3TB parity drive to arrive. Had a quick question though: On my second preclear I forgot to add the -A switch when executing the command. So now I have my first disk precleared with a starting sector of 64 and the second one with a starting sector of 63. Any issues here?? Do I need to run another preclear on the 2nd disk with the -A option? Looks very good => nothing to be concerned about in the SMART data, and no re-allocated sectors. Exactly what you want to see

I just ran 3 cycles on a Seagate barracuda 2TB drive (first pre_clear that I've run) - took 43.42 Hrs to run 3 cycles. I read that as long as there are "No SMART attributes are FAILING_NOW" indicator - the drive is fine for use. Can someone confirm if that's the case? I did notice that by the end of the 3 cycles my drive was running a little hot (46C) but I'm hoping that's just because I'm running without a case right now and once I have a proper case with fans (already ordered) it'll be better. Here's my preclear report: rpt.txt

I hope this is the right place to post this question: I have the CX430 PSU (just came in the other day). I see that it has 4 SATA connectors + 3 Molex connectors. Since I'm not planning on any drive enclosure (which would have provided me a backplane for power) I'm assuming I need these to convert those molex connectors to SATA power: http://www.monoprice.com/products/product.asp?c_id=102&cp_id=10226&cs_id=1022604&p_id=8793&seq=1&format=2 Also - that page states that " The Molex connector provides only 5 and 12 VDC power. While many SATA drives only require these power levels, some require the additional 3.3 VDC power provided for in the SATA specification. Make sure your drive does not require 3.3 VDC before purchasing this adapter cable." How do I make sure that's the drives I'm using don't need the 3.3 VDC power? The drives I'm currently planning to use are: Cache : Seagate Barracuda 7200rpm : 2 GB Parity : Seagate Go-flex 3TB drive (will take the drive out of the enclosure) DATA1 : Seagate Go-flex 3TB drive (will take the drive out of the enclosure) DATA2 : Seagate Go-flex 2TB drive (will take the drive out of the enclosure) DATA3 : Seagate Go-flex 2TB drive (will take the drive out of the enclosure) DATA4 : Seagate Barracuda 7200rpm : 2 GB