April 1, 201412 yr I've done a bunch of testing and concluded that preclear is not writing a valid preclear signature on some drives in unRAID 6. My tests included: A 4TB disk precleared in 6.0 beta4 tests as NOT precleared in both 6.0b4 and 5.05. I precleared with all plugins removed, but still had the screen package installed and I had booted into unRAID with Xen and IronicBander's archVM running. A 250GB disk precleared in 6.0 beta4 tests as precleared, even with Xen and my selection of plugins installed. I also modified the preclear_disk.sh script to be able to create very dangerous disks that have the preclear signature without actually clearing the whole disk. I call it fake_clear and it allows me to test much quicker. A 250GB disk fake_cleared in 6.0b4 tests as precleared in both 6.0b4 and 5.05. A 4TB disk fake_cleared in 6.0b4 tests as NOT precleared in both 6.0b4 and 5.05. I have run the fake_clear in many 6.0b4 boot configurations including Safe Mode without Xen and with the default go file. A 4TB disk fake_cleared in 5.05 tests as precleared in both 6.0b4 and 5.05. I would have guessed the problem is related to disks over 2TB, but tr0910's results seem to contradict this. Freddie, maybe you can dump the first 4K of a disk precleared using 5.0.5, and the first 4K of an identical disk precleared using 6.0b4, and post them. If what you say is true, the preclear script is setting the signature in a way that is not compatible for 64 bit. Maybe we can get Joe L. to take a look if he has that data.
April 1, 201412 yr Freddie, maybe you can dump the first 4K of a disk precleared using 5.0.5, and the first 4K of an identical disk precleared using 6.0b4, and post them. I'll work on those 4K dumps. I have the preclear test output available right now. It shows which tests failed and might be more valuable to Joe L.: Pre-Clear unRAID Disk /dev/sde ################################################################## 1.14 Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: Z3006WWS LU WWN Device Id: 5 000c50 04fce621c Firmware Version: CC51 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Disk /dev/sde: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 29344703 3300901822 1635778560 0 Empty Partition 1 does not start on physical sector boundary. ######################################################################## failed test 3 00000 00195 00191 00195 failed test 5 failed test 6 ========================================================================1.14 == == Disk /dev/sde is NOT precleared == 29344703 3271557120 4294967295 ============================================================================ And just in case you want to see a successful test (fake_clear in 5.05): Pre-Clear unRAID Disk /dev/sde ################################################################## 1.14 Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: Z3006WWS LU WWN Device Id: 5 000c50 04fce621c Firmware Version: CC51 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Disk /dev/sde: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 1 4294967295 2147483647+ 0 Empty Partition 1 does not start on physical sector boundary. ######################################################################## ========================================================================1.14 == == DISK /dev/sde IS PRECLEARED with a GPT Protective MBR == ============================================================================ And as I was posting this, I noticed the partition start value. That should be a big red flag.
April 1, 201412 yr So I did another preclear pass with 1.14 on R6b4 with Xen loaded just as it was 2 days ago when I last did these 3 drives. The results this time are as follows: (last time I ran it, one of the 750's precleared successfully and was added without delay and the GUI screen showed that the other drives had also precleared successfully. This must be new to R6?? ) 750 GB is not precleared (precleared with the -W flag) 750 GB is not precleared (precleared with the -W flag) 1 TB is precleared (precleared with the -n flag) Results of the -t test screen below.... But look at this first??? For the first drive unRaid is going to add it without clearing it??? root@TowerXen:/boot# preclear_disk.sh -t /dev/sda Pre-Clear unRAID Disk /dev/sda ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721010KLA330 Serial Number: GTF000PBH2VZHF LU WWN Device Id: 5 000cca 21ecf658a Firmware Version: GKAOAB0A User Capacity: 1,000,203,804,160 bytes [1.00 TB] Disk /dev/sda: 1000.2 GB, 1000203804160 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953523055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 64 1953523054 976761495+ 0 Empty ######################################################################## ========================================================================1.14 == == DISK /dev/sda IS PRECLEARED with a starting sector of 64 == ============================================================================ root@TowerXen:/boot# preclear_disk.sh -t /dev/sdd Pre-Clear unRAID Disk /dev/sdd ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721075KLA330 Serial Number: GTF202P8GGB6EF LU WWN Device Id: 5 000cca 215c68744 Firmware Version: GK8OAB0A User Capacity: 750,156,374,016 bytes [750 GB] Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 63 1416016384 708008161 0 Empty ######################################################################## failed test 6 ========================================================================1.14 == == Disk /dev/sdd is NOT precleared == 63 1416016322 1465149105 ============================================================================ root@TowerXen:/boot# preclear_disk.sh -t /dev/sdc Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721075KLA330 Serial Number: GTF202P8GGGMXF LU WWN Device Id: 5 000cca 215c69429 Firmware Version: GK8OAB0A User Capacity: 750,156,374,016 bytes [750 GB] Disk /dev/sdc: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 1416016129 708008033 0 Empty ######################################################################## failed test 6 ========================================================================1.14 == == Disk /dev/sdc is NOT precleared == 64 1416016066 1465149104 ============================================================================
April 1, 201412 yr Author So I did another preclear pass with 1.14 on R6b4 with Xen loaded just as it was 2 days ago when I last did these 3 drives. The results this time are as follows: (last time I ran it, one of the 750's precleared successfully and was added without delay and the GUI screen showed that the other drives had also precleared successfully. This must be new to R6?? ) 750 GB is not precleared (precleared with the -W flag) 750 GB is not precleared (precleared with the -W flag) 1 TB is precleared (precleared with the -n flag) Results of the -t test screen below.... But look at this first??? For the first drive unRaid is going to add it without clearing it??? root@TowerXen:/boot# preclear_disk.sh -t /dev/sda Pre-Clear unRAID Disk /dev/sda ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721010KLA330 Serial Number: GTF000PBH2VZHF LU WWN Device Id: 5 000cca 21ecf658a Firmware Version: GKAOAB0A User Capacity: 1,000,203,804,160 bytes [1.00 TB] Disk /dev/sda: 1000.2 GB, 1000203804160 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953523055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 64 1953523054 976761495+ 0 Empty ######################################################################## ========================================================================1.14 == == DISK /dev/sda IS PRECLEARED with a starting sector of 64 == ============================================================================ root@TowerXen:/boot# preclear_disk.sh -t /dev/sdd Pre-Clear unRAID Disk /dev/sdd ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721075KLA330 Serial Number: GTF202P8GGB6EF LU WWN Device Id: 5 000cca 215c68744 Firmware Version: GK8OAB0A User Capacity: 750,156,374,016 bytes [750 GB] Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 63 1416016384 708008161 0 Empty ######################################################################## failed test 6 ========================================================================1.14 == == Disk /dev/sdd is NOT precleared == 63 1416016322 1465149105 ============================================================================ root@TowerXen:/boot# preclear_disk.sh -t /dev/sdc Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.14 Model Family: Hitachi Deskstar 7K1000 Device Model: Hitachi HDS721075KLA330 Serial Number: GTF202P8GGGMXF LU WWN Device Id: 5 000cca 215c69429 Firmware Version: GK8OAB0A User Capacity: 750,156,374,016 bytes [750 GB] Disk /dev/sdc: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 1416016129 708008033 0 Empty ######################################################################## failed test 6 ========================================================================1.14 == == Disk /dev/sdc is NOT precleared == 64 1416016066 1465149104 ============================================================================ I may be wrong, but I think unRAID treats disks differently whether you have a parity drive or not. If you look at the note from garycase you can see that if there is no parity drive unRAID doesn't really need to check that the drives are zeroed out correctly as there is no current parity values to get screwed up. That's correct. It wasn't a parity check -- it was the initial parity sync. Pre-clearing has NO impact on whether or not a parity check is required when you add the parity drive. The sole purpose of a pre-clear (other than confidence testing of the drive) is to allow the drive to be added to a parity-protected array without the need to clear the drive. The pre-clear "signature" tells UnRAID that the drive has been completed zeroed -- and since UnRAID then "knows" it's all zeroes, it also knows that adding the drive doesn't require any changes to the parity drive for it to remain valid. That's the reason, by the way, that UnRAID wipes out the pre-clear "signature" -- it writes zeroes over it so the drive is truly all zeroes. Pre-clearing is completely unnecessary (again, except as a confidence check for the drive) if you're adding a drive to a system without a parity drive; and it's also irrelevant on a parity drive, since a parity sync will be required as soon as it's assigned to that role. I think any testing you are doing against this issue will have to have an assigned parity drive for it to be valid. Hopefully garycase or someone else can confirm my understanding here (though I am pretty sure I'm right).
April 1, 201412 yr I think any testing you are doing against this issue will have to have an assigned parity drive for it to be valid. Hopefully garycase or someone else can confirm my understanding here (though I am pretty sure I'm right). That would make sense and lower my concern, but it doesn't explain why the image shows that unRaid thinks the other 2 were precleared successfully. This is contrary to what the -t test shows for one of these 2 drives. Now why one was successful and the other 2 weren't is the final puzzle. I haven't even formatted disk1 yet just in case somebody needs more info about the current state of these drives.
April 2, 201412 yr The issue seems to be setting a proper preclear signature on drives over2.2TB on the 6.X versions of unRAID. probably a byte-order issue on the 64 bit OS vs the 32 bit OS. To help, please attach the output of dd if=/dev/sdX count=195 | od -c -A d | sed 30q for each (good and bad) together with the output of fdisk -l /dev/sdX
April 2, 201412 yr The issue seems to be setting a proper preclear signature on drives over2.2TB on the 6.X versions of unRAID. probably a byte-order issue on the 64 bit OS vs the 32 bit OS. To help, please attach the output of dd if=/dev/sdX count=195 | od -c -A d | sed 30q for each (good and bad) together with the output of fdisk -l /dev/sdX Here is the output from 3 disks, none of which have been touched since preclearing : ******* First the drive that precleared fine a 1tb ******** root@TowerXen:/boot# dd if=/dev/sda count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0187064 s, 5.3 MB/s * 0000448 \0 \0 \0 \0 \0 \0 @ \0 \0 \0 / e p t \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sda Disk /dev/sda: 1000.2 GB, 1000203804160 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953523055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 64 1953523054 976761495+ 0 Empty ******* Second the drive that didn't preclear a 750tb ******** * (This drive is selected as disk1, but hasn't been formatted yet) * root@TowerXen:/boot# dd if=/dev/sdc count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 11.2735 s, 8.9 kB/s * 0000448 \0 \0 203 \0 \0 \0 @ \0 \0 \0 260 f T W \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdc Disk /dev/sdc: 750.2 GB, 750156374016 bytes 1 heads, 63 sectors/track, 23256336 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 1465149167 732574552 83 Linux root@TowerXen:/boot# ******* Third the drive that didn't preclear a 750tb ******** root@TowerXen:/boot# dd if=/dev/sdd count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0189313 s, 5.3 MB/s * 0000448 \0 \0 \0 \0 \0 \0 ? \0 \0 \0 302 261 f T \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdd Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 63 1416016384 708008161 0 Empty root@TowerXen:/boot#
April 2, 201412 yr Author I just finished preclearing a drive using bjp's version 15b of the script and the first thing I've run is preclear -t: root@CydStorage:/boot# preclear_disk15b.sh -t /dev/sdo Pre-Clear unRAID Disk /dev/sdo ################################################################## 1.15b Device Model: WDC WD40EZRX-00SPEB0 Serial Number: WD-WMC4E0043050 LU WWN Device Id: 5 0014ee 25ec57909 Firmware Version: 80.00A80 User Capacity: 4,000,753,476,096 bytes [4.00 TB] Disk /dev/sdo: 4000.8 GB, 4000753476096 bytes 255 heads, 63 sectors/track, 486397 cylinders, total 7813971633 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdo1 29344703 3300901822 1635778560 0 Empty Partition 1 does not start on physical sector boundary. ######################################################################## failed test 3 00000 00195 00191 00195 failed test 5 failed test 6 ========================================================================1.15b == == Disk /dev/sdo is NOT precleared == 29344703 3271557120 4294967295 ============================================================================ root@CydStorage:/boot# Here are the results of the commands Joe requested: root@CydStorage:/boot# dd if=/dev/sdo count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00450047 s, 22.2 MB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 002 \0 \0 303 277 303 277 303 277 001 \0 \0 \0 303 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@CydStorage:/boot# root@CydStorage:/boot# fdisk -l /dev/sdo Disk /dev/sdo: 4000.8 GB, 4000753476096 bytes 255 heads, 63 sectors/track, 486397 cylinders, total 7813971633 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdo1 29344703 3300901822 1635778560 0 Empty Partition 1 does not start on physical sector boundary. root@CydStorage:/boot#
April 2, 201412 yr I isolated the problem down to the code in preclear that generates the partition data. The printf statement in awk is used to convert a byte value to a character. In unRAID 6, it seems that any byte over 127 (or 0x7f) is converted into a 2 byte character. For example, in unRAID 6: root@uwer:~# awk 'BEGIN{ printf ("%c",0x80)}' | hexdump 0000000 80c2 0000002 root@uwer:~# awk 'BEGIN{ printf ("%c",0x7f)}' | hexdump 0000000 007f 0000001 Compared to unRAID 5: root@Tower:~# awk 'BEGIN{ printf ("%c",0x80)}' | hexdump 0000000 0080 0000001 root@Tower:~# awk 'BEGIN{ printf ("%c",0x7f)}' | hexdump 0000000 007f 0000001 I think this results in obviously wrong partition data on all disks larger than 2.2TB and also some disks on the smaller side. I also think it could result in more subtle problems on smaller disks. I am starting to think about ways to generate partition data without using awk.
April 2, 201412 yr Hmmm. Interesting. Wonder why its only an issue sometimes? My 1tb drive worked but my 2 750gb ones didn't. Sent from my Nexus 7 using Tapatalk
April 2, 201412 yr Hmmm. Interesting. Wonder why its only an issue sometimes? My 1tb drive worked but my 2 750gb ones didn't. Because sometimes the values in the partition data do not have any bytes over 127.
April 2, 201412 yr A possible fix is to use the environment variable LC_CTYPE=C In unRAID 6: root@uwer:~# LC_CTYPE=C awk 'BEGIN{ printf ("%c",0x80)}' | hexdump 0000000 0080 0000001 My understanding is that LC_CTYPE=C specifies ascii character encoding instead of UTF-8. It worked with my fake_clear script on a 4TB drive. If anyone wants to try it out for real you can execute the preclear script as normal except prepend the LC_CTYPE=C LC_CTYPE=C preclear_disk.sh /dev/sdX
April 2, 201412 yr A possible fix is to use the environment variable LC_CTYPE=C In unRAID 6: root@uwer:~# LC_CTYPE=C awk 'BEGIN{ printf ("%c",0x80)}' | hexdump 0000000 0080 0000001 My understanding is that LC_CTYPE=C specifies ascii character encoding instead of UTF-8. It worked with my fake_clear script on a 4TB drive. If anyone wants to try it out for real you can execute the preclear script as normal except prepend the LC_CTYPE=C LC_CTYPE=C preclear_disk.sh /dev/sdX Is there a way that could be set in the preclear script itself rather than affecting the command line? Or could it go in the standard go script?
April 2, 201412 yr Is there a way that could be set in the preclear script itself rather than affecting the command line? I assume yes - either applied at specific lines or to the whole script. I was going to let Joe L. incorporate it, but I can work on it if he wants. Or could it go in the standard go script? I wouldn't. It has the possibility to effect too many other things.
April 2, 201412 yr If anyone wants to try it out for real you can execute the preclear script as normal except prepend the LC_CTYPE=C LC_CTYPE=C preclear_disk.sh /dev/sdX Just re-ran the script on one of the 750's that failed before using your "LC_CTYPE=C preclear_disk.sh /dev/sdX" . I now get a successful response from the -t option and the output JoeL asked for is below. (using v6b4 and latest 1.14 preclear) root@TowerXen:/boot# dd if=/dev/sdd count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0254061 s, 3.9 MB/s * 0000448 \0 \0 \0 \0 \0 \0 @ \0 \0 \0 260 f T W \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdd Disk /dev/sdd: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 64 1465149167 732574552 0 Empty root@TowerXen:/boot#
April 3, 201412 yr Just re-ran the script on one of the 750's that failed before using your "LC_CTYPE=C preclear_disk.sh /dev/sdX" . I now get a successful response from the -t option and the output JoeL asked for is below. (using v6b4 and latest 1.14 preclear) And I did the 2nd 750gb that failed to preclear. It too works... Output for Joe L below. root@TowerXen:/boot# dd if=/dev/sdc count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 , 0.0255745 s, 3.9 MB/s * 0000448 \0 \0 \0 \0 \0 \0 @ \0 \0 \0 260 f T W \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@TowerXen:/boot# fdisk -l /dev/sdc Disk /dev/sdc: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 1465149167 732574552 0 Empty root@TowerXen:/boot#
April 4, 201412 yr Author I re-ran a preclear again on my 4TB drive using bjp's 15b script and using the LC_CTYPE=C option and everything finished properly and the drive shows as precleared (finally). root@CydStorage:/boot# preclear_disk15b.sh -t /dev/sdo Pre-Clear unRAID Disk /dev/sdo ################################################################## 1.15b Device Model: WDC WD40EZRX-00SPEB0 Serial Number: WD-WMC4E0043050 LU WWN Device Id: 5 0014ee 25ec57909 Firmware Version: 80.00A80 User Capacity: 4,000,753,476,096 bytes [4.00 TB] Disk /dev/sdo: 4000.8 GB, 4000753476096 bytes 255 heads, 63 sectors/track, 486397 cylinders, total 7813971633 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdo1 1 4294967295 2147483647+ 0 Empty Partition 1 does not start on physical sector boundary. ######################################################################## ========================================================================1.15b == == DISK /dev/sdo IS PRECLEARED with a GPT Protective MBR == ============================================================================ root@CydStorage:/boot# root@CydStorage:/boot# fdisk -l /dev/sdo Disk /dev/sdo: 4000.8 GB, 4000753476096 bytes 255 heads, 63 sectors/track, 486397 cylinders, total 7813971633 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdo1 1 4294967295 2147483647+ 0 Empty Partition 1 does not start on physical sector boundary. root@CydStorage:/boot# root@CydStorage:/boot# dd if=/dev/sdo count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 002 \0 \0 377 377 377 001 \0 \0 \0 377 377 377 377 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 , 0.00195718 s, 51.0 MB/s 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 root@CydStorage:/boot# It definitely looks like this fixes the issues on 6.0. Now we just need someone to incorporate it into the actual script (assuming this is the final solution).
April 5, 201412 yr It definitely looks like this fixes the issues on 6.0. Now we just need someone to incorporate it into the actual script (assuming this is the final solution). I can incorporate it...Should be able to do it this weekend. Joe L.
April 9, 201412 yr It definitely looks like this fixes the issues on 6.0. Now we just need someone to incorporate it into the actual script (assuming this is the final solution). I can incorporate it...Should be able to do it this weekend. Joe L. I just saw the preclear post has been updated with version 1.15. Thank you Joe L.
Archived
This topic is now archived and is closed to further replies.