fireman

Joe, you're right. I was confused but thanks to your explanations, I can now relax. Since I just started preclearing the drive again, can I stop this process and use the drive right away or do I have to wait 48 hours for the process to finish ?

Here is what I got after the first preclear session: =========================================================================== = unRAID server Pre-Clear disk /dev/hdc = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 26C, Elapsed Time: 41:40:04 ============================================================================ == == Disk /dev/hdc has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 19059 --- > 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 181448684 58c58 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 4503 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 105891 63,66c63,66 < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 < 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 < 190 Airflow_Temperature_Cel 0x0022 073 066 045 Old_age Always - 27 (Lifetime Min/Max 27/29) < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 189 High_Fly_Writes 0x003a 082 082 000 Old_age Always - 18 > 190 Airflow_Temperature_Cel 0x0022 074 066 045 Old_age Always - 26 (Lifetime Min/Max 24/29) > 195 Hardware_ECC_Recovered 0x001a 058 040 000 Old_age Always 69,72c69,72 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 167873091731456 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 6833 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 176458731356202 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2895529308 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 985258449 ============================================================================ I'm going to run another preclear session in order to see if it will get better.

THe "new" drive arrived today in the mail. I just started preclear a few minutes ago. I'll get back to you guys in 48 hours !

I sure will ! As a side note, I received a notification that my replacement HD took off this morning. Should be here soon...

