March 1st, 2013, 20:30
March 1st, 2013, 21:31
Nicki2012 wrote:it took a while for the BIOS to read the SMART status.
March 1st, 2013, 23:23
Vulcan wrote:Nicki2012 wrote:it took a while for the BIOS to read the SMART status.
That behaviour likely means you've got a problem with the drive, as there is no good reason for a drive causing a (measurable) delay reporting its SMART status. As always (and especially with that indication of an internal drive problem), the drive could fail at any time. This drive problem might even have been the cause of the Win7 crash.
There are several possible options, depending on the value of the data on the drive, whether you have a recent backup or not (and how much data is not backed-up), your attitude to risk, your skills (if you decide to take the risk of DIY activities), your budget etc. etc.
If you give more info about the current situation, then readers might be able to give more replies.
March 2nd, 2013, 0:29
Nicki2012 wrote:It's a new drive.
Nicki2012 wrote:It has performed rather stably.
Nicki2012 wrote:The delay happened BEFORE the HD was spin up, as soon as the motor reached the normal speed, the SMART was displayed immediately, WITHOUT delay.
Nicki2012 wrote:There is some strange though, I can't read health status using HD tune. Don't know why.
Nicki2012 wrote:Would an error scan by HD tune help decide it's actual status?
March 2nd, 2013, 2:58
Vulcan wrote:Thanks for the clarifications.
Vulcan wrote:You haven't answered my question about whether you need the data on the drive, and whether you have a current backup.
Vulcan wrote:Why do you say rather stably? That could suggest that you have some concerns. Have there been any other problems before now?
Vulcan wrote:Has the drive always made the spin-up sound that you mention, or is this new behaviour - e.g. only since the Win7 crash?
Vulcan wrote:I think you're saying that this noise is definitely new (which is bad news), but I'm not sure.
Vulcan wrote:Thanks, that explains the delay in the BIOS displaying the SMART status, since SMART data is held on the platters, so the drive can't report it's SMART status until the platters are spinning. However this suggests that the drive took a long time to spin-up (not just being noisy), since usually a drive would be spinning before the end of even a "fast" BIOS POST.
Vulcan wrote: I'm assuming that the BIOS displayed the drive's SMART status as "pass" (since you didn't say it was reported as "fail"), but of course SMART is not guaranteed to predict all failures, so a SMART "pass" does not mean that the drive is OK.
Vulcan wrote:A screenshot may help, as well as you checking the Windows System Event Log for any error messages at the relevant time (especially any that appear disk-related). Without an error message or more data, I don't know why you can't see the expected info in HD Tune either, other than to say this also sounds worrying.
Vulcan wrote:
If the data on the drive is important and you don't have a current backup, then instead of investigating, personally I suggest the priority should be cloning the drive or using any other technique you prefer to get a backup of the data that you need (all options have risks, because we can't predict if/when the drive may fail). A long spin-up time is a bad sign.
March 3rd, 2013, 0:35
Nicki2012 wrote:Vulcan wrote:I think you're saying that this noise is definitely new (which is bad news), but I'm not sure.
Why bad? The "pooh" sound is new, but spin-down noise is rather familiar to me.
Nicki2012 wrote:I pressed F10 in MHDD and it did a screencap, but it was saved as .log file, which I haven't yet figured out how to read it.
Nicki2012 wrote:MHDD read the full, detailed SMART attribute, again, I don't know how to open it.
Nicki2012 wrote:I'm posting the full surface scan by MHDD here:
Average speed, 120M+
<3ms, 7657632
<10 3102
<50, 96
<150ms, 4 — 4 green dot, should I worry even more?
No sectors > 150ms.
March 3rd, 2013, 22:10
Vulcan wrote:There were some parts of your reply which I didn't really understand, but I'll comment on the parts which I can.
The noise from a drive when power is simply cut (e.g. press & hold the PC power-off button for >5s), i.e. without the drive receiving a Standby command first (which happens during a normal Windows shutdown or reboot), will be a different sound. Reading your previous comments, I'm not sure whether the new sounds are occurring every time the drive spins-up/down or whether you are just describing one event. However if the usual spin-up or spin-down sound has changed, than that would worry me.
Vulcan wrote:I don't have MHDD in front of me at the moment, but I'm fairly sure that it's just a text file (try looking at it with Notepad / Wordpad etc.). Or you could just take a photo of the screen with MHDD displaying the data, and attach that file to your reply (the image only has to be good enough for us to read the text, but without being a huge jpg file!)
Name Val Worst Raw
Att # 1 : Read error rate : 81 63 142604390
Att # 3 : Spin up time : 94 94 0
Att # 4 : Number of spin-up times : 100 100 88
Att # 5 : Reallocated sectors count : 100 100 0
Att # 7 : Seek error rate : 73 60 24544101
Att # 9 : Power-on time : 100 100 630
Att # 10 : Spin-up retries : 100 100 0
Att # 12 : Start/stop count : 100 100 87
Att # 184 : Unknown : 100 100 0
Att # 187 : Unknown : 100 100 0
Att # 188 : Unknown : 100 100 0
Att # 189 : Unknown : 100 100 0
Att # 190 : Unknown : 66 65 587923490
Att # 191 : Unknown : 100 100 0
Att # 192 : Power-off retract count : 100 100 4
Att # 193 : Load/unload cycle count : 100 100 88
Att # 194 : HDA Temperature : 34 40 34
Att # 195 : Hardware ECC recovered : 117 99 142604390
Att # 197 : Current pending sectors : 100 100 0
Att # 198 : Offline scan UNC sectors : 100 100 0
Att # 199 : Ultra ATA CRC Error Rate : 200 200 0
Vulcan wrote:Let's see whether the full SMART data gives any clues. Also, you said this is a Seagate drive - have you downloaded & run the SeaTools tests on the drive? If not then, after you have made a backup of this drive (and checked that the backup is readable), I suggest running the SeaTools tests.
Also I didn't see any reply to my earlier suggestion that you checked the Windows System Event Log for any error messages at the relevant time (especially any that appear disk-related). I have seen many previous examples where useful messages were logged there.
Without having the drive in front of me, those are the only suggestions I can think of
Powered by phpBB © phpBB Group.