Solaris

The link Peasent gave you is exactly what I was talking about. And as i said we do this from time to time. We have one server set aside for this purpose.

Hi all,

Thanks for your reply,

@hicksd8 : I'm using Solaris 10 update 6.
Procedure done :

1-start as single user mode.
2-Apply partionning (vtoc/fmthard)
3-Create new file-systems on different slices using newfs.
4-restoring .dump files (file systems dumps from T5220 including /root) on appropriate slices on v240.
5- make the disk bootable (installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s0).
6-reboot --> The file just loaded does not appear to be executable.

@Peasant : thanks for the link, I've already seen this article but unfortunatelly I'm not using flar image. just ufsdump files.

Thanks all of you guys for reply.

this is a wrong statement...

sun4u is arcitecture on almost all ultrasparc64 cpus

sun4v is used on all T series servers with optional virtualisation (ldom)

https://en.wikipedia.org/wiki/Sun-4

You described yourself as a "newbie" but if you've done all that I'd say that you're not. If you don't understand anything I'm about to write just post a reply and I'll expand it.

Due to the fact that you've restored a system to different hardware your devices (eg. c2d0t0) will be all wrong. Therefore, first job is to sort that out.

Boot from CD into single user (boot cdrom -s) and mount your harddisk root filesystem under /a. Then....

Code:

 
rm -f /a/dev/rdsk/c*
rm -f /a/dev/dsk/c*
rm -f /a/dev/cfg/c*
devfsadm -r /a -p /a/etc/path_to_inst

Now check that /a/etc/vfstab is right.

Now double check vfstab is right - take your time. This is the file that's going to tell a reconfiguring Solaris where everything is. Use the format command to check the device names of disk drives and the slices (show partition tables) so that you are absolutely sure that vfstab is correct (for this hardware).

When you've done that shutdown.

Now, be careful not to confuse Solaris by ensuring that you use the -r switch (reconfigure) the first time that you boot.

Code:

 
boot -r

You might need to add 'disk1' or 'disk2' or whatever after this command if you need to boot from a non-default disk.

I think that Solaris 10 U6 doesn't use a boot archive anymore (Am I correct forum members???) but we can try and update that later if an error message suggest we should.

Post the results from the above.

Hi,

I've done all the procedure described :

1- mount c1todoc0 on /a.
2-
rm -f /a/dev/rdsk/c*
rm -f /a/dev/dsk/c*
rm -f /a/dev/cfg/c*
devfsadm -r /a -p /a/etc/path_to_inst
3- check vfstab file on /a/etc.
4- Add disk on OK prompt : nvalias disk1 pci@1c,600000/scsi@2/sd@0,0

but when try to "boot -r disk1" from ok prompt I got :

ERROR: /pci@1c,600000: Last Trap: Fast Data Access MMU Miss

Any suggestions ?

Thanks

In 1 I assume you mean c1t0d0s0??

The error is something not right with "disk1".

Are you sure that the root filesystem is on a non-default disk?
What happens if you just boot -r?

"Are you sure that the root filesystem is on a non-default disk?"
How can I check this ?

- Same error when boot -r : ERROR: /pci@1c,600000: Last Trap: Fast Data Access MMU Miss