I have a NeXT Cube 68040 that only comes up in single user mode (# prompt).
The directories and files seem to be ok. Should I run fsck, or what might I do next to bring up the graphical interface?
Some of the output:
NeXT ROM Monitor 2.4 v65
NeXT Mach 3.2: Mon Oct 18 21:57:41 PDT 1993; root(rcbuilder):mk-149.38.15.obj-2/
FPU version 0x40
physical memory = 16.00 megabytes.
SCSI 53C90A Controller. Target 7, as sc8 at 0x2114000
MAXTOR XT-8380S Rev B3C as sd0 at sc0 target 8 lun 0
root on sd0
WARNING: clock lost 43 days -- CHECK AND RESET THE DATE:
erase ^? intr ^C kill ^U
# whoami
root
Hi, has this Cube booted correctly for you before?
Can you please provide a screenshot of all booting messages and the output of
cat /etc/fstab?
Quote from: "invsin"I have a NeXT Cube 68040 that only comes up in single user mode (# prompt).
The directories and files seem to be ok. Should I run fsck, or what might I do next to bring up the graphical interface?
Use the 'date' command to set the correct date/time (assuming you have y2k patches applied). Then ^D and continue on to multiuser.
The last boot was correct but a long time ago - possibly 15 years ago!
Now it comes up in single-user mode by itself, it's not something I'm asking it to do.
Rather than images I tried to type it in from photos.
By going into the ROM Monitor, setting some configuration parameters and rebooting I see there is a file problem. So fsck may be run during the beginning of every boot but below is the first of the error messages I've seen. I'm wary of running fsck myself - it's not clear to me about mounting/unmounting file systems and I don't want to gain experience by making a bad situation worse. Any suggestions?
The error message from the ROM Monitor reboot:
Wed Oct 22 21:44:04 PDT 1997
Checking disks
/dev/rsd0a: PARTIALLY ALLOCATED INODE I=50786
/dev/rsd0a: UNEXPECTED INCONSISTENCY; RUN fsck
Reboot failed...help!
Faking root mount entries
erase ^? intr ^C kill ^U
===== The default boot output: ========================
NeXT ROM Monitor 2.4 v65
NeXT Mach 3.2: Mon Oct 18 21:57:41 PDT 1993; root(rcbuilder):mk-149.38.15.obj-2/
FPU version 0x40
physical memory = 16.00 megabytes.
available memory = 14.15 megabytes.
using 102 buffers containing 0.79 megabytes of memory
NBIC present
fc0 at 0x2114100
Sony MPX-111N as fd0 at fc0 slave 0
SCSI 53C90A Controller. Target 7, as sc8 at 0x2114000
MAXTOR XT-8380S Rev B3C as sd0 at sc0 target 8 lun 0
Disk Label: MyDisk
Disk Capacity 349MB, Device Block 1024 bytes
Generic SCSI Device as sg0 at sc0 target 7 lun 7
Generic SCSI Device as sg1 at sc0 target 7 lun 7
Generic SCSI Device as sg2 at sc0 target 7 lun 7
Generic SCSI Device as sg3 at sc0 target 7 lun 7
odc0 at 0x2112000
od0 at odc0 slave 0
drive ROM v8, servo ROM v8
od1 at 0dc0 slave 1
en0 at 0x2106000
en0: Ethernet address 00:00:0f:00:98:ff
IP protocol enabled for interface en0, type "10MB Ethernet"
dsp0 at 0x2108000
np0 at 0x200f000
sound0 at 0x200e000
root on sd0
WARNING: clock lost 43 days -- CHECK AND RESET THE DATE!
erase ^? intr ^C kill ^U
#cat /etc/fstab
# DO NOT DELETE THIS FILE, IT IS REQUIRED FOR BOOTING
#
# This file contains information used to mount ....
#
/dev/sd0a / 4.3 rw,noquota,noauto 0 1
#
# exit
eno: netmask set to 0.0.0.0
The network is disabled or your computer isn't connected to it.
lo0: address automatically set to 127.0.0.1
Setting hostname to -AUTOMATIC-
Reinitializing nmservers's network portion
Multiuser startup in progress...
/usr/etc/mach_swapon: swapping on /private/vm/swapfile.front
Cleaning up: /etc/nologin ptys floppy devices editors /tmp /Net.
Starting early daemons:dev = 0x600, ino = 1, fs = /
panic: (Cpu 0) ifree: freeing free inode
NeXT ROM Monitor 2.4 v65
panic: NeXT Mach 3.2: Mon Oct 18 21:57:41 PDT 1993: rott(rcbuilder):mk-149.30.15.obj~2/RC_m
SE_M68K
panic>
Quote from: "invsin"
Wed Oct 22 21:44:04 PDT 1997
Checking disks
/dev/rsd0a: PARTIALLY ALLOCATED INODE I=50786
/dev/rsd0a: UNEXPECTED INCONSISTENCY; RUN fsck
and...
Quote from: "invsin"
panic: (Cpu 0) ifree: freeing free inode
NeXT ROM Monitor 2.4 v65
panic: NeXT Mach 3.2: Mon Oct 18 21:57:41 PDT 1993: rott(rcbuilder):mk-149.30.15.obj~2/RC_m
SE_M68K
Your filesystem isn't consistent enough to be mounted read/write without doing more damage. So, one way or another, an 'fsck' session is in your future. The only question is how much work you're willing to do to recover from even worse errors during the fsck session:
- Make a block copy of the raw device (dd command)
- Do 'dry-runs' of the fsck answering 'no' to all modification questions to see how much cleanup is needed
QuoteThe only question is how much work you're willing to do to recover from even worse errors during the fsck session:
- Make a block copy of the raw device (dd command)
- Do 'dry-runs' of the fsck answering 'no' to all modification questions to see how much cleanup is needed
Yes, I want to try but I'll have to do some research on this - the raw device, dd, .... it's all a bit above my head. I'm not even sure if I might do a trial fsck run from the single-user prompt without doing anything else. Thanks for your help!