July 2, 201115 yr Hi folks, I'ce been a happy unRAID user for a few months now but I'm having some problems getting preclear to run on a new disk. I'm currently running 5.0-beta7 and my existing shares are all good. I have, however, switched motherboards yesterday and haven't been able to get preclear to run past typing "Yes" at the prompt. My guess is that it's a system issue as preclear exits saying the disk is already precleared in about 2 seconds. I also get a bunch of error messages like this: ./grep: line 3: syntax error near unexpected token `(' ./grep: line 3: `May 11 14:49:08 Tower kernel: Linux version 2.6.36.2-unRAID (root@Develop) (gcc version 4.4.4 (GCC) ) #8 SMP Tue Feb 22 16:29:25 MST 2011' ./preclear_disk.sh: line 960: let: blocks=( / ): syntax error: operand expected (error token is "/ )") ./preclear_disk.sh: line 1025: let: bytes_read=(0 * ): syntax error: operand expected (error token is ")") ./preclear_disk.sh: line 1026: let: br=( * 100): syntax error: operand expected (error token is "* 100)") ./preclear_disk.sh: line 1027: let: percent_read=( / ): syntax error: operand expected (error token is "/ )") ./preclear_disk.sh: line 1032: [: -gt: unary operator expected ./grep: line 1: May: command not found ./grep: line 2: May: command not found ./grep: line 3: syntax error near unexpected token `(' ./grep: line 3: `May 11 14:49:08 Tower kernel: Linux version 2.6.36.2-unRAID (root@Develop) (gcc version 4.4.4 (GCC) ) #8 SMP Tue Feb 22 16:29:25 MST 2011' I'm probably overlooking something real stupid but can't for the life of me think what. Any help would be much appreciated. Thanks, Alex
July 2, 201115 yr What version of the preclear script are you running? Type: preclear_disk.sh -v to see the version. What do you get with: fdisk -l /dev/sdX (where sdX = your drive? ) The error leads me to think the output of fdisk -l was not as expected. Joe L.
July 2, 201115 yr Author Hi Joe, I'm using a freshly downloaded version 1.11. As for fdisk, here's the output for 2 of my disks, of which, sdd is the new one: Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/sdd doesn't contain a valid partition table Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders Units = cylinders of 63 * 512 = 32256 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 2 62016336 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Is it significant that the two disks share the same (null?) identifier, whereas my other disk - the parity - has a non-null identifier? Thanks for your help on this, Alex
Archived
This topic is now archived and is closed to further replies.