Well, I ran preclear once more before I RMA the drive just in case. =========================================================================== = unRAID server Pre-Clear disk /dev/hdc = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 28C, Elapsed Time: 48:20:41 ============================================================================ == == Disk /dev/hdc has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 56c56 < 1 Raw_Read_Error_Rate 0x000f 106 081 006 Pre-fail Always - 65022542 --- > 1 Raw_Read_Error_Rate 0x000f 105 081 006 Pre-fail Always - 8631358 59,60c59,60 < 5 Reallocated_Sector_Ct 0x0033 034 034 036 Pre-fail Always FAILING_NOW 2708 < 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 5041077 --- > 5 Reallocated_Sector_Ct 0x0033 013 013 036 Pre-fail Always FAILING_NOW 3567 > 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 5201647 64c64 < 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 2731 --- > 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 3458 66,70c66,70 < 189 High_Fly_Writes 0x003a 048 048 000 Old_age Always - 52 < 190 Airflow_Temperature_Cel 0x0022 074 055 045 Old_age Always - 26 (Lifetime Min/Max 22/29) < 195 Hardware_ECC_Recovered 0x001a 041 029 000 Old_age Always < 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 3 < 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 3 --- > 189 High_Fly_Writes 0x003a 028 028 000 Old_age Always - 72 > 190 Airflow_Temperature_Cel 0x0022 072 055 045 Old_age Always - 28 (Lifetime Min/Max 22/29) > 195 Hardware_ECC_Recovered 0x001a 043 029 000 Old_age Always > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 147 > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 147 72,74c72,74 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 49877455209333 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3123343013 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2680577209 --- > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 119992796316581 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1726671095 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2338902771 77c77 < ATA Error Count: 2115 (device log contains only the most recent five errors) --- > ATA Error Count: 2683 (device log contains only the most recent five errors) 92c92 < Error 2115 occurred at disk power-on lifetime: 880 hours (36 days + 16 hours) --- > Error 2683 occurred at disk power-on lifetime: 933 hours (38 days + 21 hours) 98c98 < 40 51 00 0a 71 63 01 Error: UNC at LBA = 0x0163710a = 23294218 --- > 40 51 00 25 d4 45 01 Error: UNC at LBA = 0x0145d425 = 21353509 103,107c103,107 < 25 00 00 68 70 63 e1 00 3d+17:23:27.541 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+17:23:27.520 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+17:23:27.500 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+17:23:27.480 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+17:23:27.468 READ DMA EXT --- > 25 00 00 f0 d3 45 e1 00 5d+21:56:53.962 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:56:53.959 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:56:53.944 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:56:53.942 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:56:53.941 READ DMA EXT 109c109 < Error 2114 occurred at disk power-on lifetime: 879 hours (36 days + 15 hours) --- > Error 2682 occurred at disk power-on lifetime: 933 hours (38 days + 21 hours) 115c115 < 40 51 00 e3 28 3a 00 Error: UNC at LBA = 0x003a28e3 = 3811555 --- > 40 51 00 be 78 57 00 Error: UNC at LBA = 0x005778be = 5732542 120,124c120,124 < 25 00 00 a8 28 3a e0 00 3d+15:38:17.954 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+15:38:17.952 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+15:38:17.935 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+15:38:17.934 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+15:38:17.932 READ DMA EXT --- > 25 00 00 60 78 57 e0 00 5d+21:33:20.375 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:33:20.373 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:33:20.372 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:33:20.371 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:33:20.371 READ DMA EXT 126c126 < Error 2113 occurred at disk power-on lifetime: 877 hours (36 days + 13 hours) --- > Error 2681 occurred at disk power-on lifetime: 932 hours (38 days + 20 hours) 132c132 < 40 51 00 31 46 01 00 Error: UNC at LBA = 0x00014631 = 83505 --- > 40 51 00 af a8 ce 00 Error: UNC at LBA = 0x00cea8af = 13543599 137,141c137,141 < 25 00 00 c0 45 01 e0 00 3d+13:55:59.367 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:55:59.366 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:55:59.365 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:55:59.364 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:55:59.364 READ DMA EXT --- > 25 00 00 88 a8 ce e0 00 5d+21:08:28.934 READ DMA EXT > 25 00 00 88 a7 ce e0 00 5d+21:08:28.932 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:08:28.912 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:08:28.910 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+21:08:28.909 READ DMA EXT 143c143 < Error 2112 occurred at disk power-on lifetime: 877 hours (36 days + 13 hours) --- > Error 2680 occurred at disk power-on lifetime: 932 hours (38 days + 20 hours) 149c149 < 40 51 00 51 d9 95 00 Error: UNC at LBA = 0x0095d951 = 9820497 --- > 40 51 00 21 7d ed 00 Error: UNC at LBA = 0x00ed7d21 = 15564065 154,158c154,158 < 25 00 00 a0 d8 95 e0 00 3d+13:48:39.480 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:48:39.477 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:48:39.476 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:48:39.475 READ DMA EXT < 25 00 00 ff ff ff ef 00 3d+13:48:39.474 READ DMA EXT --- > 25 00 00 c8 7c ed e0 00 5d+20:50:33.713 READ DMA EXT > 25 00 00 c8 7b ed e0 00 5d+20:50:33.712 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+20:50:33.711 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+20:50:33.684 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+20:50:33.683 READ DMA EXT 160c160 < Error 2111 occurred at disk power-on lifetime: 872 hours (36 days + 8 hours) --- > Error 2679 occurred at disk power-on lifetime: 931 hours (38 days + 19 hours) 166c166 < 40 51 00 36 af 51 02 Error: UNC at LBA = 0x0251af36 = 38907702 --- > 40 51 00 ea a6 28 01 Error: UNC at LBA = 0x0128a6ea = 19441386 171,175c171,175 < 25 00 08 30 af 51 e2 00 3d+08:32:02.795 READ DMA EXT < 25 00 08 30 af 51 e2 00 3d+08:31:59.809 READ DMA EXT < 25 00 20 90 38 51 e2 00 3d+08:31:56.313 READ DMA EXT < 25 00 20 70 38 51 e2 00 3d+08:31:56.297 READ DMA EXT < 25 00 08 60 0f 51 e2 00 3d+08:31:56.277 READ DMA EXT --- > 25 00 00 38 a6 28 e1 00 5d+19:31:59.381 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+19:31:59.380 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+19:31:59.379 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+19:31:59.377 READ DMA EXT > 25 00 00 ff ff ff ef 00 5d+19:31:59.377 READ DMA EXT ============================================================================ Since it takes 2 full days to run, I'm not sure I want to run it one more time and since the data above doesn't seem any better the the first one, I guess I'm going to contact Seagate and send it back in. What do you guys think ?

