November 7, 201312 yr I'm trying to preclear 4 preclear 3TB drives, 2 on each of 2 near-identical unRAID setups. All 4 pass smart tests, but give the same errors. There are no errors from after the time the preclear script is run in the syslog. The closest thing to an error in the log is an 'known partition table message'. (after the Nov 6 22:15:45 Server2 in.telnetd[8356]: connect from 192.168.0.3 (192.168.0.3) (Routine) Nov 6 22:15:46 Server2 in.telnetd[8396]: connect from 192.168.0.3 (192.168.0.3) (Routine) lines) The putty screen gives: =========================================================================== = unRAID server Pre-Clear disk /dev/sdl = 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 = Elapsed Time: 10:33:44 ============================================================================ == == SORRY: Disk /dev/sdl MBR could NOT be precleared == ============================================================================ 0000000 0000 0000 0000 0000 0000 0000 0000 0000 1+0 records in 1+0 records out 512 bytes (512 B) copied* , 0.000356474 s, 1.4 MB/s 0000700 0000 0000 0000 003f 0000 0a37 15d5 0000 0000720 0000 0000 0000 0000 0000 0000 0000 0000 * 0000760 0000 0000 0000 0000 0000 0000 0000 5c5c 0001000 root@Server2:/boot/custom/etc/init.d# All 4 errors are variations on that. Whats going wrong? The drives are new, and according to the syslog seem to be passing SMART tests. I thought it might be a memory error, since cache_dirs is running, but I have plenty of ram, and the syslog shows no memory errors. Perhaps because i didn't include the -A flag when running preclear? I thought i didn't need to do this anymore? I can just try and use the drives without preclearing, but would really like to preclear first and figure out whats going on if possible... Syslog from one of the computers attached. Other syslog is more of the same. Thanks for the help, Zithras syslog-2013-11-07.txt
November 7, 201312 yr I'd make sure you have the latest version of Preclear Disk, and also have 4K-alligned under disk settings in unRAID set. My guess is either it's outdated, or set wrong in unRAID so it's attempting to preclear it as a old drive. You shouldn't need any parameters on the newest version. Just run it as: /boot/preclear_disk.sh /dev/XXX (XXX = SDL in the case above)
November 8, 201312 yr Author And, of course, its the obvious solution. I downloaded the new preclear before installing 5.0, but checking the last edit date on my flashdrives, apparently saw it already there and forgot to copy over the new version while upgrading. Lets see if this works...
November 8, 201312 yr And, of course, its the obvious solution. I downloaded the new preclear before installing 5.0, but checking the last edit date on my flashdrives, apparently saw it already there and forgot to copy over the new version while upgrading. Lets see if this works... You were using a VERY VERY old version of the preclear script.
November 9, 201312 yr Author Yup all fixed now. I hate it when I spend hours trying to figure out a problem, eventually resort to asking for help, then realize minutes after I posted that it was something obvious >.< I think the script that failed dated back to 2009 or so
Archived
This topic is now archived and is closed to further replies.