I have a 68040 Cube running NeXTSTEP 3.3. It had been working perfectly. I had used it for hours at a time to type papers.
I recently moved and moved it with me and it was working for about a day. I then tried to plug in a NeXT SCSI cd rom drive I found into it. I powered off the machine, plugged in the CD ROM, made sure SCSI was dev was set above 0 to not conflict with the internal drive. I couldn't get any discs to read but the light on the front lit up and the eject button worked.
So i shut it down and unplugged the optical drive. Since then the computer can't restart. When it boots up it checks the disks and says to run FSCK manually. It also says Restart failed ... Help!. Then I can either hit power button and y to shut it off or type /etc/init to make it boot.
It boots fine but if I use it it soon kernel panics. If before it panics I try to restart the computer it will close all programs and log out and then dump me back at NeXTSTEP Mach window and I can then hit the power button and y to turn it off, but it does not restart or turn itself off.
Also, if i go into the ROM monitor and type bsd() it just freezes.
I am unable to tell if this is a hardware or software issue.
Any ideas?
Thanks
This probably does not help but I had a similar situation when I tried accessing an optical disk. The computer paniced and in the end I had to reimage the computer.
The problem was a defective optical disk.
Quote from: "jeffberg"I have a 68040 Cube running NeXTSTEP 3.3. It had been working perfectly. I had used it for hours at a time to type papers.
I recently moved and moved it with me and it was working for about a day. I then tried to plug in a NeXT SCSI cd rom drive I found into it. I powered off the machine, plugged in the CD ROM, made sure SCSI was dev was set above 0 to not conflict with the internal drive. I couldn't get any discs to read but the light on the front lit up and the eject button worked.
Boot disk in a system often *isn't* scsi unit 0 (sd0 does not imply scsi unit 0). Are you certain they weren't in conflict?
Next, moving unseats things. Open the cube and reseat everything that can be reseated. Cables, memory, power supply.
Quote from: "jeffberg"So i shut it down and unplugged the optical drive. Since then the computer can't restart. When it boots up it checks the disks and says to run FSCK manually. It also says Restart failed ... Help!. Then I can either hit power button and y to shut it off or type /etc/init to make it boot.
Did you boot to single user mode and fsck it?
Quote from: "jeffberg"It boots fine but if I use it it soon kernel panics. If before it panics I try to restart the computer it will close all programs and log out and then dump me back at NeXTSTEP Mach window and I can then hit the power button and y to turn it off, but it does not restart or turn itself off.
Also, if i go into the ROM monitor and type bsd() it just freezes.
At what point in the process?
Quote from: "jeffberg"I am unable to tell if this is a hardware or software issue.
Any ideas?
Thanks
Beyond the above, up the diagnostic level in the monitor and see what it says during power-up tests.
Quote from: "cubist"
Boot disk in a system often *isn't* scsi unit 0 (sd0 does not imply scsi unit 0). Are you certain they weren't in conflict?
Next, moving unseats things. Open the cube and reseat everything that can be reseated. Cables, memory, power supply.
If that is the case then I am not sure if they were in conflict or not
I also did reseat everything in the cube and the issue persists.
Quote from: "cubist"
Did you boot to single user mode and fsck it?
I looked for instructions on how to do this and you type bsd(0,0,0)sdmach -s but when i hit return it just freezes there. I waited 7 minutes before I gave up and had to use alt command * to restart it. The same thing happens when I just type bsd() just to try and make it boot at all. Another curious thing in the ROM monitor on first boot. If i hit the power button it asks me if I want to power down and then i type y it does not shut off. it just opens a new blank rom monitor screen.
Quote from: "cubist"
At what point in the process?
There doesn't seem to be a clear button or anything that causes to panic, it just does shortly after boot up, whether i log in or not
Quote from: "cubist"
Beyond the above, up the diagnostic level in the monitor and see what it says during power-up tests.
If i enable extended diagnostics I get the following output
System Test Passed.
boot sd(0,0,0)diagnostics
boot scsi target 1, lun0
blk0 boot sd()diagnostics
booting from SCSI target 1 lun 0
diagnostics not found
load failed
blk0 boot:
I greatly appreciate your help. I'm a bit of a novice. I hope the system does not need to be reinstalled because I don't think I have a way to do that with the hardware available to me.
well the plot thickens
the reason i was thinking this was a hardware issue was because even with no hard drives plugged in (nothing plugged in at all except monitor, mouse, keyboard, and monitor and power) the unit would still not shut off at the rom monitor when i pushed the power button. It would just open a new rom monitor window.
I plugged in an external drive from a nextstation into it and booted from that. when i choose shut down from that drive it shuts down properly (unlike with the internal drive) but even after shutting down properly, if I unplug all the drives and boot to the rom monitor it still will not shut down.
Does that help anyone's diagnosis?
Quote from: "jeffberg"
boot sd(0,0,0)diagnostics
you don't have to enable diagnostics, otherwise the machine searches a special diag-kernal wich wasn't found.
Quote from: "Andreas"Quote from: "jeffberg"
boot sd(0,0,0)diagnostics
you don't have to enable diagnostics, otherwise the machine searches a special diag-kernal wich wasn't found.
Yeah, that wasn't really what I wanted him to do. There is a monitor configuration to perform more built-in tests (or at least report more information). Wanted that one. (Really need to capture the monitor menu sometime.)
Sorry for bringing up such an old post, was wondering if Jeffberg had a solution for this issue. Have a 030 cube with the same problem...
Thanks