ram@tellab5.tellabs.CHI.IL.US (Bob Martin) (07/15/89)
HELLPPP!!!
Yesterday I was going through some Fish Disks, and I ran the AntiCBS demo on
disk 217. After it cycled through the animation sequence about 4 or 5 times,
the animation terminated and I was back at the Workbench screen (I ran the
demo from its icon, not CLI). I thought this was strange, since the intro
says to hit ^C when you want to terminate execution. Anyway, the screen is now
locked up, no mouse movement allowed, etc. I figure the GURU is about to
appear, so I wait. After a minute nothing has happened, so I do a warm reboot.
My workbench disk mounts my 4 HD partitions, assigns directories, then transfers
control to the HD, NORMALLY. However, this time the partitions get mounted, but
when the assigns start happening (all to directories on DH0:), the startup
script fails. I do an INFO command, I see all 4 partitions mounted, but next to
DH0: it says "Not a DOS disk" :-O !
Now when the lockup occurred, and afterwards, I saw no writing to the HD
occurring, so I can't figure out how the partition got trashed. Also, since
I have just recently re-formatted the HD for ffs, I have no backup of the
partition. So I have a few questions:
1) Any idea what made the machine lockup (does AntiCBS have a known bug?)
2) Any idea what corrupted DH0: ?
3) Is there a way to use some sort of utility to fix the partition so
I don't have to reformat and re-load the files?
4) I'd like to get people's recommendations for the best HD backup utilities
both PD and commercial. Prefferably one that uses data compression when
storing files to floppy (so I don't use so many disks :-)
Finally, my system is:
Amiga 1000 w/512K
Starboard II w/2M and StarDrive SCSI module
Seagate ST-277N SCSI HD (65 MB) with four partitions (5M, 19M, 19M, 19M) all
formatted for FFS
2 external Amiga floppy drives
I was running KS and WB 1.3, had a SHELL open and had JPclock (Fish 204)
running.
One last note: If anyone else has an ST-277N with StarDrive controller on
their machine, could you mail me info on your mountlist entries for
your partitions. Although the drives ran fine until the lockup,
maybe there is something in the mountlist entry that caused my lockup.
Thanks a bunch!
Bob Martin
Tellabs, Inc. uunet!att!tellab5!ram or uunet!tellab5!ram (I think)