September 20, 20241 yr 2 hours ago, awa1992 said: @itimpi I made sure not to format it afterwards. It still has the preclear signature on it. In that case I am afraid I have no idea why it is not working as expected
September 20, 20241 yr I was waiting until I heard back to add the drive but I figured since you said you were unsure, I just added it. It appears the message is just showing up but when I actually started the array, this time it only had me format and was added. I'm not sure what happened with the last one but it looks like it was fine this time. Thank you for your help!!
September 25, 20241 yr This plugin is the biggest waste of time lol, do not use. 2nd time now (added a drive months ago and the same thing), 3 days of preclear in unassigned devices, stop array, add new disks, no way to use the disks without preclearing from the array
September 25, 20241 yr 6 hours ago, Tethgar said: This plugin is the biggest waste of time Currently the primary use of preclear is to stress test the drive. Many, many, many years ago when preclear was authored, adding a drive to the array kept you from fully starting and accessing the rest of the array until the clear operation was done. This was a total pain, meant that adding a drive kept you offline from all your data for potentially days. That was the reason for preclear, which was command line only. Now, adding a drive allows you to use the system normally for the entire process, and the new drive is available to format after the clear is done. This plugin can work to accelerate that, and allow formatting to be done almost immediately, but it's very sensitive, any writes to the cleared drive before it's added to the array will invalidate the preclear status, forcing the normal clear process to happen. So, yes, if something writes to the drive after the preclear is done before it's added to the array, the preclear time is "wasted", but the statistics about drive performance and any errors happen before you commit to putting the drive in the array, which means you should find out if the drive has issues before you put the rest of your data at risk by adding a failing drive to the array. I'd say that information is still valuable, regardless of whether you still have to wait several hours to format the drive.
September 26, 20241 yr Hello! I have an odd situation I'm hoping to get help with. I'm currently in FL and I have a new system I'm setting up, running preclear on the new drive. It is currently on cycle 2 on the post read so it is almost done but still has like 15 hours to go. However, I'm worried about losing power due to the hurricane. What can I do? If I were to cancel the preclear and shut down the system, am I gonna have to run the preclear again? Thank you for any help!
September 26, 20241 yr Author 9 minutes ago, awa1992 said: Hello! I have an odd situation I'm hoping to get help with. I'm currently in FL and I have a new system I'm setting up, running preclear on the new drive. It is currently on cycle 2 on the post read so it is almost done but still has like 15 hours to go. However, I'm worried about losing power due to the hurricane. What can I do? If I were to cancel the preclear and shut down the system, am I gonna have to run the preclear again? Thank you for any help! You can stop the preclear, and then resume it where it left off when you restart the server.
September 26, 20241 yr Curious if this is working as planned..... did this x2 times now... I preclear a drive, as shown.... I then stop my array, and I add the disk... Shows as a new disk when I start up the array.... But goes into this "Disk Clear" status.... now Parity stays valid i guess... But its not really usable for some time, 8 hours to "clear it" Then it will go to formatting, which the first time, took hours, second drive took less then an hour, but noticeable Just want to know if that's what its suppose to do. Thanks - Walter.
September 26, 20241 yr On 9/24/2024 at 11:58 PM, Tethgar said: This plugin is the biggest waste of time lol, do not use. 2nd time now (added a drive months ago and the same thing), 3 days of preclear in unassigned devices, stop array, add new disks, no way to use the disks without preclearing from the array wonder if you seen the same as me, does my pics line up with what u seen? same thin twice, both times, it had to clear the drive, which takes just as long as pre-clear did. I have one more drive to add, if the author of the plugin wants to see the logs, or confirm this is how its suppose to be working
September 27, 20241 yr Preclears aren’t really necessary anymore. At one time the array had to be stopped in order to clear a drive which resulted in very long periods where the Unraid server was unusable so users would “pre-clear” the drives to avoid the downtime. Now it’s no longer necessary to stop the array in order to clear the drive. Many users (including me) do still use preclear on new drives in order to test the drives for bad sectors. I run 3 cycles normally. If the drive doesn’t pass I’ll RMA it. All this to say, if you’re in a hurry for another drive to add space in your server you can skip the preclear and just let Unraid do a clear (it’s a lot faster). You don’t need to “waste your time”. If your not in a hurry then an extra testing cycle isn’t really hurting anything. Or maybe you’re just reporting a bug.👍😁
September 27, 20241 yr Thanks for the info. Agree with your points. Doesn't seem really needed any more. I do like running it to flush out bad drives though.
October 20, 20241 yr when I run preclear any disk, it seems to fill up rootfs which is usually only at 3% usage. At some point, the GUI will become inaccessible and I am unable to pull the logs. On my most recent attempt I left the preclear log open and this was all I could get from it before the error happened again. Any idea on how to troubleshoot this?
November 13, 20241 yr I have searched but couldn't find this specific question, apologies if it's already been answered somewhere. New to unraid, but not new to IT. Bought three used server HDDs (12TB) and took advice from someone to run more than 1 pass in preclear. I'm 45 hours in and now willing to risk 1 pass in preclear. (In reality, pre-read, zero, and post-read means 2 read and 1 write pass of the entire drive.) Currently 45 hours in and almost done (each drive is at: 85%, 65%, 65%) with the post read on the first pass... I am guessing that after the first pass while in the second pre-read, I could cancel the operation and the disk will be fine. Unless there is any way to alter the number of passes, but since this is just a GUI on a script, I'm guessing not. So, the question is: Can I cancel a multi-pass preclear during pre-read of a second pass and be just fine to add to the array? (meaning I don't mess up the signature etc.) Thanks!
November 13, 20241 yr I'm unclear how this version is implemented, but some versions only write the signature after the last pass is successful.
November 13, 20241 yr Author 22 minutes ago, JonathanM said: I'm unclear how this version is implemented, but some versions only write the signature after the last pass is successful. You'll see this message in the report when the signature is written: Step 3 of 5 - Writing Unraid's Preclear signature: SUCCESS
November 14, 20241 yr 5 hours ago, dlandon said: You'll see this message in the report when the signature is written: Step 3 of 5 - Writing Unraid's Preclear signature: SUCCESS Thank you all. Yes, preclear signature was valid after step 3. Stopped during pre-read of pass 2 and everything started fine. Thanks again!
December 21, 20241 yr I have a bit of an odd one - have checked all 29 pages and can't see anything similar. I am preclearing two 20TB drives as they are from ServerPartDeals and are manufacturer recertified drives, so figured it was best to test them before adding to the array. The preclear for each drive keeps pausing - they run smartctl for approx 25-30 seconds and then pause for 15 seconds or so before resuming: Dec 21 23:04:04 preclear_disk_WVT0A9L4_26987: Pause (smartctl run time: 25s) Dec 21 23:04:05 preclear_disk_WVT0A9L4_26987: Paused Dec 21 23:04:05 preclear_disk_WVT0A11D_27555: Pause (smartctl run time: 26s) Dec 21 23:04:05 preclear_disk_WVT0A11D_27555: Paused Dec 21 23:04:25 preclear_disk_WVT0A9L4_26987: Resumed Dec 21 23:04:26 preclear_disk_WVT0A11D_27555: Resumed Dec 21 23:05:01 preclear_disk_WVT0A9L4_26987: Pause (smartctl run time: 25s) Dec 21 23:05:02 preclear_disk_WVT0A9L4_26987: Paused Dec 21 23:05:03 preclear_disk_WVT0A11D_27555: Pause (smartctl run time: 27s) Dec 21 23:05:03 preclear_disk_WVT0A11D_27555: Paused Dec 21 23:05:22 preclear_disk_WVT0A9L4_26987: Resumed Dec 21 23:05:24 preclear_disk_WVT0A11D_27555: Resumed Dec 21 23:05:58 preclear_disk_WVT0A9L4_26987: Pause (smartctl run time: 25s) Dec 21 23:05:59 preclear_disk_WVT0A9L4_26987: Paused Dec 21 23:06:00 preclear_disk_WVT0A11D_27555: Pause (smartctl run time: 27s) Dec 21 23:06:00 preclear_disk_WVT0A11D_27555: Paused Dec 21 23:06:19 preclear_disk_WVT0A9L4_26987: Resumed Dec 21 23:06:21 preclear_disk_WVT0A11D_27555: Resumed Dec 21 23:06:55 preclear_disk_WVT0A9L4_26987: Pause (smartctl run time: 24s) Dec 21 23:06:56 preclear_disk_WVT0A9L4_26987: Paused Dec 21 23:06:57 preclear_disk_WVT0A11D_27555: Pause (smartctl run time: 26s) Dec 21 23:06:57 preclear_disk_WVT0A11D_27555: Paused In the Unraid system log, there are some sporadic I/O errors on both of the new disks (/dev/sdh and /dev/sdi, this screenshot only shows issues with sdi), but not anywhere near as often as the commands are pausing: Dec 21 15:26:29 subete kernel: sd 9:0:3:0: attempting task abort!scmd(0x0000000037a59339), outstanding for 30051 ms & timeout 30000 ms Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2060 CDB: opcode=0x12 12 00 00 00 24 00 Dec 21 15:26:29 subete kernel: scsi target9:0:3: handle(0x000c), sas_address(0x4433221107000000), phy(7) Dec 21 15:26:29 subete kernel: scsi target9:0:3: enclosure logical id(0x500605b0054cc4e0), slot(7) Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2096 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2096 CDB: opcode=0x88 88 00 00 00 00 03 8b 5a 6e 20 00 00 04 00 00 00 Dec 21 15:26:29 subete kernel: I/O error, dev sdi, sector 15222861344 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3 Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] Unaligned partial completion (resid=58364, sector_sz=512) Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2094 CDB: opcode=0x88 88 00 00 00 00 03 8b 5a 68 00 00 00 02 00 00 00 Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2094 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2094 CDB: opcode=0x88 88 00 00 00 00 03 8b 5a 68 00 00 00 02 00 00 00 Dec 21 15:26:29 subete kernel: I/O error, dev sdi, sector 15222859776 op 0x0:(READ) flags 0x80700 phys_seg 59 prio class 3 Dec 21 15:26:29 subete kernel: sd 9:0:3:0: task abort: SUCCESS scmd(0x0000000037a59339) Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2095 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2095 CDB: opcode=0x88 88 00 00 00 00 03 8b 5a 6a 00 00 00 04 20 00 00 Dec 21 15:26:29 subete kernel: I/O error, dev sdi, sector 15222860288 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3 Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2097 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:26:29 subete kernel: sd 9:0:3:0: [sdi] tag#2097 CDB: opcode=0x88 88 00 00 00 00 03 8b 5a 72 20 00 00 01 e0 00 00 Dec 21 15:26:29 subete kernel: I/O error, dev sdi, sector 15222862368 op 0x0:(READ) flags 0x80700 phys_seg 60 prio class 3 Dec 21 15:26:29 subete kernel: sd 9:0:3:0: Power-on or device reset occurred Dec 21 15:26:30 subete kernel: sd 9:0:3:0: Power-on or device reset occurred Dec 21 15:27:00 subete kernel: sd 9:0:3:0: attempting task abort!scmd(0x00000000cd0ec85d), outstanding for 30050 ms & timeout 30000 ms Dec 21 15:27:00 subete kernel: sd 9:0:3:0: [sdi] tag#2091 CDB: opcode=0x12 12 00 00 00 24 00 Dec 21 15:27:00 subete kernel: scsi target9:0:3: handle(0x000c), sas_address(0x4433221107000000), phy(7) Dec 21 15:27:00 subete kernel: scsi target9:0:3: enclosure logical id(0x500605b0054cc4e0), slot(7) Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2099 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2099 CDB: opcode=0x88 88 00 00 00 00 03 8c 39 64 00 00 00 04 00 00 00 Dec 21 15:27:01 subete kernel: I/O error, dev sdi, sector 15237473280 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3 Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2095 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2095 CDB: opcode=0x88 88 00 00 00 00 03 8c 39 62 f8 00 00 01 08 00 00 Dec 21 15:27:01 subete kernel: sd 9:0:3:0: task abort: SUCCESS scmd(0x00000000cd0ec85d) Dec 21 15:27:01 subete kernel: I/O error, dev sdi, sector 15237473016 op 0x0:(READ) flags 0x80700 phys_seg 31 prio class 3 Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2094 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2094 CDB: opcode=0x88 88 00 00 00 00 03 8c 39 5e 00 00 00 04 f8 00 00 Dec 21 15:27:01 subete kernel: I/O error, dev sdi, sector 15237471744 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3 Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2100 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Dec 21 15:27:01 subete kernel: sd 9:0:3:0: [sdi] tag#2100 CDB: opcode=0x88 88 00 00 00 00 03 8c 39 68 00 00 00 02 00 00 00 Dec 21 15:27:01 subete kernel: I/O error, dev sdi, sector 15237474304 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 3 Dec 21 15:27:01 subete kernel: sd 9:0:3:0: Power-on or device reset occurred Dec 21 15:27:01 subete kernel: sd 9:0:3:0: Power-on or device reset occurred They're still only in stage 1 so it's early days, the preview of the log for one of the drives shows the following: #################################################################################################### # Unraid Server Preclear of disk WVT0A9L4 # # Cycle 1 of 1, partition start on sector 64. # # # # Step 1 of 5 - Pre-read in progress: (58% Done) # # # # # # # # # # # # ** Time elapsed: 13:22:28 | Current speed: 216 MB/s | Average speed: 244 MB/s # # # #################################################################################################### # Cycle elapsed time: 13:22:26 | Total elapsed time: 13:22:24 # #################################################################################################### #################################################################################################### # S.M.A.R.T. Status (device type: default) # # # # ATTRIBUTE INITIAL STATUS # # Reallocated_Sector_Ct 0 - # # Power_On_Hours 172 - # # Reported_Uncorrect 0 - # # Airflow_Temperature_Cel 39 - # # Current_Pending_Sector 0 - # # Offline_Uncorrectable 0 - # # UDMA_CRC_Error_Count 0 - # # # # # #################################################################################################### # Report genereated on: December 21, 2024 at 23:14:07 # #################################################################################################### Can't tell if there's any particular errors here or not to be honest - is this just normal? The speeds seem to be reasonable (~240MB/sec on both drives), and the process is happening at the same time, so it's not like it is pausing one to progress the other - they both pause and unpause within a few seconds of each other... I believe both of these drives are connected to an HBA card rather than directly to my motherboard, I suppose it's possible that running a preclear on both might be overtaxing that card? I haven't done much with the server so the other drives attached to the HBA are mostly spun down. Any ideas appreciated! Not sure if I should attempt any SMART tests while the preclear is running?
December 22, 20241 yr I want to clear the disk before selling and have this error: [error] 12201#12201: *109048 open() "/usr/local/emhttp/plugins/<" failed (2: No such file or directory) while sending to client, client: 192.168.0.43, server: , request: "GET /plugins/%3C?=UNASSIGNED_PRECLEAR_PLUGIN;? HTTP/1.1", host: "192.168.0.5", referrer: "http://192.168.0.5/plugins/unassigned.devices.preclear/Preclear.php?action=show_preclear&serial=PNY22342208260100F95"
December 22, 20241 yr Hi, I am currently running a pre-clear on 4 new drives simultaneously using plugin version 2024.12.17 on UNRAID RC1. I noticed that the OS will try to spin down the drives with the global spin down of 3h in my case after the drive has been zeroed, and the post read being in progress. Dec 21 20:01:37 Anton emhttpd: spinning down /dev/sdm Dec 21 20:01:42 Anton emhttpd: read SMART /dev/sdm The drives will immediately spin back up because they are being used of course. Attached are the logs since first inserting the drive and starting the pre clear plugin. Is this known or maybe a bug in RC? disklog.txt preclear_disk_ZVT4M7QA_72825.txt
December 22, 20241 yr Author 3 hours ago, Hendrik112 said: Hi, I am currently running a pre-clear on 4 new drives simultaneously using plugin version 2024.12.17 on UNRAID RC1. I noticed that the OS will try to spin down the drives with the global spin down of 3h in my case after the drive has been zeroed, and the post read being in progress. Dec 21 20:01:37 Anton emhttpd: spinning down /dev/sdm Dec 21 20:01:42 Anton emhttpd: read SMART /dev/sdm The drives will immediately spin back up because they are being used of course. Attached are the logs since first inserting the drive and starting the pre clear plugin. Is this known or maybe a bug in RC? disklog.txt 2.21 kB · 0 downloads preclear_disk_ZVT4M7QA_72825.txt 2.28 kB · 0 downloads What version of Unraid are you using? This has been fixed since Unraid 6.12.5. If you are using a later version of Unraid, please post the full diagnostics.
December 22, 20241 yr 10 minutes ago, dlandon said: What version of Unraid are you using? This has been fixed since Unraid 6.12.5. If you are using a later version of Unraid, please post the full diagnostics. I am using Unraid 7.0.0-rc.1. The complete diagnostics are attached. anton-diagnostics-20241222-1348.zip
December 22, 20241 yr Author 1 hour ago, Hendrik112 said: I am using Unraid 7.0.0-rc.1. The complete diagnostics are attached. anton-diagnostics-20241222-1348.zip 218.7 kB · 1 download I see an issue and will update UD Preclear after my testing. For now it is fairly harmless.
December 22, 20241 yr Author 3 hours ago, Hendrik112 said: I am using Unraid 7.0.0-rc.1. The complete diagnostics are attached. anton-diagnostics-20241222-1348.zip 218.7 kB · 1 download What browser do you use?
December 22, 20241 yr 45 minutes ago, dlandon said: What browser do you use? Chrome, but on macOS. So WebKit under the hood. Edit: I am actually not sure which parts of WebKit Chrome uses anymore, I just know that there are differences between macOS Chrome and the other Chrome versions. Edited December 22, 20241 yr by Hendrik112
December 24, 20241 yr Author On 12/22/2024 at 3:27 AM, Hendrik112 said: The drives will immediately spin back up because they are being used of course. Unraid will attempt to spin down a disk if it has a partition. If there is no partition, it will not attempt to spin down the disk. Once a disk is precelared, the preclear signature and a blank partition are created on the disk. Unraid will attempt to spin down the disk during post read. As you noted, the disk will spin back up. The reason this happens is Unraid is detecting file reads and writes to determine if a disk should be spun down and because there is no file system, there will not be any file reads and writes. The spin downs can be ignored. I did release a new version of UD Preclear today to address some nginx issues I saw in your log.
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.