Welcome, Guest. Please login or register.

Author Topic: HDD Validating Nightmare  (Read 3893 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline SlashTopic starter

  • Full Member
  • ***
  • Join Date: Mar 2002
  • Posts: 112
  • Country: gb
  • Gender: Male
    • Show all replies
    • http://www.the-snakepit.co.uk
HDD Validating Nightmare
« on: September 08, 2003, 04:14:59 PM »
Last night while compiling an application, my Amiga crashed as GCC was writing the executable to the disk.

Of course, after I reboot, the SCSI disk started thrashing away trying to validate itself.

However, after approx 3 minutes, instead of successfully fixing the disk, or giving an error such as "Error validating HD2..." etc, the machine just reset itself with a "Software Failure". I'm sure it's a "8000 0004" in the Guru.

Anyone come across this strange error?

Disk is partitioned and formatted with the standard 3.1 ROM version of FFS and is setup as DC-FFS.

Help  please :-?
 

Offline SlashTopic starter

  • Full Member
  • ***
  • Join Date: Mar 2002
  • Posts: 112
  • Country: gb
  • Gender: Male
    • Show all replies
    • http://www.the-snakepit.co.uk
Re: HDD Validating Nightmare
« Reply #1 on: September 08, 2003, 04:49:56 PM »
Thanks for the info Paul, glad to see I'm not the only one experiencing this problem.

I'm a bit sceptical about installing SFS, I have it on my internet cache partition but I don't trust it with as my main file system yet. Although a lot of people seem to be giving it good reports.

I did manage to get the machine to stay up without guru'ing only by booting into the OS4 beta partition I have installed. Don't know what it does, but it stops it crashing.

I have since managed to salvage my data (all 18,000 files) and reformat the disk with FFS2 so I'll see how that goes. Maybe I will move to SFS if that fails.

I was just posting to see if anyone else had this problem, and what the actual guru code of 8000 0004 was, and how it was related to my validation process.

No salvage utility I have used successfully in the past (Disksalv, Quarterback, TurboVal) could repair the problem, as you say it needed a re-format. Nasty stuff.