jbuszkie
-
Posts
693 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jbuszkie
-
-
I just ran 2 disks single cycle. One disk was fine the other was not so much. Do you agree that this might be an RMA canidate? I'm running a sencond cycle to be sure..
S.M.A.R.T. error count differences detected after pre-clear
note, some 'raw' values may change, but not be an indication of a problem
57c57
< 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
---
> 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5005
66c66
< 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0
---
> 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4648
69c69
< 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
---
> 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 4952
71c71
< 190 Airflow_Temperature_Cel 0x0022 070 070 000 Old_age Always - 30 (Lifetime Min/Max 30/30)
---
> 190 Airflow_Temperature_Cel 0x0022 068 067 000 Old_age Always - 32 (Lifetime Min/Max 30/33)
74c74
< 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
---
> 197 Current_Pending_Sector 0x0012 092 092 000 Old_age Always - 331
78c78
< 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0
---
> 201 Soft_Read_Error_Rate 0x000a 097 097 000 Old_age Always - 228
============================================================================
-
But why the big descrepency with the cycle time? 17 hours vs 28 and 30 hours? I wouldn't think the 7200 vs 5400 would have that much of a difference. I'm running a single drive now again to see how much one drive vs 2 does.
Jim
-
What was your cycle time for a 1.5T disk?
It seemed like yours was in the 17 hour time frame from your screen capture? I would hope that I would get closer to that rather than the 28 hour time frame.
Oh.. And the zeroing took ~5 hours.
-
I wasn't doing anything else with the array.. It was stopped. I was getting parity check speeds of 90-100MBs (parity synch was about 50-60MB/s) with the two drives when I tested that.. That's why I would expect to get something similiar with the pre-read.
Maybe I'll try some dd comands. The preclear cycle for the disks took about 28 hours for one and 30 hours for the other. One was fine and the longer one had some smart errors which I'll post in the other thread.
Jim
-
I've added a temperature readout to the display while pre-clearing a drive. I'm running it through a test now on one of my spare 1.5TB drives. It is writing at about 63MB/s on my old PCI bus based server. I'll run a second test tomorrow, and if nothing odd occurs I'll post a new version of preclear_disk.sh with the enhancement you suggested. (probably on Monday) My script has been running on the 1.5TB drive for about 7 hours and is about through with a third of the writing of zeros. The temperature of the drive has gone from 29 degrees up to 35 degrees.
Joe,
I just got a new unraid MB and CPU and I'm currently testing it with two new Samsung 1.5T drives. I'm preclearing both and I'm not getting nowhere near the speeds you are. If yours was a PCI based system.. Mine is a new pci-e based system. I only have the two drives attached. Syslog says they are runnign in 3.0Gbs... But they are both going at a rate of about 25% every 4 hours for the preread. Even when I just did one drive I was getting 2GB/min ~ 34MB/s. I would expect a lot better than that! Right now I'm getting about 25.6MB/s. Am I missing something. In the log I see:
Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Home page is http://smartmontools.sourceforge.net/ Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: === START OF INFORMATION SECTION === Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Device Model: SAMSUNG HD154UI Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Serial Number: S1Y6J1KS743788 Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Firmware Version: 1AG01118 Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: User Capacity: 1,500,301,910,016 bytes Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Device is: In smartctl database [for details use: -P show] Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: ATA Version is: 8 Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: ATA Standard is: ATA-8-ACS revision 3b Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Local Time is: Fri Aug 21 23:17:43 2009 EDT Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: SMART support is: Available - device has SMART capability. Aug 21 23:17:43 Tower2 preclear_disk-start[14626]: SMART support is: Enabled Aug 21 23:17:43 Tower2 preclear_disk-start[14626]:
What is this -F samsung?
I'm running in AHCI mode set in the bios. Anything else I'm missing?
-
Oh.. Can can this be under-clocked easily to reduce power?
-
Are you still happy with this board? I'm about to pull the trigger on this one...
-
Seems like the code is no good.. It told me it had already been redeemed..
May be oneone else will have better luck.
-
Brainbone,
I've run into a little issue with the script. I was running parity syncs and my drive temps were going up. I stopped getting emails. After I looked into it a little I found out I was supposed to be getting error e-mails. If I commented out the RcptTo field in the cfg file, I started getting the e-mails.
In debug mode it looks like my e-mail server didn't like the format when there was a RcptTo and an ErrorRcptTo. I dove in the script and I commented out the second a=0 in the place where it's building the To: header. That seems to make it work correctly. What are your thoughts?
Jim
-
Update.. I'm still getting the errors in the syslog running the parity synch. I'm not getting any parity synch errors.. just the disk errors..
Would this be something that a disk check would fix.. Or might this be a cable thing? Or is the disk starting to die?
It is next in line for being replaced! Plus I don't like the fact that it seems to be running in UDMA66 which I don't like..
Jim
-
Here's what I just did recently..
I added a new 1T drive as drive5. - fine.
I copied all the files off of disk 3 in preperation for removal.
I zeroed out the drive3 using this thread
I unassigned disk3
When did the set invalidslot thing. It behaved fine. The parity check started and I went to bed. In the morning I checked on it
and I have 240 parity synch issues so I looked at the syslog and this is what I found:
Jul 28 20:10:00 Tower emhttp: shcmd (38): cp /etc/exports- /etc/exports Jul 28 20:10:00 Tower emhttp: shcmd (39): mkdir -m 700 /mnt/user Jul 28 20:10:00 Tower emhttp: shcmd (40): /usr/local/sbin/shfs /mnt/user 1 2000000 Jul 28 20:10:00 Tower emhttp: shcmd (41): mkdir -m 700 /mnt/user0 Jul 28 20:10:00 Tower emhttp: shcmd (42): /usr/local/sbin/shfs /mnt/user0 0 Jul 28 20:10:01 Tower emhttp: shcmd (43): killall -HUP smbd Jul 28 20:10:01 Tower emhttp: shcmd (44): /etc/rc.d/rc.nfsd restart >/dev/null Jul 28 20:33:35 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 20:33:35 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 20:33:35 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 20:33:35 Tower kernel: ata4.00: cmd 25/00:00:8f:c4:7b/00:04:04:00:00/e0 tag 0 dma 524288 in Jul 28 20:33:35 Tower kernel: res 51/04:00:8f:c4:7b/00:04:04:00:00/f0 Emask 0x1 (device error) Jul 28 20:33:35 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 20:33:35 Tower kernel: ata4.00: error: { ABRT } Jul 28 20:33:35 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 20:33:35 Tower kernel: ata4: EH complete Jul 28 20:33:35 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 20:33:35 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 20:33:35 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 20:33:35 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 20:34:10 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 20:34:10 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 20:34:10 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 20:34:10 Tower kernel: ata4.00: cmd 25/00:00:97:f9:99/00:04:04:00:00/e0 tag 0 dma 524288 in Jul 28 20:34:10 Tower kernel: res 51/04:00:97:f9:99/00:04:04:00:00/f0 Emask 0x1 (device error) Jul 28 20:34:10 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 20:34:10 Tower kernel: ata4.00: error: { ABRT } Jul 28 20:34:11 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 20:34:11 Tower kernel: ata4: EH complete Jul 28 20:34:11 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 20:34:11 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 20:34:11 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 20:34:11 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 20:49:01 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 20:49:01 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 20:49:01 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 20:49:01 Tower kernel: ata4.00: cmd 25/00:00:07:5d:7a/00:04:07:00:00/e0 tag 0 dma 524288 in Jul 28 20:49:01 Tower kernel: res 51/04:00:07:5d:7a/00:04:07:00:00/f0 Emask 0x1 (device error) Jul 28 20:49:01 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 20:49:01 Tower kernel: ata4.00: error: { ABRT } Jul 28 20:49:02 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 20:49:02 Tower kernel: ata4: EH complete Jul 28 20:49:02 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 20:49:02 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 20:49:02 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 20:49:02 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 20:58:54 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 20:58:54 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 20:58:54 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 20:58:54 Tower kernel: ata4.00: cmd 25/00:00:57:75:64/00:04:09:00:00/e0 tag 0 dma 524288 in Jul 28 20:58:54 Tower kernel: res 51/04:00:57:75:64/00:04:09:00:00/f0 Emask 0x1 (device error) Jul 28 20:58:54 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 20:58:54 Tower kernel: ata4.00: error: { ABRT } Jul 28 20:58:54 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 20:58:54 Tower kernel: ata4: EH complete Jul 28 20:58:55 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 20:58:55 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 20:58:55 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 20:58:55 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 21:03:17 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 21:03:17 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 21:03:17 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 21:03:17 Tower kernel: ata4.00: cmd 25/00:00:57:c3:3d/00:04:0a:00:00/e0 tag 0 dma 524288 in Jul 28 21:03:17 Tower kernel: res 51/04:00:57:c3:3d/00:04:0a:00:00/f0 Emask 0x1 (device error) Jul 28 21:03:17 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 21:03:17 Tower kernel: ata4.00: error: { ABRT } Jul 28 21:03:17 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 21:03:17 Tower kernel: ata4: EH complete Jul 28 21:03:17 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 21:03:17 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 21:03:17 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 21:03:17 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 21:13:11 Tower emhttp: shcmd (45): /usr/sbin/hdparm -y /dev/hdb >/dev/null Jul 28 21:59:26 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 21:59:26 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 21:59:26 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 21:59:26 Tower kernel: ata4.00: cmd 25/00:00:f7:91:37/00:04:15:00:00/e0 tag 0 dma 524288 in Jul 28 21:59:26 Tower kernel: res 51/04:00:f7:91:37/00:04:15:00:00/f0 Emask 0x1 (device error) Jul 28 21:59:26 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 21:59:26 Tower kernel: ata4.00: error: { ABRT } Jul 28 21:59:27 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 21:59:27 Tower kernel: ata4: EH complete Jul 28 21:59:27 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 21:59:27 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 21:59:27 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 21:59:27 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:05:05 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:05:05 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:05:05 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:05:05 Tower kernel: ata4.00: cmd 25/00:00:27:93:52/00:01:16:00:00/e0 tag 0 dma 131072 in Jul 28 22:05:05 Tower kernel: res 51/04:00:27:93:52/00:01:16:00:00/f0 Emask 0x1 (device error) Jul 28 22:05:05 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:05:05 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:05:05 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 22:05:05 Tower kernel: ata4: EH complete Jul 28 22:05:05 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:05:05 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:05:05 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:05:05 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:35:30 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:35:30 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:35:30 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:35:30 Tower kernel: ata4.00: cmd 25/00:00:a7:58:51/00:04:1c:00:00/e0 tag 0 dma 524288 in Jul 28 22:35:30 Tower kernel: res 51/04:00:a7:58:51/00:04:1c:00:00/f0 Emask 0x1 (device error) Jul 28 22:35:30 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:35:30 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:35:31 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 22:35:31 Tower kernel: ata4: EH complete Jul 28 22:35:31 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:35:31 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:35:31 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:35:31 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:35:56 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:35:56 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:35:56 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:35:56 Tower kernel: ata4.00: cmd 25/00:00:0f:45:67/00:04:1c:00:00/e0 tag 0 dma 524288 in Jul 28 22:35:56 Tower kernel: res 51/04:00:0f:45:67/00:04:1c:00:00/f0 Emask 0x1 (device error) Jul 28 22:35:56 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:35:56 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:35:56 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 22:35:56 Tower kernel: ata4: EH complete Jul 28 22:35:56 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:35:56 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:35:56 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:35:56 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:36:26 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:36:26 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:36:26 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:36:26 Tower kernel: ata4.00: cmd 25/00:00:9f:96:7f/00:04:1c:00:00/e0 tag 0 dma 524288 in Jul 28 22:36:26 Tower kernel: res 51/04:00:9f:96:7f/00:04:1c:00:00/f0 Emask 0x1 (device error) Jul 28 22:36:26 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:36:26 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:36:27 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 22:36:27 Tower kernel: ata4: EH complete Jul 28 22:36:27 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:36:27 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:36:27 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:36:27 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:40:08 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:40:08 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:40:08 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:40:08 Tower kernel: ata4.00: cmd 25/00:00:cf:c5:3b/00:04:1d:00:00/e0 tag 0 dma 524288 in Jul 28 22:40:08 Tower kernel: res 51/04:00:cf:c5:3b/00:04:1d:00:00/f0 Emask 0x1 (device error) Jul 28 22:40:08 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:40:08 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:40:08 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 22:40:08 Tower kernel: ata4: EH complete Jul 28 22:40:08 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:40:09 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:40:09 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:40:09 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:40:15 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:40:15 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:40:15 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:40:15 Tower kernel: ata4.00: cmd 25/00:00:87:85:41/00:04:1d:00:00/e0 tag 0 dma 524288 in Jul 28 22:40:15 Tower kernel: res 51/04:00:87:85:41/00:04:1d:00:00/f0 Emask 0x1 (device error) Jul 28 22:40:15 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:40:15 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:40:15 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 22:40:15 Tower kernel: ata4: EH complete Jul 28 22:40:15 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:40:15 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:40:15 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:40:15 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:40:19 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:40:19 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:40:19 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:40:19 Tower kernel: ata4.00: cmd 25/00:00:5f:52:45/00:04:1d:00:00/e0 tag 0 dma 524288 in Jul 28 22:40:19 Tower kernel: res 51/04:00:5f:52:45/00:04:1d:00:00/f0 Emask 0x1 (device error) Jul 28 22:40:19 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:40:19 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:40:20 Tower kernel: ata4.00: configured for UDMA/100 Jul 28 22:40:20 Tower kernel: ata4: EH complete Jul 28 22:40:20 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:40:20 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:40:20 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:40:20 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:40:29 Tower kernel: ata4.00: limiting speed to UDMA/66:PIO4 Jul 28 22:40:29 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x6 Jul 28 22:40:29 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:40:29 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:40:29 Tower kernel: ata4.00: cmd 25/00:00:5f:a6:4d/00:04:1d:00:00/e0 tag 0 dma 524288 in Jul 28 22:40:29 Tower kernel: res 51/04:00:5f:a6:4d/00:04:1d:00:00/f0 Emask 0x1 (device error) Jul 28 22:40:29 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:40:29 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:40:29 Tower kernel: ata4: hard resetting link Jul 28 22:40:29 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jul 28 22:40:30 Tower kernel: ata4.00: configured for UDMA/66 Jul 28 22:40:30 Tower kernel: ata4: EH complete Jul 28 22:40:30 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:40:30 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:40:30 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:40:30 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 28 22:52:28 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0 Jul 28 22:52:28 Tower kernel: ata4.00: BMDMA2 stat 0xd0009 Jul 28 22:52:28 Tower kernel: ata4: SError: { 10B8B BadCRC } Jul 28 22:52:28 Tower kernel: ata4.00: cmd 25/00:b0:bf:b3:af/00:00:1f:00:00/e0 tag 0 dma 90112 in Jul 28 22:52:28 Tower kernel: res 51/04:b0:bf:b3:af/00:00:1f:00:00/f0 Emask 0x1 (device error) Jul 28 22:52:28 Tower kernel: ata4.00: status: { DRDY ERR } Jul 28 22:52:28 Tower kernel: ata4.00: error: { ABRT } Jul 28 22:52:29 Tower kernel: ata4.00: configured for UDMA/66 Jul 28 22:52:29 Tower kernel: ata4: EH complete Jul 28 22:52:29 Tower kernel: sd 4:0:0:0: [sdb] 586114704 512-byte hardware sectors (300091 MB) Jul 28 22:52:29 Tower kernel: sd 4:0:0:0: [sdb] Write Protect is off Jul 28 22:52:29 Tower kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jul 28 22:52:29 Tower kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 29 00:09:13 Tower emhttp: shcmd (46): /usr/sbin/hdparm -y /dev/sdb >/dev/nullI'm currently running another parity check to see if everything's ok. Should I be worried about any of this?
How do I figure out which drive is ATA4?
Thanks,
Jim
-
Wow! They fixed that pretty quickly! I didn't get the $160 so I'm actually happy... I saved myself $160
-
someone PLEASE talk me out of this! Seems like too good of a deal!!!
-
]If not in a real rush, let it run another cycle or two, or overnight. Remember, you did 3 cycles to identify the first 5 sectors... you do not know if they all showed up in the the first cycle, or the third.
It is good that no more bad sectors were identified.
Glad it is working for you. How long did it take to run a cycle on the 1TB drive in your server?
Joe L.
Each cycle is just about 12hours. I'm in no immediate rush so I just popped off another cycle. Maybe an interesting additiion to the script would be to save the smart data after every cycle so we can see when the events happend. When I ran the 1st 3 cycles I don't know if the events happened in the 1st, 2nd, or 3rd cycle..
Jim
-
You might want to start a thread with your preclear experience. It will allow the questions about the output to all be in one spot.
Joe L.
Done! I started a new thread that can be devoted to just questions about the results of the script. Hopefully all the gurus will monitor that thread too!
Thanks again, Joe, for a great script!
Results discussion thread can be found here
-
In an effort to keep the Preclear script thread more about questions about the script itself, I've started another thread here to discuss the results. The preclear thread is peppered with result questions and questions about the script and is now 15 pages long! So I'm thinking that a seperate thread was warranted. So I'll start it off...
If it stays at 5, in my opinion, no problem. If it increases over time, then you might want to use the RMA process. Odds are good it will stabilize. I have one 250Gig drive that has had 100 relocated sectors since the first time I ran smartctl on it. That number has never changed on that disk.After running 3 interations on my new 1TB green disk I had
< 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
---
> 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 5
64c64
< 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
---
> 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always - 1
Are 5 reallocated sectors anything to worry about.. I was hoping for 0!
This is still running on the old version of the script.. Maybe I should try the new version.. (I started my test the morning before Joe posted the new version!) I did start a cycle again on a different controller (one cycle this time - and still the old script)
Another thought... Should we start a new thread for preclear disk result questions and keep this thread for questions/comments about the functionality of preclear?
Jim
I'd say, download the new version of preclear_disk.sh and run another set of test cycles and see if it shows an increase in re-allocated sectors. (the new version stress-tests the drive more. The old one had a bug that prevented the random cylinders from being read in addition to the linear read that was properly occurring) If the number stays at 5, fine, if not another test cycle might be in order. At that point you have all the evidence you need if an RMA is warranted.
You might want to start a thread with your preclear experience. It will allow the questions about the output to all be in one spot.
Joe L.
Ok.. I ran one more full cycle with the new verions of the script and I got no reallocated sector changes. Should I run once more or do you think I'm good now and can put the disk into service?
So... first 3 cycles. - 5 reallocated sectors
4th cycle - no more reallocated sectors.
Jim
-
I haven't tried any of these.. but they seem pretty new. Good competition for the WD green drives?
@ $109.. This seems like a good deal! Too bad I just bought a 1TB.. Have to wait till next credit card cycle!
They are normally $115 but if you get hte newsletter and the code it's $109.99
FYI...
-
After running 3 interations on my new 1TB green disk I had
< 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
---
> 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 5
64c64
< 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
---
> 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always - 1
Are 5 reallocated sectors anything to worry about.. I was hoping for 0!
This is still running on the old version of the script.. Maybe I should try the new version.. (I started my test the morning before Joe posted the new version!) I did start a cycle again on a different controller (one cycle this time - and still the old script)
Another thought... Should we start a new thread for preclear disk result questions and keep this thread for questions/comments about the functionality of preclear?
Jim
-
If you do use the mail programs listed from the posts above (from unraid_notify and it's mail offshoot) you will have to use the
command line parameter
It will not default to the e-mail address in the unraid_notify.config file. Maybe we can change the mail script to handle "root" as a recipient someday.. I'm still hoping that brianbone will update the package into a seperate mail and unraid_notify package!
Jim
-
My slightly more efficient PS (replacement - first died) should come in tomorrow. That will be another7-8 watts. (That's what I noticed when I swapped it out the first time before it died)
Maybe I won't have to switch to a new MB yet. If I still get ~70 watts with the drives spun down with the new power supply, I probably should be happy with that! I'm at ~74W with the older PS.
-
I just took out my apg video card and put in the dirt cheap pci radeon and my power dropped almost 25 watts! I was hoping for about 10 watts! I was surprised to say the least!
-
Fine with me!
-
My eathlink requires authentication?
Does it?
Maybe I'm thinking of Quest or Comcast. I'm going from a distant memory of an ISP that does not require SMTP Auth, as long as you're sending mail from within their network... Earthlink had come to mind for some reason.
Man -- I'm getting old.
Let me rephrase that.. Outside the network (which) is how I mostly operate... They require authentication. I don't know if I've ever tried smtp from with in the network. Since it's only for dialup backup and my mom's internet (she uses webmail) I've never tried from within... At least not with in the last 8 years or so!
-
Unfortunately, ISPs like earthlink do not require authentication, but do require ESMTP, so falling back to HELO on lack of authentication will still fail in this case.
I'll work on changing bashmail to fall back to HELO on rejection of ELHO. It appears that's the proper thing to do.
My eathlink requires authentication?
Preclear.sh results - Questions about your results? Post them here.
in User Customizations
Posted
I ran the disk one more time. This is what I got:
S.M.A.R.T. error count differences detected after pre-clear
note, some 'raw' values may change, but not be an indication of a problem
57c57
< 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5005
---
> 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5264
66c66
< 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4648
---
> 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4912
69c69
< 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 4952
---
> 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 9596
71c71
< 190 Airflow_Temperature_Cel 0x0022 071 067 000 Old_age Always - 29 (Lifetime Min/Max 29/33)
---
> 190 Airflow_Temperature_Cel 0x0022 068 067 000 Old_age Always - 32 (Lifetime Min/Max 29/33)
74c74
< 197 Current_Pending_Sector 0x0012 092 092 000 Old_age Always - 331
---
> 197 Current_Pending_Sector 0x0012 100 092 000 Old_age Always - 0
78c78
< 201 Soft_Read_Error_Rate 0x000a 097 097 000 Old_age Always - 228
---
> 201 Soft_Read_Error_Rate 0x000a 100 097 000 Old_age Always - 0
============================================================================
The Current_Pending_Sector didn't go up.. But neither did the Reallocated_Sectors?? what Happened to the 331 previous pending?
Also the Raw_Read_Error_Rate and the Read_Soft_Error_Rate both went up.. but not as much as the first time. However the Reported_Uncorrect almost doubled.
I also noted a bunch of errors in the syslog from the first time I ran the test (with both disks going) Here is a snippit of the error:
Aug 23 16:20:49 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Aug 23 16:20:49 Tower2 kernel: ata1.00: irq_stat 0x40000008 Aug 23 16:20:49 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in Aug 23 16:20:49 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) Aug 23 16:20:49 Tower2 kernel: ata1.00: status: { DRDY ERR } Aug 23 16:20:49 Tower2 kernel: ata1.00: error: { UNC } Aug 23 16:20:49 Tower2 kernel: ata1.00: configured for UDMA/133 Aug 23 16:20:49 Tower2 kernel: ata1: EH complete Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 23 16:20:52 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Aug 23 16:20:52 Tower2 kernel: ata1.00: irq_stat 0x40000008 Aug 23 16:20:52 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in Aug 23 16:20:52 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) Aug 23 16:20:52 Tower2 kernel: ata1.00: status: { DRDY ERR } Aug 23 16:20:52 Tower2 kernel: ata1.00: error: { UNC } Aug 23 16:20:52 Tower2 kernel: ata1.00: configured for UDMA/133 Aug 23 16:20:52 Tower2 kernel: ata1: EH complete Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 23 16:20:55 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Aug 23 16:20:55 Tower2 kernel: ata1.00: irq_stat 0x40000008 Aug 23 16:20:55 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in Aug 23 16:20:55 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) Aug 23 16:20:55 Tower2 kernel: ata1.00: status: { DRDY ERR } Aug 23 16:20:55 Tower2 kernel: ata1.00: error: { UNC } Aug 23 16:20:55 Tower2 kernel: ata1.00: configured for UDMA/133 Aug 23 16:20:55 Tower2 kernel: ata1: EH complete Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 23 16:20:57 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Aug 23 16:20:57 Tower2 kernel: ata1.00: irq_stat 0x40000008 Aug 23 16:20:57 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in Aug 23 16:20:57 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) Aug 23 16:20:57 Tower2 kernel: ata1.00: status: { DRDY ERR } Aug 23 16:20:57 Tower2 kernel: ata1.00: error: { UNC } Aug 23 16:20:57 Tower2 kernel: ata1.00: configured for UDMA/133 Aug 23 16:20:57 Tower2 kernel: ata1: EH complete Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 23 16:21:00 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Aug 23 16:21:00 Tower2 kernel: ata1.00: irq_stat 0x40000008 Aug 23 16:21:00 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in Aug 23 16:21:00 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) Aug 23 16:21:00 Tower2 kernel: ata1.00: status: { DRDY ERR } Aug 23 16:21:00 Tower2 kernel: ata1.00: error: { UNC } Aug 23 16:21:00 Tower2 kernel: ata1.00: configured for UDMA/133 Aug 23 16:21:00 Tower2 kernel: ata1: EH complete Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 23 16:21:03 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Aug 23 16:21:03 Tower2 kernel: ata1.00: irq_stat 0x40000008 Aug 23 16:21:03 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in Aug 23 16:21:03 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) Aug 23 16:21:03 Tower2 kernel: ata1.00: status: { DRDY ERR } Aug 23 16:21:03 Tower2 kernel: ata1.00: error: { UNC } Aug 23 16:21:03 Tower2 kernel: ata1.00: configured for UDMA/133 Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Aug 23 16:21:03 Tower2 kernel: Descriptor sense data with sense descriptors (in hex): Aug 23 16:21:03 Tower2 kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Aug 23 16:21:03 Tower2 kernel: 62 a1 fa b8 Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] ASC=0x11 ASCQ=0x4 Aug 23 16:21:03 Tower2 kernel: end_request: I/O error, dev sda, sector 1654782648 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847831 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847832 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847833 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847834 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847835 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847836 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847837 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847838 Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847839 Aug 23 16:21:03 Tower2 kernel: ata1: EH complete Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB) Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUAFull syslog attached except for a bug chunk in the middle I had to cut out to make the attacment the right size.
It seems like there were a lot less errors the second time around. Now is this still an RMA canidate or do you think this might be a MB error? (It's new too)
I'm running one more cycle
Thanks,
Jim