Hubert Feyrer wrote:
> On Mon, 12 May 2003, leam wrote:
> 
>>I did a dump from the working disk to the secondary and tried to boot
>>from the secondary. Even though the /etc/fstab was modified I see mount
>>syntax errors and the filesystems fail to mount. Unfortunately it also
> 
> 
> "Mount syntax errors" sounds like you foobar'd /etc/fstab.
> Care to copy it here (or just sanity check it yourself ;)?

All my sanity checks bounce. However, on the off chance of sufficient 
fun, I have both /etc/fstabs:

# cat /etc/fstab
/dev/sd1a / ffs rw 1 1
/dev/sd1b none swap sw 0 0
/dev/sd1d /var ffs rw 1 2
/dev/sd1e /usr ffs rw 1 2

# cat /mnt/etc/fstab
/dev/sd0a / ffs rw 1 1
/dev/sd0b none swap sw 0 0
/dev/sd0d /var ffs rw 1 2
/dev/sd0e /usr ffs rw 1 2

What happens with my script is that it takes /etc/fstab and edits it. In 
this case it changed sd1 to sd0. At the moment I can mount /dev/sd0a and 
look at it, so the filesystem itself isn't totally munged.

>>prevents me from doing a "stop-a" to copy the message.
> 
> Well, a few lines of context including errors should be doable by hand...

That was what I wanted with the stop a. To get the point where it was 
failing. However it even prevents me from using stop a, so a lot of 
stuff scrolls off the screen.

>>Where can I look into what the poot process is to see where it is dying?
> 
> 
> That's hard to tell, given that you give no information.
> Of course you could try to boot singleuser "boot -s", then fsck and mount
> things manually (fsck -p, mount -va), then check /etc/rc and run it with
> sh -v or so.

Well, more info. boot -s works, I get Martin's openfirmware 1.6, and 
progress to where it asks for shell or press return for /bin/sh.

fsck -p /dev/rsd0 a, d, and e are fine.

mount -va fails:

usage: mount_umap [ -o option] -u usermap -g groupmap target_fs mount_point

trying -a, -A, -o va, all fail. "option not supported"

Doing the sh -v anyway, it scrolls for a long while. The first real 
error I see, other than the mount issue, is an error setting the tty 
flags. If the sh -v ever finishes I'll cd to /dev and do a MAKEDEV all 
and see if that helps.

So far sh -v hasn't stopped, it has been about 10 minutes. re-strating 
again, the MAKEDEV failed as it is still a read-only filesystem

ciao!

leam