dlandon Posted January 2, 2023 Author Share Posted January 2, 2023 2 hours ago, Spyderturbo007 said: If I stop the array, will that interfere with a current preclear operation? I have a disk that I need to reassign, but I have a preclear running on 3 other disks. You can pause the preclears, stop and restart the array, and then restart the preclears. Quote Link to comment
Spyderturbo007 Posted January 2, 2023 Share Posted January 2, 2023 Thank you @dlandon That worked perfectly. Quote Link to comment
chrisp1992 Posted January 3, 2023 Share Posted January 3, 2023 (edited) Having some consistent issues with trying to preclear a 12 TB Seagate Ironwolf. I thought something was wrong with the first drive, so I RMA’d it, but the second drive is having the same issues. It seems to happen towards the end of the pre-read verification, and it’s always been a “low memory detected, aborting”, even though my memory usage is only around 30%. I’ve attached the Preclear log. Any ideas? EDIT: I installed and used Binhex's Preclear Docker, and it worked. Seems like the Unassigned Devices Preclear doesn't always work within the GUI. preclear_disk_DB98765432143_28936.txt Edited January 10, 2023 by chrisp1992 Quote Link to comment
bobokun Posted January 10, 2023 Share Posted January 10, 2023 I'm having some issues with preclearing a new drive that I purchased. Every time I try to preclear it always fails at the last step in verifying Unraid's signature. I'm running on the latest version of the plugin. Is my drive bad? Running on Unraid version 6.11.5 Unassigned Devices Preclear version 2023.01.08 Quote Link to comment
trurl Posted January 10, 2023 Share Posted January 10, 2023 13 minutes ago, bobokun said: Every time I try to preclear it always fails at the last step in verifying Unraid's signature. Did you also let it do post-read verification? Doesn't look like it from the log, though I haven't precleared a disk in a long time. The reason I ask is post-read failure can be an indication of bad RAM, since bad RAM can result in the data being changed from zero either when being written or when being read. Possibly bad RAM could have a similar effect on signature verification. Quote Link to comment
bobokun Posted January 10, 2023 Share Posted January 10, 2023 30 minutes ago, trurl said: Did you also let it do post-read verification? Doesn't look like it from the log, though I haven't precleared a disk in a long time. The reason I ask is post-read failure can be an indication of bad RAM, since bad RAM can result in the data being changed from zero either when being written or when being read. Possibly bad RAM could have a similar effect on signature verification. Yes I had post-read verification on but because it failed at the verifying Unraid's Signature stage it never got to the last stage. Quote Link to comment
trurl Posted January 10, 2023 Share Posted January 10, 2023 21 minutes ago, bobokun said: Yes I had post-read verification on but because it failed at the verifying Unraid's Signature stage it never got to the last stage. Have you done memtest recently? Quote Link to comment
bobokun Posted January 10, 2023 Share Posted January 10, 2023 1 hour ago, trurl said: Have you done memtest recently? I did memtest maybe 1 year ago when I upgrade my RAM. Ran it for 48hours without any issues. I'm using a external HDD docking station plugged into my server via USB to do the preclear. Do you think that might be the reason? Quote Link to comment
trurl Posted January 10, 2023 Share Posted January 10, 2023 Just now, bobokun said: I'm using a external HDD docking station plugged into my server via USB to do the preclear. Do you think that might be the reason? Might depend on how transparent the interface is. But since it is giving SMART reports for the disk and reporting the correct size for a standard 14TB disk I think it is probably OK. Quote Link to comment
bobokun Posted January 11, 2023 Share Posted January 11, 2023 I tried running preclear again on the disk and once again it failed. This is what I found in the disk log information, does it help? Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 08:58:36 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 7 08:58:39 unNAS emhttpd: WDC_WD14_0EFGX-68B0GN0_PROLIFICMP000000001-0:0 (sdl) 512 27344764928 Jan 7 08:59:55 unNAS emhttpd: spinning up /dev/sdl Jan 7 08:59:55 unNAS emhttpd: read SMART /dev/sdl Jan 7 12:59:56 unNAS emhttpd: spinning down /dev/sdl Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:52:06 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 7 15:55:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 7 15:55:57 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 8 08:57:02 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 8 08:57:02 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 Sense Key : 0x5 [current] Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 ASC=0x20 ASCQ=0x0 Jan 8 11:08:05 unNAS kernel: sd 10:0:0:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 c1 98 68 00 00 00 08 00 00 00 Jan 8 11:08:05 unNAS kernel: critical target error, dev sdl, sector 3247990784 op 0x1:(WRITE) flags 0x104000 phys_seg 256 prio class 0 Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998848, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998849, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998850, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998851, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998852, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998853, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998854, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998855, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998856, lost async page write Jan 8 11:08:05 unNAS kernel: Buffer I/O error on dev sdl, logical block 405998857, lost async page write Jan 9 08:33:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:34:05 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:34:06 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:34:06 unNAS kernel: sdl: sdl1 Jan 9 08:34:06 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. Jan 9 08:34:07 unNAS emhttpd: read SMART /dev/sdl Jan 9 08:45:58 unNAS unassigned.devices: Removing all partitions from disk '/dev/sdl'. Jan 9 08:46:00 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:46:02 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:51:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 08:51:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 9 12:34:08 unNAS emhttpd: spinning down /dev/sdl Jan 10 08:27:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 08:28:16 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 08:28:17 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 08:28:17 unNAS kernel: sdl: sdl1 Jan 10 08:28:17 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB) Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Write Protect is off Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Mode Sense: 03 00 00 00 Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] No Caching mode page found Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Assuming drive cache: write through Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 10:16:49 unNAS kernel: sdl: sdl1 Jan 10 10:16:49 unNAS kernel: sd 10:0:0:0: [sdl] Attached SCSI disk Jan 10 10:16:51 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. Jan 10 10:18:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 10 10:18:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:54:13 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:54:58 unNAS emhttpd: read SMART /dev/sdl Jan 11 09:55:12 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:55:13 unNAS kernel: sd 10:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16). Jan 11 09:55:13 unNAS kernel: sdl: sdl1 Jan 11 09:55:13 unNAS unassigned.devices: Partition 'sdl1' does not have a file system and cannot be mounted. ** Press ANY KEY to close this window ** Quote Link to comment
bobokun Posted January 12, 2023 Share Posted January 12, 2023 On 1/10/2023 at 11:50 AM, trurl said: Might depend on how transparent the interface is. But since it is giving SMART reports for the disk and reporting the correct size for a standard 14TB disk I think it is probably OK. So I ran memtest and after 8 passes I don't have any memory errors.. still not sure what the solution is. Quote Link to comment
bobokun Posted January 13, 2023 Share Posted January 13, 2023 I tried connecting the drive directly to my server rather than using the external dock and ran a preclear but it still fails at the verifying Unraid's preclear signature step. I'm not sure if there's an issue with this drive or the preclear plugin. Quote Link to comment
bobokun Posted January 14, 2023 Share Posted January 14, 2023 I just tried to preclear a different disk and it once again also failed and got a invalid MBR signature from Unraid. Can someone verify the latest version of preclear is working with unraid 6.11.5? Quote Link to comment
dlandon Posted January 14, 2023 Author Share Posted January 14, 2023 3 hours ago, bobokun said: I just tried to preclear a different disk and it once again also failed and got a invalid MBR signature from Unraid. Can someone verify the latest version of preclear is working with unraid 6.11.5? Working for me: The script to do the preclear itself has not changed in a long time. You might try the preclear docker and see if you get different results. Quote Link to comment
bobokun Posted January 15, 2023 Share Posted January 15, 2023 On 1/14/2023 at 10:48 AM, dlandon said: You might try the preclear docker and see if you get different results. Thanks! Just ran preclear again with binhex docker preclear and it all passed okay. Weird how we couldn't figure out why it wasn't working with the preclear plugin. It used to work fine before 😅. Quote Link to comment
thorneo Posted January 20, 2023 Share Posted January 20, 2023 I have tried numerous times to get my server to use a 6 tera precleared drive (i used UD preclear) and all I get is is new device it won't foremat the new drive or anything like that.. What am I doing wrong?? Quote Link to comment
Kilrah Posted January 20, 2023 Share Posted January 20, 2023 8 hours ago, thorneo said: I have tried numerous times to get my server to use a 6 tera precleared drive (i used UD preclear) and all I get is is new device it won't foremat the new drive or anything like that.. What am I doing wrong?? What unraid version? Quote Link to comment
thorneo Posted January 20, 2023 Share Posted January 20, 2023 3 hours ago, Kilrah said: What unraid version? UNRAID 6.11.5 and ALL addons up to date Quote Link to comment
Kilrah Posted January 20, 2023 Share Posted January 20, 2023 So what did you do with that precleared drive? Post screenshot of main page Quote Link to comment
thorneo Posted January 20, 2023 Share Posted January 20, 2023 9 hours ago, Kilrah said: So what did you do with that precleared drive? Post screenshot of main page All it says when I add it is new device. It will not let me format or start the raid.. Quote Link to comment
Kilrah Posted January 21, 2023 Share Posted January 21, 2023 35 minutes ago, thorneo said: It will not let me format or start the raid.. It will say why next to the start button but you cropped that out. Quote Link to comment
thorneo Posted January 21, 2023 Share Posted January 21, 2023 (edited) 4 hours ago, Kilrah said: It will say why next to the start button but you cropped that out. I will take an other with it and post that here . Edited January 21, 2023 by thorneo I can't spell Quote Link to comment
thorneo Posted January 21, 2023 Share Posted January 21, 2023 here is what it says at the bottom where the start button is.. Quote Link to comment
trurl Posted January 21, 2023 Share Posted January 21, 2023 1 hour ago, thorneo said: here is what it says It says the disk assigned as parity is not the largest. No data disk can be larger than any parity disk. Attach diagnostics to your NEXT post in this thread. Quote Link to comment
Kilrah Posted January 21, 2023 Share Posted January 21, 2023 (edited) 5 hours ago, thorneo said: I will take an other with it and post that here . You added a 6TB data drive which requires that neither parity1 or parity2 be smaller than 6TB, but you have 4TB for parity2. See https://wiki.unraid.net/Manual/Storage_Management#Parity_Swap Edited January 21, 2023 by Kilrah 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.