I just finished preclearing a Seagate 1.5 TB drive and I got the following errors. =========================================================================== = unRAID server Pre-Clear disk /dev/hdc = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 27C, Elapsed Time: 44:33:59 ============================================================================ == == Disk /dev/hdc has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 115 081 006 Pre-fail Always - 92558283 --- > 1 Raw_Read_Error_Rate 0x000f 114 081 006 Pre-fail Always - 65005954 57,58c57,58 < 5 Reallocated_Sector_Ct 0x0033 070 070 036 Pre-fail Always - 1232 < 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 4859598 --- > 5 Reallocated_Sector_Ct 0x0033 038 038 036 Pre-fail Always - 2578 > 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 5028369 62c62 < 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1551 --- > 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 2725 64,68c64,68 < 189 High_Fly_Writes 0x003a 076 076 000 Old_age Always - 24 < 190 Airflow_Temperature_Cel 0x0022 074 055 045 Old_age Always - 26 (Lifetime Min/Max 22/29) < 195 Hardware_ECC_Recovered 0x001a 038 029 000 Old_age Always < 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 80 < 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 80 --- > 189 High_Fly_Writes 0x003a 049 049 000 Old_age Always - 51 > 190 Airflow_Temperature_Cel 0x0022 073 055 045 Old_age Always - 27 (Lifetime Min/Max 22/29) > 195 Hardware_ECC_Recovered 0x001a 044 029 000 Old_age Always > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 132 > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 132 70,72c70,72 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 209465555026757 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 198967231 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1753641191 --- > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 36013300777841 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3093423191 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2680571171 75c75 < ATA Error Count: 1340 (device log contains only the most recent five errors) --- > ATA Error Count: 2115 (device log contains only the most recent five errors) 90c90 < Error 1340 occurred at disk power-on lifetime: 830 hours (34 days + 14 hours) --- > Error 2115 occurred at disk power-on lifetime: 880 hours (36 days + 16 hours) 96c96 < 40 51 00 83 bc 01 00 Error: UNC at LBA = 0x0001bc83 = 113795 --- > 40 51 00 0a 71 63 01 Error: UNC at LBA = 0x0163710a = 23294218 101,105c101,105 < 25 00 00 40 bb 01 e0 00 1d+14:43:10.607 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+14:43:10.606 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+14:43:10.605 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+14:43:10.604 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+14:43:10.603 READ DMA EXT --- > 25 00 00 68 70 63 e1 00 3d+17:23:27.541 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+17:23:27.520 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+17:23:27.500 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+17:23:27.480 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+17:23:27.468 READ DMA EXT 107c107 < Error 1339 occurred at disk power-on lifetime: 827 hours (34 days + 11 hours) --- > Error 2114 occurred at disk power-on lifetime: 879 hours (36 days + 15 hours) 113c113 < 40 51 00 3d e7 0a 01 Error: UNC at LBA = 0x010ae73d = 17491773 --- > 40 51 00 e3 28 3a 00 Error: UNC at LBA = 0x003a28e3 = 3811555 118,122c118,122 < 25 00 00 40 e6 0a e1 00 1d+12:05:54.346 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+12:05:54.345 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+12:05:54.344 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+12:05:54.343 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+12:05:54.342 READ DMA EXT --- > 25 00 00 a8 28 3a e0 00 3d+15:38:17.954 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+15:38:17.952 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+15:38:17.935 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+15:38:17.934 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+15:38:17.932 READ DMA EXT 124c124 < Error 1338 occurred at disk power-on lifetime: 826 hours (34 days + 10 hours) --- > Error 2113 occurred at disk power-on lifetime: 877 hours (36 days + 13 hours) 130c130 < 40 51 00 92 26 00 00 Error: UNC at LBA = 0x00002692 = 9874 --- > 40 51 00 31 46 01 00 Error: UNC at LBA = 0x00014631 = 83505 135,139c135,139 < 25 00 00 00 24 00 e0 00 1d+11:00:59.221 READ DMA EXT < 25 00 00 00 18 00 e0 00 1d+11:00:59.190 READ DMA EXT < 25 00 00 00 14 00 e0 00 1d+11:00:58.965 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+11:00:58.962 READ DMA EXT < 25 00 00 ff ff ff ef 00 1d+11:00:58.931 READ DMA EXT --- > 25 00 00 c0 45 01 e0 00 3d+13:55:59.367 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:55:59.366 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:55:59.365 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:55:59.364 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:55:59.364 READ DMA EXT 141c141 < Error 1337 occurred at disk power-on lifetime: 826 hours (34 days + 10 hours) --- > Error 2112 occurred at disk power-on lifetime: 877 hours (36 days + 13 hours) 147c147 < 40 51 00 92 26 00 00 Error: UNC at LBA = 0x00002692 = 9874 --- > 40 51 00 51 d9 95 00 Error: UNC at LBA = 0x0095d951 = 9820497 152,156c152,156 < 25 00 00 00 24 00 e0 00 1d+11:00:19.587 READ DMA EXT < 25 00 00 00 20 00 e0 00 1d+11:00:19.527 READ DMA EXT < 25 00 00 00 18 00 e0 00 1d+11:00:19.507 READ DMA EXT < 25 00 00 00 14 00 e0 00 1d+11:00:19.217 READ DMA EXT < 25 00 00 00 10 00 e0 00 1d+11:00:19.167 READ DMA EXT --- > 25 00 00 a0 d8 95 e0 00 3d+13:48:39.480 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:48:39.477 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:48:39.476 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:48:39.475 READ DMA EXT > 25 00 00 ff ff ff ef 00 3d+13:48:39.474 READ DMA EXT 158c158 < Error 1336 occurred at disk power-on lifetime: 826 hours (34 days + 10 hours) --- > Error 2111 occurred at disk power-on lifetime: 872 hours (36 days + 8 hours) 164c164 < 40 51 00 92 26 00 00 Error: UNC at LBA = 0x00002692 = 9874 --- > 40 51 00 36 af 51 02 Error: UNC at LBA = 0x0251af36 = 38907702 169,173c169,173 < 25 00 00 00 24 00 e0 00 1d+10:59:38.204 READ DMA EXT < 25 00 00 00 20 00 e0 00 1d+10:59:38.154 READ DMA EXT < 25 00 00 00 18 00 e0 00 1d+10:59:38.133 READ DMA EXT < 25 00 00 00 14 00 e0 00 1d+10:59:37.838 READ DMA EXT < 25 00 00 00 10 00 e0 00 1d+10:59:37.774 READ DMA EXT --- > 25 00 08 30 af 51 e2 00 3d+08:32:02.795 READ DMA EXT > 25 00 08 30 af 51 e2 00 3d+08:31:59.809 READ DMA EXT > 25 00 20 90 38 51 e2 00 3d+08:31:56.313 READ DMA EXT > 25 00 20 70 38 51 e2 00 3d+08:31:56.297 READ DMA EXT > 25 00 08 60 0f 51 e2 00 3d+08:31:56.277 READ DMA EXT ============================================================================ Is it safe to use this drive as a parity drive ?

