Reply
Regular Visitor
bart_bender
Posts: 3
Registered: ‎03-03-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

 

ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) ata4.00: status: { DRDY } ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: limiting SATA link speed to 1.5 Gbps ata4: hard resetting link ata4: COMRESET failed (errno=-16) ata4: reset failed, giving up ata4.00: disabled ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: COMRESET failed (errno=-16) ata4: reset failed, giving up ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: COMRESET failed (errno=-16) ata4: reset failed, giving up ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: COMRESET failed (errno=-16) ata4: reset failed, giving up ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link ata4: COMRESET failed (errno=-16) ata4: reset failed, giving up ata4: EH pending after 5 tries, giving up ata4: EH complete sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 962005375 Buffer I/O error on device sdb1, logical block 120250664 lost page write due to I/O error on sdb1 Buffer I/O error on device sdb1, logical block 120250665 lost page write due to I/O error on sdb1 Buffer I/O error on device sdb1, logical block 120250666 lost page write due to I/O error on sdb1 sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sdb, sector 962334807 Buffer I/O error on device sdb1, logical block 120291843 lost page write due to I/O error on sdb1 JBD: Detected IO errors while flushing file data on sdb1 ata4: hard resetting link ata4: link is slow to respond, please be patient (ready=0) ata4: COMRESET failed (errno=-16) ata4: hard resetting link

 

 

This is the output of the linux kernel when the harddisk fails 

Visitor
wenqi
Posts: 1
Registered: ‎04-05-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

I have exactly the same problem and my firmwire version is CC1H too. Could some one from Seagate response this please?
Regular Visitor
nevion
Posts: 4
Registered: ‎04-14-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

I get very similiar output to this:

 

ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata3.00: cmd ec/00:00:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in res 40/00:00:f7:b2:ac/00:00:02:00:00/40 Emask 0x4 (timeout) ata3.00: status: { DRDY } ata3: hard resetting link ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3.00: configured for UDMA/133 ata3: EH complete sd 2:0:0:0: [sdc] 2930277168 512-byte hardware sectors: (1.50 TB/1.36 TiB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

 Happens quite often (100+ times per day) whenever the drive is doing any io, curiously not at all when the drive isn't accessed (even though it's mounted).

 

 

/dev/sdc: ATA device, with non-removable media Model Number: ST31500341AS Serial Number: 9VS0HKJ6 Firmware Revision: LC1A Transport: Serial Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 2930277168 device size with M = 1024*1024: 1430799 MBytes device size with M = 1000*1000: 1500301 MBytes (1500 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * DOWNLOAD_MICROCODE SET_MAX security extension * 48-bit Address feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * 64-bit World wide name * Write-Read-Verify feature set * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * SATA-I signaling speed (1.5Gb/s) * SATA-II signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 258min for SECURITY ERASE UNIT. 258min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c500107c1526 NAA : 5 IEEE OUI : c50 Unique ID : 0107c1526 Checksum: correct

 

 I'm quite convinced this is a firmware issue.  I tested it in ahci and ide modes.. ncq disabled and even with write cache disabled.  It does not seem to change the frequency of dropouts at all.  Data integrity looks good though.

 

 

Regular Visitor
sony111
Posts: 2
Registered: ‎04-14-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

[ Edited ]

My 2 "ST31500341AS"  they are defective (BAD!!!!) revision fw CC1H

 

[Edited in compliance of the community rules and regulations.]

Message Edited by BradC on 04-21-2009 10:54 PM
Byte
prune998
Posts: 20
Registered: ‎04-15-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

I have 8 of these disks in CC1H firmware :

 

1 ST31500341AS-9VS0PBWJ 1.50 TB CC1H

2 ST31500341AS-9VS0SJ6L 1.50 TB CC1H 
3 ST31500341AS-9VS0RNVB 1.50 TB CC1H 
4 ST31500341AS-9VS0PBQK 1.50 TB CC1H 
5 ST31500341AS-9VS0SJGS 1.50 TB CC1H 
6 ST31500341AS-9VS0PD2W 1.50 TB CC1H 
7 ST31500341AS-9VS0SJQJ 1.50 TB CC1H 

8 ST31500341AS-9VS0PM6L 1.50 TB CC1H 

 

They are in a RAID enclosure with a Highpoint 4322 card (the best they make).

When I use the disk, the I/O's freeze, then the card, then the whole computer (brand new Macpro 2009 nehalem). After some time (5 mins ? ) I/O's start again, then freeze.... etc, etc.

 

RAID enclosure manufacturer and RAID card manufacturer ALL SAID this was a known problem with CC1H firmware, and I need to "upgrade" to enterprise firmware, SDxx.

For the moment, seagate support is just telling me this is not possible. I'm tryingto get a replacement....

 

I'm sure you're problem is the same as mine, and the same that was there with the "bad" firmware which had an upgrade : the disk stop responding for some time. This is juste more obvious when using 8 disks in a RAID array.

 

Of course, SEAtool don't say anything, BUT, the test just never ends when the disk is in the RAId array (probably due to timeouts and ho windows manage this). Needless to say I had to buy a windows CD to test this, as I'm a MAC user and seagate have NO TOOL for us.

 

Please, seagate, provide SDxx firmware or exchange the disks !!!! 

Regular Visitor
sony111
Posts: 2
Registered: ‎04-14-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

UP UP UP UP UP------->UP UP UP!!!!!!!!!!!!!!!!!!!!
Visitor
sean.snydely
Posts: 2
Registered: ‎04-23-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

I'm having the same problem. I have a ST31500341AS with the CC1H firmware. It keeps freezing up and a "clicking" noise is very audible. The drive is only a couple of months old and I'm VERY concerned about my data!
Visitor
touchstone
Posts: 1
Registered: ‎05-05-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

I've also been having this problem on an array with 4 drives, CC1H firmware, connected to a Highpoint RocketRaid 4310.  Even just initializing an array from the Highpoint BIOS, or attempting to, will freeze the computer.  Highpoint says the CC1x firmware line is buggy, which seems consistent with the experiences posted online. Has anyone heard from Seagate regarding the possibility of switching to the SD1A firmware (or whatever the latest version in the SD1 line is)?
Byte
Anosh
Posts: 2
Registered: ‎05-06-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

[ Edited ]
Today marks two months plus two days of owning and using a Seagate 7200.11 1.5Tb harddisk.

Yesterday in the evening the disk started to make mechanical clicking everytime it was accessed and performance drop to zero during these clicks. Some hours later while checking the seagate forums suddenly I noticed the disk disappeared from windows. So I turned the computer off and later right before going to bed I turned the computer on and the disk appeared but the mechanical clicks are still present.

This drive is among those that according to seagate isn't faulty and there are no firmware upgrades. The drive has worked fine during these two months.

Now I bought the drive cause I needed space and I don't have any other to backup the data it contains. I can still get a new one from the place of purchase and perhaps even change it for another brand, say WD.

But the problem is how do I transfer the data to the new drive? Do I really have to buy yet another drive I don't need?
Message Edited by Anosh on 05-07-2009 12:51 AM
Visitor
sean.snydely
Posts: 2
Registered: ‎04-23-2009
0

Re: My Barracuda 1.5TB ST31500341AS fw.CC1H is affected by firmware Issues

[ Edited ]
I had to order a 1TB WD drive. There have been TONS of reported problems with these drives. Shame on you Seagate for selling this c r a p!. I want my money back!
Message Edited by sean.snydely on 05-06-2009 08:52 AM