arga

Member
  • Content Count

    837
  • Joined

  • Last visited

Everything posted by arga

  1. Hi: sorry for the delay. here is the update: The Bad Blocks were unmarked after I erased the drive with HDDScan. Now this drive seems ok. The other drive, the one with many "greens", remains the same, now about 60 greens. I will wait a couple of weeks, and scan again, to see if the number of greens rise again.
  2. I have bought 2 Samsung hard disks, both are the same model HD103UJ, 1 Terabyte, SATA. I bought the first one in July, and the second one in August, in different shops. I have scanned both units using HDDScan. The first one has an acceptable HDDScan (only 9 slow blocks-green) But the second one has a lot of slow blocks (476 green blocks). Both units pass the Samsung diagnostics OK. I would like to return the second one, but I wonder if the shop will be willing to change it for a new one. I fear that they will argue that the disk is not defective because it passes the Samsung test ok. I bought this disk just last week. I would like your opinion. Here are the scans:
  3. okay, understood. Anyway, before running ESTOOL>erase I will try to erase these sectors with HDDScan (this way they won't be reallocated yet). Now I am still doing the full scan to see if there are more bads. Something I don't understand, is why this disk didn't develop Bad Sectors when it was formatted first time (long format, writing to disk), but developed 6 bad sectors when I filled it with data.
  4. sorry for the delay: I have formatted the drive using Windows. Long format. But nothing has changed. In SMART, the sectors are still marked as Bad, but only pending, and in HDDScan they show up when I do a partial scan around the affected area. Proceeding to full scan.
  5. @666: Ok, thanks for the detailed explanation about bad sectors. I will format this drive, and see if the pending bads have been unmarked. But first I will ground the drive. @weaker: yes, 666 suggested that my disk's shrinkage to 32MB was caused by Gigabyte Ghosting function, but I agree with you, I think the cause was the Bios backup function. I think the Gigabyte Ghosting function doesn't reserve any space in disk unless you invoke this function... but I have no confirmation of this, because I haven't tested it.
  6. I think these 6 Bad sectors are not bad sectors really. Is there any way to free them up? I have been googling, and nothing conclusive, but it seems that you can "unmark the bad blocks" and get them back for use, by simply deleting the MBR, or repartitioning the drive. Is that ok? well, maybe just erasing them, will do the trick, as they are still "pending", and "not yet reallocated"...
  7. Hey, I know it sounds ridiculous, but could it be that my bad sectors happened because my drive is mounted on a plastic adaptor, without electric contact with the chassis? The bad sectors appeared when I did the massive writing on the disk. Look at this: http://users.iafrica.com/c/cq/cquirke/baddata.htm I don't understand well what it says, but could be related.
  8. okay, I see that md5 redundancy can solve many other situations when a file is broken. I was referring to bad sectors. Apparently Windows can detect that a file is broken when the cause is a bad sector. without having any other redundancy. I am going to explain the precise sequence of what happened to my F1 (1TB) drives. Drive 1: Purchased in July. Initially good scans. Drive 2: Purchased in August. Initially horrible scans, lots of greens, but no bad blocks. Lots of tests but no writting on the disks... ... Now, first I filled Drive 2 with data. Scan improved. and no bad blocks. Then I copied Drive 2 contents into Drive 1 (just Copy in Windows). And then, I run MHDD, and BadBlock appears in Drive 1. I have just checked SMART in this drive 1: it says: "6 pending sectors". No less than 6 sectors! They are still not reallocated. Just pending for reallocation. If I erase them with ESTOOL, I think it will map them out, and the drive will be "ok" again.
  9. md5? but in theory there is no need for that. The normal filesystem already has built in redundancy to detect errors, no? in fact, HDDScan and MHDD detect Bad Sectors without the need of md5 or any other extra redundancy. Just that they don't tell you what files are affected. Isn't there any program capable of verifying the files, using this built-in redundancy? --- Is there any way to disable Gigabyte's Virtual DualBIOS backup? After what has happened, I don't feel safe with it. I would gladly disable it. But I don't see anything about it on BIOS or in the manual. ----- re. the bad sectors that I got, I don't know if should erase the disk to force reallocation, because once reallocated, the ESTOOL will pass without error, and thus, the shop wouldn't want to RMA... this is all very annoying grrr.
  10. Well, I don't know, I did read the SMART report several times when I ran HDDScan, and there was no pending allocation. Everything was ok. I saved these reports, and I have them with me. The bad sector appeared suddenly after I filled the drive with data, and I ran MHDD. This was the first time I wrote data on this drive. Until then, it was only formatted Yes, I powered this drive at the same time with the other one. In fact, after I filled the other one with data, I copied that data to this one. I have ran Samsung's ESTOOL, and indeed it detects the problem: it reports 6 consecutive bad LBAs. It prompts me to ERASE the drive, and in case the error persists, contact Samsung. So, isn't a bad block enough to return the drive? This one is less than 2 months old!!
  11. Surprise: I got a bad sector in my good 1TB drive!! Until now, the drive was empty, and formatted, and scans were good. But today, I have filled the drive with data, and now a Bad sector appears!! The scan is good (8 greens) but now there is a bad block. The bad block appears in both MHDD and HDDScan!! How is this possible?? I did nothing out of the ordinary on this drive. It was in the other one, where I did all the experiments. On the other side, I have also filled the bad 1TB drive with data, and the scan has improved a lot. Now only 49 greens in MHDD. And no bads.
  12. @both: I think: Xpress BIOS Rescue=Vitual BIOS Xpress Recovery=Ghost No, I didn't install nor run any of these. @666: Is the MBR restored automatically when you Init, partition, and Format the drive with Windows?
  13. and does it work with modern hard drives??
  14. ok, as I don't have linux, I will do fine with the russians. I trust them I am using a software called MyTheatre, for satellite TV. This is a russian program too, and it is great. ProgDVB is also russian. Don't underestimate russian programmers, baby. I don't know anything about FTP servers, but I understand what you say about the benefits of open-source code.
  15. guys, after my disk was shrinked to 32MB, I went to Samsung ESTOOL, and out of desperation, I erased the MBR. Is this important? Is there any distinct info in the MBR that can't be restored? The drive is working ok now, doesn't look like there is any problem with that.
  16. GIGABYTE Xpress BIOS Rescueâ„¢ Technology http://www.gigabyte.com.tw/FileList/NewTec...s_explained.htm
  17. Another possible correction: I think the Gigabyte mobo *creates* the HPA, which otherwise doesn't exist.
  18. Yep, most freeware SMART toold show the raw value. But at that time, I didn't pay attention to the RAW values, as I thought they were "scrambled", hehe. Well, not really. This 160GB drive already had a high green count from the beginning. And the bad sector came from the beginning. I just didn't have the knowledgement to react appropriately when I bought it. thats a luxury OS someday I will build a Linux PC. maybe the refurbished is worse I use Bartstuff for 1 or 2 hours.But I am not expert in burning in. I also have very low failure rates. Just one drive came DOA. Sometimes, there's a drive that looks like it is dying, but then I find that it is just the molex that is loose.
  19. Hello 666: I once tried HDDRegenerator in one of my drives. It was a Samsung P80, 160GB. I bought it in 2003. To keep the story short, it had a bad block. I used HDDRegenerator, and the bad block dissapeared. I though this bad block was fixed, but now, looking at the Smart Report carefully, I see it was really mapped out, because Reallocating events (RAW) =1 Uncorrectable sector count (RAW) =1. This are the Raw values. The "processed value" is =100=perfect. The semaphore is yellow, but back then, I thought it was an error, because the "Processed Values"=100=Perfect. But now I realize that there was 1 sector reallocated. So maybe HDDRegenerator is not as good as I thought... I have scanned this drive now with MHDD, and it shows 30 "greens". Considering that its only 160GB, its pretty high. The rest of my drives are ok. No problems. Ok, I think I will try to create a Bad Block with MHHD. Can I create a single bad block in the location I choose? Another doubt: will I get a new one, or a refurbished one? I am sorry to hear your experience with that fridge. You wanted a specific product, and the salesman fooled you. Then you had to spend time modding it, and you had to take risks. Just imagine if it fails just after the warranty expiration. I am also very demanding about noise. I have read testimonies of people buying TFT monitors with noisy power supplies. This is also a delicate situation because the manufacturer could deny a replacement. In Spain, there is a mandatory 7-day no-question warranty. Some shops extend it to 10, 15, or even 30 days. Internet shops normally give the minimum (7 days). I was slow, and didn't test the Samsung F1 quickly enough. Next time I will test it in the first day, and it will go back to the shop immediately if there are too many greens.
  20. just another question: If I create bad blocks with MHDD, will I be able to regenerate them (eg, with HDDregenerator), or at least map them out? I say this, because if I create a bad block to force the RMA, but Samsung doesn't accept the RMA, then I would get the disk back with the bad block.
  21. MHDD bypasses DOS and BIOS and talks directly from controller to the drive. You eliminate OS/driver issues in this scenario. In windows, there are too many factors to consider to single out a problem. For example, my jmicron controller driver is buggy. They were listing PATA drives as removable storage in windows till just a few weeks ago! It bails out every once in a while and windows test results get screwed. In this scenario, i drop to DOS and test drive fitness from there. Almost all the time problems are not arising from the drive. In fact, I never had any drive fail after running stress tests for a day on it. If it did not fail, or if it was not a defective drive, i do not get problems with it later on [except when i really fiddle with a drive quite a lot]. HDDScan... has some bugs... For example, when chosen READ test, it is supposed to transfer the data through the controller. But it does not. I think it just does verify when READ is chosen. SOLUTION: Run Victoria for Windows 4.3 for READ tests. It also does not create proper MHT reports for archival purposes. I was shocked to find the graph for one of my drives was replaced with the current scan. Apparently, it does not include the image in the MHT file but makes a reference to its location in hddscan folder. This is not good. By the time i found this out, i lost many reports. Because after you run the test, the report works fine even if you move it elsewhere. So you think it is done with, and move it and run another drive. Only to find out in the future that none of your graphs are present! SOLUTION: Open the hddscan report file in IE. Save it as html. Open the html, save as MHT. Hello 666: thanks for your many advices. Okay, I will use MHDD in DOS to scan the drives, instead of HDDScan in Windows. In the hddguru forum, I have received the same advice from several posters. Now I have just realized, that this would be particularly useful when you need to scan the boot, primary drive. I only use "verify" in HDDScan. I didn't know the difference between read and verify. I decided to use "verify" long ago, I don't remember why I guess I tried both and I chose verify as giving more meaningful results. Now, reading your post, I understand that if you choose "verify", then the data is read by the disk, and verified, and you don't get the data, but only the result of the verification made by the disk. And if you choose "read" then the data should be read by the controller, and the program. Ok, I will try Victoria and the READ test. Yes, the MHT files lose the images. I noticed it very quickly. I tried to open the mht files in another computer and instead of images, there were little crosses. And, as you say, if I open the mht file in the same PC, then the images are shown, because it finds the image in the HDDScan folder. What I was doing to keep the result, was simply copying image captures into a text file (.rtf). and I copy the log too (I highlight the slow sector list, copy and paste). But now I see your technique, and it is better: open the MHT file in IE, and resave it. I have tried to save it directly in MHT format, and the images are kept. You don't need the extra step of saving in HTML first, unless you really want to keep both formats. cheers
  22. Hello 666: Yes, I tried MHDD scanning, and the results are approximately the same as those of HDDScan in Windows. I am running HDDScan on a pretty clean installation of Windows, and nothing else is running, no internet connection, nothing. So the results are reliable. But it is good to know MHDD, just in case I don't have a clean installation of Windows available, then I will use MHDD in DOS. I erased the disk with MHDD too, but no improvement in slow sectors beyond what I achieved with the first erasure using CMRR. By the way, as I have said before, CMRR didn't cause the shrinkage to 32MB. It was the Gigabyte mobo. Gigabyte mobos normally reserve 1 MB of disk space on the primary disk. But this mobo reserved much more My other Gigabyte mobo (G31 chipset) works correctly. It only reserves 1 MB. Furthermore, I have upgraded the BIOS of the buggy mobo,to version F6c, and now works correctly too, reserving just 1 MB on the Samsung. So this has been a good day, I guess. Yes, now is time to rest @ weaker: I have flashed my Gigabyte mobo (the one who shrinked the drive to 32MB) to the latest version, the F6c, and voilá, the problem has been solved, and now the mobo only reserves 1 MB on the disk when it is the primary disk. It is funny because this improvement is not documented in the F6c legend. The buggy Gigabyte mobos, instead of reserving 1MB, they reserve almost the full Terabyte, and you are left with only 32MB. I think this is what happens. But now both GB mobos have the problem solved.
  23. @weaker: I have just tried the Samsung in my other Gigabyte mobo (G31 chipset). The 32MB problem doesn't happen here (I have tried the drive alone, of course). BUT size decreases by 1 MB. It seems that the mobo is reserving 1 MB for itself. Maybe this is the HPA/DCO area.
  24. Alas, I found the cause. When I run the CMRR eraser with the Samsung drive as only drive (as Secondary master) , HPA and DCO areas appear in the disc, and are detected by CMRR. Also, the drive will shrink to 32MB, even if the CMRR Erasure is not finally run. So both things are related: When the drive is the only drive, size goes down to 32MB, and HPA/DCO areas appear. But if I run CMRR with 2 disks, one Primary Master, and the Samsung as Secondary Master, then these areas doesn't exist, and the 32MB problem doesn't appear. More: I have run tjhe CMRR erase a second time, but this time there was no improvement regarding slow blocks. I am now above 100 'greens'.