antunes@ASTRO.PSU.EDU (Alex Antunes) (03/14/90)
Hello, folks. I still have this problem. Basically, my A500 guru-ed, and when I went to reboot, it now either gurus or locks up when it tries to mount my hard disk partitions. Now, someone suggested I change the mount=1 line so it will mount without accessing, so I can use Disksalv, etc. Great. But why will it not access any of the partitions, i.e. WHY does it lockup or guru? Even the partitions that were NOT mounted when the crash happened are inaccessible. So how could they have also been affected? Is this a hardware problem or a software problem? I'd rather not have to disksalv all 65 meg then reformat the entire drive only to find that isn't the problem... The story: My A500 w/1 meg, 65 meg seagate drive, cltd controller, running qmouse, gomf3.0, ff, and with assorting things running which i don't recall which probably caused the crash :-) just inexplicably crashed. When I try to reboot and access the HD with my startup-sequence, it locks up on the mount command, this disk light on, the disk still spinning... If I bootup without the HD then clearscsi (which seems to behave) then try to mount a partition, I get a guru (I have so far gotten 000600F5.00C003D8, 0000000A.00C1D748, and 0000002F.00C14078, depending on the bootup disk used) My HD has six partitions, four of which had been mounted at the time of the crash. Now, all six of them cause this guru/lockup problem. Help! Help! Help! Help!!! sandy ------------ Sandy Antunes antunes@astro.psu.edu "The Hermit of Waupelani" CBA: Center for Bad Astrophysics