SSD Posted October 26, 2014 Share Posted October 26, 2014 This is an exceedingly rare scenario. It may mean bad memory in the computer, bad (cache) memory on the disk, or even bad memory on a controller. Remotely possible is a bad connection. Faced with this I'd likely run a 24 hour memory test on my server. thanks for all the feedback. can anyone point me in the right direction in terms of how to run a memory test on the server? One of the boot options on the unRAID server is to run the memory test. Quote Link to comment
grither Posted October 28, 2014 Share Posted October 28, 2014 just as an update, i can't seem to format the drive in windows either regardless of quick format or long format. so something must be really screwed with the drive can someone tell me how to reboot with memtest? i've tried searching but can't tell how... Quote Link to comment
JustinChase Posted October 28, 2014 Share Posted October 28, 2014 can someone tell me how to reboot with memtest? i've tried searching but can't tell how... when you reboot the unraid server, after the bios boots, the screen/monitor connected to the server shows the boot options of unraid for several seconds. one of the choices is memtest. use your keyboard to navigate to memtest, then hit enter, it will start the memtest. Quote Link to comment
Hogwind Posted November 2, 2014 Share Posted November 2, 2014 ... The current version is 1.15. If you have an older version, please download the newest one. Older versions prior to 1.14 did not have the ability to properly handle larger disks. (larger than 2.2TB)... Joe L. I have precleared several disks 3-4Tb with v 1.13, is it a big problem? Did that version not completely test disks lager than 2.2Tb? Quote Link to comment
itimpi Posted November 2, 2014 Share Posted November 2, 2014 ... The current version is 1.15. If you have an older version, please download the newest one. Older versions prior to 1.14 did not have the ability to properly handle larger disks. (larger than 2.2TB)... Joe L. I have precleared several disks 3-4Tb with v 1.13, is it a big problem? Did that version not completely test disks lager than 2.2Tb? The believe that earlier versions tested the whole of the disks. The issue was that on 64-bit unRAID systems the pre-clear signature was not being written correctly, so when you tried to add the disk to an existing array, then unRAID still thought it needed to be cleared. Quote Link to comment
Joe L. Posted November 2, 2014 Share Posted November 2, 2014 ... The current version is 1.15. If you have an older version, please download the newest one. Older versions prior to 1.14 did not have the ability to properly handle larger disks. (larger than 2.2TB)... Joe L. I have precleared several disks 3-4Tb with v 1.13, is it a big problem? Did that version not completely test disks lager than 2.2Tb? The testing was fine, the written pre-clear signature was, at times, not recognized by unRAID as being present. Quote Link to comment
Hogwind Posted November 2, 2014 Share Posted November 2, 2014 ... The current version is 1.15. If you have an older version, please download the newest one. Older versions prior to 1.14 did not have the ability to properly handle larger disks. (larger than 2.2TB)... Joe L. I have precleared several disks 3-4Tb with v 1.13, is it a big problem? Did that version not completely test disks lager than 2.2Tb? The testing was fine, the written pre-clear signature was, at times, not recognized by unRAID as being present. Ok, I guess I'm fine then. Thanks for the answer. Quote Link to comment
franciscohs Posted November 5, 2014 Share Posted November 5, 2014 Hello, I've done the preclear about two different disks but I'm having trouble interpreting the results. I'm attaching both results, these are old disks. The first one clearly says there is a SMART error, but why does the script says it's been successfully cleared?, I would assume it's the reallocated error count, on the other hand it didn't go up in the whole test. Regarding the second disk, it seems to have passed the test well, but it kind of worries me the presence of corrected ECC errors, is that something I should be worried about? Thanks! ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdb == ST31500341AS 9VS3H1C2 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 5:58:20 (69 MB/s) == Last Cycle's Zeroing time : 4:12:25 (99 MB/s) == Last Cycle's Post Read Time : 9:47:38 (42 MB/s) == Last Cycle's Total Time : 19:59:26 == == Total Elapsed Time 19:59:26 == == Disk Start Temperature: 26C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 114 6 ok 148786265 Reallocated_Sector_Ct = 1 1 36 FAILING_NOW 4095 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 284 Airflow_Temperature_Cel = 67 74 45 In_the_past 33 Temperature_Celsius = 33 26 0 ok 33 Hardware_ECC_Recovered = 47 46 0 ok 148786265 *** Failing SMART Attributes in /tmp/smart_finish_sdb *** ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 001 001 036 Pre-fail Always FAILING_NOW 4095 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 4095 sectors had been re-allocated before the start of the preclear. 4095 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. SMART overall-health status = FAILED! ============================================================================ ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdb == ST2000DL003-9VT166 5YD3RA0J == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 5:49:15 (95 MB/s) == Last Cycle's Zeroing time : 5:17:09 (105 MB/s) == Last Cycle's Post Read Time : 11:37:45 (47 MB/s) == Last Cycle's Total Time : 22:45:10 == == Total Elapsed Time 22:45:10 == == Disk Start Temperature: 20C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 71 80 45 ok 29 Temperature_Celsius = 29 20 0 ok 29 Hardware_ECC_Recovered = 37 33 0 ok 215947560 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Quote Link to comment
itimpi Posted November 5, 2014 Share Posted November 5, 2014 The first disk was reported as successfully pre-cleared as no errors occurred during the read/write process. However once you start getting a SMART reports indicating imminent failure I would not trust the disk. In my experience if SMART indicates imminent failure it is normally true. Unfortunately the converse is not always true - you can get a disk go bad without warnings at the SMART level. The second disk looks fine. Quote Link to comment
franciscohs Posted November 6, 2014 Share Posted November 6, 2014 The first disk was reported as successfully pre-cleared as no errors occurred during the read/write process. However once you start getting a SMART reports indicating imminent failure I would not trust the disk. In my experience if SMART indicates imminent failure it is normally true. Unfortunately the converse is not always true - you can get a disk go bad without warnings at the SMART level. The second disk looks fine. Just what I thought, thanks for confirming. What about the spin retry count? should I read the NEW and OLD value or the RAW? kind of worries me. Quote Link to comment
Joe L. Posted November 6, 2014 Share Posted November 6, 2014 The first disk was reported as successfully pre-cleared as no errors occurred during the read/write process. However once you start getting a SMART reports indicating imminent failure I would not trust the disk. In my experience if SMART indicates imminent failure it is normally true. Unfortunately the converse is not always true - you can get a disk go bad without warnings at the SMART level. The second disk looks fine. Just what I thought, thanks for confirming. What about the spin retry count? should I read the NEW and OLD value or the RAW? kind of worries me. RAW. It has never had to re-try. (the value is zero) Therefore the normalized value is at its starting value of 100. Apparently, if it fails to spin up a few times, the smart firmware will consider that drive to have failed. Quote Link to comment
djasani Posted November 16, 2014 Share Posted November 16, 2014 I have cleared two of my new Seagate 2 TB. Attached here results are for both drives. Total time it took was around 36 hours for 3 Cycles on both of them while running in parellel. == invoked as: ./preclear_disk.sh -c 3 /dev/sdd == ST2000DM001-1ER164 Z4Z0L4B9 == Disk /dev/sdd has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 0:-45:-4 (-739 MB/s) == Last Cycle's Zeroing time : 3:35:24 (154 MB/s) == Last Cycle's Post Read Time : 6:37:10 (83 MB/s) == Last Cycle's Total Time : 10:13:33 == == Total Elapsed Time 29:52:06 == == Disk Start Temperature: 26C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 100 6 ok 72878800 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 89 100 0 ok 11 Airflow_Temperature_Cel = 71 74 45 ok 29 Temperature_Celsius = 29 26 0 ok 29 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ and below is for second disk. root@Tower:/tmp# more preclear_report_sde ========================================================================1.15 == invoked as: ./preclear_disk.sh -c 3 /dev/sde == ST2000DM001-1ER164 Z4Z0KYR8 == Disk /dev/sde has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 0:-58:-44 (-567 MB/s) == Last Cycle's Zeroing time : 3:18:31 (167 MB/s) == Last Cycle's Post Read Time : 6:27:15 (86 MB/s) == Last Cycle's Total Time : 9:46:45 == == Total Elapsed Time 28:07:08 == == Disk Start Temperature: 28C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 100 6 ok 174456264 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 70 72 45 near_thresh 30 Temperature_Celsius = 30 28 0 ok 30 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ I think both of them were successfull but just wanted to share results for expert's advice. Quote Link to comment
nadavya Posted December 10, 2014 Share Posted December 10, 2014 Trying to preclear the following disks, here is the result for 3TB disk. barand new never been used. Disk: 2x2TB WD Green, 2x2TB Seagate, 1x 3TB RED, 1x 256GB SSD, Sandisk ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 3, partition start on sector 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 = **** This will take a while... you can follow progress below: = = = = = = = = Disk Temperature: 39C, Elapsed Time: 3:49:11 ./preclear_disk.sh: line 633: 1254 Segmentation fault (core dumped) dd if=/dev/zero bs=$write_bs seek=$sb of=$theDisk 2> /tmp/zero$disk_basename 403234+2 records in 403234+2 records out 845644144640 bytes (846 GB) copied malloc: jobs.c:741: assertion botched free: start and end chunk sizes differ Aborting..../preclear_disk.sh: line 660: let: percent_wrote=(84564414464000 / ): syntax error: operand expected (error token is ")") Wrote bytes out of bytes (% Done) ./preclear_disk.sh: line 1871: / (1418184481 - 1418178370) / 1000000 : syntax error: operand expected (error token is "/ (1418184481 - 1418178370) / 1000000 ") malloc: dispose_cmd.c:249: assertion botched free: start and end chunk sizes differ Aborting...Aborted (core dumped) root@Tower:/boot# Quote Link to comment
Joe L. Posted December 10, 2014 Share Posted December 10, 2014 Trying to preclear the following disks, here is the result for 3TB disk. barand new never been used. Disk: 2x2TB WD Green, 2x2TB Seagate, 1x 3TB RED, 1x 256GB SSD, Sandisk ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 3, partition start on sector 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 = **** This will take a while... you can follow progress below: = = = = = = = = Disk Temperature: 39C, Elapsed Time: 3:49:11 ./preclear_disk.sh: line 633: 1254 Segmentation fault (core dumped) dd if=/dev/zero bs=$write_bs seek=$sb of=$theDisk 2> /tmp/zero$disk_basename 403234+2 records in 403234+2 records out 845644144640 bytes (846 GB) copied malloc: jobs.c:741: assertion botched free: start and end chunk sizes differ Aborting..../preclear_disk.sh: line 660: let: percent_wrote=(84564414464000 / ): syntax error: operand expected (error token is ")") Wrote bytes out of bytes (% Done) ./preclear_disk.sh: line 1871: / (1418184481 - 1418178370) / 1000000 : syntax error: operand expected (error token is "/ (1418184481 - 1418178370) / 1000000 ") malloc: dispose_cmd.c:249: assertion botched free: start and end chunk sizes differ Aborting...Aborted (core dumped) root@Tower:/boot# only two possibilities I can think of.. 1. you've run out of memory. 2. you've got some defective memory. Are you running a lot of add-ons that might be using all/most of your low-memory? Have you looked at your syslog for other hints of memory related issues? Odds are better that it is #2 with an assertion error. I'd perform a memory check for several cycles, preferably overnight. Joe L. Quote Link to comment
nadavya Posted December 12, 2014 Share Posted December 12, 2014 hi Joe, 1. you've run out of memory. - i have 2 sticks of 4GB 2. you've got some defective memory. - i ran memtest, by now it completed 3 cycles and passed so i dont think its the problem. Are you running a lot of add-ons that might be using all/most of your low-memory? Have you looked at your syslog for other hints of memory related issues? - i am not runing any addons, this a brnad new machine, i started with preclearing the disk. i didnt looked at the syslog, i already rebooted the system without saving the log. i will do so for the next run i do. a few things: 1. the preclear for the SSD went OK. 2. i have found the following thread, tried what you mention there, i got to step #10 and there is stuck in 15% of post reading. i will try to run it again. http://lime-technology.com/forum/index.php?topic=22984.0 3. how should i preclear the 2tb disk, since they are stucked in the same way. btw, i am using the following syntax: preclear_disk.sh -A -c 3/dev/sdX thanks Quote Link to comment
JustinChase Posted December 12, 2014 Share Posted December 12, 2014 btw, i am using the following syntax: preclear_disk.sh -A -c 3/dev/sdX Is X really the right drive designation? Do you really have over 20 drives in this machine? Quote Link to comment
nadavya Posted December 12, 2014 Share Posted December 12, 2014 no, 6 drives total. X - b,c,d,e,f,g Quote Link to comment
Joe L. Posted December 14, 2014 Share Posted December 14, 2014 no, 6 drives total. X - b,c,d,e,f,g Good that your memory tested OK. It is always the first suspect. What version of unRAID? I suppose it is possible for newer versions to have an issue with malloc/free in (apparently) either the shell or "dd". Nobody else has reported the same issues. In any case, you can use the -r -b and -w options to the preclear script to alter the memory "dd" uses when pe-clearing. Quote Link to comment
nadavya Posted December 15, 2014 Share Posted December 15, 2014 hi, i am using the latest version, 5.0.6. i have succedded in completing once cycle but i get stuck in the 2nd one at this stage: " ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdg = cycle 2 of 3, partition start on sector 1 = = 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 - Verifying if the MBR is cleared. DONE = Disk Temperature: 37C, Elapsed Time: 50:03:42 Segmentation fault (core dumped) root@Tower:/boot# " i am adding my syslog. i am using the following syntax: preclear_disk.sh -b 500 -r 32768 -w 32768 -c 3 /dev/sdg please your help. thanks syslog.txt Quote Link to comment
Joe L. Posted December 16, 2014 Share Posted December 16, 2014 hi, i am using the latest version, 5.0.6. i have succedded in completing once cycle but i get stuck in the 2nd one at this stage: " ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdg = cycle 2 of 3, partition start on sector 1 = = 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 - Verifying if the MBR is cleared. DONE = Disk Temperature: 37C, Elapsed Time: 50:03:42 Segmentation fault (core dumped) root@Tower:/boot# " i am adding my syslog. i am using the following syntax: preclear_disk.sh -b 500 -r 32768 -w 32768 -c 3 /dev/sdg please your help. thanks My first gut instinct response is that it is a memory related problem. I know you said you tested it, but not with the disks also drawing power. What make/model power supply are you using? Many have reported issues with over 6 or 7 drives on a multi-rail power supply... perhaps it is the interaction of both drawing from the power supply. If a single-rail power supply is being used, I would try a different version of unRAID (with a different version of "bash" as it seems to be the one with the segfault) from your syslog: segfault at 2 ip 0807e3a0 sp bfd912a0 error 4 in bash[8048000+be000] Quote Link to comment
nadavya Posted December 16, 2014 Share Posted December 16, 2014 I am using Seasonic X-400FL. I will try to use a different rev. which one do you suggest? how do you explain that i have succeed in running one full cycle and got stuck in the 2nd one near the end. BTW, I am running now another cycle and its close to the end (44%), that will bring me to 2 full cycles of preclear which is OK to my understanding and means the drive is OK to work with. please correct me if i am wrong. thanks Quote Link to comment
nadavya Posted December 17, 2014 Share Posted December 17, 2014 hi, finished one complete cycle without errors. no i am trying to run it on anther drive but it stopped after getting 40% of pre-read. i rebotted the machine and trying to run again. i dont understand why i am gettign all of these errors? i hope that the work with unraid is free from this bugs. i am a bit afarid to my data on it now. Quote Link to comment
RobJ Posted December 17, 2014 Share Posted December 17, 2014 no i am trying to run it on anther drive but it stopped after getting 40% of pre-read. i rebooted the machine and trying to run again. i don't understand why i am getting all of these errors? i hope that the work with unraid is free from this bugs. i am a bit afraid to my data on it now. You have only mentioned a single segfault, what other errors have you seen? By the way, without knowing your hardware, I'd stay with the simple Preclear command, without the -b, -r, and -w options. Quote Link to comment
taros14 Posted December 26, 2014 Share Posted December 26, 2014 Hello! I seem to be having a problem clearing new disks. I have added 2 new disks and ran the preclear script on both. When I query the disk with the -l to see if they are cleared already, it says they are cleared. When I stop the array and try to add the disks, it wants to clear them again. So I bit the bullet one day and ran the clear from the webgui. Took over 24 hours and then it said it still was not cleared. It stopped the array after the clear was done and then asked for it to be cleared again. I can add the disk as a cache drive, but not a normal drive. I am running 5.0.6 with preclear script 1.15 Any suggestions would be greatly appreciated! Great community unRaid has and never had any issue besides this Quote Link to comment
RobJ Posted December 26, 2014 Share Posted December 26, 2014 Hello! I seem to be having a problem clearing new disks. I have added 2 new disks and ran the preclear script on both. When I query the disk with the -l to see if they are cleared already, it says they are cleared. When I stop the array and try to add the disks, it wants to clear them again. So I bit the bullet one day and ran the clear from the webgui. Took over 24 hours and then it said it still was not cleared. It stopped the array after the clear was done and then asked for it to be cleared again. I can add the disk as a cache drive, but not a normal drive. I am running 5.0.6 with preclear script 1.15 Any suggestions would be greatly appreciated! Great community unRaid has and never had any issue besides this Can you attach a zip file of all the preclear reports? I'm afraid I won't have time until evening, but someone else may. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.