I've received the rest of my Next mono Turbo system but unfortunately It won't complete the boot-up.
Could anyone spot what may be wrong and assist me. Sorry for this long posting.
It starts with the Next graphic "testing system", then: * my comments are in square brackets.
CPU ---- ---
Ethernet address --------
Memory sixe 32mb
testing - [various system items]
Starting Exrended Self Test ...
Extended scsi test
System test passed
boot command: sd
boot sd (0,0,0)
booting from target 1 lun 0
[Then it kicks into Rom monitor]
Rom monitor 3.1 v.71
controller Target7, as sd0 Target 1 lun0
Seagate ST1480 assd0 at sc0 Target1 lun0
disk label next_2.2_ext
scsi [INFO SG 0-3 at Target7,lun7
ethernet [ ethernet info ]
root on sd0
date -----checking disks
/dev/rsd0a:file system clean:skipping check
Can't open /dev/rsd1a
(null pointer):CAN'T CHECK FILE SYSTEM
(null pointer)UNEXPECTED INCONSISTENCY, RUN fsck MANUALLY
REBOOT FAILED ... HELP !
faking root mount entries
erase ^? intr ^C kill ^U
#
[when I run fsck]
# fsck
**/dev/rsd0a
**Currently Mounted on /
** [various phase checks]
14467 files, 338804 used, 63449 free (865frag,7823blocks,.2% fragmentation
Cant open /dev/rsd1a
#
Thanks for any help.
Lawrence
Quote from: "NextMach"
Rom monitor 3.1 v.71
Should be replaced against a v74 one.
Quote
Seagate ST1480 assd0 at sc0 Target1 lun0
disk label next_2.2_ext
Oh, an 2.2 Install, have never seen one. Only 2.1 and than 3.x systems.
Quote
/dev/rsd0a:file system clean:skipping check
Your root-system seems to be OK.
Quote
Can't open /dev/rsd1a
Soemone have mounted an external harddrive for example on LocalApps. You need to boot into single user mode, see other threads in this forum, and edit the file /etc/fstab
You have two lines in it, the first for your root partion and a second for this external drive. remove this line.
Quote
faking root mount entries
erase ^? intr ^C kill ^U
#
Oh, you have allready the command promt? change to /etc and edit the fstab...
That was easy :-))))
How do I get to rsd0a. Anything I enter returns a not found because I imagine it looks on rsd1a.
I was able to get into the ROM Monitor using "command ~" after the "testing system" log-in. This brings up the "NeXT" prompt not the
"#" one. Where do I go from there ?
Lawrence
Quote from: "NextMach"How do I get to rsd0a.
You are already on rsd0a. From this:
faking root mount entries
erase ^? intr ^C kill ^U
#
you have to type:
cd /etc
vi fstab
Quote
Anything I enter returns a not found because I imagine it looks on rsd1a.
What exactly is anything.
Quote
I was able to get into the ROM Monitor using "command ~" after the "testing system" log-in. This brings up the "NeXT" prompt not the
"#" one. Where do I go from there ?
You should do something like this:
http://www.bangmoney.org/nextstep/root_password.html
If I type
#cd /etc
it replies cd /etc not found. Similar response to admin/etc, root, bsd, home or some of the other things I have typed.
I brought up the "Next" prompt and tried cd /etc
It responded kernel flag /etc unknown and then kicked me back to the monitor screen I detailed at the top of my listing above.
Same thing if I do cd /admin/etc
next[prompt] "bsd" does the same as when I start up.
I've got into the Parameter app before I asked for help and set them as recommended, so using the password instructions won't do anything for me. Would removing the battery/shorting the poles, perhaps get rid of the rsd1a entry/pointer and restore the defaults?
I managed finally to access /etc and then used vi to edit fstab. I entered a couple of Unix commands to see if they responded, which they did. I then
entered cd /etc and VOILA it changed to the /etc directory. Strange.
I removed the rsd1a line then quit and when I rebooted it came up (after an interminable delay while it checked and then gave up on a long list of hosts) with the login graphic. I notice it was also branded with the company who I imagined formerly owned it.
I did the root password thing, then powered down and tried to login, which it refused. I'll see if removing the battery and shorting the contacts returns it to default status.
Thanks.