Greetings!

Well, to try to save time, I have mounted my newly installed Solaris,
on c0t1d0 (DISK1) from the disk I'm currently booting off of c0t0d0 (DISK0).
I have "cp'd" numerous files over, from my existing /etc to
/mnt/new_disk/etc, etc.

(I was also wanting to get the sendmail on my currently running
system, because the sendmail from Solaris 8 needed several patches,
because CERT found security flaws in it. I had patched the one I'm
currently running.)

Okay. :-) I suspect this wasn't the best way to do it. (I need to
save time wherever I can.) So, I thought the best way to do was to "cp"
certain things over. (The /etc directory, for example, has all kinds of
customized network files [hosts, defaultrouter, defaultdomain, gateways,
etc.], as well as /etc/mail, so I was thinking it would be good to cp
certain things over. I cp'd all of /etc, and only selected portions of
other directories [var/spool/patch, etc].)

<sigh> I should know better, but I keep thinking it is my highest
need to do this as quickly as possible, and -- from what I recall, from
2003, it took a while to figure out how to get and apply patches to the
sendmail, etc.

Sure enough, when I try to boot from DISK1, here are the error
messages I get, after getting a normal-looking start to the boot:

<<>>
mount: /dev/dsk/c0t0d0s0 is not this fstype.
/sbin/rcS: /etc/dfs/sharetab: cannot create
failed to open /etc/coreadm.confsyseventd: Unable to open daemon lock file
'/etc/sysevent/syseventd_lock': 'Read-only file system'
INIT: Cannot create /var/ad/utmpx

INIT: failed write of utmpx entry:" "

INIT: failed write of utmpx entry:" "

INIT: SINGLE USER MODE
<<>>

I appear to have a read-only file system, yet, when I typed "mount"
it showed read/write everywhere -- though it didn't show as many lines of
output as "mount" showed me just now, having booted (successfully) off of
DISK0.

Does anyone have any suggestions for what I look at, first, given the
above error messages while booting?

(At least, with a "boot disk0" working just perfectly, as it has been
working for years now, it is not critical if I'm not booting off of disk1
yet!) :-)

Thank you!

Barry
--
Barry L. Bond | http://home.cfl.rr.com/os9barry/
Software Engineer, ITT Corporation | (My personal home web page, last
bbondATcfl.rr.com | updated February 17, 2005)

Barry L. Bond wrote:

>
> Well, to try to save time, I have mounted my newly installed Solaris,
> on c0t1d0 (DISK1) from the disk I'm currently booting off of c0t0d0 (DISK0).
> I have "cp'd" numerous files over, from my existing /etc to
> /mnt/new_disk/etc, etc.
>
<<SNIP>>
> Sure enough, when I try to boot from DISK1, here are the error
> messages I get, after getting a normal-looking start to the boot:
>
> <<>>
> mount: /dev/dsk/c0t0d0s0 is not this fstype.
>

When you copied /etc/ from DISK0, you copied the fstab file which has
correct entries to mount filesystems from c0t0d0s* , but for the boot
to work correctly for DISK1, your fstab file need to reference c0t1d0s*
..

jimleong@dorsai.org wrote:
> Barry L. Bond wrote:
>
> >
> > Well, to try to save time, I have mounted my newly installed Solaris,
> > on c0t1d0 (DISK1) from the disk I'm currently booting off of c0t0d0 (DISK0).
> > I have "cp'd" numerous files over, from my existing /etc to
> > /mnt/new_disk/etc, etc.
> >
> <<SNIP>>
> > Sure enough, when I try to boot from DISK1, here are the error
> > messages I get, after getting a normal-looking start to the boot:
> >
> > <<>>
> > mount: /dev/dsk/c0t0d0s0 is not this fstype.
> >
>
> When you copied /etc/ from DISK0, you copied the fstab file which has
> correct entries to mount filesystems from c0t0d0s* , but for the boot
> to work correctly for DISK1, your fstab file need to reference c0t1d0s*
> .

If you used cp to copy the files over from one disk to the next you may
eventually going to run into
nagging problems. when cp sees a link it copies the actual file in
place of the link.

You would probably be much better off using dd to copy disks as special
files such as links, sockets
, etc are preserved.

Dean

Hi Jim!

>When you copied /etc/ from DISK0, you copied the fstab file which has
>correct entries to mount filesystems from c0t0d0s* , but for the boot
>to work correctly for DISK1, your fstab file need to reference c0t1d0s*

Well, <DUHH!>!

Thank you. <sigh> My goodness. I'm familiar enough with Linux
system administration that I can't believe I didn't think of that, even if
I was in a hurry (which I was)!

The file is mnttab, in Solaris, but still, I should have thought of
it!

Barry
--
Barry L. Bond | http://home.cfl.rr.com/os9barry/
Software Engineer, ITT Corporation | (My personal home web page, last
bbondATcfl.rr.com | updated February 17, 2005)

Hi Dean!

Thank you for offering whatever ideas come to your mind! Everything
I hear (or READ, in this case) can help me realize something I didn't
realize, on my own!

>If you used cp to copy the files over from one disk to the next you may
>eventually going to run into
>nagging problems. when cp sees a link it copies the actual file in
>place of the link.

And, you're right. When I fixed the device.tab and mnttab files, on
my "disk1", and tried to boot, just now, I got further, but hit another,
as you say, nagging problem...

It couldn't find "ipf", when running ipfboot.

When I boot back into disk0, I see the ipfboot script, in
/etc/init.d. And, when I "ls -l /sbin/ipf", I see it's a link to
/usr/sbin/ipf.

>You would probably be much better off using dd to copy disks as special
>files such as links, sockets
>, etc are preserved.

Thank you. I'll look into this. I haven't actually used "dd", but
I've read where it can be used for some wonderful things! :-)

I'll read the man page on it, and do some FAQ reading/googling, but I
guess I can use it similar to cp?

So, perhaps it would be faster to do it this way, providing a copy in
a way that links, etc. (which I hadn't even thought about) are
preserved...

Thank you again!

Barry
--
Barry L. Bond | http://home.cfl.rr.com/os9barry/
Software Engineer, ITT Corporation | (My personal home web page, last
bbondATcfl.rr.com | updated February 17, 2005)

Hi Dean, and others!

I see "dd if=/dev/rdsk/... of=/dev/rdsk...".

A question I have now, though, is, since I have already copied (cp)
the files in /etc, /usr/local, and a few others, will issuing the dd
command now still work the same way?

Barry
--
Barry L. Bond | http://home.cfl.rr.com/os9barry/
Software Engineer, ITT Corporation | (My personal home web page, last
bbondATcfl.rr.com | updated February 17, 2005)

On Fri, 24 Nov 2006 01:35:27 GMT barry@barrycon.cfl.rr.com (Barry L. Bond) wrote:
> The file is mnttab, in Solaris, but still, I should have thought of
> it!

Hi Barry!

The file is vfstab in Solaris! mnttab is generated!

-frank!

Hi to you, Frank!

>The file is vfstab in Solaris! mnttab is generated!

Ah yes... thank you! I did a grep 'c0t[01]d0' and I had actually
edited the vfstab file last week, so I had the latest file which I had
found that contained that string (mnttab) as the file I indicated!

Thank you for your correction!

Barry

--
Barry L. Bond | http://home.cfl.rr.com/os9barry/
Software Engineer, ITT Corporation | (My personal home web page, last
bbondATcfl.rr.com | updated February 17, 2005)