May be of some use to people out there.
Most people spend their time on the "urgent" rather than on the "important."
Most people spend their time on the "urgent" rather than on the "important."
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Seagate HDD Firmware flaw.
- Thread starter Sympology
- Start date
- Status
goombawaho
MIS
This type of thing is more common than you think - firmware affecting reliability of a hard drive.
More often it's seen in the enterprise type of storage systems using SCSI drives where there are semi-regular updates for HDD firmware and utilities to easily flash the firmware.
But that's not to say that consumer drives don't have updates/update utilities. Something to look for periodically if you want to keep all bases covered.
More often it's seen in the enterprise type of storage systems using SCSI drives where there are semi-regular updates for HDD firmware and utilities to easily flash the firmware.
But that's not to say that consumer drives don't have updates/update utilities. Something to look for periodically if you want to keep all bases covered.
This might be some interesting reading as well for some. Of course, extreme caution is warranted if you decide to try any of it.
Measurement is not management.
Measurement is not management.
- Thread starter
- #5
UPDATE
DO NOT install the update. It has been pulled.
Most people spend their time on the "urgent" rather than on the "important."
DO NOT install the update. It has been pulled.
Most people spend their time on the "urgent" rather than on the "important."
Also read for more info: thread751-1525155
Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Apologies if I'm hijacking, but this seems appropriate..
I've got 2 of the 1.5tb drives with SD17 firmware in my Thecus NAS.
SMART information shows the following:
Drive 1 (reads OK according to NAS)
- Reallocated Sector Count 0
- Current Pending Sector Count 0
- Seek Error Rate : 18292138
Drive 2(reads Warning according to NAS)
- Reallocated Sector Count 0
- Current Pending Sector Count 0
- Seek Error Rate : 2147483647 (and rising slowly)
Neither drive has issues with stuttering when streaming DVD isos - which was the original reason for the firmware fix (if I'm correct).
I've also read that SMART readings other than SeaTools readings are unreliable with Seagate disks.
Should I be concerned about either drive? I've got a Seagate support query pending, but I suspect they may be a little busy.
I've over 1.72TB of data to try and backup if there's an issue so I'm slightly concerned (lol)...
TazUk
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
Martin Golding
I've got 2 of the 1.5tb drives with SD17 firmware in my Thecus NAS.
SMART information shows the following:
Drive 1 (reads OK according to NAS)
- Reallocated Sector Count 0
- Current Pending Sector Count 0
- Seek Error Rate : 18292138
Drive 2(reads Warning according to NAS)
- Reallocated Sector Count 0
- Current Pending Sector Count 0
- Seek Error Rate : 2147483647 (and rising slowly)
Neither drive has issues with stuttering when streaming DVD isos - which was the original reason for the firmware fix (if I'm correct).
I've also read that SMART readings other than SeaTools readings are unreliable with Seagate disks.
Should I be concerned about either drive? I've got a Seagate support query pending, but I suspect they may be a little busy.
I've over 1.72TB of data to try and backup if there's an issue so I'm slightly concerned (lol)...
TazUk
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
Martin Golding
It was probably better to start your own thread as the title of this thread won't attract anyone to your problem...
Having said that, those seek error numbers seem incredibly high and I can't believe SMART hasn't thrown errors. Is the device functioning okay? Numbers like those I would think you would see slow data access. Have you tried contacting Thecus support? They may be a little less busy than Seagate at the moment. What tool is reading these numbers?
And the flash referred to in this thread wasn't for stuttering. It is for the potential of a drive's data to become inaccessible after a power cycle.
Having said that, those seek error numbers seem incredibly high and I can't believe SMART hasn't thrown errors. Is the device functioning okay? Numbers like those I would think you would see slow data access. Have you tried contacting Thecus support? They may be a little less busy than Seagate at the moment. What tool is reading these numbers?
And the flash referred to in this thread wasn't for stuttering. It is for the potential of a drive's data to become inaccessible after a power cycle.
Thanks for responding Freestone.
It's the basic onboard diagnostics on a Thecus N3200 NAS that are reporting these figures, hence my comment about Seatools vs other SMART reporting tools.
I've seen no issue with streaming films from the drives - the NAS functions primarily as a Movie Jukebox as well as secondary backup for my Debian server.
I'll raise a case with Thecus tonight, although I suspect they'll refer me to their HDD compatibility list (which excludes the 1.5tb drives although the 1tb from the same family are listed as compatible).
TazUk
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
Martin Golding
It's the basic onboard diagnostics on a Thecus N3200 NAS that are reporting these figures, hence my comment about Seatools vs other SMART reporting tools.
I've seen no issue with streaming films from the drives - the NAS functions primarily as a Movie Jukebox as well as secondary backup for my Debian server.
I'll raise a case with Thecus tonight, although I suspect they'll refer me to their HDD compatibility list (which excludes the 1.5tb drives although the 1tb from the same family are listed as compatible).
TazUk
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
Martin Golding
May not be the cause for concern that I first thought, per:
(different model NAS but much of the firmware is similar).
I'll monitor it for now and create a new thread if problems persist..
TazUk
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
Martin Golding
(different model NAS but much of the firmware is similar).
I'll monitor it for now and create a new thread if problems persist..
TazUk
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
Martin Golding
I personally think that the SMART numbers are just plain wrong, and I wouldn't worry too much about it. The concern is regarding the Seagate 1.5 TB model, however.
This thread has some remarks regarding both SMART (apparently there is a Beta release for the NAS, not sure if it applies to your model) and further talk of the Seagate 1.5 firmware release(s).
You may also want to peruse some of the Seagate Community Forums.
I am unsure how one would apply firmware updates to drives contained within a NAS.
Good Luck.
This thread has some remarks regarding both SMART (apparently there is a Beta release for the NAS, not sure if it applies to your model) and further talk of the Seagate 1.5 firmware release(s).
You may also want to peruse some of the Seagate Community Forums.
I am unsure how one would apply firmware updates to drives contained within a NAS.
Good Luck.
![[shocked]](/data/assets/smilies/shocked.gif "[shocked] [shocked]")
Hi Guys....I ordered a 7200.11 500gig yesterday! I came very close to cancelling it last night but didn't, I'm not absolutely sure I have done the right thing but from my take on events....the actually drives are basically sound and this is just a firmware issue...and that once flashed to the latest (as of yesterday) firmware these problems are resolved.
My question is...as this will be my boot drive on my main machine, shall I run the drive as is and firmware upgrade in a few weeks time when perhaps a better firmware is available or should I upgrade straight away before installing the OS. I mean, chances are the thing will run OK with the original firmware until a fully sorted update appears....what U reckon?
Martin
On wings like angels whispers sweet
my heart it feels a broken beat
Touched soul and hurt lay wounded deep
Brown eyes are lost afar and sleep
My question is...as this will be my boot drive on my main machine, shall I run the drive as is and firmware upgrade in a few weeks time when perhaps a better firmware is available or should I upgrade straight away before installing the OS. I mean, chances are the thing will run OK with the original firmware until a fully sorted update appears....what U reckon?
Martin
On wings like angels whispers sweet
my heart it feels a broken beat
Touched soul and hurt lay wounded deep
Brown eyes are lost afar and sleep
I would personally wait until the firmware is settled. I am running 500GB 7200.11s here and at home, and have had no problems with them. Aside from the 1Tb drives, nobody I know has had any problems with the stock firmware.
"We can categorically state that we have not released man-eating badgers into the area" - Major Mike Shearer
"We can categorically state that we have not released man-eating badgers into the area" - Major Mike Shearer
Hey Martin,
I've been following this closely and remember reading that ALL 7200.11 drives are affected and need new firmware. I tried to find the link where that was stated but all those links within links leading to other links left me lost (Oh my!). Anyway, I have several dogs in this fight (about {10} 7200.11 drives scattered around my network) so I am wanting to make sure I am doing the right thing. Only a few are the 500GB and no 1 or 1.5 TB drives in my army, but that statement that ALL 7200.11 drives are subject to the "320th-write-bricking-drive" disease NOT the "firmware-updating-bricking disease" which resulted from customers updating working drives with bum firmware.
I am taking the "wait-and-see" approach as I see the probability of the 320th-write etc. problem being VERY low and tend to be of the mind "don't fix what ain't broke" since the biggest problem seems to have been caused by people updating firmware. Read through that SlashDot post linked to in thread751-1525155 to get more info.
I have always been a Seagate fan (almost exclusively except for the Raptor, my favorite drive) and have not decided yet whether this will change my mind or not, probably not, the chances are just about the same for all drives to fail, especially with prices falling and shortcuts being taken. Still, when you think about what they do, HDDs are amazing little machines, and will be around for quite a while even after SSDs get competitive price-wise.
Tony
Users helping Users...
I've been following this closely and remember reading that ALL 7200.11 drives are affected and need new firmware. I tried to find the link where that was stated but all those links within links leading to other links left me lost (Oh my!). Anyway, I have several dogs in this fight (about {10} 7200.11 drives scattered around my network) so I am wanting to make sure I am doing the right thing. Only a few are the 500GB and no 1 or 1.5 TB drives in my army, but that statement that ALL 7200.11 drives are subject to the "320th-write-bricking-drive" disease NOT the "firmware-updating-bricking disease" which resulted from customers updating working drives with bum firmware.
I am taking the "wait-and-see" approach as I see the probability of the 320th-write etc. problem being VERY low and tend to be of the mind "don't fix what ain't broke" since the biggest problem seems to have been caused by people updating firmware. Read through that SlashDot post linked to in thread751-1525155 to get more info.
I have always been a Seagate fan (almost exclusively except for the Raptor, my favorite drive) and have not decided yet whether this will change my mind or not, probably not, the chances are just about the same for all drives to fail, especially with prices falling and shortcuts being taken. Still, when you think about what they do, HDDs are amazing little machines, and will be around for quite a while even after SSDs get competitive price-wise.
Tony
Users helping Users...
Martin - The firmware has been out a little over a week and seems to be stable. There appears to be no outcry from anyone who has applied the LATEST SD1A fix.
The problem that is addressed by the fix has a low-probability of occurring, or at least that it what I've been reading (This appears legit -
Given that you are getting a new drive, the chance of hitting journal number 320 when powering up is pretty slim. You would probably be okay to use the drive for awhile to see if the firmware changes at all.
The problem that is addressed by the fix has a low-probability of occurring, or at least that it what I've been reading (This appears legit -
What isn't clear to me is if the problem does occur can it be revived through a flash? I think not if it isn't being detected in BIOS, but I am not absolutely sure.
Given that you are getting a new drive, the chance of hitting journal number 320 when powering up is pretty slim. You would probably be okay to use the drive for awhile to see if the firmware changes at all.
![[sunshine]](/data/assets/smilies/sunshine.gif "[sunshine] [sunshine]")
OK guys.......just recieved the new OEM Seagate 7200.11 model number (ST3500320AS) which after checking said it had SD15 firmware installed (actually says this on the label as well, this IS one of the effected firmwares.
Downloaded the new SD1A firmware with it's upgrade tool, executed the ISO to burn to CDR, set CDrom as first in the boot sequence and booted into utility. It gives four options so I chose 'A' for ST3500320AS and it imediately and without further warning started to flash the drive...took about 25 seconds and afterwards warns NOT to ctr/alt/del but press any key to power down (heart in mouth at this point lol) counted 20 seconds and rebooted.
Wayhay!!!!!!! detected and reporting new firmware.
Quite easy really but slightly disconcerting nonetheless.
Hopefully now I have a fast reliable drive to replace my 2X WD SE16 Raid 0..don't ask....I will keep you posted..
Martin
On wings like angels whispers sweet
my heart it feels a broken beat
Touched soul and hurt lay wounded deep
Brown eyes are lost afar and sleep
Downloaded the new SD1A firmware with it's upgrade tool, executed the ISO to burn to CDR, set CDrom as first in the boot sequence and booted into utility. It gives four options so I chose 'A' for ST3500320AS and it imediately and without further warning started to flash the drive...took about 25 seconds and afterwards warns NOT to ctr/alt/del but press any key to power down (heart in mouth at this point lol) counted 20 seconds and rebooted.
Wayhay!!!!!!! detected and reporting new firmware.
Quite easy really but slightly disconcerting nonetheless.
Hopefully now I have a fast reliable drive to replace my 2X WD SE16 Raid 0..don't ask....I will keep you posted..
Martin
On wings like angels whispers sweet
my heart it feels a broken beat
Touched soul and hurt lay wounded deep
Brown eyes are lost afar and sleep
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question