DSM-G600, DNS-3xx and NSA-220 Hack Forum
Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Announcement
IRC Channel #funplug on irc.freenode.org
#26 2009-01-23 03:16:00
- skydreamer
- Member
- From: At the Atlantic Coast
- Registered: 2007-01-06
- Posts: 232
Re: Failing Seagate 1TB hard drives
devotee wrote:
Just one thing: the leds are blue on startup, after a little while they go pink, and one of them (the left one) is blinking (pink-red/amber)
No problem about the pink leds (I already had them before, I think it' well-known problem after updating to the latest firmwares), but I don't like the left led blinking like the disk has problems (however, no problems are reported by dmesg or smartctl). I don't understand
Strange indeed, I just finished upgrading 8 disks and no pink issues whatsoever.
To speed things up I had two disks hooked up at the same time on ICH9 and also ICH5 - the former was in the RAID1 mode- and everything went smoothly. Let's hope they will release NS06 soon.
Offline
#27 2009-01-23 15:27:54
- devotee
- Member
- From: Valencia, Spain
- Registered: 2008-12-12
- Posts: 43
Re: Failing Seagate 1TB hard drives
skydreamer wrote:
Strange indeed, I just finished upgrading 8 disks and no pink issues whatsoever.
Right now, the problem seems to be gone. I think I found the cause and solution for the pink leds, at least in my case. I'll post it on another thread.
No issues with the flashed drives, either.Will keep an eye just in case Seagate releases a new version with more fixes, but I'm more self-confident right now with the disks and the backup I0m performing regularly.
CH3SNAS • 2x Seagate Barracuda ES 7200.11 ST31000340AS 1TB SATAII (3.0Gb/s) 7200RPM 32MB (Rev: SD1A) • Individual volumes • FW1.05 (Firmware Date: 12/31/2008) • ext2
Offline
#28 2009-01-24 10:28:02
- krackpot
- Member
- Registered: 2009-01-24
- Posts: 44
Re: Failing Seagate 1TB hard drives
According to a few posters at slashdot: http://slashdot.org/comments.pl?sid=109 … d=26543359
"The conditions have to be just right - you have to reboot just after the drive writes the 320th log file to the firmware space of the drive. this is a log file that's written only occasionally, usually when there are bad sectors, missed writes, etc... might happen every few days on a computer in a nin-RAID home use situation.. and if that log file is written even one time after the magic #320, it rolls over the oldest file kept on the drive and there's no issue. It'll only stop responding IF the drive is powered up with log file #320 being the latest one written... a perfect storm situation."
How do you check with smartctl what the number of the log file is?
DNS-323 (B1) on Alt-F 0.1B7
2x2TB WD20EARS
Offline
#29 2009-01-24 10:56:07
- devotee
- Member
- From: Valencia, Spain
- Registered: 2008-12-12
- Posts: 43
Re: Failing Seagate 1TB hard drives
krackpot wrote:
How do you check with smartctl what the number of the log file is?
I don't think you can get that information with smartctl. As the SMART specifications for each hard drive are different (model, brand,...) the log file might be written differently in each of them, so the "320th line" differs in each case.
With people having half of their hard disks failing, I don't think that this is a very difficult condition to meet. I mean, if the chances are soooo low, how comes there is such a high rate of failing hard disks? Yeah, there's a lot of drives manufactured (millions!) but even if it's a 1% chance (which would affect quite a lot of drives) it wouldn't explain why people is being so lucky... ahem, unlucky and stepping in that randomdish situation in half of their hard drives.
On the other hand, I wonder if disabling SMART in the bios for the hard drives that have the problem would lower even more the risk, or even make it disappear (I'm not sure if that option would disable SMART completely on the disk, or if it's just an "end-user" block and the SMART data is still being silently collected by the drive itself). There are a couple of options in smartctl (-s , -o , -S) that could help there too. However, I can't find any option to do a verbose ouput or a direct dump of the SMART data read from the disk, which could help to determine how many lines the log file has.
CH3SNAS • 2x Seagate Barracuda ES 7200.11 ST31000340AS 1TB SATAII (3.0Gb/s) 7200RPM 32MB (Rev: SD1A) • Individual volumes • FW1.05 (Firmware Date: 12/31/2008) • ext2
Offline
#30 2009-01-25 23:09:39
- Stork
- Member
- Registered: 2008-12-18
- Posts: 32
Re: Failing Seagate 1TB hard drives
I, too, don't have an affected drive - ST31000333AS! 
Although I don't know how long my luck will last.
Thanks to fonz for the tip about smartmontools. Thanks to InBonobo for the login script. And, thanks to devotee for all the running dialog full of good information including helpful links at Seagate.
Keep on sharing.
Offline
#31 2009-01-27 16:46:54
Re: Failing Seagate 1TB hard drives
A new serial number check is online at https://apps1.seagate.com/rms_af_srl_chk/
Offline
#32 2009-01-27 17:45:21
- cheesefood
- Member
- Registered: 2008-11-09
- Posts: 15
Re: Failing Seagate 1TB hard drives
How will this affect my RAID 1 set up? If I pull out one disk, lash it with the new software, then put it back will it reformat and copy? Not too big a problem I guess, but part of my RAID has a JBOD partition left over (since I have a 1TB and a 750, both affected).
Offline
#33 2009-01-27 18:37:15
- skydreamer
- Member
- From: At the Atlantic Coast
- Registered: 2007-01-06
- Posts: 232
Re: Failing Seagate 1TB hard drives
cheesefood wrote:
How will this affect my RAID 1 set up? If I pull out one disk, lash it with the new software, then put it back will it reformat and copy? Not too big a problem I guess, but part of my RAID has a JBOD partition left over (since I have a 1TB and a 750, both affected).
Cheesefood- as long as you shut down the DNS-323 before flashing the drives it is not going to affect anything: Unless there is another bug in the SD1A firmware.....
Offline
#34 2009-01-27 19:46:39
- cheesefood
- Member
- Registered: 2008-11-09
- Posts: 15
Re: Failing Seagate 1TB hard drives
OK, then dumb question #2:
Is it OK if I flash one drive, then wait a few days before flashing the other drive? I'd like to make sure that they don't both crash from the flash. Would there be any problems with having one drive on the update but not the other?I'm figuring that if the flash causes one to crash I can always get a new drive and restore it via the non-flashed drive.
Offline
#35 2009-01-27 21:00:24
- skydreamer
- Member
- From: At the Atlantic Coast
- Registered: 2007-01-06
- Posts: 232
Re: Failing Seagate 1TB hard drives
cheesefood wrote:
OK, then dumb question #2:
Is it OK if I flash one drive, then wait a few days before flashing the other drive? I'd like to make sure that they don't both crash from the flash. Would there be any problems with having one drive on the update but not the other?I'm figuring that if the flash causes one to crash I can always get a new drive and restore it via the non-flashed drive.
Seagate support suggested to upgrade all disks at once when I asked them the same question last week.
Offline
#36 2009-02-18 17:15:10
Re: Failing Seagate 1TB hard drives
I just wanted to report in that I successfully flashed both my Seagate 1TB ST31000340AS drives without issue. I yanked and flashed drive 2, plugged it back in to verify, and then yanked and flashed drive 1. I've got a detailed write up here for anyone interested.
horto.ca, my personal DNS-323 howto blog
Offline