rbp@investor.pgh.pa.us (Bob Peirce #305) (02/21/91)
The other day I fired up the cube (1.0) and it started through the checking process. It got to the point where the little HD icon started spinning but after a few seconds it stopped. I knew there was something having to do with tilde that would get me to the monitor screen. I tried variations on command, control and shift and accomplished this, although I still don't know which command did it! Through trial and error, I figured out how to run the boot command and I booted from the OD. When I was up I compared the OS on the OD to the HD. They were different. I copied the OS over to the HD, powered down (there is probably an undocumented command to avoid this too) and rebooted. It came up fine. So, anybody have any idea what happened? In eight years with SysIII and SysV boxes I have never seen anything like this. Why should it happen here? Should I expect this to be a frequent occurrence? Is it a 1.0 thing a BSD thing or a fluke of some sort? -- Bob Peirce, Pittsburgh, PA 412-471-5320 ...!uunet!pitt!investor!rbp rbp@investor.pgh.pa.us
lacsap@plethora.media.mit.edu (Pascal Chesnais) (02/22/91)
In article <1991Feb21.151922.5888@investor.pgh.pa.us> rbp@investor.pgh.pa.us (Bob Peirce #305) writes: > The other day I fired up the cube (1.0) and it started through the > checking process. It got to the point where the little HD icon started > spinning but after a few seconds it stopped. > Why should it happen > here? Should I expect this to be a frequent occurrence? Is it a 1.0 > thing a BSD thing or a fluke of some sort? > > Bob Peirce, Pittsburgh, PA From our FAQ: 5. Why does my 030 NeXT system using Release 1.0 hang a few seconds after attempting to boot from the optical disk? Release 1.0 contains a bug that can corrupt the kernel /odmach if a user attempts to launch /odmach from the browser. The solution is to copy a clean /odmach from another NeXT system. Be sure to change the permissions of the newly installed /odmach to remove execute permissions to prevent future occurrences of the same problem. Release 2.0 does not have this problem. Pascal Chesnais, Research Specialist, Electronic Publishing Group Media Laboratory, E15-351, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311 email: lacsap@plethora.media.mit.edu (NeXT)
lacsap@plethora.media.mit.edu (Pascal Chesnais) (02/22/91)
In article <1991Feb21.151922.5888@investor.pgh.pa.us> rbp@investor.pgh.pa.us
Ooops, the FAQ needs to say that this same problem exists with sdmach,
so once you have copied a new uncorrupted version of sdmach from the OD
to the hard disk, remove the execute access from the sdmach kernal.
Pascal Chesnais, Research Specialist, Electronic Publishing Group
Media Laboratory, E15-351, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311
email: lacsap@plethora.media.mit.edu (NeXT)