WorriedAboutDataLoss

Done! mediatower-diagnostics-20180324-1511 (1).zip

So: We had a power outage and my server went down. Usually when this happens and the server comes back up and I start the array it performs a parity check (as expected due to unclean shutdown). Right now when I brought the server back up it is also showing Disk 4 as "No Device" and I can hear a strange clicking so I'm guessing the drive's gone bad. How do I bring my array back up now? Do I just replace the drive and reboot and start the array - I'm guessing that won't work since the server thinks parity is not valid and will start a new parity check! I hope I'm not going to lose all that data on the 4th disk! Thanks in advance for any advice!

I recently pre-cleared a drive over USB. Didn't really bother me with the time it takes. The only issue was that it cannot obtain the SMART reports over USB. So you should get a SMART report to verify everything is OK if clearing over USB.

Interesting!! Looks like Seagate has started offering advance replacement for RMA drives under warranty as well (for US / Canada). I just ordered mine today so hopefully should have it soon

I just checked SMART report - So I guess time to RMA this drive. Sad that Seagate doesn't do pre-ship on RMA. SMART overall-health self-assessment test result: FAILED! SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 202738824 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 131 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 029 028 030 Pre-fail Always FAILING_NOW 9740987573038 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1344 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 28 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 075 052 045 Old_age Always - 25 (Min/Max 20/33) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 932 194 Temperature_Celsius 0x0022 025 048 000 Old_age Always - 25 (0 20 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 242987774771347 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 15689232310 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 52233913360

Hmm. Found this topic: http://forums.seagate.com/t5/Desktop-HDD-Desktop-SSHD/Seagate-s-Seek-Error-Rate-Raw-Read-Error-Rate-and-Hardware-ECC/td-p/122382 From what I understand these can be ignored. Please feel free to chime in...

Also - when I added this drive a couple of months back - it ran 3 pre-clears without any issues

I've been running SMART History from umenu and one drive (Seagate Barracuda 2TB) in particular keeps showing as "health failed". Here are the latest reported values for the drive: 2013-09-25 querytime 1380112006 2013-09-25 health FAILED! 2013-09-25 ATA_Error_Count 2013-09-25 Raw_Read_Error_Rate 226261784 2013-09-25 Spin_Up_Time 0 2013-09-25 Start_Stop_Count 130 2013-09-25 Spin_Retry_Count 0 2013-09-25 Power_Cycle_Count 28 2013-09-25 Reallocated_Sector_Ct 0 2013-09-25 Seek_Error_Rate 9736692595110 2013-09-25 Temperature_Celsius 28 (0 20 0 0) 2013-09-25 Current_Pending_Sector 0 2013-09-25 Power_On_Hours 1339 2013-09-25 Offline_Uncorrectable 0 2013-09-25 UDMA_CRC_Error_Count 0 Should I be worried about the Seek_Error_Rate and Raw_Read_Error_Rate? Time to replace this drive?? Thanks!!

So I've been running and tinkering around with my system for about a week now. Decided to take a look at the syslog and one thing I notice (this occurs every time I restart the system) are the following warnings in the logs: Aug 12 09:10:02 MediaTower kernel: xor: measuring software checksum speed (Minor Issues) Aug 12 09:10:02 MediaTower kernel: ACPI Warning: 0x0000f040-0x0000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) (Minor Issues) Aug 12 09:10:59 MediaTower avahi-daemon[11069]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! (Minor Issues) Aug 12 09:11:43 MediaTower emhttp: shcmd (44): killall -HUP smbd (Minor Issues) Are these anything to be concerned about or should I just ignore them??

Thx guys!! You just convinced me to stick to WD Reds / Seagate NAS for my purchases. Just ordered 2 Reds from newegg!!!!

Tried that. But if you go for that bulk discount then you can't get the savings from the promo code

Newegg has the WD Red 3TB (WD30EFRX) for 127.99 with promo code EMCYTZT3963 http://www.newegg.com/Product/Product.aspx?Item=N82E16822236344

I'm really confused whether to spend the extra bucks for Seagate NAS / WD Reds ... In my scenario - I expect my disks to be spun down for the most of the time. Perhaps spinning 2-3 hrs a day when I access my media server. Does it make sense to go for the 24x7 capabilities of those newer NAS drives mentioned or save money and get seagate barracudas / WD green drives!!! Any thoughts??

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

WOW! I thought this drive was 4 years old but I just checked seagate's warranty site and it still shows the drive under warranty till next month - so perfect time for the drive to fail. So definitely going to RMA it!! Hopefully they'll accept the internal drive (I had taken it out from an external drive that I bought). The warranty came up valid on the internal drive's serial # as well.

Here's the smart report I just called up for the drive smart.txt

So I started running pre_clear on a drive that I had pulled out of an external enclosure recently. I thought this would be a good test to see if I had everything setup properly before I started other pre_clears on new drives. I noticed that the pre read was stuck @ 0 bytes read even half an hour I had started pre_clear and I saw a lot of drive related information in the syslog (attached). Is this drive pretty much toast ? Or do the logs indicate some other error? The drive was recognized properly by BIOS and by unRAID. The drive is no longer in warranty but it has been running for the past 4 years syslog-2013-07-26.zip