SUMMARY: Mount failure - why

All


Cracked it! First of all, many thanks (in no particular order) to Steven
Haywood, Pascal Grostabussiat, Jeffrey Wimmer, Trent Petrasek, Rainer
Heilke, Bertrand Hutin and Bryan Crawford.

They all provided some great suggestions, but as it turned out, Rainier
led me towards the answer when he said:

Rainer: "The one "problem" with this rearrangement is that you have to
make sure your OBP knows what partition to boot from."

Now, I'd spent all morning (basically, ahem...) trying different
versions on the "ls -l c1t0d0s3" output which I thought was quite
logical.

lrwxrwxrwx   1 root     root          48 Mar  3 16:32 c1t0d0s3 ->
../../devices/pci@1f,0/pci@1/scsi@8/sd@0,0:d,raw

So, boot /pci@1f,0/pci@1/scsi@8/sd@0,0:d,raw
boot /pci@1f,0/pci@1/scsi@8/sd@0,0:d
boot /pci@1f,0/pci@1/scsi@8/sd@0,3:d
Etc..

The winner in the end was to do a 'show-disks' in OBP.

This told me that - amongst others - the disk I was interested in was
/pci@1f,0/pci@1/scsi@8/disk

Of course, 'disk' shows up in devalias already. But naturally that's
slice 0.

Therefore: boot /pci@1f,0/pci@1/scsi@8/disk:d

":d" means "slice 3". This I did, and everything comes up roses. I set
boot-device to be "disk:d mirror_root net"

It's *so* obvious now I've done it, but I spent so long pursuing the
/sd@etcetc route that I never thought of trying this syntax. Doubtless
there's a similar @sd one, but I'm not inclined to look for it at the
moment !

Many thanks again to all. Now I can get back on mirroring the disk.

Lastly, the main points to remember if you find yourself in this
situation - apart from the above - are:

Check your vfstab!
Check it again!
Perhaps try to reinstall a boot block on the slice you are trying to
boot
Swap on slice 0 is not a bad idea, but make it start at cylinder 1 in
case it erases the partition table

Andrew
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers