I have a damaged kernel on a Solaris 10 system (can't boot). I'd like to
use FTP to get some user files from that system. I can "boot cdrom -s",
but, of course, that doesn't bring up the network. So...

I used "ifconfig" and "route" to configure the ce0 interface and a default
route. But, as I see it (and I could be wrong-- correct me, please), I
still need the inetd daemon, er, service running. I tried 'svcadm enable
inetd', but got the following error message:

svcadm: svc:/network/inetd:default: Repository read-only.


Is there some way to get network access from Solaris 10 when using 'boot
cdrom -s'?

Thank you.

DG

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"I think not," said Descartes, and disappeared.

David E. Grove wrote:
> I have a damaged kernel on a Solaris 10 system (can't boot). I'd like to
> use FTP to get some user files from that system. I can "boot cdrom -s",
> but, of course, that doesn't bring up the network. So...
>
> I used "ifconfig" and "route" to configure the ce0 interface and a default
> route. But, as I see it (and I could be wrong-- correct me, please), I
> still need the inetd daemon, er, service running. I tried 'svcadm enable
> inetd', but got the following error message:
>
> svcadm: svc:/network/inetd:default: Repository read-only.
>
>
> Is there some way to get network access from Solaris 10 when using 'boot
> cdrom -s'?

No idea.

But assuming the data on the disk is on partitions you can mount, would
it not be eaier to mount them on a temporarary directory from the cdrom
(which is ram) and copy from there to tape or another disk?

ok> boot -s cdrom
# mkdir /tmp/new
# mkdir /tmp/data-is-here

then copy it with cp, tar, to tape or whatever you like.


to copy it to a new disk:

# mkdir /dev/dsk/whatevver /tmp/data-is-here
# cp -pr /tmp/data-is-here /tmp/new

Dave wrote:

> No idea.
>
> But assuming the data on the disk is on partitions you can mount, would
> it not be eaier to mount them on a temporarary directory from the cdrom
> (which is ram) and copy from there to tape or another disk?
>
> ok> boot -s cdrom
> # mkdir /tmp/new
> # mkdir /tmp/data-is-here
>

I forgot the mount command's


# mount /dev/dsk/file-system-with-data-on
# mount /dev/dsk/new-file-system /tmp/new

Once the data is mounted, copying is easy, with no need for any network
access.

Thank you for your reply, Dave.

But..... The damaged machine has no tape drive. It relies on network to
extract data from the machine.

I can mount the file system with the files, and I can copy them to another
mounted file system. I just can't "get them off the machine".

Sun tech support sent me an "unsupported recipe", that consisted only of
instructions to use ifconfig to plumb and set address for an interface, and
that was all. Of course, those instructions by themselves, although
necessary, are insufficient to get network connectivity.




"Dave" <nospam@nowhere.com> wrote in message news:4368deb9@212.67.96.135...
> Dave wrote:
>
> > No idea.
> >
> > But assuming the data on the disk is on partitions you can mount, would
> > it not be eaier to mount them on a temporarary directory from the cdrom
> > (which is ram) and copy from there to tape or another disk?
> >
> > ok> boot -s cdrom
> > # mkdir /tmp/new
> > # mkdir /tmp/data-is-here
> >
>
> I forgot the mount command's
>
>
> # mount /dev/dsk/file-system-with-data-on
> # mount /dev/dsk/new-file-system /tmp/new
>
> Once the data is mounted, copying is easy, with no need for any network
> access.
>

David E. Grove wrote:

> Thank you for your reply, Dave.
>
> But..... The damaged machine has no tape drive. It relies on network to
> extract data from the machine.
>
> I can mount the file system with the files, and I can copy them to another
> mounted file system. I just can't "get them off the machine".
>
> Sun tech support sent me an "unsupported recipe", that consisted only of
> instructions to use ifconfig to plumb and set address for an interface, and
> that was all. Of course, those instructions by themselves, although
> necessary, are insufficient to get network connectivity.
>
>
>
>
> "Dave" <nospam@nowhere.com> wrote in message news:4368deb9@212.67.96.135...
>
>>Dave wrote:
>>
>>
>>>No idea.
>>>
>>>But assuming the data on the disk is on partitions you can mount, would
>>>it not be eaier to mount them on a temporarary directory from the cdrom
>>>(which is ram) and copy from there to tape or another disk?
>>>
>>>ok> boot -s cdrom
>>># mkdir /tmp/new
>>># mkdir /tmp/data-is-here
>>>
>>
>>I forgot the mount command's
>>
>>
>># mount /dev/dsk/file-system-with-data-on
>># mount /dev/dsk/new-file-system /tmp/new
>>
>>Once the data is mounted, copying is easy, with no need for any network
>>access.
>>
>
>
>
inetd is very useful, but isn't it just in the nature of a "traffic
cop?"

I mean, if you wanted to use, e.g., ftp, couldn't you start the ftp
daemon directly rather than have inetd load it? Of course, doing so
could have its own issues.

Just thinking "aloud" ...

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.

"CJT" <abujlehc@prodigy.net> wrote in message
news:436937D5.5020701@prodigy.net...
> David E. Grove wrote:
>
> > Thank you for your reply, Dave.
> >
> > But..... The damaged machine has no tape drive. It relies on network to
> > extract data from the machine.
> >
> > I can mount the file system with the files, and I can copy them to
another
> > mounted file system. I just can't "get them off the machine".
> >
> > Sun tech support sent me an "unsupported recipe", that consisted only of
> > instructions to use ifconfig to plumb and set address for an interface,
and
> > that was all. Of course, those instructions by themselves, although
> > necessary, are insufficient to get network connectivity.
> >
> >
> >
> >
> > "Dave" <nospam@nowhere.com> wrote in message
news:4368deb9@212.67.96.135...
> >
> >>Dave wrote:
> >>
> >>
> >>>No idea.
> >>>
> >>>But assuming the data on the disk is on partitions you can mount, would
> >>>it not be eaier to mount them on a temporarary directory from the cdrom
> >>>(which is ram) and copy from there to tape or another disk?
> >>>
> >>>ok> boot -s cdrom
> >>># mkdir /tmp/new
> >>># mkdir /tmp/data-is-here
> >>>
> >>
> >>I forgot the mount command's
> >>
> >>
> >># mount /dev/dsk/file-system-with-data-on
> >># mount /dev/dsk/new-file-system /tmp/new
> >>
> >>Once the data is mounted, copying is easy, with no need for any network
> >>access.
> >>
> >
> >
> >
> inetd is very useful, but isn't it just in the nature of a "traffic
> cop?"
>
> I mean, if you wanted to use, e.g., ftp, couldn't you start the ftp
> daemon directly rather than have inetd load it? Of course, doing so
> could have its own issues.
>
> Just thinking "aloud" ...
>
> --
> The e-mail address in our reply-to line is reversed in an attempt to
> minimize spam. Our true address is of the form che...@prodigy.net.




I did a 'svcs -a | grep ftp' (on the damaged machine that's currently booted
from cdrom) and didn't get any response, not even a "disabled" response. I
do get a "disabled" response from 'svcs -a|grep inetd'. Figured maybe inetd
would start ftp as needed, so I tried to start inetd. As I described
initially, no go.

Is there any way to get network access from a 'boot cdrom -s' ?

Thank you.

DG

David E. Grove wrote:

> "CJT" <abujlehc@prodigy.net> wrote in message
> news:436937D5.5020701@prodigy.net...
>
>>David E. Grove wrote:
>>
>>
>>>Thank you for your reply, Dave.
>>>
>>>But..... The damaged machine has no tape drive. It relies on network to
>>>extract data from the machine.
>>>
>>>I can mount the file system with the files, and I can copy them to
>
> another
>
>>>mounted file system. I just can't "get them off the machine".
>>>
>>>Sun tech support sent me an "unsupported recipe", that consisted only of
>>>instructions to use ifconfig to plumb and set address for an interface,
>
> and
>
>>>that was all. Of course, those instructions by themselves, although
>>>necessary, are insufficient to get network connectivity.
>>>
>>>
>>>
>>>
>>>"Dave" <nospam@nowhere.com> wrote in message
>
> news:4368deb9@212.67.96.135...
>
>>>>Dave wrote:
>>>>
>>>>
>>>>
>>>>>No idea.
>>>>>
>>>>>But assuming the data on the disk is on partitions you can mount, would
>>>>>it not be eaier to mount them on a temporarary directory from the cdrom
>>>>>(which is ram) and copy from there to tape or another disk?
>>>>>
>>>>>ok> boot -s cdrom
>>>>># mkdir /tmp/new
>>>>># mkdir /tmp/data-is-here
>>>>>
>>>>
>>>>I forgot the mount command's
>>>>
>>>>
>>>># mount /dev/dsk/file-system-with-data-on
>>>># mount /dev/dsk/new-file-system /tmp/new
>>>>
>>>>Once the data is mounted, copying is easy, with no need for any network
>>>>access.
>>>>
>>>
>>>
>>>
>>inetd is very useful, but isn't it just in the nature of a "traffic
>>cop?"
>>
>>I mean, if you wanted to use, e.g., ftp, couldn't you start the ftp
>>daemon directly rather than have inetd load it? Of course, doing so
>>could have its own issues.
>>
>>Just thinking "aloud" ...
>>
>>--
>>The e-mail address in our reply-to line is reversed in an attempt to
>>minimize spam. Our true address is of the form che...@prodigy.net.
>
>
>
>
>
> I did a 'svcs -a | grep ftp' (on the damaged machine that's currently booted
> from cdrom) and didn't get any response, not even a "disabled" response. I
> do get a "disabled" response from 'svcs -a|grep inetd'. Figured maybe inetd
> would start ftp as needed, so I tried to start inetd. As I described
> initially, no go.
>
> Is there any way to get network access from a 'boot cdrom -s' ?
>
> Thank you.
>
> DG
>
>
Did you try to start in.ftpd directly, as I suggested?

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.

David E. Grove wrote:
> Thank you for your reply, Dave.
>
> But..... The damaged machine has no tape drive. It relies on network to
> extract data from the machine.
>
> I can mount the file system with the files, and I can copy them to another
> mounted file system. I just can't "get them off the machine".

You seem to know what you are doing, so I don;t wish to teach my
grandmother to suck eggs (as we say in England).

But since you can copy the files to a mounted file system, can't you
then remove the good disk and transport that disk to another machine?
Once you move it to the other machine, you can boot that machine in
multi-user mode, mount the disk you just moved on /tmp and the job and
then you have the files on a networked machine.

I must be missing something somewhere!

> Sun tech support sent me an "unsupported recipe", that consisted only of
> instructions to use ifconfig to plumb and set address for an interface, and
> that was all. Of course, those instructions by themselves, although
> necessary, are insufficient to get network connectivity.
>
>
>
>
> "Dave" <nospam@nowhere.com> wrote in message news:4368deb9@212.67.96.135...
>
>>Dave wrote:
>>
>>
>>>No idea.
>>>
>>>But assuming the data on the disk is on partitions you can mount, would
>>>it not be eaier to mount them on a temporarary directory from the cdrom
>>>(which is ram) and copy from there to tape or another disk?
>>>
>>>ok> boot -s cdrom
>>># mkdir /tmp/new
>>># mkdir /tmp/data-is-here
>>>
>>
>>I forgot the mount command's
>>
>>
>># mount /dev/dsk/file-system-with-data-on
>># mount /dev/dsk/new-file-system /tmp/new
>>
>>Once the data is mounted, copying is easy, with no need for any network
>>access.
>>
>
>
>

>But since you can copy the files to a mounted file system, can't you
>then remove the good disk and transport that disk to another machine?
>Once you move it to the other machine, you can boot that machine in
>multi-user mode, mount the disk you just moved on /tmp and the job and
>then you have the files on a networked machine.


Well, the internal drives are FC-AL. Thus, moving those drives around
involves the "landmines" associated with (maybe it's just my association)
the WWNs that are part and parcel of FC-AL drives. Guess I can actually do
a little work and go refresh my memory on 'luxadm' and moving FC-AL drives.
The external drive is a large, heavy, multi-Terabyte RAID enclosure that
lives in a nice rack-mounted house.

But, your idea might be the only way. Between the two (FC-AL internal
drives, or big RAID external SCSI drive), I can probably physically
transport storage media and get the job done.

Because I'm lazy, I was hoping to find a way to get a network connection.

How would the folks with NAS do it, I wonder.

Thank you.

DG

> >
> Did you try to start in.ftpd directly, as I suggested?
>

I didn't, yet. I mean no disrespect, but, since 'ping' doesn't work after I
used 'ifconfig' to plumb and set address, and then set "hosts", etc., and
then used 'route' to set a default gateway, it seemed to me like ftp
couldn't be expected to work.

Come to think of it, since ping doesn't work, I'm not even sure why I was so
eager to get inetd working.

Is it really the case that no one does any networking when booted from
cdrom? It's beginning to look like it to me.

Thank you for taking the time to comment.

Regards,

DG