From: Reiner H. <re...@re...> - 2010-11-29 09:29:34
Attachments:
signature.asc
|
Hi Steve, I can confirm the behavior you observed. When copying much data to the drives (F4EG), I get the errors from below, which occured more than once. Smartmontools was uninstalled before copying. Regards, Reiner [48767.840118] ata3.00: exception Emask 0x40 SAct 0xfffff SErr 0x800 action 0x6 frozen [48767.840144] ata3: SError: { HostInt } [48767.840158] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840181] ata3.00: cmd 61/78:00:3f:44:b8/00:00:01:00:00/40 tag 0 ncq 61440 out [48767.840184] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840213] ata3.00: status: { DRDY } [48767.840224] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840244] ata3.00: cmd 61/20:08:b7:44:b8/00:00:01:00:00/40 tag 1 ncq 16384 out [48767.840247] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840275] ata3.00: status: { DRDY } [48767.840286] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840304] ata3.00: cmd 61/18:10:d7:44:b8/00:00:01:00:00/40 tag 2 ncq 12288 out [48767.840307] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840335] ata3.00: status: { DRDY } [48767.840346] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840365] ata3.00: cmd 61/18:18:ef:44:b8/00:00:01:00:00/40 tag 3 ncq 12288 out [48767.840367] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840395] ata3.00: status: { DRDY } [48767.840406] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840425] ata3.00: cmd 61/10:20:07:45:b8/00:00:01:00:00/40 tag 4 ncq 8192 out [48767.840428] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840456] ata3.00: status: { DRDY } [48767.840467] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840485] ata3.00: cmd 61/50:28:3f:45:b8/00:00:01:00:00/40 tag 5 ncq 40960 out [48767.840488] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840516] ata3.00: status: { DRDY } [48767.840527] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840546] ata3.00: cmd 61/10:30:77:46:b8/00:00:01:00:00/40 tag 6 ncq 8192 out [48767.840548] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840577] ata3.00: status: { DRDY } [48767.840587] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840606] ata3.00: cmd 61/28:38:17:45:b8/00:00:01:00:00/40 tag 7 ncq 20480 out [48767.840609] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840637] ata3.00: status: { DRDY } [48767.840648] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840666] ata3.00: cmd 61/30:40:8f:45:b8/00:00:01:00:00/40 tag 8 ncq 24576 out [48767.840669] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840697] ata3.00: status: { DRDY } [48767.840708] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840726] ata3.00: cmd 61/28:48:bf:45:b8/00:00:01:00:00/40 tag 9 ncq 20480 out [48767.840729] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840757] ata3.00: status: { DRDY } [48767.840768] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840786] ata3.00: cmd 61/20:50:e7:45:b8/00:00:01:00:00/40 tag 10 ncq 16384 out [48767.840789] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840818] ata3.00: status: { DRDY } [48767.840828] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840847] ata3.00: cmd 61/48:58:07:46:b8/00:00:01:00:00/40 tag 11 ncq 36864 out [48767.840850] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840878] ata3.00: status: { DRDY } [48767.840889] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840907] ata3.00: cmd 61/28:60:4f:46:b8/00:00:01:00:00/40 tag 12 ncq 20480 out [48767.840910] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840938] ata3.00: status: { DRDY } [48767.840949] ata3.00: failed command: WRITE FPDMA QUEUED [48767.840968] ata3.00: cmd 61/e8:68:87:46:b8/00:00:01:00:00/40 tag 13 ncq 118784 out [48767.840970] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.840999] ata3.00: status: { DRDY } [48767.841009] ata3.00: failed command: WRITE FPDMA QUEUED [48767.841028] ata3.00: cmd 61/38:70:bf:47:b8/00:00:01:00:00/40 tag 14 ncq 28672 out [48767.841031] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.841059] ata3.00: status: { DRDY } [48767.841069] ata3.00: failed command: WRITE FPDMA QUEUED [48767.841088] ata3.00: cmd 61/30:78:0f:48:b8/00:00:01:00:00/40 tag 15 ncq 24576 out [48767.841091] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.841119] ata3.00: status: { DRDY } [48767.841130] ata3.00: failed command: WRITE FPDMA QUEUED [48767.841148] ata3.00: cmd 61/18:80:f7:47:b8/00:00:01:00:00/40 tag 16 ncq 12288 out [48767.841151] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.841179] ata3.00: status: { DRDY } [48767.841190] ata3.00: failed command: WRITE FPDMA QUEUED [48767.841209] ata3.00: cmd 61/10:88:e7:43:b8/00:00:01:00:00/40 tag 17 ncq 8192 out [48767.841211] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.841239] ata3.00: status: { DRDY } [48767.841250] ata3.00: failed command: WRITE FPDMA QUEUED [48767.841269] ata3.00: cmd 61/48:90:f7:43:b8/00:00:01:00:00/40 tag 18 ncq 36864 out [48767.841271] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.841300] ata3.00: status: { DRDY } [48767.841310] ata3.00: failed command: WRITE FPDMA QUEUED [48767.841329] ata3.00: cmd 61/50:98:6f:47:b8/00:00:01:00:00/40 tag 19 ncq 40960 out [48767.841331] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x44 (timeout) [48767.841360] ata3.00: status: { DRDY } [48767.841373] ata3: hard resetting link [48768.160134] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [48768.172465] ata3.00: configured for UDMA/133 [48768.172477] ata3.00: device reported invalid CHS sector 0 [48768.172484] ata3.00: device reported invalid CHS sector 0 [48768.172489] ata3.00: device reported invalid CHS sector 0 [48768.172493] ata3.00: device reported invalid CHS sector 0 [48768.172498] ata3.00: device reported invalid CHS sector 0 [48768.172502] ata3.00: device reported invalid CHS sector 0 [48768.172506] ata3.00: device reported invalid CHS sector 0 [48768.172511] ata3.00: device reported invalid CHS sector 0 [48768.172515] ata3.00: device reported invalid CHS sector 0 [48768.172519] ata3.00: device reported invalid CHS sector 0 [48768.172524] ata3.00: device reported invalid CHS sector 0 [48768.172528] ata3.00: device reported invalid CHS sector 0 [48768.172533] ata3.00: device reported invalid CHS sector 0 [48768.172537] ata3.00: device reported invalid CHS sector 0 [48768.172541] ata3.00: device reported invalid CHS sector 0 [48768.172546] ata3.00: device reported invalid CHS sector 0 [48768.172550] ata3.00: device reported invalid CHS sector 0 [48768.172554] ata3.00: device reported invalid CHS sector 0 [48768.172559] ata3.00: device reported invalid CHS sector 0 [48768.172563] ata3.00: device reported invalid CHS sector 0 [48768.172604] ata3: EH complete |
From: Steve <St...@ow...> - 2010-12-03 13:07:20
|
Hi Reiner, ok. Can you maybe paste the output from "fdisk -ul /dev/sdX" (where X is of course one of your Samsung F4 EcoGreen). Or let's ask the other way did you do a correct 4kb alignment with fdisk? Cause of some strange reason after I created a correct 4Kb alignment with fdisk I don't get those errors anymore... Here is my output: fdisk -ul /dev/sda Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 224 heads, 56 sectors/track, 311465 cylinders, total 3907029168 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: 0x421f5ca0 Device Boot Start End Blocks Id System /dev/sda1 56 3907016959 1953508452 fd Linux raid autodetect I'm quite unsure atm if i should keep those disks or send them back. Best regards Steve On 29.11.2010 10:13, Reiner Herrmann wrote: > Hi Steve, > > I can confirm the behavior you observed. > When copying much data to the drives (F4EG), I get > the errors from below, which occured more than once. > Smartmontools was uninstalled before copying. > > Regards, > Reiner > > [48767.840118] ata3.00: exception Emask 0x40 SAct 0xfffff SErr 0x800 > action 0x6 frozen > [48767.840144] ata3: SError: { HostInt } > [48767.840158] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840181] ata3.00: cmd 61/78:00:3f:44:b8/00:00:01:00:00/40 tag 0 > ncq 61440 out > [48767.840184] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840213] ata3.00: status: { DRDY } > [48767.840224] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840244] ata3.00: cmd 61/20:08:b7:44:b8/00:00:01:00:00/40 tag 1 > ncq 16384 out > [48767.840247] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840275] ata3.00: status: { DRDY } > [48767.840286] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840304] ata3.00: cmd 61/18:10:d7:44:b8/00:00:01:00:00/40 tag 2 > ncq 12288 out > [48767.840307] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840335] ata3.00: status: { DRDY } > [48767.840346] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840365] ata3.00: cmd 61/18:18:ef:44:b8/00:00:01:00:00/40 tag 3 > ncq 12288 out > [48767.840367] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840395] ata3.00: status: { DRDY } > [48767.840406] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840425] ata3.00: cmd 61/10:20:07:45:b8/00:00:01:00:00/40 tag 4 > ncq 8192 out > [48767.840428] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840456] ata3.00: status: { DRDY } > [48767.840467] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840485] ata3.00: cmd 61/50:28:3f:45:b8/00:00:01:00:00/40 tag 5 > ncq 40960 out > [48767.840488] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840516] ata3.00: status: { DRDY } > [48767.840527] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840546] ata3.00: cmd 61/10:30:77:46:b8/00:00:01:00:00/40 tag 6 > ncq 8192 out > [48767.840548] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840577] ata3.00: status: { DRDY } > [48767.840587] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840606] ata3.00: cmd 61/28:38:17:45:b8/00:00:01:00:00/40 tag 7 > ncq 20480 out > [48767.840609] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840637] ata3.00: status: { DRDY } > [48767.840648] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840666] ata3.00: cmd 61/30:40:8f:45:b8/00:00:01:00:00/40 tag 8 > ncq 24576 out > [48767.840669] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840697] ata3.00: status: { DRDY } > [48767.840708] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840726] ata3.00: cmd 61/28:48:bf:45:b8/00:00:01:00:00/40 tag 9 > ncq 20480 out > [48767.840729] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840757] ata3.00: status: { DRDY } > [48767.840768] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840786] ata3.00: cmd 61/20:50:e7:45:b8/00:00:01:00:00/40 tag 10 > ncq 16384 out > [48767.840789] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840818] ata3.00: status: { DRDY } > [48767.840828] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840847] ata3.00: cmd 61/48:58:07:46:b8/00:00:01:00:00/40 tag 11 > ncq 36864 out > [48767.840850] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840878] ata3.00: status: { DRDY } > [48767.840889] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840907] ata3.00: cmd 61/28:60:4f:46:b8/00:00:01:00:00/40 tag 12 > ncq 20480 out > [48767.840910] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840938] ata3.00: status: { DRDY } > [48767.840949] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.840968] ata3.00: cmd 61/e8:68:87:46:b8/00:00:01:00:00/40 tag 13 > ncq 118784 out > [48767.840970] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.840999] ata3.00: status: { DRDY } > [48767.841009] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.841028] ata3.00: cmd 61/38:70:bf:47:b8/00:00:01:00:00/40 tag 14 > ncq 28672 out > [48767.841031] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.841059] ata3.00: status: { DRDY } > [48767.841069] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.841088] ata3.00: cmd 61/30:78:0f:48:b8/00:00:01:00:00/40 tag 15 > ncq 24576 out > [48767.841091] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.841119] ata3.00: status: { DRDY } > [48767.841130] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.841148] ata3.00: cmd 61/18:80:f7:47:b8/00:00:01:00:00/40 tag 16 > ncq 12288 out > [48767.841151] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.841179] ata3.00: status: { DRDY } > [48767.841190] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.841209] ata3.00: cmd 61/10:88:e7:43:b8/00:00:01:00:00/40 tag 17 > ncq 8192 out > [48767.841211] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.841239] ata3.00: status: { DRDY } > [48767.841250] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.841269] ata3.00: cmd 61/48:90:f7:43:b8/00:00:01:00:00/40 tag 18 > ncq 36864 out > [48767.841271] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.841300] ata3.00: status: { DRDY } > [48767.841310] ata3.00: failed command: WRITE FPDMA QUEUED > [48767.841329] ata3.00: cmd 61/50:98:6f:47:b8/00:00:01:00:00/40 tag 19 > ncq 40960 out > [48767.841331] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask > 0x44 (timeout) > [48767.841360] ata3.00: status: { DRDY } > [48767.841373] ata3: hard resetting link > [48768.160134] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [48768.172465] ata3.00: configured for UDMA/133 > [48768.172477] ata3.00: device reported invalid CHS sector 0 > [48768.172484] ata3.00: device reported invalid CHS sector 0 > [48768.172489] ata3.00: device reported invalid CHS sector 0 > [48768.172493] ata3.00: device reported invalid CHS sector 0 > [48768.172498] ata3.00: device reported invalid CHS sector 0 > [48768.172502] ata3.00: device reported invalid CHS sector 0 > [48768.172506] ata3.00: device reported invalid CHS sector 0 > [48768.172511] ata3.00: device reported invalid CHS sector 0 > [48768.172515] ata3.00: device reported invalid CHS sector 0 > [48768.172519] ata3.00: device reported invalid CHS sector 0 > [48768.172524] ata3.00: device reported invalid CHS sector 0 > [48768.172528] ata3.00: device reported invalid CHS sector 0 > [48768.172533] ata3.00: device reported invalid CHS sector 0 > [48768.172537] ata3.00: device reported invalid CHS sector 0 > [48768.172541] ata3.00: device reported invalid CHS sector 0 > [48768.172546] ata3.00: device reported invalid CHS sector 0 > [48768.172550] ata3.00: device reported invalid CHS sector 0 > [48768.172554] ata3.00: device reported invalid CHS sector 0 > [48768.172559] ata3.00: device reported invalid CHS sector 0 > [48768.172563] ata3.00: device reported invalid CHS sector 0 > [48768.172604] ata3: EH complete > > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > > > > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support |
From: Steve <St...@ow...> - 2010-12-03 14:25:14
|
Hi Rainer, there you have plenty of information about the alignment stuff. http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/index.html?ca=dgr-lnxw074KB-Disksdth-LX "Another approach with fdisk is to launch it as fdisk -H 224 -S 56 /dev/sda, which changes the cylinder/head/sector (CHS) geometry to guarantee proper 4096-byte alignment when the program aligns to cylinders, as it does by default." Then you need to delete the partition and recreate it. After that it should be proper aligned. If you want you can paste your output then again and pls tell me if it did solve your issues as well. P.S.: All of this has nothing to do with the "IDENTIFY DEVICE"-Error. Best regards, Steve On 03.12.2010 14:37, Reiner Herrmann wrote: > Hi Steve, > > I haven't done any manual alignment with fdisk. Just created the > partitions and set up a raid5 with them. > > My fdisk output: > > Disk /dev/sda: 2000.4 GB, 2000398934016 bytes > 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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 63 3907024064 1953512001 83 Linux > > How can I tell whether the alignment is correct? And how can it be > set correctly? > > Regards, > Reiner > > On 12/03/2010 02:07 PM, Steve wrote: >> Hi Reiner, >> >> ok. Can you maybe paste the output from "fdisk -ul /dev/sdX" (where X is >> of course one of your Samsung F4 EcoGreen). Or let's ask the other way >> did you do a correct 4kb alignment with fdisk? >> Cause of some strange reason after I created a correct 4Kb alignment >> with fdisk I don't get those errors anymore... >> >> Here is my output: >> fdisk -ul /dev/sda >> >> Disk /dev/sda: 2000.4 GB, 2000398934016 bytes >> 224 heads, 56 sectors/track, 311465 cylinders, total 3907029168 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: 0x421f5ca0 >> >> Device Boot Start End Blocks Id System >> /dev/sda1 56 3907016959 1953508452 fd Linux raid >> autodetect >> >> >> I'm quite unsure atm if i should keep those disks or send them back. >> >> >> Best regards >> Steve >> > |
From: Reiner H. <re...@re...> - 2010-12-16 00:08:58
Attachments:
signature.asc
|
Hi Steve, I upgraded the firmware this week and also aligned the partitions properly. Since then the problem hasn't occured again. Unfortunately I can't tell if it's because of the alignment or the firmware upgrade. Regards, Reiner On 12/03/2010 03:24 PM, Steve wrote: > Hi Rainer, > > there you have plenty of information about the alignment stuff. > http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/index.html?ca=dgr-lnxw074KB-Disksdth-LX > > "Another approach with fdisk is to launch it as fdisk -H 224 -S 56 > /dev/sda, which changes the cylinder/head/sector (CHS) geometry to > guarantee proper 4096-byte alignment when the program aligns to > cylinders, as it does by default." > > Then you need to delete the partition and recreate it. After that it > should be proper aligned. If you want you can paste your output then > again and pls tell me if it did solve your issues as well. > > P.S.: All of this has nothing to do with the "IDENTIFY DEVICE"-Error. > > Best regards, > Steve > > |
From: Tim E. <sma...@eh...> - 2010-12-03 15:19:45
|
On Fri, 3 Dec 2010, Steve wrote: Hi, > ok. Can you maybe paste the output from "fdisk -ul /dev/sdX" (where X is > of course one of your Samsung F4 EcoGreen). Or let's ask the other way > did you do a correct 4kb alignment with fdisk? I don't think that it has someting to do with the 4K alignment. I have two of these discs. One is correctly aligned, one is partitioned with one big partition in default behavior of fdisk: mod:0 15:53:42 ~ # fdisk -lu [...] Device Boot Start End Blocks Id System /dev/sdb1 2048 41961783 20979868 83 Linux Partition 1 does not end on cylinder boundary. /dev/sdb2 41961784 48256047 3147132 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/sdb3 48256048 3907029167 1929386560 83 Linux Partition 3 does not end on cylinder boundary. [...] Device Boot Start End Blocks Id System /dev/sdc3 63 3907024064 1953512001 83 Linux [...] And I have errors on the bus from time to time (both disks): mod:0 15:54:37 ~ # tail -9999 /var/log/messages | grep "] ata" Nov 27 03:14:56 mod kernel: [41092.000089] ata4: lost interrupt (Status 0x51) Nov 27 03:14:56 mod kernel: [41092.000114] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen Nov 27 03:14:56 mod kernel: [41092.000120] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } Nov 27 03:14:56 mod kernel: [41092.000125] ata4.00: failed command: READ DMA EXT Nov 27 03:14:56 mod kernel: [41092.000134] ata4.00: cmd 25/00:08:57:0c:d4/00:00:a8:00:00/e0 tag 0 dma 4096 in Nov 27 03:14:56 mod kernel: [41092.000139] ata4.00: status: { DRDY } Nov 27 03:14:56 mod kernel: [41092.000148] ata4: hard resetting link Nov 27 03:14:56 mod kernel: [41092.320045] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 27 03:14:56 mod kernel: [41092.336313] ata4.00: configured for UDMA/133 Nov 27 03:14:56 mod kernel: [41092.336326] ata4: EH complete Nov 27 03:29:19 mod kernel: [41955.000028] ata4: lost interrupt (Status 0x51) Nov 27 03:29:19 mod kernel: [41955.000053] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen Nov 27 03:29:19 mod kernel: [41955.000059] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } Nov 27 03:29:19 mod kernel: [41955.000064] ata4.00: failed command: READ DMA EXT Nov 27 03:29:19 mod kernel: [41955.000072] ata4.00: cmd 25/00:08:57:05:e0/00:00:87:00:00/e0 tag 0 dma 4096 in Nov 27 03:29:19 mod kernel: [41955.000077] ata4.00: status: { DRDY } Nov 27 03:29:19 mod kernel: [41955.000086] ata4: hard resetting link Nov 27 03:29:19 mod kernel: [41955.320046] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 27 03:29:19 mod kernel: [41955.336313] ata4.00: configured for UDMA/133 Nov 27 03:29:19 mod kernel: [41955.336326] ata4: EH complete Nov 27 03:33:46 mod kernel: [42222.000092] ata4: lost interrupt (Status 0x51) Nov 27 03:33:46 mod kernel: [42222.000117] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen Nov 27 03:33:46 mod kernel: [42222.000123] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } Nov 27 03:33:46 mod kernel: [42222.000128] ata4.00: failed command: READ DMA EXT Nov 27 03:33:46 mod kernel: [42222.000136] ata4.00: cmd 25/00:08:c7:01:6c/00:00:71:00:00/e0 tag 0 dma 4096 in Nov 27 03:33:46 mod kernel: [42222.000141] ata4.00: status: { DRDY } Nov 27 03:33:46 mod kernel: [42222.000150] ata4: hard resetting link Nov 27 03:33:46 mod kernel: [42222.320045] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 27 03:33:46 mod kernel: [42222.336311] ata4.00: configured for UDMA/133 Nov 27 03:33:46 mod kernel: [42222.336324] ata4: EH complete Nov 27 07:32:07 mod kernel: [56523.000031] ata4: lost interrupt (Status 0x51) Nov 27 07:32:07 mod kernel: [56523.000056] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen Nov 27 07:32:07 mod kernel: [56523.000061] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } Nov 27 07:32:07 mod kernel: [56523.000066] ata4.00: failed command: READ DMA EXT Nov 27 07:32:07 mod kernel: [56523.000075] ata4.00: cmd 25/00:08:8f:ca:2c/00:00:4f:00:00/e0 tag 0 dma 4096 in Nov 27 07:32:07 mod kernel: [56523.000080] ata4.00: status: { DRDY } Nov 27 07:32:07 mod kernel: [56523.000089] ata4: hard resetting link Nov 27 07:32:07 mod kernel: [56523.320045] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 27 07:32:07 mod kernel: [56523.336313] ata4.00: configured for UDMA/133 Nov 27 07:32:07 mod kernel: [56523.336326] ata4: EH complete Nov 27 07:42:57 mod kernel: [57173.442140] ata3.00: exception Emask 0x2 SAct 0x0 SErr 0x600401 action 0x6 Nov 27 07:42:57 mod kernel: [57173.442145] ata3.00: BMDMA stat 0x25 Nov 27 07:42:57 mod kernel: [57173.442149] ata3: SError: { RecovData Proto BadCRC Handshk } Nov 27 07:42:57 mod kernel: [57173.442154] ata3.00: failed command: READ DMA Nov 27 07:42:57 mod kernel: [57173.442162] ata3.00: cmd c8/00:40:c8:61:e1/00:00:00:00:00/e0 tag 0 dma 32768 in Nov 27 07:42:57 mod kernel: [57173.442167] ata3.00: status: { DRDY ERR } Nov 27 07:42:57 mod kernel: [57173.442169] ata3.00: error: { ICRC ABRT } Nov 27 07:42:57 mod kernel: [57173.442177] ata3: hard resetting link Nov 27 07:42:58 mod kernel: [57173.760048] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 27 07:42:58 mod kernel: [57173.776325] ata3.00: configured for UDMA/133 Nov 27 07:42:58 mod kernel: [57173.776338] ata3: EH complete Since I stopped smartd (on 27. 11.) I have not had any of these errors. Interestingly sometimes these errors has also been logged as SMART errors: Error 2 occurred at disk power-on lifetime: 193 hours (8 days + 1 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 40 c8 61 e1 e0 Error: ICRC, ABRT 64 sectors at LBA = 0x00e161c8 = 14770632 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 40 c8 61 e1 e0 08 00:00:57.206 READ DMA c8 00 08 c0 61 e1 e0 08 00:00:57.206 READ DMA c8 00 40 80 61 e1 e0 08 00:00:57.206 READ DMA c8 00 20 60 61 e1 e0 08 00:00:57.206 READ DMA c8 00 08 e0 08 e0 e0 08 00:00:57.206 READ DMA This was directly after the last error: Nov 27 07:50:33 mod smartd[2482]: Device: /dev/sdb [SAT], ATA error count increased from 1 to 2 I have now 2 errors on this disk and 3 errors on the other disk, always with command "READ DMA". I think I'm lucky with this, "WRITE DMA" would possibly lead to data loss. Cheers Tim |
From: Steve <St...@ow...> - 2010-12-03 17:57:12
|
Hi, I don't have any errors logged by smart. As well it's strange that my errors suddently disappeared. I didn't just have them once, they were easy reproduceable. Copying data to the disks or running performance tools like bonnie++ and I had a 100% chance of hitting that error. But after I corrected the alignment, nothing. I already ran bonnie++ 10+ times and copied ~ 1Tb data around. But still no error. What kernel do you use? uname -a Linux dark 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC 2010 x86_64 GNU/Linux Best regards Steve On 03.12.2010 16:07, Tim Ehlers wrote: > On Fri, 3 Dec 2010, Steve wrote: > > Hi, > >> ok. Can you maybe paste the output from "fdisk -ul /dev/sdX" (where X is >> of course one of your Samsung F4 EcoGreen). Or let's ask the other way >> did you do a correct 4kb alignment with fdisk? > > I don't think that it has someting to do with the 4K alignment. I have > two of these discs. One is correctly aligned, one is partitioned with one > big partition in default behavior of fdisk: > > mod:0 15:53:42 ~ # fdisk -lu > [...] > Device Boot Start End Blocks Id System > /dev/sdb1 2048 41961783 20979868 83 Linux > Partition 1 does not end on cylinder boundary. > /dev/sdb2 41961784 48256047 3147132 82 Linux swap / Solaris > Partition 2 does not end on cylinder boundary. > /dev/sdb3 48256048 3907029167 1929386560 83 Linux > Partition 3 does not end on cylinder boundary. > [...] > Device Boot Start End Blocks Id System > /dev/sdc3 63 3907024064 1953512001 83 Linux > [...] > > And I have errors on the bus from time to time (both disks): > > mod:0 15:54:37 ~ # tail -9999 /var/log/messages | grep "] ata" > Nov 27 03:14:56 mod kernel: [41092.000089] ata4: lost interrupt (Status 0x51) > Nov 27 03:14:56 mod kernel: [41092.000114] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen > Nov 27 03:14:56 mod kernel: [41092.000120] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } > Nov 27 03:14:56 mod kernel: [41092.000125] ata4.00: failed command: READ DMA EXT > Nov 27 03:14:56 mod kernel: [41092.000134] ata4.00: cmd 25/00:08:57:0c:d4/00:00:a8:00:00/e0 tag 0 dma 4096 in > Nov 27 03:14:56 mod kernel: [41092.000139] ata4.00: status: { DRDY } > Nov 27 03:14:56 mod kernel: [41092.000148] ata4: hard resetting link > Nov 27 03:14:56 mod kernel: [41092.320045] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > Nov 27 03:14:56 mod kernel: [41092.336313] ata4.00: configured for UDMA/133 > Nov 27 03:14:56 mod kernel: [41092.336326] ata4: EH complete > Nov 27 03:29:19 mod kernel: [41955.000028] ata4: lost interrupt (Status 0x51) > Nov 27 03:29:19 mod kernel: [41955.000053] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen > Nov 27 03:29:19 mod kernel: [41955.000059] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } > Nov 27 03:29:19 mod kernel: [41955.000064] ata4.00: failed command: READ DMA EXT > Nov 27 03:29:19 mod kernel: [41955.000072] ata4.00: cmd 25/00:08:57:05:e0/00:00:87:00:00/e0 tag 0 dma 4096 in > Nov 27 03:29:19 mod kernel: [41955.000077] ata4.00: status: { DRDY } > Nov 27 03:29:19 mod kernel: [41955.000086] ata4: hard resetting link > Nov 27 03:29:19 mod kernel: [41955.320046] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > Nov 27 03:29:19 mod kernel: [41955.336313] ata4.00: configured for UDMA/133 > Nov 27 03:29:19 mod kernel: [41955.336326] ata4: EH complete > Nov 27 03:33:46 mod kernel: [42222.000092] ata4: lost interrupt (Status 0x51) > Nov 27 03:33:46 mod kernel: [42222.000117] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen > Nov 27 03:33:46 mod kernel: [42222.000123] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } > Nov 27 03:33:46 mod kernel: [42222.000128] ata4.00: failed command: READ DMA EXT > Nov 27 03:33:46 mod kernel: [42222.000136] ata4.00: cmd 25/00:08:c7:01:6c/00:00:71:00:00/e0 tag 0 dma 4096 in > Nov 27 03:33:46 mod kernel: [42222.000141] ata4.00: status: { DRDY } > Nov 27 03:33:46 mod kernel: [42222.000150] ata4: hard resetting link > Nov 27 03:33:46 mod kernel: [42222.320045] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > Nov 27 03:33:46 mod kernel: [42222.336311] ata4.00: configured for UDMA/133 > Nov 27 03:33:46 mod kernel: [42222.336324] ata4: EH complete > Nov 27 07:32:07 mod kernel: [56523.000031] ata4: lost interrupt (Status 0x51) > Nov 27 07:32:07 mod kernel: [56523.000056] ata4.00: exception Emask 0x2 SAct 0x0 SErr 0x700401 action 0x6 frozen > Nov 27 07:32:07 mod kernel: [56523.000061] ata4: SError: { RecovData Proto Dispar BadCRC Handshk } > Nov 27 07:32:07 mod kernel: [56523.000066] ata4.00: failed command: READ DMA EXT > Nov 27 07:32:07 mod kernel: [56523.000075] ata4.00: cmd 25/00:08:8f:ca:2c/00:00:4f:00:00/e0 tag 0 dma 4096 in > Nov 27 07:32:07 mod kernel: [56523.000080] ata4.00: status: { DRDY } > Nov 27 07:32:07 mod kernel: [56523.000089] ata4: hard resetting link > Nov 27 07:32:07 mod kernel: [56523.320045] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > Nov 27 07:32:07 mod kernel: [56523.336313] ata4.00: configured for UDMA/133 > Nov 27 07:32:07 mod kernel: [56523.336326] ata4: EH complete > Nov 27 07:42:57 mod kernel: [57173.442140] ata3.00: exception Emask 0x2 SAct 0x0 SErr 0x600401 action 0x6 > Nov 27 07:42:57 mod kernel: [57173.442145] ata3.00: BMDMA stat 0x25 > Nov 27 07:42:57 mod kernel: [57173.442149] ata3: SError: { RecovData Proto BadCRC Handshk } > Nov 27 07:42:57 mod kernel: [57173.442154] ata3.00: failed command: READ DMA > Nov 27 07:42:57 mod kernel: [57173.442162] ata3.00: cmd c8/00:40:c8:61:e1/00:00:00:00:00/e0 tag 0 dma 32768 in > Nov 27 07:42:57 mod kernel: [57173.442167] ata3.00: status: { DRDY ERR } > Nov 27 07:42:57 mod kernel: [57173.442169] ata3.00: error: { ICRC ABRT } > Nov 27 07:42:57 mod kernel: [57173.442177] ata3: hard resetting link > Nov 27 07:42:58 mod kernel: [57173.760048] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > Nov 27 07:42:58 mod kernel: [57173.776325] ata3.00: configured for UDMA/133 > Nov 27 07:42:58 mod kernel: [57173.776338] ata3: EH complete > > > Since I stopped smartd (on 27. 11.) I have not had any of these errors. > Interestingly sometimes these errors has also been logged as SMART errors: > > Error 2 occurred at disk power-on lifetime: 193 hours (8 days + 1 hours) > When the command that caused the error occurred, the device was active or idle. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 84 51 40 c8 61 e1 e0 Error: ICRC, ABRT 64 sectors at LBA = 0x00e161c8 = 14770632 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > c8 00 40 c8 61 e1 e0 08 00:00:57.206 READ DMA > c8 00 08 c0 61 e1 e0 08 00:00:57.206 READ DMA > c8 00 40 80 61 e1 e0 08 00:00:57.206 READ DMA > c8 00 20 60 61 e1 e0 08 00:00:57.206 READ DMA > c8 00 08 e0 08 e0 e0 08 00:00:57.206 READ DMA > > > This was directly after the last error: > > Nov 27 07:50:33 mod smartd[2482]: Device: /dev/sdb [SAT], ATA error count increased from 1 to 2 > > > I have now 2 errors on this disk and 3 errors on the other disk, always > with command "READ DMA". I think I'm lucky with this, "WRITE DMA" would > possibly lead to data loss. > > Cheers > > Tim > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > |
From: Tim E. <sma...@eh...> - 2010-12-03 19:35:19
|
On Fri, 3 Dec 2010, Steve wrote: Hi, > What kernel do you use? > uname -a > Linux dark 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC 2010 > x86_64 GNU/Linux mod:0 20:31:22 ~ # uname -a Linux mod 2.6.34.7-0.5-pae #1 SMP 2010-10-25 08:40:12 +0200 i686 athlon i386 GNU/Linux mod:0 20:31:25 ~ # cat /etc/SuSE-release openSUSE 11.3 (i586) VERSION = 11.3 Cheers Tim |
From: Reiner H. <re...@re...> - 2010-12-03 13:37:59
Attachments:
signature.asc
|
Hi Steve, I haven't done any manual alignment with fdisk. Just created the partitions and set up a raid5 with them. My fdisk output: Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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 63 3907024064 1953512001 83 Linux How can I tell whether the alignment is correct? And how can it be set correctly? Regards, Reiner On 12/03/2010 02:07 PM, Steve wrote: > Hi Reiner, > > ok. Can you maybe paste the output from "fdisk -ul /dev/sdX" (where X is > of course one of your Samsung F4 EcoGreen). Or let's ask the other way > did you do a correct 4kb alignment with fdisk? > Cause of some strange reason after I created a correct 4Kb alignment > with fdisk I don't get those errors anymore... > > Here is my output: > fdisk -ul /dev/sda > > Disk /dev/sda: 2000.4 GB, 2000398934016 bytes > 224 heads, 56 sectors/track, 311465 cylinders, total 3907029168 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: 0x421f5ca0 > > Device Boot Start End Blocks Id System > /dev/sda1 56 3907016959 1953508452 fd Linux raid > autodetect > > > I'm quite unsure atm if i should keep those disks or send them back. > > > Best regards > Steve > |
From: Bernd M. <melchers@CIS.FU-Berlin.DE> - 2010-12-03 14:44:24
|
> > Device Boot Start End Blocks Id System > /dev/sda1 56 3907016959 1953508452 fd Linux raid Windows 7 formats the disk 4k-aligned as follows: Start End Blocks 2048s 3907026943s 3907024896s one can reproduce this with parted as follows: parted /dev/sdX unit s mkpart prim 2048s 3907026943s maybe the correct aligment is the cause for less problems with this disk in windows? Mit freundlichen Grüßen Bernd Melchers -- |