|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
||||
Got an update, and a few more questions.
Update first: After I got the replacement disk, I first ran the MHDD tools to see what a good hard drive should look like. Here's what the SMART test looked like on December 4: I got busy reinstalling everything, and soon had a system that wasn't locking up. This morning I got up and was doing my usual morning net things when a phone call came in. I returned to a black screen, with no response to mouse, keyboard, CTRL-ALT-F1, or anything other than the power button. Of course, the first thing I thought of was to find out what the SMART data said: In not quite a month, it has acquired 998 reallocated sectors! with an enormous increase in read errors and seek errors. Around noon today, I bought a replacement disk, this time, a Western Digital Caviar 1tb, and followed this procedure to move the installed OS and programs to the new disk: http://www.bsdguides.org/guides/free..._harddrive.php , which I was relieved to be able to complete without the disk freezing, and I was overjoyed to be able boot onto the new drive after I finished. The Seagate 1tb will go back to the store tomorrow, so before I started the Seagate test program, I ran the MHDD program again for the SMART test, out of curiousity. It had 1026 reallocated sectors. That is 28 new ones just over the course of today! I am currently running Seagate's SeaTools long test, but the short test showed the drive as passing. Needless to say, I don't have much faith in Seagate at this point, but at least I'll be able (thanks to this forum) to tell the guy at the store what to look at instead. Now my new questions are these: One of my transferred files ended up being copied as a 0 byte file, when it had been about 21k, and fortunately, I had a copy elsewhere, but it occurs to me that other files may be missing pieces too, due to the errors on the drive they were dumped from. Is there something I can do now that will recompile everything with a few steps, replacing any missing pieces, or will that be a slow and individual process? I have not done the security updates that came out on Dec 3 yet, and one of them requires rebuilding world. Will this cover recompiling and making complete the missing pieces, mentioned above, for the base system, leaving only the ports to be fixed? Is there anything else I should be concerned about doing in order to deal with any issues from having copied the files using dump/restore from the bad HD to the new one? |
|
||||
It may well be within the manufacturer's 'normal' range. Drive speeds and capacities are pushed to where errors are unavoidable, and recovered by the drive's internals.
If you know what a 'bathtub curve' is, you would understand that a large amount of reallocated sectors in the first month could well be expected. maybe not 1000, though - I have never done the type of investigation you have. (Note that, back in the days of huge 10MB scsi drives, a new drive would have a list of maybe 10 bad sectors printed on its label. The user had to enter those sectors in to the software as part of the setup. A new drive will have some bad sectors, guaranteed. It's just that the drive now takes care of the, not the software.)
__________________
The only dumb question is a question not asked. The only dumb answer is an answer not given. |
|
||||
Very high Read error rate, Seek error rate, and hardware ECC recovered are normal for SeaGate drives. Reallocated sectors, however, are not AFAIK.
Did you also run a surface scan (F4 key twice)?
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
||||
Here's the surface scan from December 4:
And here's the one from this morning: While it was running, it hit patches where the <150ms, <500ms, and >500ms were in an area, and the drive made more noise when it got to them. Here's an error from the drive yesterday: I was in an ssh session finding out how much space I would need to copy it all over to somewhere else. It was running du (I think) when it lost contact. I am thinking that even though it didn't show any UNC errors, the longer access times are just too long for the time FBSD allows for the disk to be read. There were several times it froze yesterday as I tried to get my most important stuff off of it. The thing is, I don't really care about the number of reallocated sectors and whatnot, I care about having a system that doesn't freeze up on me while I'm working, and that I can rely on to keep my data from day-to-day. robbak, I don't remember the bad sector labels on the 10 mb SCSIs, but I do remember thinking I had more space than I would ever need when my workplace bought me a 20 mb drive. When adding a new piece of hardware like a video card meant adding all kinds of stuff into autoexec.bat and config.sys manually to find the magic combination that worked. (I don't miss that at all!) And the floppy disks were actually floppy. |
|
||||
The first MHDD results look fine. The second do not. For a new drive <150ms results are normal, <500ms are hmmish, and >500ms are definitely not OK.
The reason you don't see any UNC errors is because the bad sectors are already reallocated. Now you also see why I recommended MHDD specifically, AFAIK MHDD is only one of two programs which display the time it takes to access sectors (The other being an internal test utility we have at work that someone once wrote). The kernel panic could be a FreeBSD bug or some random glitch, but in combination with all the previous data I have little doubt that the "new" hard drive is broken. This is not uncommon by the way, the drive you received probably isn't new but a refurbished (repaired) drive, IIRC you can actually see that on the Seagate label (Or at least the mfgr. date). There is a good reason why I test RMA drives Quote:
Also, it's my experience that once you have 1 reallocated sector, others start showing up soon (Not always, but often). As a sidenote, there's smartmontools in ports to monitor SMART data and send emails or something after something happens. Very useful for servers and stuff to monitor and preventing problems/unplanned downtime (As we say in Dutch "voorkomen is beter dan genezen", meaning: Preventing is better than curing ). Anyway, any computer store worth it's money will replace this drive, even if the official tool says the drive is OK. If they give you problems you can also return the drive yourself on the Seagate website, this does take about a week though while the store may replace it immediately.
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
|||||
Quote:
Quote:
I guess I am actually pretty lucky because I've never had a disk be bad when I got it, or go bad soon afterwards; in fact I still have a 1gb disk still in use occasionally. Quote:
Quote:
Quote:
Anyway, now that that's all settled, is there an easy one-step way to make sure everything on the new disk that was dumped from the bad disk is complete, and if not, to get it that way? |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
FreeBSD 8.0-RELEASE | Nightweaver | FreeBSD Installation and Upgrading | 10 | 10th December 2009 12:12 AM |
OpenBSD OpenBSD 4.6 Release | Carpetsmoker | News | 21 | 11th November 2009 11:13 PM |
FreeBSD 7.2-RELEASE | vermaden | FreeBSD General | 6 | 12th May 2009 08:33 PM |
-Release vs. -Stable | guitarscn | OpenBSD Installation and Upgrading | 3 | 2nd October 2008 02:32 PM |
FreeBSD 6.2-RELEASE > 7.0-RELEASE Upgrade | Marci | FreeBSD Installation and Upgrading | 2 | 23rd July 2008 02:10 PM |