December 3, 200817 yr At least it won't overheat It might still run a bit hot... it has no forced air cooling. On the other hand, the fans in the open case are probably not drawing air across the other drives as intended either, so they are probably also running a bit warm.
December 3, 200817 yr Added to the FAQ (link back only), here. Feel free to edit or expand. Just like to encourage everyone to continue adding topics to the FAQ (as well as the rest of the unRAID Wiki). There are many current and past discussions, that might produce useful FAQ entries.
December 3, 200817 yr I'm very disappointed from that hdd! I bought one about one month ago and after two weeks i got read/write errors (it worked as the parity disk) caused by badsectors (9 reported by mhdd), so i went to the shop and was given a new one which had the same manufacturing date and was coming from the same series (-300 SD17). I took it home and updated the firmware to SD1A as described in this thread. Then i ran and MHDD test just to make sure i can put it into my unraid box and have no problems in near future. Unfortunately MHDD showed 3 blocks with response time between 150 and 500ms and 233 blocks with response time between 50 and 150ms which are very likely to change into badsectors soon. That's very disappointing. I guess that a faulty set of them must have been manufactured, because it's not possible that two similar disks suffer such an issue from the very beginning. Has any of you experienced that problem? Here are photos of the old disk (left) and the new (right):
December 4, 200817 yr Got my 2 new drives today. Both are part #9JU138-301 Firmware CC1G Date Code 09212 Does this mean I don't need to worry about the firmware upgrade?
December 5, 200817 yr Got my 2 new drives today. Both are part #9JU138-301 Firmware CC1G Date Code 09212 Does this mean I don't need to worry about the firmware upgrade? I ran them both through the Seatools Long Test in DOS (4 hours each) Both passed fine and no loud clicks or noises, pretty much dead quiet. So looks good so far, waiting to here back from Seagate about the firmware, hope to get the Parity drive swaped out tonight.
December 5, 200817 yr Got my 2 new drives today. Both are part #9JU138-301 Firmware CC1G Date Code 09212 Does this mean I don't need to worry about the firmware upgrade? Where did you get them?
December 5, 200817 yr Got my 2 new drives today. Both are part #9JU138-301 Firmware CC1G Date Code 09212 Does this mean I don't need to worry about the firmware upgrade? Where did you get them? Newegg $119.99
December 6, 200817 yr Just though I would update that I installed one of the new 1.5tb drives as the new Parity drive last night. My old mother board saw the PROMISE SATA300 TX4 PCI, and recognized the drive as 1500meg no problem. Parity check with no errors. This afternoon I will add in the other 1.5tb drive is as a new data drive (along with my old parity drive) Still haven't heard anything from Seagate if the CC1G firmware needs any update, its been olmost 25 days and the tech support says within 24 hours, typical BS
December 6, 200817 yr Author Still haven't heard anything from Seagate if the CC1G firmware needs any update, its been olmost 25 days and the tech support says within 24 hours, typical BS Keep Bugg'n them. This would be good info!! I'm guessing no update is needed, but it'd be nice to hear from Seagate.
December 6, 200817 yr Still haven't heard anything from Seagate if the CC1G firmware needs any update, its been olmost 25 days and the tech support says within 24 hours, typical BS Keep Bugg'n them. This would be good info!! I'm guessing no update is needed, but it'd be nice to hear from Seagate. If I don't get an answer by Monday I might just call them. Went to buy the Pro version of UnRaid, only have the free now. Didn't realize that you have to wait to get the registration file, so I might not get the other drives added today, don't know whow long it takes to get the file, week end besides....
December 7, 200817 yr I bought two of these drives from Newegg and received them on Friday. One was SD17 and the other was CC1G. I read on avsforums that CC1G should be replaced with the CC1H firmware. Someone posted a link to the files there. I have updated the firmware on both and ran tests using SeaTools. I now have them both incorporated into my unraid system with no issues so far.
December 8, 200817 yr I bought two of these drives from Newegg and received them on Friday. One was SD17 and the other was CC1G. I read on avsforums that CC1G should be replaced with the CC1H firmware. Someone posted a link to the files there. I have updated the firmware on both and ran tests using SeaTools. I now have them both incorporated into my unraid system with no issues so far. I also got ahold of Seagate today and they confirmed that CC1G needs an update, they are suppose to be e-mailing it to me. I asume that it is CC1H. I do have 2 of these drive with CC1G running in my server now and haven't noticed any problems, have not tried to watch a movie of one yet, just writing data to them. One is the parity drive. Am I correct that I can just pull these drives out and update the firmware on my wimdows machine with a boot CD and not effect the data on the drives?
December 12, 200817 yr Haven't got a chance to update my firmware yet, hope to this week end. But I learned how to run smart reports this morning, figured I would take a look at these 2 new drive. Well I really don't know what I am looking at but thought the rest of you might want to take a look.
January 8, 200917 yr Thought I would up date that both of my 1.5TB drives have been running fine in the server, and they are full (1 parity) So I ordered up another and got it today from New Egg, this one came with Firmware CC1J. From what I have read this one doesn't need to be updated. Got one question though, I have UnMenu now so I figured I would run the smart long test on it. Can I add this drive to the server and run the long set with the array running as long as I don't add it to the array yet?
January 8, 200917 yr Thought I would up date that both of my 1.5TB drives have been running fine in the server, and they are full (1 parity) So I ordered up another and got it today from New Egg, this one came with Firmware CC1J. From what I have read this one doesn't need to be updated. Got one question though, I have UnMenu now so I figured I would run the smart long test on it. Can I add this drive to the server and run the long set with the array running as long as I don't add it to the array yet? You can run the long test on any drive at any time, in the array or not. A better way to evaluate the drive is to "burn it in" while it is outside of the array. Physically install it, but do not assign it to the array... Then, install my "preclear_disk.sh" script and run it on the drive. It will perform a SMART test at the beginning and end, and compare the results to show you what has changed. It will probably take 12 to 20 hours for a single cycle, so don't ask for multiple pre-read/zero/post-read cycles unless you are prepared to wait. We've calculated 20 cycles with a drive that size could take a few weeks. On the other hand, after a few weeks, if it still looks good in the SMART reports, odds are good you will not suffer an early failure. An advantage of using the pre-clear script is that your array will only be off-line for a few minutes when you go to add the drive to your array instead of being unavailable for 4 to 6 hours while unraid clears the drive. Find the script here: http://lime-technology.com/forum/index.php?topic=2817.0 Joe L.
January 9, 200917 yr I ran it last night and it got done this morning, 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 51c51 < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 8057 --- > 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 27674 35 55c55 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 5632 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 16693 60,63c60,63 < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 < 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0 < 190 Unknown_Attribute 0x0022 067 067 045 Old_age Always - 55495 8881 < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 189 Unknown_Attribute 0x003a 093 093 000 Old_age Always - 7 > 190 Unknown_Attribute 0x0022 068 064 045 Old_age Always - 60529 0528 > 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always 66,69c66,69 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 22788 6669758464 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3281 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 60331 405606925 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 29297 73402 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 15645 95134
January 9, 200917 yr I ran it last night and it got done this morning, 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 51c51 < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 8057 --- > 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 27674 35 55c55 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 5632 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 16693 60,63c60,63 < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 < 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0 < 190 Unknown_Attribute 0x0022 067 067 045 Old_age Always - 55495 8881 < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 189 Unknown_Attribute 0x003a 093 093 000 Old_age Always - 7 > 190 Unknown_Attribute 0x0022 068 064 045 Old_age Always - 60529 0528 > 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always 66,69c66,69 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 22788 6669758464 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3281 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 60331 405606925 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 29297 73402 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 15645 95134 Nothing there looks really odd to me, the counts that differ don't look like anything to worry about. Most of the values look like internal numnbers that will change from test to test.
January 9, 200917 yr It working on copying 180 gig to the new drive now, but all looks good. These drives make me a little nerves but for the price you can't beat it. By the way that is a great little program. It only took a couple of minutes to add the drive to the array, hardly any down time at all. Thanks
January 27, 200917 yr Author What a freaking mess.... Click here to download the SDIB firmware. Be sure to verify the model number of your drive so you don't cause any damage by installing the incorrect firmware: http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207957
January 28, 200917 yr It's even more of a mess because certain drives with firmware SD17, SD18, and SD19 are stated on the Seagate website (through their serial number tool) as being "unaffected, no action necessary." While this might be true, to me there also seems a substantial chance that they will later say -- "oops, those drives were affected" and only after we've all suffered more drive failures. I am upgrading all my drives with firmware in this range. I appreciate that Seagate's response has been more than perfunctory, but what they need to do is make volumes of information available so that we can all really easily determine whether any sort of firmware upgrade is necessary on every possible drive.
January 29, 200917 yr Does anyone know this? I've been upgrading my Seagate 1.5 TB (firmware SD17) to firmware SD1B and then doing the long test from Seatools on them. One drive upgraded well and then passed the long test without too much concern. A second drive seems to randomly freeze the long test at various, inconsistent points. It has made it through the long test twice and frozen 4 times. Basically the whole Seatools (for DOS, bootable ISO for CD-ROM) interface freezes up, and I have to reboot to get out of it. The first drive didn't freeze Seatools, although possibly I just got lucky. However, I am wondering if it's possible Seatools is freezing by some issue external to the second drive since the drive has passed the test twice and I would think that Seatools would be designed well enough that if the drive is the cause of the freeze that Seatools would report this as a problem rather than just freezing. What I am trying to figure out is whether this drive is failing and I should RMA it. I've asked the same question through the support interface at Seagate but I hardly expect an answer before summer. Anyone know enough about Seatools to know if this is more of a software problem, or a problem with my desk-assembled caseless firmware upgrade rig, or it really is this drive? Thanks
Archived
This topic is now archived and is closed to further replies.