November 29, 201213 yr It just sit's there.... I know the script works because I was able to preclear a 1.5TB drive earlier this week. Earlier today I let it run for about 4 hours, and nothing..... root@Tower:/boot# ./preclear_disk.sh -A /dev/hde Pre-Clear unRAID Disk /dev/hde ################################################################## 1.13 Device Model: ST3000DM001-9YN166 Serial Number: Z1F0S58F Firmware Version: CC4B User Capacity: 3,000,592,982,016 bytes WARNING: GPT (GUID Partition Table) detected on '/dev/hde'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/hde: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 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/hde1 1 4294967295 2147483647+ ee GPT ######################################################################## invoked as ./preclear_disk.sh -A /dev/hde ######################################################################## (-A option elected, partition will start on sector 64) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/hde = cycle 1 of 1, partition start on sector 1 = Disk Pre-Read in progress: 0% complete = ( 0 bytes of 3,000,592,982,016 read ) = = = = = = = = = = Disk Temperature: 33C, Elapsed Time: 0:00:01 thanks! -Marcus
November 29, 201213 yr Author Ended up formatting the drive, and all of the sudden now it is running. It's running at 1.1MB/s, but I also have a parity check going with the 4 drives in the array and the parity drive. I'll keep it running and see what it does. thanks!
November 30, 201213 yr I had a somewhat similar situation with a WD 3TB green drive. It would run at 100MB/s on the pre-read until about half the drive was read and then lockup on two different boxes. So I RMA'd the drive to the Retailer for replacement. The replacement did the same thing but at a different % complete even when using the -b, -r and -w commands to limit the memory usage. So I removed it and did one last test before RMA'ing again - I did a long Windows format. When that completed I took a shot and tried a 3 cycle pre-clear. It ran to completion with a time of 94:40:05 with no sector problems so only 10 hours more than the 3TB Red I did a couple of weeks earlier. Not sure why there was a problem I've never had the problem before or since on the same pre-clear station. So long store short. If I do get the problem again I'm going to do a write only first to the whole disk then start a regular pre-clear cycle series.
December 1, 201213 yr Author I had a somewhat similar situation with a WD 3TB green drive. It would run at 100MB/s on the pre-read until about half the drive was read and then lockup on two different boxes. So I RMA'd the drive to the Retailer for replacement. The replacement did the same thing but at a different % complete even when using the -b, -r and -w commands to limit the memory usage. So I removed it and did one last test before RMA'ing again - I did a long Windows format. When that completed I took a shot and tried a 3 cycle pre-clear. It ran to completion with a time of 94:40:05 with no sector problems so only 10 hours more than the 3TB Red I did a couple of weeks earlier. Not sure why there was a problem I've never had the problem before or since on the same pre-clear station. So long store short. If I do get the problem again I'm going to do a write only first to the whole disk then start a regular pre-clear cycle series. Well, figured out a lot in the last 36 hours. Pulled the drive, took my bedroom HTPC, booted off of a unraid install, and precleared the drive there with no issues. It turns out the SATA Controller I purchased, SYBAUSA - SY-PEX40013, has 2 SATA II ports, and 2 SATA I ports. I didn't read the fine print and the Parity drive and cache drive were connected to the SATA I Ports. So now, I've only got the parity drive connected to SATA II, disconnected the cache drive, and am using neither of the SATA I ports. I'm still seing some issues, it looks like the drive is being dropped and then coming back up. I've swapped out power supplies so I'm pretty sure it's not that. Perhaps it's just the card that's bad? Can someone verify the things I'm seing toward the end of this syslog are not right? My next step may just be going out and either purchasing a motherboard with 6 x SATA II ports, or buying the SuperMicro 8 x SATA II via 2 SAS Connections. Granted it's $160 after card and cables.... but I'm assuming I'll be better off and will have room for growth. Current board has 4 x SATA II. Nov 30 22:55:48 Tower kernel: REISERFS (device md2): checking transaction log (md2) Nov 30 22:55:48 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Nov 30 22:55:48 Tower emhttp: shcmd (22): chmod 770 '/mnt/disk2' Nov 30 22:55:48 Tower emhttp: shcmd (23): chown nobody:users '/mnt/disk2' Nov 30 22:55:48 Tower emhttp: shcmd (24): mkdir /mnt/disk3 Nov 30 22:55:48 Tower emhttp: shcmd (25): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 |& logger Nov 30 22:55:48 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Nov 30 22:55:48 Tower kernel: REISERFS (device md3): using ordered data mode Nov 30 22:55:48 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 22:55:48 Tower kernel: REISERFS (device md3): checking transaction log (md3) Nov 30 22:55:48 Tower kernel: REISERFS (device md3): Using r5 hash to sort names Nov 30 22:55:48 Tower emhttp: shcmd (26): chmod 770 '/mnt/disk3' Nov 30 22:55:48 Tower emhttp: shcmd (27): chown nobody:users '/mnt/disk3' Nov 30 22:55:48 Tower emhttp: shcmd (28): mkdir /mnt/disk4 Nov 30 22:55:48 Tower emhttp: shcmd (29): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md4 /mnt/disk4 |& logger Nov 30 22:55:48 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal Nov 30 22:55:48 Tower kernel: REISERFS (device md4): using ordered data mode Nov 30 22:55:48 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 22:55:48 Tower kernel: REISERFS (device md4): checking transaction log (md4) Nov 30 22:55:48 Tower kernel: REISERFS (device md4): Using r5 hash to sort names Nov 30 22:55:48 Tower emhttp: shcmd (30): chmod 770 '/mnt/disk4' Nov 30 22:55:48 Tower emhttp: shcmd (31): chown nobody:users '/mnt/disk4' Nov 30 22:55:48 Tower emhttp: shcmd (32): mkdir /mnt/disk5 Nov 30 22:55:48 Tower emhttp: shcmd (33): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 |& logger Nov 30 22:55:48 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal Nov 30 22:55:48 Tower kernel: REISERFS (device md5): using ordered data mode Nov 30 22:55:48 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 22:55:48 Tower kernel: REISERFS (device md5): checking transaction log (md5) Nov 30 22:55:48 Tower kernel: REISERFS (device md5): Using r5 hash to sort names Nov 30 22:55:48 Tower emhttp: shcmd (34): chmod 770 '/mnt/disk5' Nov 30 22:55:48 Tower emhttp: shcmd (35): chown nobody:users '/mnt/disk5' Nov 30 22:55:49 Tower emhttp: shcmd (36): mkdir /mnt/user Nov 30 22:55:49 Tower emhttp: shcmd (37): /usr/local/sbin/shfs /mnt/user -disks 2097150 -o noatime,big_writes,allow_other,default_permissions,use_ino Nov 30 22:55:49 Tower emhttp: shcmd (38): crontab -c /etc/cron.d -d &> /dev/null Nov 30 22:55:49 Tower emhttp: shcmd (39): /usr/local/sbin/emhttp_event disks_mounted Nov 30 22:55:49 Tower emhttp_event: disks_mounted Nov 30 22:55:49 Tower emhttp: shcmd (40): :>/etc/samba/smb-shares.conf Nov 30 22:55:49 Tower emhttp: shcmd (41): cp /etc/exports- /etc/exports Nov 30 22:55:49 Tower emhttp: shcmd (42): echo '/mnt/user/ISO -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports Nov 30 22:55:49 Tower emhttp: Restart SMB... Nov 30 22:55:49 Tower emhttp: shcmd (43): killall -HUP smbd Nov 30 22:55:49 Tower emhttp: shcmd (44): ps axc | grep -q rpc.mountd Nov 30 22:55:49 Tower emhttp: _shcmd: shcmd (44): exit status: 1 Nov 30 22:55:49 Tower emhttp: Start NFS... Nov 30 22:55:49 Tower emhttp: shcmd (45): /etc/rc.d/rc.nfsd start |& logger Nov 30 22:55:49 Tower logger: Starting NFS server daemons: Nov 30 22:55:49 Tower logger: /usr/sbin/exportfs -r Nov 30 22:55:49 Tower logger: /usr/sbin/rpc.nfsd 8 Nov 30 22:55:49 Tower logger: /usr/sbin/rpc.mountd Nov 30 22:55:49 Tower mountd[1985]: Kernel does not have pseudo root support. Nov 30 22:55:49 Tower mountd[1985]: NFS v4 mounts will be disabled unless fsid=0 Nov 30 22:55:49 Tower mountd[1985]: is specfied in /etc/exports file. Nov 30 22:55:49 Tower emhttp: shcmd (46): /usr/local/sbin/emhttp_event svcs_restarted Nov 30 22:55:49 Tower emhttp_event: svcs_restarted Nov 30 22:55:49 Tower kernel: sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both Nov 30 22:56:07 Tower in.telnetd[1990]: connect from 192.168.1.3 (192.168.1.3) Nov 30 22:56:08 Tower login[1991]: invalid password for 'UNKNOWN' on '/dev/pts/0' from 'new-host.home' Nov 30 22:56:11 Tower login[1991]: ROOT LOGIN on '/dev/pts/0' from 'new-host.home' root@Tower:/var/log# tail -f /var/log/syslog Nov 30 22:55:49 Tower emhttp: shcmd (46): /usr/local/sbin/emhttp_event svcs_restarted Nov 30 22:55:49 Tower emhttp_event: svcs_restarted Nov 30 22:55:49 Tower kernel: sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both Nov 30 22:56:07 Tower in.telnetd[1990]: connect from 192.168.1.3 (192.168.1.3) Nov 30 22:56:08 Tower login[1991]: invalid password for 'UNKNOWN' on '/dev/pts/0' from 'new-host.home' Nov 30 22:56:11 Tower login[1991]: ROOT LOGIN on '/dev/pts/0' from 'new-host.home' Nov 30 22:58:37 Tower kernel: mdcmd (23): check CORRECT Nov 30 22:58:37 Tower kernel: md: recovery thread woken up ... Nov 30 22:58:37 Tower kernel: md: recovery thread checking parity... Nov 30 22:58:37 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks. ^[[A Nov 30 22:59:02 Tower kernel: md: parity incorrect: 4539784 Nov 30 22:59:04 Tower kernel: md: parity incorrect: 4807336 Nov 30 22:59:08 Tower kernel: md: parity incorrect: 5365616 Nov 30 22:59:34 Tower kernel: ata7.00: exception Emask 0x32 SAct 0x0 SErr 0x0 action 0xe frozen Nov 30 22:59:34 Tower kernel: ata7.00: irq_stat 0xffffffff, unknown FIS 00000000 00000000 00000000 00000000, host bus Nov 30 22:59:34 Tower kernel: ata7.00: failed command: READ DMA EXT Nov 30 22:59:34 Tower kernel: ata7.00: cmd 25/00:00:78:37:92/00:04:00:00:00/e0 tag 0 dma 524288 in Nov 30 22:59:34 Tower kernel: res 50/00:00:77:3b:92/00:00:00:00:00/e0 Emask 0x32 (host bus error) Nov 30 22:59:34 Tower kernel: ata7.00: status: { DRDY } Nov 30 22:59:34 Tower kernel: ata7: hard resetting link Nov 30 22:59:35 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 30 22:59:35 Tower kernel: ata7.00: configured for UDMA/133 Nov 30 22:59:35 Tower kernel: ata7: EH complete Nov 30 23:00:27 Tower kernel: ata7: illegal qc_active transition (00000001->ffffffff) Nov 30 23:00:27 Tower kernel: ata7.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 30 23:00:27 Tower kernel: ata7.00: failed command: READ DMA EXT Nov 30 23:00:27 Tower kernel: ata7.00: cmd 25/00:00:10:9b:28/00:04:01:00:00/e0 tag 0 dma 524288 in Nov 30 23:00:27 Tower kernel: res 50/00:00:0f:9f:28/00:00:01:00:00/e0 Emask 0x2 (HSM violation) Nov 30 23:00:27 Tower kernel: ata7.00: status: { DRDY } Nov 30 23:00:27 Tower kernel: ata7: hard resetting link Nov 30 23:00:27 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 30 23:00:27 Tower kernel: ata7.00: configured for UDMA/133 Nov 30 23:00:27 Tower kernel: ata7: EH complete Nov 30 23:00:34 Tower kernel: ata7: illegal qc_active transition (00000001->ffffffff) Nov 30 23:00:34 Tower kernel: ata7.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 30 23:00:34 Tower kernel: ata7.00: failed command: READ DMA EXT Nov 30 23:00:34 Tower kernel: ata7.00: cmd 25/00:00:28:78:3b/00:04:01:00:00/e0 tag 0 dma 524288 in Nov 30 23:00:34 Tower kernel: res 50/00:00:27:7c:3b/00:00:01:00:00/e0 Emask 0x2 (HSM violation) Nov 30 23:00:34 Tower kernel: ata7.00: status: { DRDY } Nov 30 23:00:34 Tower kernel: ata7: hard resetting link Nov 30 23:00:35 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 30 23:00:35 Tower kernel: ata7.00: configured for UDMA/133 Nov 30 23:00:35 Tower kernel: ata7: EH complete Nov 30 23:03:31 Tower kernel: ata8: illegal qc_active transition (00000001->ffffffff) Nov 30 23:03:31 Tower kernel: ata8.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 30 23:03:31 Tower kernel: ata8.00: failed command: READ DMA EXT Nov 30 23:03:31 Tower kernel: ata8.00: cmd 25/00:00:88:c6:40/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 30 23:03:31 Tower kernel: res 50/00:00:87:ca:40/00:00:03:00:00/e0 Emask 0x2 (HSM violation) Nov 30 23:03:31 Tower kernel: ata8.00: status: { DRDY } Nov 30 23:03:31 Tower kernel: ata8: hard resetting link Nov 30 23:03:32 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 30 23:03:32 Tower kernel: ata8.00: configured for UDMA/133 Nov 30 23:03:32 Tower kernel: ata8: EH complete Nov 30 23:03:56 Tower kernel: ata8: illegal qc_active transition (00000001->ffffffff) Nov 30 23:03:56 Tower kernel: ata8.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 30 23:03:56 Tower kernel: ata8.00: failed command: READ DMA EXT Nov 30 23:03:56 Tower kernel: ata8.00: cmd 25/00:00:58:a3:88/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 30 23:03:56 Tower kernel: res 50/00:00:57:a7:88/00:00:03:00:00/e0 Emask 0x2 (HSM violation) Nov 30 23:03:56 Tower kernel: ata8.00: status: { DRDY } Nov 30 23:03:56 Tower kernel: ata8: hard resetting link Nov 30 23:03:57 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 30 23:03:57 Tower kernel: ata8.00: configured for UDMA/133 Nov 30 23:03:57 Tower kernel: ata8: EH complete Nov 30 23:04:20 Tower kernel: ata8.00: exception Emask 0x32 SAct 0x0 SErr 0x0 action 0xe frozen Nov 30 23:04:20 Tower kernel: ata8.00: irq_stat 0xffffffff, unknown FIS 00000000 00000000 00000000 00000000, host bus Nov 30 23:04:20 Tower kernel: ata8.00: failed command: READ DMA EXT Nov 30 23:04:20 Tower kernel: ata8.00: cmd 25/00:00:b0:20:cd/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 30 23:04:20 Tower kernel: res 50/00:00:af:24:cd/00:00:03:00:00/e0 Emask 0x32 (host bus error) Nov 30 23:04:20 Tower kernel: ata8.00: status: { DRDY } Nov 30 23:04:20 Tower kernel: ata8: hard resetting link Nov 30 23:04:21 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 30 23:04:21 Tower kernel: ata8.00: configured for UDMA/133 Nov 30 23:04:21 Tower kernel: ata8: EH complete
December 1, 201213 yr Author So I switched motherboards to one with six sata ports onboard and things are MUCH better. No crashes since, parity checks happen between 100-126MB/s. Thanks!
Archived
This topic is now archived and is closed to further replies.