I'd be also interested to know if there are Mac OS utilities that do the same thing.

PS3 with PS3mediaserver running on my unRaid box.

I've had the same problem for the first time today. I'm currently running BubbaRaid Version 0.01.17-Beta based on unRAID 4.4.2 on a Gigabyte GA-MA74GM-S2. This server has been running 24/7 for the last 3 weeks - that's when I built it - and it's the first time it occurred. Let's hope it will not start occurring more often.

Thanks for the response smino but I'm not sure you realise how PS3mediaserver works. The PS3 will not see samba shares. It is a function of PMS to present the shares to the PS3. I know it is mostly a PMS problem but since many unRaid users run this app, I was wondering if someone else has/had this problem and how they solved it.

I have been running ps3mediaserver (PMS) for a couple of week now and I really love it. Along with unRaid and rTorrent, this is a really great combo. The only "problem" I am encountering at this time id the fact that PMS will no let me see my user shares when I'm looking at it on my PS3. I can see disk 1 and disk 2 but I cannot see the user share called "HD Movies". I have to go on disk 1 and see if my movie is ther and if not, I need to go to disk 2 to find it. That is really anoying, especially when my wife is looking for a movie or a TV show and she doesn't remember if it's on disk 1 or 2. I've posted the question on the PMS forum as well but I was wondering if somebody here had the same experience and if and how it got solved.

Many already have. Detailed instructions are in the Wiki. Agreed.... no need to do so, particularly as there are many ways to get extended functionality (add a web server, compile your own kernel, unMenu, etc) So do I. I would, however, like to know that Tom has escrowed the source code.... just in case. +1 I, by no means, have the necessary skills to go beyond what I already have on my server so that's why I am hesitant to put more money in that project at this time. I know that a $100 isn't a whole lot of money for many and as a matter of fact, it isn't all that much money for me too but I want to make sure my money is spent on something durable. I want Lime-technology to grow so I can enjoy my unRaid server for a long time. I won't even mind spending more, if need be, for upgrades and add-ons because they're worth it to me. But I refuse to put money in a product that I can't figure if it's still gonna be around next year or even next month...

I don't see where I said something wrong but at the same time, why could I not say what I have on my mind ? It's not my fault if Tom chooses not to show his face in that forum any more. As far as I can tell, I was polite in my previous posts. I only expressed my disappointment. As NAS said earlier, having Tom abstain from his official support forum and ignore bugs and requests for his input is pretty disappointing. If, as was pointed out, he logs in from time to time and he finds my comments inappropriate, hopefully he'll get in touch with me to address the situation. If not, then it means that either he's OK with what I said or he doesn't care. I just hope it's the former.

Well I'm probably old enough to be your dad too !!! My oldest son - the one who just started his second year of college studying computer science - turned 18 last spring so you're probably pretty close in age. So keep working hard and make your dad proud. With the baby boomers retiring en masse during the next 10 years or so, there will be plenty of job opportunities for you guys. You'll have plenty of jobs to choose from and employers will be more than willing to provide you with decent work environment. If you play your cards right, you'll be able to enjoy a fruitful career and earn a decent pay check every week. Now I sound like my grand father... Better quit while I'm ahead !!!

+1