I'm currently trying to move a perfectly find harddrive from a V210 to a V440. From what I can tell, the disk labeling a bit different, (V210 is c1t0d0 and V440 is c0t0d0). My question is, what all do I have to change to get the V440 to boot off of this with very little complications. Right now, it boots into failsafe mode and mount "/" and only "/".
I tried to manually change the vfstab file prior to boot. Seems to not worked.
Here's what I have going:
# mount
/ on /pci@1f,700000/scsi@2/disk@0,0:a read/write/setuid/devices/dev=800010 on Thu Jan 1 00:00:00 1970
/devices on /devices read/write/setuid/devices/dev=4b40000 on Fri Mar 19 12:39:39 2010
/system/contract on ctfs read/write/setuid/devices/dev=4b80001 on Fri Mar 19 12:39:39 2010
/proc on proc read/write/setuid/devices/dev=4bc0000 on Fri Mar 19 12:39:39 2010
/etc/mnttab on mnttab read/write/setuid/devices/dev=4c00001 on Fri Mar 19 12:39:39 2010
/etc/svc/volatile on swap read/write/setuid/devices/xattr/dev=4c40001 on Fri Mar 19 12:39:39 2010
/system/object on objfs read/write/setuid/devices/dev=4c80001 on Fri Mar 19 12:39:39 2010
/etc/dfs/sharetab on sharefs read/write/setuid/devices/dev=4cc0001 on Fri Mar 19 12:39:39 2010
mount -F ufs -o rw /dev/dsk/c0t0d0s7 /mnt
mount: /dev/dsk/c0t0d0s7 write-protected
and because /usr will not mount, I get this:
# format
ld.so.1: format: fatal: libdiskmgt.so.1: open failed: No such file or directory
Killed
I modified the vfstab file to look like:
# more /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s3 - - swap - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 no -
/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1 /var ufs 1 no -
/dev/dsk/c0t0d0s7 /dev/rdsk/c0t0d0s7 /export/home ufs 2 yes -
/dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /opt ufs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
sharefs - /etc/dfs/sharetab sharefs - no -
# ls | grep eeprom
eeprom
# ./eeprom
./eeprom: not found
#
It asks me for a firmware password, which I don't have. I could reset it in eeprom, but eeprom won't work on what little OS I can log into. Any ideas on how to reset the OK prompt password without having a working eeprom?
-a ... ask for configuration files, kernel location, ...
-r ... do a reconfigure boot (scan for devices)
-s ... boot into single user mode
-w ... mount the root filesystem r/w right from the beginning
Nothing really changed... Still didn't work. Any other solutions?
Boot device: /pci@1f,700000/scsi@2/disk@0,0 File and args: -wars
Name of system file [/etc/system]:
SunOS Release 5.10 Version Generic_142900-03 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
root filesystem type [ufs]:
Enter physical name of root device
[/pci@1f,700000/scsi@2/disk@0,0:a]:
Hardware watchdog enabled
WARNING: consconfig: cannot find driver for screen device /pci@1d,700000/SUNW,XVR-100@1
Booting to milestone "milestone/single-user:default".
ERROR: svc:/system/filesystem/root:default failed to mount /usr (see 'svcs -x' for details)
Failed to plumb IPv4 interface(s): bge0
Hostname: solaris
Requesting System Maintenance Mode
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
Mar 20 06:36:34 su: 'su root' succeeded for root on /dev/console
Contents of /etc/system
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
*
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
set c2audit:audit_load = 1
Thank you all for your help. I really appriciate it.
---------- Post updated at 02:16 AM ---------- Previous update was at 01:37 AM ----------
What other file, other than /etc/vfstab could be causing this thing not working. I installed an image on the V440.. and I can not take that one to a V210.
What am I missing? It has to be possible. If you can do it on DOS with similar type of hardware, you should be able to do it here with the similar chipsets.
maybe you installed a minor software cluster on the v210 and there are parts missing for the v440. the "cannot find driver..." message is a hint for that...
I copied these files to /toolbelt because upon bootup (My original question) /usr will not mount. There for, I can not use simple commands such as, ls, more, vi, etc. Then went entering the setup, I can change my PATH to /toolbelt to have some form of functionality.
---------- Post updated at 11:10 PM ---------- Previous update was at 02:14 AM ----------
Any idea on how to swap this harddrive from a V210 into a V440? Anyone?
reboot to failsafe. Mount then ufsdump - and restore to the other.
I'm unsure how that would result in that drive working fine in a V210 but not a V440. Also, how a V440 with a full install would not work in a V210. You think the way the drive was cloned affects this issue that I'm having?
perhaps.... but was your disk in the v210 partitioned the same way as it is now in the v440? meaning /usr, /var sitting on separate slice?
or after you ufsrestore, did you do fsck on all the slices in single user before you booted up the v440?
The partitions are in different slices, yes. Now if the origin V440 drive doesn't work in the V210, could this also be a fsck error? No I did not run it. Think it would make a difference?
---------- Post updated at 03:34 AM ---------- Previous update was at 02:59 AM ----------
Ran fsck on the slices with the mountpoints and all was fine.
The system is up fine after rebooted? any errors?
I will suggest you to create a flash archive in future and restore the flash image on your destined server. It will eliminate all sorts of problems
simple steps
On your V210, do the following:
flar create -n archive /tmp/archive.flar
OR
flar create -n anyname /mnt/anyname .flar (where /mnt is your another disk slice)
once created,
On V440,boot the system from the OS dvd, follow the installation screen (ip, hostname, partitioning etc), then choose "Flash Installation" method. follow through and your OS will start to install.
Reboot, and you're done!!
