Karlston Posted January 23, 2009 Share Posted January 23, 2009 So do we know that CC1H and newer (CC1J) are good?Stated very clearly and openly on the update page...* Note: If your drive has CC or LC firmware, your drive is not affected and no further action is required. Attempting to flash the firmware of a drive with CC or LC firmware will result in rendering your drive inoperable. Link to comment Share on other sites More sharing options...
mikesw Posted January 23, 2009 Share Posted January 23, 2009 (edited) So do we know that CC1H and newer (CC1J) are good?Stated very clearly and openly on the update page...* Note: If your drive has CC or LC firmware, your drive is not affected and no further action is required. Attempting to flash the firmware of a drive with CC or LC firmware will result in rendering your drive inoperable. Yes it does; however, people want to have the latest and greatest firmware no matter what. The reason is becausewhat ever is the newest version must fix something: a bug, make it faster, make it more reliable etc.I'd like to get newer firmware versions to for my non-SATA seagate, maxtor, western digital drives regardless if they are3.5 or 2.5 drives. I update my dvd/cd rw drives as soon as they provide a newer firmware fix under the assumption itmust of fixed something - likewise for the HDD drives too.Note:the newest firmware is S1B and the various xDxH means the number of disks and the number of heads in the HDD.Since the filename doesn't mention cache size. One can say either the firmware is independent of it or they are all thesame cache size. for the model numbers listed.The easiest way is to find a tool that can dump the firmware in the drive and save it to a file from ones current drive.One could also write the new firmware to the drive, read it back and do a comparison of what got written or do achecksum, md5 hash too. Edited January 24, 2009 by mikesw Link to comment Share on other sites More sharing options...
Gradius2 Posted January 23, 2009 Share Posted January 23, 2009 So do we know that CC1H and newer (CC1J) are good?Stated very clearly and openly on the update page...* Note: If your drive has CC or LC firmware, your drive is not affected and no further action is required. Attempting to flash the firmware of a drive with CC or LC firmware will result in rendering your drive inoperable. LOL, and you still believe on them?Just unbelievable !Yes it does; however, people want to have the latest and greatest firmware no matter what. The reason is becausewhat ever is the newest version must fix something: a bug, make it faster, make it more reliable etc.I'd like to get newer firmware versions to for my non-SATA seagate, maxtor, western digital drives regardless if they are3.5 or 2.5 drives. I update my dvd/cd rw drives as soon as they provide a newer firmware fix under the assumption itmust of fixed something - likewise for the HDD drives too.Note:the newest firmware is S2B and the various xDxH means the number of disks and the number of heads in the HDD.Since the filename doesn't mention cache size. One can say either the firmware is independent of it or they are all thesame cache size. for the model numbers listed.The easiest way is to find a tool that can dump the firmware in the drive and save it to a file from ones current drive.One could also write the new firmware to the drive, read it back and do a comparison of what got written or do achecksum, md5 hash too.On old days (back in 2000) I used to hack firmwares for Pioneer burners (DVR-Axx family) as you can see here:http://gradius.rpc1.orgYou're 100% right, they always fix something, improves stability and speed, on newer firmwares.The biggest issue I'm getting with CC1F is access time, way too high, they're 15.6ms on my 1TBs HDDs, while the normal would be 12.5ms or less (I get that on my 750GBs). Link to comment Share on other sites More sharing options...
Karlston Posted January 24, 2009 Share Posted January 24, 2009 LOL, and you still believe on them?Just unbelievable !Huh? Why not?You think we should do the direct opposite and flash it anyway?After you...You're 100% right, they always fix something, improves stability and speed, on newer firmwares.Absolutely!SD15 fixed the non-bricking issue of previous firmware.SD17 fixed the non-stuttering issue on RAIDed drives or during video streaming.:-) Link to comment Share on other sites More sharing options...
spankerer Posted January 24, 2009 Share Posted January 24, 2009 Was it a drive with the busy or LB0 issue?Ok I successfully flash my ST3500320AS to the SD1A firmware. Hopefully it will work fine until the end of it's natural life cycle.I have 2 500 GBs, one has the BSY error, the other one still functions. So i flashed the survivor. I'm still looking for the RS232-TTL part to fix my bricked HDD. Link to comment Share on other sites More sharing options...
timha Posted January 24, 2009 Share Posted January 24, 2009 Hey guys,...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware2. swap back the pcb'svoila !! full recovery from bsy hd with no LB0.this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way as far as i know you do need to 7200.11's though .. . Link to comment Share on other sites More sharing options...
eli2k Posted January 24, 2009 Share Posted January 24, 2009 Hey guys,...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware2. swap back the pcb'svoila !! full recovery from bsy hd with no LB0.this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way as far as i know you do need to 7200.11's though .. .Should I just buy a new 7200.11, try this, then return it and give them an excuse to return it? Anyone here happen to be from orange county, CA? =/ Link to comment Share on other sites More sharing options...
velos Posted January 24, 2009 Share Posted January 24, 2009 Has anyone tested the hdd before and after the firmware update to check if the update affects the hdd performance (speed)? I m sorry if I missed a previous post about it. Is it supposed to have no effect on the hdd speed?I still haven’t updated mine; I am waiting a while to be sure (I hope my hdd will not kick the bucket in the meantime). Link to comment Share on other sites More sharing options...
spankerer Posted January 24, 2009 Share Posted January 24, 2009 Hey guys,...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware2. swap back the pcb'svoila !! full recovery from bsy hd with no LB0.this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way as far as i know you do need to 7200.11's though .. .Question, after you swap the PCB boards, and then you boot up, does the BIOS detect the HDD? Link to comment Share on other sites More sharing options...
pksw Posted January 24, 2009 Share Posted January 24, 2009 (edited) Has anyone tested the hdd before and after the firmware update to check if the update affects the hdd performance (speed)? I m sorry if I missed a previous post about it. Is it supposed to have no effect on the hdd speed?I still haven’t updated mine; I am waiting a while to be sure (I hope my hdd will not kick the bucket in the meantime).I have found no difference.ST31000333AS SD15 flashed to SD1BOS: WinXp SP3CPU: Intel Q6600, overclocking turned off for benchingHD Tach 3.0.4.0 usedI had no issue with my drive - it was only used as a backup disk. Decided to flash it to the new firmware. After flashing, WinXP detected a hardware change, and a new hard disk.During the flashing process, the HDD made a few clicking noises (not unlike the click of death I used to hear from my IBM Deskstar aka Deathstar drives years ago), but it finished ok, and the BIOS detected the new firmware as SD1B.SD15 BIOSRandom access 15.3msCPU utilization 4%Average read: 99.3 MB/sSB1B BIOSRandom access 15.2msCPU utilization 4%Average read: 98.8 MB/sThere were a few clicks at the start of the test, which I thought the system had hung, but the bench finished ok. That point is seen in the graph (red line).However, lots of clicking sounds from the drive at random times since I've updated the firmware. I'm not sure if that's a good sign. The system almost seems to pause when that happens. Edited January 24, 2009 by pksw Link to comment Share on other sites More sharing options...
velos Posted January 24, 2009 Share Posted January 24, 2009 Thank you pksw for your detailed answer! Link to comment Share on other sites More sharing options...
sandersoni Posted January 24, 2009 Share Posted January 24, 2009 This Computerworld article mentions that law firm Kabateck, Brown Kellner LLP is considering filing a lawsuit again Seagate for the failed drives. You can let them know if your are affected by clicking here: [link] Link to comment Share on other sites More sharing options...
ViniciusFerrao Posted January 24, 2009 Share Posted January 24, 2009 Hey guys,...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware2. swap back the pcb'svoila !! full recovery from bsy hd with no LB0.this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way as far as i know you do need to 7200.11's though .. .Question, after you swap the PCB boards, and then you boot up, does the BIOS detect the HDD?Hello, I'm very happy now because I figured this out. :) :)When you swap the boards the "old" board should boot the new drive with 0Mb. Since the disk is not made for that PCB. Will be normally detected on BIOS.After this fireup firmware update. You'll some errors like Cylinder 0, assuming 63! Something like this. But just ignore and flash the drive.After the power cycle reswap PCB's and use the old drive. It should be fixed from BSY and from LBA=0!See details of what I've done in the Solution Thread.[]'s Link to comment Share on other sites More sharing options...
mikesw Posted January 24, 2009 Share Posted January 24, 2009 (edited) Hey guys,...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware2. swap back the pcb'svoila !! full recovery from bsy hd with no LB0.this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way as far as i know you do need to 7200.11's though .. .Question, after you swap the PCB boards, and then you boot up, does the BIOS detect the HDD?Hello, I'm very happy now because I figured this out. :) :)When you swap the boards the "old" board should boot the new drive with 0Mb. Since the disk is not made for that PCB. Will be normally detected on BIOS.After this fireup firmware update. You'll some errors like Cylinder 0, assuming 63! Something like this. But just ignore and flash the drive.After the power cycle reswap PCB's and use the old drive. It should be fixed from BSY and from LBA=0!See details of what I've done in the Solution Thread.[]'sI'm wondering if one can get away with not even attaching the PCB to the disk of the 2nd drive. The reason being is that when they make these at thefactory, they probably just attach the PCB to a test machine which flashes the PCB and runs electrical tests on it. This would be easierto make these in mass and then ship a box of these to another site that attaches the PCBs to the actual disk that some other factorysite made in mass. Then both are run through another test machine to make sure the PCB and drive heads and platters work together.Thus, for those with the PCB having LBA=0 and BSY, try just removing the PCB from the drive, attach the PCB to the power andIDE/SATA cable, and then reflash with the new firmware. It'd be interesting to see if this works. Maybe the BIOS doesn't need todetect them. This will also eliminate the possible damaging of the disk heads and platter of the drive that is incompatible since there isn't one.The most that will happen is there is no spinup, 0 heads, 0MB/GB, 0 cylinders etc or this method won't work. The only thing that will happenis that you are SOL!The other possiblilty to bypass the BIOS is to attach just the PCB to an external SATA or IDE to USB adaptor cable (see sabrent adaptors or equiv)and power cable ,then plug in the USB and flash thru the USB port. I'm not sure if one can flash thru the USB even if updating working drives, butwithout any knowledge about it working or not, the only way to attain knowledge is to experiment.....and hopefully the BIOS is too stupid. Edited January 24, 2009 by mikesw Link to comment Share on other sites More sharing options...
timha Posted January 24, 2009 Share Posted January 24, 2009 Hey guys,...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware2. swap back the pcb'svoila !! full recovery from bsy hd with no LB0.this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way as far as i know you do need to 7200.11's though .. .Should I just buy a new 7200.11, try this, then return it and give them an excuse to return it? Anyone here happen to be from orange county, CA? =/i happen to have 3 barracuda st300320AS, it would probably work on any two different models, when you swap the bad pcb to a good disk it is seen in the bios and that gets you half there.....flash the new firmware and your done....remember to flash the other hard disk as well when you swap back.. i used PowerISo to make the firmware cd.... as a note i've been swapping that pcb back and forth and tinkering with it so much with that dang rs232 that it should be broke but it isnt, dont be scared of it use torx6 screwdriver , but dont break it either ....good to have my hd back Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now