12 September 2011, 22:22 | #1 |
Moderator
Join Date: Nov 2004
Location: Eksjö / Sweden
Posts: 5,645
|
DH1 Never finishes validating - fix?
(Ye olde problem. Just looking for proper software to stop it from validating forever for my A1200/060/Kick3.1.)
When copying files in WinUAE to the card with Diskmaster, it stopped in the middle saying DH1 wasn't validated. I copied the same dir to DH0: right after, and that went fine. On each reset, the same block comes up as having a read/write error. I've added 2000 buffers and left it on for hours, still validating. Also tried the card in WinUAE again, as sometimes that fixes it in a jiffy. Works fine to access and run all the files on DH1, just can't write to it anymore. Any neat software that removes the file(s) pointing the the bad block(s), marks them up as non-working if they're unwritable, and removes the 'requires validation' flag? You know, something like DiskDoctor, but that actually fixes the disk instead of destroying it. Edit: Jesus, I didn't write it's FFS!? DH1/DH0 are both FFS formatted under kick 3.1, using HDToolbox to partition in WinUAE weeks ago. Last edited by Photon; 13 September 2011 at 20:58. |
12 September 2011, 23:53 | #2 |
Registered User
Join Date: Jun 2002
Location: .
Age: 48
Posts: 5,562
|
Fixdisk possibly:
http://aminet.net/search?query=fixdisk |
13 September 2011, 01:36 | #3 | |
MC68060@85MHz
Join Date: Jan 2011
Location: Poland/Wroclaw
Age: 38
Posts: 76
|
Quote:
Give this a try: http://aminet.net/package/disk/salv/DiskSalv11_32 As far as I remember, DiskSalv can also mark BadBlocks. Even if not, it will certainly fix the validation. Best practice is to replace the disk with another one as badblocks tend to grow with time. I also noticed that newer drives (mostly WD's) suffer from a phenomenon I call "soft badblocks" that disappear completely when given "badblock" is erased (or simply being written any data to). This happens very often on newer WD drives, and on other manufacturers (Seagate, Samsung) to some extent, too. Most of the time I receive a bad PC for service is that it has a single badblock that prevents the OS from booting. I run MHDD on PC to determine which block it is, and once found, erase it. It disappears and suddenly the PC is booting fine. Last edited by altcomputing; 13 September 2011 at 01:44. Reason: Added some info on badblocks. |
|
13 September 2011, 04:14 | #4 |
I hate potatos and shirts
|
If you can't rescue the disk with DiskSalv, then Quarterback Tools 5.x is the shiz.
|
13 September 2011, 09:25 | #5 |
-
Join Date: Jul 2003
Location: Helsinki / Finland
Age: 43
Posts: 9,883
|
And if QBTools doesn't do it, then ABTools. Naturally all of these only work for FFS partitions.
|
13 September 2011, 12:25 | #6 |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
hi photon
have you tried lowering the amount of buffers to around 120.and re-format it. |
13 September 2011, 21:06 | #7 |
Moderator
Join Date: Nov 2004
Location: Eksjö / Sweden
Posts: 5,645
|
I have 110 buffers actually And... rescue the disk... sure, DH1 might go all corrupted, who knows. But normally it's a backup/copyto kind of disk so it's not end of times if one file is corrupted, not being able to write to it is a much more severe PITA.
But in WinUAE I've copied about 100MB to DH1 without a single error (and 400 MB to DH0). Must say I haven't written to it much when I've used in the Amiga, but when I have it has worked fine. I've used it for maybe 1.5 weeks. Thanks for the program tips, will try'em I used QB & Disksalv back in the day of course, but it's always nice to know true tested ones on the 68060+CF+FFS combo. Edit: Worked fine on 2GB (<4GB) CF card (DH1 start within 1GB) with ABtools (Aminet patches not needed), 'Analyst' button. Apparently Quarterback is in TOSEC, only patches on Aminet. Might try Dave Haynie's DiskSalv on Aminet if it happens again just to test... Last edited by Photon; 13 September 2011 at 21:56. |
13 September 2011, 23:32 | #8 |
Da Digger :)
Join Date: Nov 2008
Location: Monza, Italy
Posts: 2,822
|
|
14 September 2011, 00:48 | #9 |
Global Moderator
Join Date: Aug 2008
Location: Sidcup, England
Posts: 10,300
|
|
14 September 2011, 20:38 | #10 |
Moderator
Join Date: Nov 2004
Location: Eksjö / Sweden
Posts: 5,645
|
Let it be said that it's unlikely a pretty new CF card like this would get a bad block from anything but an incompatibility or software misfire during a write, unlike HDDs*, who suck. So much that I will never put a harddisk in any computer I ever fix up or buy. Ever. Not once.
* noisy, hot, slow record players with technology from the 1970s. |
15 September 2011, 01:01 | #11 | |
Da Digger :)
Join Date: Nov 2008
Location: Monza, Italy
Posts: 2,822
|
Quote:
I didn't know it. |
|
20 August 2021, 00:50 | #12 |
Registered User
Join Date: Jul 2021
Location: Aarslev, Denmark
Posts: 90
|
Sorry, I know this is somewhat off topic, but I can't help mentioning it here.
A couple of weeks ago I was running WB 1.3 with KS 1.3 on a tiny 43 MB SCSI drive on my CDTV, and shortly before that I actually only had a floppy drive, since my CD-ROM drive was failing. Now I'm running AmigaOS 3.2, KS 3.2 from a 36 GB Compaq Ultra Wide drive, and have a Toshiba 40x SCSI CD-ROM drive attached. It wasn't without several issues to get this far, though... in the middle of everything, my 36 GB drive's bitmap turned sour, and even with the new OS 3.2 diskdoctor I wasn't able to salvage it. Since I had a primary boot disk and merely intended to clone everything to that Compaq 36 Gig drive, I didn't bother trying any more repairs... but another preparation in WINUAE was needed, though. I haven't yet been successful with installing SFS and make it work afterwards, but I think I know the reason - it turned out the FFS version or whatever, included with AmigaOS 3.2 might cause problems, too, IF "direct SCSI access" is not ticked in HDToolBox. I think that's why my bitmap was ruined. Once I have my 50-to-68 pin adapter idle again, I'll try once again with SFS on a 73 GB SCSI drive... I have a strong feeling the "direct SCSI access" will solve the problem with that file system as well. Anyway, it seems I have no problems running two 18 GB partitions, of which the primary is also boot partition, with AmigaOS 3.2 and it's native file system. That's quite an evolution for my system in such a short span of time...wow! :-D Last edited by brufnus; 20 August 2021 at 01:07. |
20 August 2021, 01:04 | #13 | |
Registered User
Join Date: Jul 2021
Location: Aarslev, Denmark
Posts: 90
|
Quote:
That being said - I'm still using 20 MB MFM full height 5.25" drives on my Myarc Geneve 9640... c".) even more exotic than the CDTV... |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Installing WHDLoad to DH1: partition | DoJu91 | project.WHDLoad | 2 | 10 August 2013 13:59 |
Error validating... | mai | support.Hardware | 4 | 21 July 2013 20:31 |
CWB 3.5 system HDF needs DH1 but DH1 already in use. | voyager | project.ClassicWB | 3 | 18 July 2013 13:26 |
IGame pack and A-Games on DH1 | fitzsteve | project.ClassicWB | 18 | 28 January 2010 17:10 |
Harddisk validating too much ? | Galatran | support.Hardware | 6 | 11 September 2008 09:34 |
|
|